Writing the Decision Down Within the Hour
The single cheapest mechanism, what it actually costs, and why the hour matters more than the format.
three things · two reached them · the room side is not counted
What a week looks like once somebody is actually doing this.
What one mechanism actually moved, measured over a quarter against the quarter before it
Five a week, written by one named person within the hour, which is the whole of the mechanism
Two of the five carry the second sentence; the other three say only what was decided
Recorded once, as a condition rather than as a person's doubt, and it was the most useful line of the quarter
A channel exists and was used for this on no occasion in thirteen weeks
No start, no participants, no artefact: there is nothing for the mechanism to catch
Carried by tone, and deliberately not recorded, because recording somebody's state of mind is a different thing
six things · three reached them · two with no channel at all · the room side is not counted
Six things, and one cheap habit moved three of them. The left side carries no number and never will: nobody counts what a room tells them. One manager's own quarter, compared with the quarter before; what any team's figures look like differs by team and by who was named to do the writing.
A decision written down within an hour of being taken, by a named person, in two sentences, is the cheapest and most effective mechanism available to a split team. It costs under a minute and it addresses the largest single loss.
The missing context described in “Writing the Decision Down Within the Hour” is an operating-process gap. Teams considering continue here for product information for how to manage remote teams can attach clearer time and project evidence to work already being discussed, provided decisions, reasons and corrections remain visible to people who were not present.
Almost every team believes it already does this and almost none does.
The questions raised by “Writing the Decision Down Within the Hour” can also be compared with Nonprofit Leadership Alliance. A useful review identifies a responsible owner and a practical change rather than copying a generic checklist.
Why the hour matters
Because after an hour the decision has started to feel like something that was always true. The participants stop being able to distinguish what was decided from what they now believe, and the record becomes a reconstruction.
Within the hour it is still an event.
What the two sentences contain, and what happens when the second is missing:
| Present | Absent | |
|---|---|---|
| What was decided | Somebody can comply | — |
| The binding constraint | Somebody can apply it at the edges | They guess, or they wait |
| Who wrote it, and when | It can be questioned | It becomes anonymous policy |
What "written down" means here
Two sentences in a place the team already looks. Not minutes, not a document, not a template with fields.
Anything that requires a decision about where to put it will not be done.
The two sentences
What was decided, and the constraint that forced it. The second one is where the value is, and it is the one people leave out when they are in a hurry.
Without it, somebody six weeks later can obey the decision and cannot apply it.
Naming who does it
One person, by name, permanently. Not whoever was in the meeting, not a rota, not everybody.
Shared responsibility for a one-minute task produces a task that is done in weeks when somebody happens to remember and not in weeks when they do not. Naming one person is the difference between a mechanism and a good intention, and it is the step most often skipped because naming somebody feels like an imposition.
Who it should be
The manager, in most cases. It is a minute, it carries authority, and delegating it to the person outside the room makes them responsible for solving a problem the room created.
Delegating it to the most junior person in the room is the second worst option.
What happens when it decays
It will. Three weeks of good practice, a busy fortnight, and it stops without anybody noticing, because nothing fails visibly when a decision is not written down.
The absence has no symptom until something goes wrong a month later.
Detecting the decay
Ask the person outside the room, once a month, whether it is still happening. They will know immediately and precisely, and they will not raise it unprompted because raising it is about them.
A single question in a one-to-one is the entire maintenance regime, and it needs to be in the calendar because you will not remember to ask.
What a decision actually is
Narrower than people assume. Not every conclusion reached in a meeting is a decision; most are observations, and recording all of them produces a log nobody can use.
The test is whether somebody could act differently because of it. If nobody's behaviour changes, it is information rather than a decision, and it belongs in the weekly summary instead. Teams that get this wrong produce fifty entries a week and then abandon the practice as bureaucratic, which it had become.
Decisions taken outside meetings
These are the majority and they are the ones the mechanism misses. A decision taken in a corridor has no moment at which anybody thinks to write it down.
The habit that catches them is noticing when you hold a position you cannot remember adopting.
What not to turn it into
A decision log with a template, an owner field, a status and a review cycle. Every addition reduces the chance of it being done at all.
The format is less important than the fact, by a wide margin.
Telling people it exists
A mechanism nobody knows about is not a mechanism. Say where the decisions go, say it again in a month, and say it to anybody who joins.
The person outside the room should be able to find the last ten decisions in under a minute.
The weekly backstop
Once a week, a short list of what was decided that week, including anything that never got written at the time. It catches what the hourly habit missed.
Four minutes, and it is the second most valuable thing in this section.
What this does not carry
Everything else in the sorted list: the diffuse conversation, the firmness of agreement, the sense that somebody is struggling, the accident of being overheard. The mechanism is narrow by design, and narrowness is why it survives.
It is also not a substitute for anybody having been there. Somebody reading the last ten decisions knows what the team concluded and does not know what it nearly concluded, or how close any of it was. What they have is enough to work from without guessing, which is a modest claim and is more than most teams in this position manage.
Next door
- Writing the Reason Beside It
- One Named Channel, and What Belongs In It
- The One-to-One That Is Not a Status Report
- Rotation: the Meeting, the Work, the Seat
- Saying Out Loud That Something Has Been Decided
- Why the Deliberate Invitation Feels Staged
- What Each Mechanism Costs, in Minutes
- What to Stop Doing in the Room