What Is Organisational Truth?

A customer objection is information, but it is not automatically a new rule for the business. Before it changes what a team says or promises, someone needs to assess what it shows, decide whether the accepted position should change and establish where that change applies.

Here, Organisational Truth means the reviewed working understanding a business currently accepts for decisions and operations. It is a proposed working definition—not a formal standard or a claim that the organisation has found an unchanging, universal truth. The point is to distinguish what the organisation has accepted for use from every message, document, hypothesis or AI-generated suggestion it encounters.

From a signal to a working decision#

A practical sequence is:

Observation → hypothesis → reviewed decision → use within scope

• An observation records what was seen or heard, its source and, where relevant, its date.
• A hypothesis offers an interpretation that may explain the observation.
• A reviewed decision records what the organisation accepts, who had authority to accept it and what choice or action it changes.
• Use within scope means applying the decision only where its conditions hold.

The level of review should match the consequences. A passing comment may need no formal process. A change to a shared rule, customer commitment or repeated way of working needs more than a signal: someone with the right authority must decide what it means for the business.

Illustrative example—not a customer case: Several buyers say they do not understand a company’s offer. That feedback is worth examining, but it does not by itself show that the offer is wrong. The team might compare the comments with the approved positioning and consider whether the problem lies in the message, the audience or the buying context. An authorised decision-maker could keep the offer unchanged, revise part of it, limit a change to one market or defer a decision until more evidence is available.

The distinction is simple: feedback can prompt a review without changing what the team is authorised to promise.

Keep the basis and boundaries attached#

A conclusion that makes sense in one situation can mislead in another. When people reuse a decision, they need enough context to judge whether it still applies:

• Source and date: Where did the information come from, and might it have changed? A customer comment, a contract term and a sales interpretation may carry different weight for different questions.
• Context and scope: Which product, market, contract or situation does the conclusion cover?
• Decision relevance: What choice or action changes because the conclusion was accepted? If nothing changes, it may be useful background rather than a working rule.
• Authority: Who could access or analyse the information, and who could approve a new position or customer commitment?
• Review: How can someone challenge or revise the decision when evidence or conditions change? Keep the reason for a revision visible.

These distinctions also matter when AI contributes an interpretation. A model-generated summary or suggestion can inform a review; its fluency does not make it an authorised business decision. NIST’s AI Risk Management Framework provides broader guidance organised around the functions Govern, Map, Measure and Manage. It does not define Organisational Truth or show that any particular system follows these practices. NIST, AI RMF Core

Questions to test a consequential decision#

Before relying on a claim of Organisational Truth, ask:

1. What source supports this conclusion, and how relevant is it to the decision?
2. What interpretation has been accepted, by whom, and with what authority?
3. Where does the decision apply, and when does it take effect?
4. What happens when evidence conflicts, is missing or falls outside that scope?
5. Can an authorised person inspect and revise the conclusion, including why it changed?

Test the process with a negative case. Suppose one unusual buyer comment contradicts the approved offer. Does the process preserve it as a signal for review, or can it silently change what the team is authorised to promise? A credible process must allow a proposed change to be qualified, deferred or rejected—not just accepted.

These questions make a decision’s source, authority, scope and revision path inspectable. They do not certify a product or prove the decision is correct.

ISO 30401:2018 sets requirements and provides guidance for establishing, implementing, maintaining, reviewing and improving knowledge-management systems. It does not define “Organisational Truth”; that term is used here for the narrower distinction between information that may inform a decision and an interpretation the organisation has accepted for a stated purpose. ISO, ISO 30401:2018 — Knowledge management systems — Requirements

Use the distinction when it helps people tell a signal from a decision. The aim is not to turn every observation into policy, but to make clear when the organisation has accepted an interpretation—and what must remain attached when others rely on it.