The Four-Pass Method

The method started as a personal filter in January 2026, after two write-ups had to be pulled because they described a mood rather than a structure. It is a sequence for processing information: what was said, what the work is actually about, whether the structure holds on more than one case, and whether anyone outside this desk can use it. It does not describe people, personality types or workshop energy.

Each pass has an entrance artefact, an exit artefact and a failure that shows up when the pass is skipped. The cycle is linear until Test fails; then the note returns to Frame or is retired with the collapse condition written down. Nothing in the method is a judgement of the person who filed the raw log.

Capture → Frame → Test → Publish or retire. A failed test returns to Frame or writes a retirement line.

The four passes

Each plate is the working brief for that pass: what you bring, what you leave with, the exit test, and the error that shows up when someone is new to the sequence.

1 · Capture

In. The incident, meeting or measurement as it happened, in the words used that day. Dates, quotes and the actual artefact — a ticket title, a dashboard screenshot, a sentence from a review. No tidy verbs yet.

Out. A dated raw log entry. One file or one row. Time of capture is part of the record so later framing cannot pretend the event was clearer than it was.

Exit. A second reader could reconstruct what happened without asking you to “just explain the vibe”. If a proper noun is missing, Capture is not done.

Novice error. Paraphrasing into a lesson before the log exists. The write-up then argues with a memory, and the table gets fields that were never in the room.

2 · Frame

In. The raw log. Nothing else. Tools, vendors and org names are treated as scenery until the decision or measurement is named in one sentence.

Out. A one-sentence problem statement that does not mention a product. “We need a better board” is not a frame. “Intake waits for a weekly committee that cannot say no” is a frame.

Exit. The sentence still makes sense if you swap the tool. If replacing the vendor collapses the sentence, you framed the software, not the work.

Novice error. Starting from the template you already like. The frame then becomes a justification for a file, and Test will only ever pass on the original case. If the sentence still names a board, a vendor or a ritual, stay in this pass until those nouns fall out.

3 · Test

In. The framed sentence plus two further cases that were not the inspiration. If you do not have two further cases, you do not have a method. You have an anecdote with formatting.

Out. A filled table or checklist that all three cases can sit in without a leftover column labelled “notes / other”. Leftover columns are a signal that Frame is still soft.

Exit. A person who disagrees with the original call can still use the table. If the table only works when you already agree, it is rhetoric.

Novice error. Testing only on the case that inspired the note. That pass always succeeds and teaches nothing. The third case is the one that usually retires the draft. If you cannot name two further cases, stop here and keep Capture running until they exist.

4 · Publish or retire

In. A table that survived three cases and a failure paragraph that names collapse conditions. Without the failure paragraph the note is not offered to anyone else.

Out. Either a public note with a lift-able artefact, or a single line on the retired list with the date and the reason. Both outcomes are complete work.

Exit. Someone who does not share your calendar can use the artefact on Monday morning. If they would need you on a call to interpret a column, publish is refused.

Novice error. Publishing a method that worked once because the prose is ready. Ready prose is not a test. The retired list exists so that vanity does not keep a broken structure in circulation.

Time budget

These are the minutes this practice actually spends per note, not a promise that your team will match them. Tools stay dull on purpose so the pass cannot hide inside a new app.

Pass	Minutes per note	Tools	Artefact
Capture	15–25	dated text file, quote paste	raw log entry
Frame	20–40	one sentence at the top of the file	problem statement
Test	45–90	table in the same file	filled table or checklist
Publish or retire	30–50	public note or retired list	note, or a dated retirement line

Applying it to a team process

The method was written for a single desk. It still works in a team if you keep the artefacts and drop the fantasy that everyone must enjoy the same writing ritual. The passes describe documents, not stand-ups. A team of five can share one log file; a cross-functional programme should not share one slide.

The adaptation is always the same: name the owner role for each pass, put the artefact where the next pass can find it, and refuse to hold a meeting that has no artefact. If a programme wants a workshop, the workshop produces a filled table or it is cancelled.

Do not appoint a “method owner” as a personality. Appoint a role that checks exit criteria. When that role is vacant, publishing stops. That is a healthier failure than a ceremony that continues without a table.

Context	Who runs Capture	Where Test lives	What you drop
Solo practice	the person who saw the incident	the same dated file	any second tool “for polish”
Team of 5	rotating scribe role	shared table, reviewed weekly	status narrative around the table
Cross-functional programme	each workstream files its own log	one joint table, three sample cases	a single deck that claims alignment

What the method does not do

It does not coach people

There is no language here about mindset, psychological safety as a product, or how to “show up”. If a room is stuck, the method asks for a better frame or a retired method. It will not fix a staffing or incentive problem, and it should not be sold as if it will.

It does not replace judgement

A filled table can still be wrong. The passes make the wrongness inspectable. They do not make the call. If a team wants the method to decide for them, they are asking for a committee with extra columns.

It does not scale by software

Putting the four passes into a workflow tool does not make them faster. It usually hides skipped tests behind a green state. The cheap file is a feature. If you need seats and files for a group, that is a licence question, not a new platform.

Run it with the files

The Workbook is the method as pages and tables. A Systems Review is a written pass over one artefact you already use. Both are billed in CA$ and start from the contact form.

Four-Pass Workbook

CA$48 one-off

44-page PDF and nine fillable tables.

Open the Library

Systems Review

CA$480

Written review of a decision log or metric tree in five business days.

Open the Library