The Cost of Information Living in Too Many Places

Ask three people in a business what a customer's current status is and you may get three answers. Not because anyone is careless, but because the answer lives in four places — the CRM, an email thread, a spreadsheet on someone's desktop, and the memory of the person who took the call.

This is one of the most common structural problems in a growing business, and one of the least likely to be raised in a meeting. It does not feel like a problem. It feels like the way things are.

How it happens

Nobody decides to scatter their information. It accumulates through reasonable decisions:

• A system does not support a field the team needs, so someone starts a spreadsheet.
• A department buys a tool that fits their work well and does not talk to anything else.
• An urgent situation is handled over email and the outcome never makes it back into a system.
• A person leaves and their knowledge stays in a folder nobody opens.
• Two systems both hold customer records because the migration was never finished.

Each step is locally sensible. The cumulative effect is a business where finding out what is true takes effort.

What it actually costs

Time spent locating rather than working. The most measurable cost. Every question that requires checking three places instead of one carries a tax. Multiply by the number of times a day someone needs to know something.

Decisions made on stale information. Someone quotes a price from an old sheet. Someone calls a customer about a problem that was resolved last week. Someone orders stock that was already ordered. These are not rare events in a scattered business; they are weekly ones.

Arguments about numbers instead of decisions. The most expensive meeting in any company is the one where two people disagree about what the figure is, and the actual decision gets deferred. This happens whenever two systems can both plausibly claim to be authoritative.

Customers noticing. The clearest external symptom is a customer having to repeat themselves — explaining their situation again to a second person, or receiving a message that contradicts one they got yesterday. To the customer this reads as disorganisation, and it is.

Risk you cannot see. If personal data lives in six places, you do not know where it all is, which makes deletion requests, access control and breach response substantially harder. The same applies to contractual obligations sitting in an inbox.

New hires taking longer to become useful. Onboarding in a scattered business means learning a map that only exists in colleagues' heads.

The distinction that matters

Information does not need to live in one place. It needs one place that is authoritative for each fact.

This is a more achievable goal, and it is worth being precise about. Copies are fine. Systems that hold a subset are fine. What is not fine is ambiguity about which copy wins when they disagree.

For each important category of information, you should be able to name the system of record in one word:

• Customer contact details → ?
• Current job or order status → ?
• What was quoted, and at what price → ?
• Whether an invoice is paid → ?
• What was promised to the customer verbally → ?

That last one is where most businesses go quiet. Verbal commitments made on the phone are real obligations, and in a scattered business they have no home at all.

Practical moves that work

Name the system of record, explicitly and in writing. Not a project — a decision and a one-page document. Half the confusion disappears when everyone knows which system wins.

Make the authoritative place the easiest place. People route around systems that are slow, require too many fields, or are hard to reach from a phone. If your CRM takes two minutes to log a call, calls will not be logged. Reducing friction is more effective than reminding people about policy.

Kill duplicate entry at the source. Where the same fact is entered twice, connect the two systems or eliminate one of them. Every duplicate entry point is a future disagreement. See the hidden cost of re-entering the same information.

Give the shadow spreadsheets an amnesty. Ask what unofficial files people maintain and why. Do not treat this as misconduct — each one is a precise specification of a gap in your systems. Some should be absorbed; some should be made official.

Attach information to the thing, not the person. Notes on a job should live with the job. Files for a client should live with the client. Anything filed by who happened to handle it will be lost the moment they are on holiday.

Decide what to do about email. Email is where most scattered information hides. You will not stop people using it, so the practical rule is: any commitment or decision made in email must be reflected in the system of record before the thread is closed.

What to do first

Do not start with a consolidation project. Start with one workflow where the scattering is causing visible harm — usually the one where customers repeat themselves — and fix the authority question for that workflow only. Then the next.

Businesses that attempt to unify everything at once tend to produce a large migration, a long outage of confidence, and a new set of shadow spreadsheets built during the transition.

The goal is not tidiness for its own sake. It is that when someone asks a question about the business, there is one place to look, and the answer found there can be relied upon. Everything else — reporting, automation, useful metrics — depends on that being true first.