Skip to content
Risk ResilienceFramework 01

The Trust Audit

Three tests. Three fixes. Fifteen minutes with a leadership team.

Framework still

When to use this

  • Something went wrong and leadership was the last to know.
  • Your risk reporting is current, complete, and never surprises anyone.
  • A transformation is on schedule on paper and behind it in the corridor.
  • You have inherited a team and cannot yet tell what they are not saying.

Risk Resilience

The mechanism

Three questions, asked in order, about information you already have. The tests do not measure sentiment. They measure distance, consequence, and delay — the three things that decide whether the truth reaches you while it is still cheap. Run all three with a leadership team in fifteen minutes.

  1. 01

    The escalation count

    What it is
    The number of people standing between whoever saw a problem first and whoever had the authority to fix it.
    How to run it
    Take the last three issues that surprised leadership. For each one, name the first person who knew and the first person who could act. Count everybody in between. Do not estimate — use names.
    What the answer tells you
    Every layer is both a delay and an edit. At three or more you are not receiving information, you are receiving a summary of a summary, and the parts that went missing are the parts that were expensive to say. The fix: give the person who sees it first a named, direct route to the person who can act, then use that route once in public so the rest of the organization learns it is real.
  2. 02

    The contradiction record

    What it is
    The date on which somebody last told the most senior person in the room they were wrong, and what happened to that person afterwards.
    How to run it
    Ask your leadership team for the date and the name. Wait through the silence rather than filling it. If nobody can produce both, you have your answer.
    What the answer tells you
    Quiet in a room of senior people is not agreement. It is arithmetic — they have priced the cost of speaking and decided against it. The fix is not an invitation to challenge, which costs nothing and proves nothing. The next time somebody contradicts you, say so where others can hear, and name what changed as a result.
  3. 03

    The bad news clock

    What it is
    The time between a problem becoming visible to anyone in the organization and becoming visible to you, and whether it arrived whole.
    How to run it
    Pick something you found out about late. Work backwards to the hour it was first visible to any employee. Then set what you were told beside what was known at the time.
    What the answer tells you
    The elapsed time is your exposure window; the difference between the two accounts is your blind spot, and it is the more serious of the two numbers. The fix: make it a standing rule that bad news travels unedited and inside a fixed window, then hold people to the window rather than to the wording. Punishing phrasing teaches better phrasing, not faster reporting.

Personal and enterprise application

Personal

Run the three tests on your own information supply before you run them on anyone else. Count the layers between you and the work. Establish when you last changed your position in public because somebody junior was right.

Most leaders discover the same thing here: they are not badly informed, they are informed late and politely. That is a design problem in how they receive, not a character problem in the people who report.

Enterprise

Run it as a fifteen-minute standing item with the leadership team, once a quarter, with the three answers written down. Written answers make the trend visible; spoken ones flatter whoever speaks last.

Track the escalation count and the bad news clock as operating numbers alongside the ones you already report. They move faster than engagement scores and they predict more.

What good looks like in 90 days

A framework that cannot be used in the next 90 days is an opinion. These are the changes you should be able to point at, or the audit did not take.

  • The escalation count on your three most recent issues has dropped by at least one layer.
  • Somebody can name a specific decision that was reversed because a junior person objected, and can name the person.
  • Bad news arrives inside the window you set, unedited, without anyone being asked for it.

The Trust Audit

The worksheet

The one-page version, for running the three tests with your leadership team.

One issue at a time, no more than twice a month. One-click unsubscribe, always.