Clear decisions
Write a decision note you can use a month later
Capture the question, context, options, tradeoffs, and review trigger so a future reader can understand why a choice made sense.
A month after a decision, the conclusion may be easy to remember while its reasons have become blurry. A short note can preserve the conditions that made the choice sensible. It also gives you a fair starting point when those conditions change.
Software teams use architecture decision records for this purpose. Their structure adapts well to ordinary projects. The following book-swap planning example is fictional; it illustrates a note rather than reporting a real decision or outcome.
Give the note a specific question
Name the choice in language someone can recognize later. “How will visitors find a suitable book?” is more useful than “Planning update.” Add a date, the decision’s scope, and whether it is proposed or accepted.
The original architecture decision record approach separates context, decision, status, and consequences. This helps distinguish a suggestion under discussion from a choice people should act on. Keep one consequential question in each note, with links to related decisions when they matter.
Sources: Documenting Architecture Decisions
Reconstruct the situation
Describe the information and constraints available at the time. In the fictional project, that might include a temporary table, limited space, and a collection that changes as books arrive and leave. Identify which details are known and which are assumptions.
Include only context that affects the choice. A future reader needs to understand the pressure you were responding to, not every discussion that happened along the way. Link the relevant plan or observation so they can examine it without searching through a conversation.
Sources: Documenting Architecture Decisions
Represent the alternatives fairly
List the options you seriously considered, including continuing with the current arrangement. For the swap, alternatives might be a shared catalog, a photo board, or broad category signs.
Use the same questions to compare each option: what would visitors gain, who would maintain it, and what could become misleading? Give a rejected option its strongest relevant advantage. Microsoft’s decision-record guidance includes alternatives and their implications. A note that explains why a reasonable option lost is useful when priorities later shift.
State the choice and its cost
A sample note could choose category signs because the table is temporary and maintaining an accurate item-by-item catalog would add work. State what this choice makes easier and what it gives up. Visitors would have less detail before browsing.
Explain the tradeoff directly. Avoid a polished account in which the selected option has every benefit and no drawback. Consequences can be positive, negative, or neutral. Record who takes the next action and any condition that must hold before the decision can be implemented.
Sources: Maintain an architecture decision record (ADR), Documenting Architecture Decisions
Write the reason to revisit it
Choose a review trigger that relates to the original reasoning. The fictional signs decision might need review if the swap becomes permanent, the collection requires more precise organization, or observations reveal a need the signs cannot meet.
A calendar reminder can help, but name what you want to examine when it arrives. Keep unresolved questions visible. AWS describes reviewing decision records through their lifecycle; for a small project, the practical equivalent is checking whether the original constraints and rationale still fit.
Preserve what you knew then
When a decision changes, write a new note and link it to the old one. Mark the earlier decision as replaced. AWS recommends retaining accepted records rather than rewriting them to match a later conclusion.
This makes the history easier to learn from. A disappointing outcome does not automatically mean the original reasoning was careless, and a good outcome does not prove every assumption was correct. Compare what you knew, what you chose, and what you learned.
Use the Small Steps Planner to identify the next action the decision creates. The decision note explains the choice; the planner gives that choice somewhere practical to go.