Stop Chasing a Single Source of Truth: Build a System of Context

A “single source of truth” sounds comforting. One place. One number. One answer.

It breaks down the moment leadership asks questions that include words like:

• real
• available
• profitable
• active
• committed

Those aren’t data fields. They’re definitions.

SSOT solves storage. It doesn’t solve meaning.

A single system can consolidate facts:

• transactions
• orders
• invoices
• tickets
• payroll

But executives don’t just ask “what happened?” They ask “what does it mean?” and “what do we do next?”

That requires a layer most stacks don’t have.

The missing layer: System of Context (SoC)

A System of Context is where the business keeps its shared language:

• metric definitions (what the KPI actually means)
• hierarchies (customer → segment → channel)
• mapping rules (how things classify)
• thresholds (what counts as an exception)
• ownership (who can change what)

Think of it as the legend on a map.

Without the legend, you can have the world’s best map—and still get lost.

A practical framing: Facts, Meaning, Decisions

1) Facts (Systems of Record)

Answer: What happened?

2) Meaning (System of Context)

Answer: What does it mean in this business?

3) Decisions (Cadence + Interface)

Answer: What do we do next?

Most companies try to jump from Facts → Decisions. That’s how dashboards become debates.

Signs you need a System of Context

If any of these are true, you don’t have a “data problem.” You have a meaning problem:

• The same metric exists in multiple tools with slightly different logic.
• A number is “right” only after someone explains it.
• A spreadsheet is the final arbiter of reality.
• New hires need tribal knowledge to interpret basic reports.

The SoC minimum viable spec

If you’re building this from scratch, keep it boring and enforceable.

1. Metrics Dictionary

   • Name, definition, formula, source systems, owner, change log.

2. Controlled Vocabulary

   • A small set of approved categories and dimensions.

3. Change Control

   • Who can change a definition, how it’s reviewed, where it’s announced.

4. Integrity Rules

   • What gets reconciled, how often, and what happens when it fails.

5. Decision Surfaces

   • Where leaders see truth + exceptions without interpretation.

A small metaphor (because it helps)

A System of Record is the library. A System of Context is the card catalog.

Yes, that makes you feel old. That’s fine. The library still works.

Bottom line

Stop trying to find “one truth.”

Install one language for decision-making.

That language is your System of Context—and it’s what makes your tools behave like a system instead of a collection.