What a Single Source of Truth Actually Requires

What does a single source of truth actually require?

A named owner for each field that matters, decided before any connector gets bought. A record is authoritative because somebody determined which system wins a conflict and who is allowed to change the value. That decision costs nothing and is almost never made, which is why so many integrations connect a disagreement rather than resolve one.

The idea itself is not new. Master data management has been making this argument since roughly 2003. What the modern pitch drops is the governance half.

Why does buying an integration not fix disagreeing data?

Because a connector moves values, it does not adjudicate them. If two systems hold different customer addresses and nothing states which one is correct, syncing them faster propagates the disagreement in both directions at machine speed.

As of 2026, integration coverage consistently notes that governed data matters as much as connectivity. Small and mid-sized companies are also markedly more likely than large enterprises to defer an integration purchase over cost and skills, which makes doing the free part first more valuable, not less.

Which fields should you start with?

The five your company already argues about. You know them, because they produce the meeting where two screens do not match. Common candidates:

• Customer address, which changes without anyone announcing it.
• Job or order status, which different teams define differently.
• Price, where the exception lives in somebody's memory.
• Promised date, which sales and operations each believe they set.
• Quantity on hand, which is right in one system and stale in another.

Five is enough. A comprehensive data dictionary is a project. Five fields is an afternoon.

Who should own a field?

One named individual, or the role a specific individual holds today. Not a department. Departments do not make decisions; they contain people who do, and "operations owns it" is functionally identical to nobody owning it.

The owner answers two questions: where does this value get entered, and who may change it after entry.

What happens when two systems disagree?

Somebody decides, and that rule gets written down once instead of relitigated per record. Most companies already resolve these conflicts informally, in the head of whoever sits between the two systems. That works until the seat is empty or the volume grows.

Watch that person do one full pass before automating them away. Much of what looks like retyping is judgment, and judgment needs a home before the retyping disappears.

How long does this take?

An afternoon for five fields. Most teams move through three comfortably and stall on the fourth. The stall is the finding: that field has never had an owner, and the reconciliation problems downstream of it are symptoms rather than defects.

When is an integration platform the right purchase?

After the ownership page exists. At that point the connector has something real to connect, the requirements write themselves, and the evaluation gets easier because you know what the tool has to enforce. Buy it first and you are guessing at requirements you have not derived yet.