Shared context
Keep the reason for a decision close to the decision itself.
2 min read
Capture enough context
Decisions are easier to revisit when their reasoning is visible. A short note can record the choice, the alternatives considered and the constraints that mattered at the time. The aim is to preserve context without turning every decision into a report.
Make it easy to find again
Place the note with the project or topic it affects, and use a title that says what changed. Add a date and a clear owner for the next action. When the situation changes, update the record rather than leaving conflicting instructions in separate places.
A useful record preserves a reason and a next step without trying to preserve every sentence of the discussion.
Write a title that distinguishes the choice
A title such as “Review decision” becomes difficult to find once several projects use it. A more specific title might say that new requests enter a triage queue before an owner is assigned. The reader can recognize the choice without opening several records. The supporting note can then explain the reason and the important limitation, rather than repeating a title that never identified the decision in the first place.
Keep an amendment visible
When a situation changes, record the new choice alongside the reason for changing it. Quietly replacing the original explanation can make related work appear inconsistent even when it followed the agreement at the time. A short dated amendment is often enough. Link it to the work affected and identify who will carry the change forward, so a history remains useful without becoming a transcript of every conversation.
Keep the record proportionate
A small reversible choice may need only a few sentences. A decision with several teams or a difficult constraint may need more context. Use the consequences to decide how much detail is useful. Sensitive research or personal information can remain in an appropriate restricted location, with only an approved summary in the general record. A decision log should help an intended reader understand the work, not expose information merely because it was available.