Leave a decision trail

A decision can feel obvious in the meeting and become mysterious a month later. The people have changed, the evidence is harder to find and the rejected options quietly return. A short decision note helps preserve the reasoning without attempting to transcribe the whole conversation.

Begin with the question and the choice. Use plain language. A reader should not have to work through the history of the project to discover what was agreed. Add the date and the people responsible for the decision, especially if someone else will carry it forward.

Then explain the reason. Which evidence mattered? What constraint shaped the result? What trade-off was accepted? The purpose is not to make the choice look inevitable. It is to show why it was reasonable with the information available at the time.

Keep the alternatives brief and fair. Describe what made an option attractive as well as why it was not selected. A useful record leaves room for a different decision if the circumstances change. Avoid turning the note into a defence of the person who wrote it.

Link the decision to its consequences. Someone may need to update a plan, notify a collaborator or test an assumption. Name that next step and its owner. If the decision depends on something uncertain, say when it should be reviewed rather than quietly treating it as permanent.

A decision trail works when it becomes part of ordinary work. Write the note while the context is fresh, keep it near the brief and update it when a later choice replaces it. The goal is a reliable starting point for the next conversation, not an archive that nobody can navigate. Be thoughtful about access as well: a useful record should be available to the people who need it, while sensitive information stays within its agreed audience.