# The Reliability Ledger — Debrief

> A ledger earns trust only when it gets read, tested and repaid — the debrief is where commitments stop being wallpaper.
> Use with `the-reliability-ledger-guide.md`. The repair phase at minute 19 is the compressed version; this sheet is the full one.

## How to run this debrief

- Keep the wall up — Commitments, Needs and the repaired unspoken one all visible. This debrief reads a document the team just wrote, not a memory.
- Separate the three verbs: read (what's on the wall), test (will the repair hold), commit (what each person keeps). Don't blend them into feelings talk.
- Close with the check-in date read aloud. A repair nobody will be asked about again is a note, not a promise.

## Read the ledger

- Scan the Commitments column. Which ones surprise you — things people were already doing that you didn't know about?
- Scan the Needs column. Which need was hardest to say aloud, and what made it risky?
- How many needs are actually requests for something someone else already committed to? That overlap is free trust.

## The six debrief questions

**1. The hidden overlap.**
"Which need on this wall is already someone's commitment — and were we solving that one by accident before?"
→ Targets: free trust; the overlap the implicit contract was hiding, now visible and nameable.

**2. The risky need.**
"Which need was hardest to say out loud today? What would have to change here for it to be cheap to ask for next time?"
→ Targets: the cost curve of asking; the unsayable need is the ledger's early-warning line.

**3. Projection check.**
"Is the unspoken one genuinely shared, or did two people quietly project it onto the room?"
→ Targets: honesty about the group's story; a projected expectation gets rewritten as a pair conversation, not a team fact.

**4. The repair's load-bearing part.**
"Will the repair action actually hold, or does it need a decision right nobody has yet? And did the owner take it — or was it assigned?"
→ Targets: whether the repair can fail for structural reasons; an assigned owner is a complaint with a name on it.

**5. Fixed looks like what.**
"What is the check-in date, and what will 'this got fixed' look like on that date — specifically enough that anyone could spot it?"
→ Targets: converting intent into an observable; unfalsifiable repairs quietly dissolve.

**6. The personal keep.**
"What is the one commitment each person will personally keep to make the repair real — and what did you assume someone would do that they never knew you were waiting for?"
→ Targets: the ledger's double entry closing on every person, not just the culprit of the story.

## Failure modes of the debrief

| Failure mode | Why it happens | The rescue |
|---|---|---|
| Needs resurface as grievances | The wall has started feeling safe enough to unload on | Re-phrase live: "you never X" becomes "I need X by Y" before the sentence finishes. A posted request is a promise someone can keep. |
| The unspoken one gets re-personalised | In discussion, the pattern quietly slides back onto one person | Reframe as "we've all started assuming…" out loud, twice if needed. The moment it becomes one person's failure, the room closes. |
| The repair fades after the meeting | Nobody is scheduled to ask whether it held | Set the check-in date before anyone leaves and put it on the team calendar; if it fails, ask what was missing — owner, decision right, or willingness to name it again. |