Decisions and governance
A rejected option is part of the decision
Keeping the reasoning behind a rejection makes a decision easier to explain—and easier to revisit when its assumptions change.
A decision register can tell you what was chosen and still leave you unable to explain the choice. The missing piece is often an option that was considered, rejected, and then quietly forgotten.
When that option returns six months later, the conversation begins again. Was it technically impossible? Too expensive? A poor fit for the people who would have to use it? Or simply more than was needed at the time?
Those are different reasons. They also have different expiry dates.
A small example
Imagine a project team deciding where to keep its working documents. It considers one shared workspace and a set of separate spaces for each workstream.
The team chooses a single workspace. Its members work across the same material, and separate spaces would create extra administration without solving a current access problem.
“Separate spaces rejected” captures the outcome. A more useful record captures the condition behind it:
We chose one workspace because everyone currently needs access to the same working material. Revisit this if a workstream needs a distinct audience or an independent owner.
The alternative has a place in the record, together with an observable reason to reconsider it. Someone joining the project later can understand the choice without reconstructing the whole meeting.
Keep the part that carries the reasoning
For a decision like this, a short entry can be enough:
- Question: what do we need to decide, and why now?
- Choice: what will we do, and who owns that decision?
- Alternative: which credible option did we set aside?
- Reason: which requirement, assumption or constraint made the difference?
- Consequence: what do we accept by choosing this route?
- Review trigger: what change would make the alternative relevant again?
The point is to preserve what someone needs to assess the choice. A transcript of every suggestion would make that harder.
Reconsidering can be a sign of continuity
A changed decision does not automatically mean the earlier decision was poor. The original choice may have fitted the original circumstances very well.
Recording those circumstances gives a later discussion something concrete to test. If the team now has a distinct audience for one workstream, it can revisit the workspace structure without having to disown its earlier reasoning.
If nothing material has changed, the same record can explain why repeating the proposal is unlikely to produce a different answer.
A practical starting point
Take one decision your team has made recently. Add a sentence about the strongest alternative and another about what would make you reconsider it.
If those sentences are difficult to write, that difficulty is useful information. It may reveal an assumption that was never shared, a requirement that remains unclear, or a choice whose ownership was left implicit.
A decision register earns its place when it helps the next person continue the reasoning.