Connected Is Not the Same as Joined Up

There is a demonstration every integration product can give and which proves almost nothing. Two systems are connected. A record created in one appears in the other. Everybody agrees this is good, and it is. Connection is useful and genuinely hard to maintain.

But an organisation that watches this and concludes its problem is solved has misread what it saw. What was demonstrated is that the systems will talk to each other. What was not demonstrated is that they agree.

Access is not the same as an account

Consider what actually happens when four systems each hold a version of one person. One has a surname spelled the way it was heard on the phone four years ago. One has whatever was on the card, which belongs to a spouse. One has a mobile number and a first name. One has initials and a code. Every one of those is a correct record of a real interaction.

Connect all four and you have not produced one person. You have produced four records that now travel faster. Nobody in the organisation is any better able to answer a question about that human being than they were the week before, and the organisation has paid for the privilege.

Being joined up is a different achievement. It means the organisation holds one account of one person, and can say, and show, where every part of it came from. The distance between connected and joined up is the distance between having four people's testimony and having a finding of fact.

The habit: solving it by copying

The common answer is to copy everything into one place and sort it out there. This works for a while, and then produces the failure that defines the category. The copy drifts. The original changes and the copy does not, or the copy is corrected and the original is not, and now the organisation has two accounts of the same fact and no principled way to say which one governs.

At which point a question arrives that nobody planned for: which one does the regulator believe?

Whoever holds the second copy owns the discrepancy.

The answer is never the copy. And the organisation is now defending a discrepancy it created by trying to solve a problem, which is a materially worse position than the one it started in.

The commitment that follows

This is why we sit above the systems an organisation runs rather than replacing them or duplicating them. They stay authoritative. Nothing is migrated, nothing is switched off, and the organisation is never in the position of defending a second version of its own record.

It costs us something to hold that line, and the costs are worth naming, because a commitment with no cost attached is a slogan. We cannot correct a source system's data by decree, we can only surface the disagreement so the organisation resolves it where it belongs. Every new connection is real work rather than a configuration screen. And an organisation can leave, taking everything with it, at any point, which removes a commercial lever this category relies on heavily.

What it buys

One thing, and it is enough. The organisation is never asked to defend a copy. Everything it is told can be traced back to the system that asserted it, and those systems are the ones it has always been accountable for. There is no second record to reconcile at audit, because there was never a second record.

For an organisation that has to answer for what it did, that is not a technical preference. It is the difference between an answer and an argument.