The coordinator at a small training organisation had a problem she could not quite name. Every quarter, schedules slipped in much the same way, and every quarter the review meeting ended with the same sentence: “We will plan better next time.” Nobody could say what “better” meant, because nobody could say what had been expected at the start. The symptoms were obvious. The diagnosis took a while. This is the story of how a decision journal turned a vague complaint into a specific, fixable cause, and how you can run the same diagnosis on your own planning.
The symptom: the same slip, again
The pattern looked like this. A plan was agreed, work began, and somewhere around the middle the timetable bent. Tasks ran longer, handovers took more effort than anticipated, and one or two commitments quietly moved to the following week. In the review, people recalled the events vividly but disagreed about causes. One person blamed workload. Another blamed communication. A third thought the plan had simply been too ambitious.
Each explanation was plausible. None could be tested, because the plan existed only as a calendar and a few messages. The reasons for the original choices had never been written down.
First diagnostic question: what was the plan based on?
When she tried to reconstruct the reasoning, the coordinator found a gap. She remembered agreeing a timetable, but not which assumptions it rested on. Had they assumed staff would be free on certain days? That tasks would take as long as the previous term’s? That nothing else would compete for attention? Without a written trail, she was guessing about her own past thinking, and the guesses were suspiciously tidy.
This is the heart of the problem. When decisions are not recorded, hindsight rebuilds them to fit the outcome, and the real cause hides inside the rebuild.
The treatment: a short decision journal
She introduced one small rule. Before any plan took effect, whoever made the key choices would jot down four short items: the choice itself, the rival options, the case for the winner, and a forecast that could later be proved wrong. A review date went at the bottom. Entries were brief. Several took less than two minutes.
The first entries were clumsy, and some predictions were vague. “Should be fine” appeared more than once. But by the second month they sharpened. A typical entry read: “Decision: set the practical sessions two days after the theory block. Alternatives: the same week, or a week later. Reasoning: gives time to absorb material, and equipment is free then. Prediction: no more than a minor reshuffle, and the sessions start on the planned date.”
What the journal revealed
At the end of the quarter she lined up the entries against what had actually happened. A pattern appeared that no review meeting had caught. Nearly every slip traced back to one assumption: that equipment and rooms would be free on the days chosen. The reasoning in each entry cited availability without evidence. Nobody had checked a booking calendar; everyone had assumed.
That was the diagnosis. The problem was not workload, communication or ambition, though each played a small part. It was a single unexamined assumption, repeated across decisions, that no one had ever had to state.
The solution: make the assumption explicit
The fix was almost embarrassingly simple. A new line went into the template: “Evidence for availability.” If the answer was “none”, the entry said so, and the decision was flagged as a guess. Guesses were allowed, but they were labelled, and the review looked at them first.
Within a quarter, the same type of slip fell away. Not completely, because the world still intervenes, but the repeat offences disappeared. When one did occur, the journal showed whether the assumption had been flagged, so the team could tell bad luck from a known gamble.
The resistance she met
Not everyone welcomed the change. Two colleagues felt the journal was extra paperwork in a week already full of paperwork. A third worried that written predictions would be used against people later. She answered the first concern by keeping the format small and the second by agreeing, in front of everyone, that entries would be read for patterns and never for blame. The agreement mattered more than the template. Once people trusted that an honest “I guessed here” would not be punished, the entries became more candid, and candid entries are the only kind that diagnose anything.
She also made a point of writing her own entries first, including the ones that exposed her own shaky assumptions. Leading by example did more than any memo could have done, and by the second month others were copying the habit without being asked.
What a diagnosis like this cannot do
The method has boundaries, and they deserve a mention. Keeping the journal finds patterns in your own reasoning; it does not supply facts you lack, and it cannot remove disruptions that come from outside. If a plan fails because of a circumstance nobody could have foreseen, the entry will simply record that the reasoning was sound and the result unlucky. That is still useful, since it spares the team from changing a method that was working.
How to run the same diagnosis yourself
If your plans keep slipping in a similar way, try this sequence:
- Pick one recurring kind of plan, such as a weekly schedule or a course timetable.
- For the next four plans, write the four-line entry before work begins.
- Add one line listing the assumptions you are relying on.
- At the review date, mark each entry for reasoning and for outcome.
- Scan across entries for the assumption that appears most often when things go wrong.
The method works because it replaces argument about causes with a small body of evidence. You are no longer asking people to remember what they thought. You are reading what they wrote.
A common trap: treating every miss as a failure
The coordinator was careful to separate two ideas. A missed prediction is not automatically a bad decision. If the reasoning was sound and the world intervened, the entry is marked “sound, unlucky”. If the reasoning relied on an unchecked assumption, it is marked “thin”. Only the second category triggers a change to how the team plans. That distinction kept the journal from becoming a blame tool, which in turn kept people willing to write honest entries.
A small aside on choosing tools
As the team grew comfortable with written reasoning, members began using it outside the workplace, for instance when deciding how to get around on days off. One of them noted in passing that a marketplace website, MotoShareGo, brings motorbike and scooter hire and sharing together on one site and routes sign-in through a central account system, and wrote a short entry about why she was only browsing, not committing. That is the whole point. The journal does not tell you what to choose; it records why you chose, so you can learn from it.
What to keep in mind
Three lessons stand out from the story. First, vague complaints such as “we plan badly” hide specific causes, and written reasoning is the quickest way to find them. Second, the most damaging assumptions are the ones nobody has stated. Third, review is where the learning happens, so protect the time for it.
The coordinator’s quarterly meeting no longer ends with “we will plan better”. It ends with a line from the journal: this assumption held, that one did not, and here is what we will check next time. A diagnosis you can read back is worth far more than a resolution you cannot define.
