After the Three Doors decision: a follow-through guide

The Three Doors decision discipline ends the Listen session with a specific commitment for each cluster: a door chosen (Remove, Defer With Clarity, or Accept), a named structural change, and a date or condition by which the change will be visible. The commitment is not the end of the work — it is the start of an accountability structure that the team will hold the facilitator to, whether or not the facilitator intends to be held.

This is the follow-through problem. Teams are very good at waiting. They have usually waited through several cycles of 'we heard your concerns and we are working on it' before the Listen. The Three Doors commitment is different — it is specific enough that the team can look at it in three months and say 'this was committed, and either it happened or it did not.' That specificity is the framework's core value. It is also its accountability mechanism.

The commitment record

The first follow-through action after a Three Doors session is publishing the commitment record — a document that lists each cluster, the door chosen, the specific structural commitment, and the owner and date. The commitment record is not a session summary; it is an accountability document. It should be accessible to the team and treated as a live record that is updated as commitments are completed, revised, or superseded.

The minimum fields for each commitment entry are: the cluster name and Architecture, the door chosen, the specific structural change committed (in concrete terms, not a direction of travel), the named owner, and the committed date or condition. Entries that lack a named owner or a committed date are incomplete — they are directions of travel, not commitments.

The thirty-day check

Within thirty days of the Three Doors session, the facilitator should return to the team with an update on each commitment — not a promise that the structural change will happen, but a specific update on where each commitment stands. For Remove commitments, the update names the structural change and confirms it is in motion or complete. For Defer With Clarity commitments, the update confirms the clarifying information is accessible. For Accept commitments, the update confirms the constraint has been named in a format the team can reference.

The thirty-day check is not a second Listen. It is a short, direct communication — in most cases, an email or a five-minute slot in an existing meeting — that acknowledges the commitment record and reports against it. Teams do not need a new session; they need evidence that the commitment is being tracked.

What 'done' looks like for each door

Remove commitments

A Remove commitment is done when the structural change has been made and is visible in the team's day-to-day work. For a Decision Bottleneck, done means the team can make the decision category without the prior bottleneck point — and has successfully done so at least once. For an Approval Loop, done means a piece of work has completed the review process and been closed without cycling. For a Role Ambiguity, done means a contested decision has been made by the designated owner without escalation.

The test for done is operational, not documentary. A decision matrix published but not yet used is a committed Remove in progress, not a done Remove. The commitment is complete when the structural change has been demonstrated in practice.

Defer With Clarity commitments

A Defer With Clarity commitment is done when the team has the specific information the commitment promised — the queue length and clearing date for a Decision Bottleneck, the release date for an Approval Loop's current version, the DRI and handover date for a Role Ambiguity, the constraint duration and scope for an Unspoken Constraint. The information must be accessible without requiring a separate request; it must be retrievable by any team member who looks for it.

A Defer With Clarity commitment expires when the committed date or condition arrives. At that point, one of two things must happen: the constraint lifts and a Remove commitment takes effect, or a new Three Doors commitment is made for the updated situation. A Defer With Clarity commitment that expires and is not followed up is structurally identical to no commitment — the team is back in the original condition with added evidence that the process does not produce follow-through.

Accept commitments

An Accept commitment is done when the structural condition is named in a published format and the team has updated their planning to reflect the constraint. Accept is not a passive door — it requires an active communication that names the constraint, explains why it is the right structural answer, and describes what the team should assume in their planning. An Accept commitment that is published but not followed by updated planning assumptions on the team's side is incomplete.

When a commitment needs revision

Structural commitments sometimes need to be revised — the constraint changes, the owner changes, the date slips, or a new Listen reveals that the structural fix did not hold. Revision is not a failure of the Three Doors discipline; it is an expected part of operating in a changing environment. The failure is unacknowledged revision — the commitment quietly expires or changes without the team being told.

When a commitment needs revision, the follow-through obligation is to publish the revision with the same specificity as the original: name what changed, name the new commitment, name the new owner and date. A revision communicated at the same specificity as the original maintains the accountability structure. A revision communicated as a general update ('things have changed so we are revisiting our approach') collapses back into a direction of travel.

How the next Listen reads the prior commitments

When a second or third Cross-Functional Listen is run with the same team, the prior commitment record is the first input. Before the open-text collection begins, the facilitator reviews the prior commitments with the team: what was committed, what door was chosen, and whether the structural change is visible in the team's day-to-day experience. This is not a retrospective; it is a calibration.

The calibration serves three functions. It signals to the team that the prior commitments were tracked and are being accounted for. It updates the facilitator's model of which architectures are resolved and which are not. And it creates a comparative baseline: clusters that appeared in the prior Listen and still appear in the current one, despite a Remove commitment, are a diagnostic signal — either the structural change was not made, was made but did not hold, or addressed the symptom rather than the structure.

The Withdrawal Arc as a follow-through indicator

The Withdrawal Arc — the behavioural sequence from raised frustration to reduced output to quiet withdrawal to exit — is the primary outcome the Three Doors discipline is designed to interrupt. The follow-through obligation is therefore not just about keeping commitments in the abstract; it is about moving the Arc in the right direction. Teams whose commitments are followed through in full should show measurable Arc improvement: cluster scores declining, arc progression slowing, engagement signals recovering.

If the commitment record shows completed Remove commitments but Arc metrics are not improving, one of three structural conditions is present: the commitments addressed the named Architecture but not the underlying driver; there are Unspoken Constraints that were not named in the Listen; or the Arc has progressed far enough that the structural fix alone is insufficient and a direct re-engagement is needed with the individuals furthest along the Arc.