What is a Data Archipelago?

A data archipelago is a business whose information is scattered across disconnected 'islands' (CRM, email, drive, chat, finance and people's heads) with no shared source of truth, forcing people to manually ferry context between systems (and in and out of AI chat boxes) to get work done.

A hand-drawn map titled 'Data Archipelagos' showing a business as a sea of separate islands (People's Heads, CRM, Email, Documents, Messaging, Meetings, Project Management, Spreadsheets, SOPs & Policies, Finance and AI Tools) with tiny people rowing boats of information between them. It illustrates the definition of a data archipelago: business information scattered across disconnected systems with no shared source of truth.

A data archipelago is a business whose information is scattered across disconnected "islands" (the CRM, email, the shared drive, Slack or Teams, WhatsApp, the finance system, the project tool, and people's heads) with no shared source of truth. Because nothing is organised around the work, people (and AI) have to manually ferry context from one island to another to get anything done.

The term is a metaphor: an archipelago is a group of separate islands, and most organisations are built the same way. Each system holds something useful, but none of them talk to each other, so the human becomes the bridge, copying and pasting data in and out of documents, spreadsheets and AI chat boxes all day.

Why the term matters for AI

AI can only do useful work when it has the right context: which customer, which version of the document, what was promised, what the policy allows. In a data archipelago that context is spread across ten different systems, so the AI either cannot reach it, cannot find it, or cannot tell which version to trust. This is why AI often feels underwhelming inside a business: the model is capable, but the context is fragmented.

Signs your business is a data archipelago

  • You spend more time gathering context than doing the actual work.
  • The same question gets different answers depending on who you ask.
  • Key knowledge lives in one person's head, or in a meeting three months ago.
  • Every decision starts with a "let me find the latest version" hunt.
  • You copy from one app, paste into an AI chat box, then move the answer somewhere else.

How to fix it

You don't fix a data archipelago by buying another tool. You fix it by designing AI loops: repeatable paths that pull the right context together, get a human check where it matters, send the output where it needs to go, and capture what was learned so the next run starts from cleaner inputs. Over time, scattered context becomes shared operating memory that both people and AI can rely on.

Bottom line: a data archipelago is fragmented business information with no shared source of truth, and AI loops are how you turn those islands into connected, reusable operating memory.

For the full breakdown, see Data Archipelagos: why you spend most of your time copying and pasting data in and out of AI chat boxes.

Keep reading — it's free

Pop in your email to keep reading and join AI Dispatch, our newsletter of practical advice for leaders scaling AI. Unsubscribe anytime.

Related

What is an AI leash?

An AI leash is what you feel when an AI tool or agent keeps pulling you back every 90 seconds to ask what to do next, so instead of freeing you for higher-value work it keeps you tethered to reviewing, redirecting and re-prompting it.