Practice · Practice

2. Separate the layers

Use this to slow down, separate observation from inference, and choose a next step that can still be revised.

01

What this practice is for

Use this when slowing down would help you separate what happened, what you inferred, and what can still be checked.

02

What this does not prove

This organizes reflection. It does not prove that an interpretation is correct.

Where this comes fromAudit and Re-Render · 2. Separate the layersv0.16 website edition

Most hot moments become less confusing when six different things stop sharing one sentence. What is the event or known state? What active signals are present now?

What archived traces have become available? What am I inferring? What is the render?

What interpretation and action impulse followed? In the low-stakes version of Morgan's case:

Event: a message arrived from the chief operating officer saying, Approved. Move it today.

Active signals: late Friday timing, terse wording, familiar sender name, project thread. Archived traces: the earlier criticism about being cautious; prior requests from this executive; memory of a missed deadline.

Inference: the executive expects immediate action and will judge delay as weakness.

Render: a narrow world in which speed equals competence and clarification equals failure.

Continue in the complete chapter →