
Map your data silos as entity gaps
You'll have a visual diagram showing which entities (customers, products, documents, teams) exist in your systems but don't talk to each other, and which AI tasks fail because of that fragmentation.
What you'll make
Entity Gap Map
- Systems Layer: boxes for each major system/database
- Entity Types: customers, products, documents, teams overlaid across systems
- Gap Indicators: visual markers where same entities don't connect
- AI Impact Zones: which AI tasks break at each gap
- Priority Rankings: numbered urgency for each connection gap
Upload a diagram (hand-drawn, digital tool, or screenshot) showing your systems, entities, and gaps with clear visual indicators
The 4 parts
Each part ends with a check you can see.
Hunt down entity mismatches
Find the same real-world entities that appear differently across your systems
Done when
A list of 3-5 specific entity mismatches with evidence of how the same thing appears differently in different systems
Find where AI breaks on your entities
Test specific AI tasks that should work across your entities and document where they fail
Done when
3-5 documented AI task failures where the same entity appears differently across systems, with specific examples of the failure output
Rank which gaps hurt most
Score your entity gaps by how much AI capability they're blocking
Done when
A ranked list of entity connection gaps with impact scores based on frequency and AI task importance
Draw your entity fragmentation
Create a visual map showing systems, entity overlaps, and AI impact zones
Done when
A complete visual diagram showing systems as boxes, entities flowing across them, gaps marked clearly, and AI impact zones labeled with priority rankings
Capstone: you put together your Entity Gap Map.
Where this helps
An elective: a single lesson that sits outside rtwo's job certificates and doesn't count toward one.
About this lesson
What you'll be able to do
- Draw a visual map showing which core entities (customers, products, documents) exist in disconnected systems across your organization
- Identify 3-5 specific AI tasks that fail because entities can't be linked across your data silos
- Have a prioritized list of entity connections that would unlock the most AI capability if fixed
Who it's for
- Data professionals who suspect their organization's AI struggles come from fragmented data, not model limitations
- Anyone who's seen AI give different answers about the same customer/product depending on which system you ask
- People responsible for connecting systems who want to understand which connections matter most for AI use cases
What it won't cover
- Technical implementation of entity resolution algorithms
- Vendor selection for data integration platforms
- Building actual data pipelines or ETL processes
- Vector database administration or configuration
Skills you'll practise
- Entity relationship mapping across disparate systems
- AI failure mode diagnosis through data lens
- Cross-system data audit for entity consistency
- AI task impact assessment