Skip to content

Guides

Record the decision

After the team compares implementation options and chooses a design, use Driver to turn the decision into a reviewable architecture record. Bring the chosen option, accepted tradeoffs, decision owner, and unresolved questions into your conversation.

  1. Supply the team’s decision notes. If the comparison happened in another person’s private investigation, paste the reviewed comparison or link its shared Jira record; your conversation does not inherit their private work.
  2. Ask: “Draft an architecture decision record from these notes. Separate the team’s decision from source-supported facts and unverified assumptions. Include the alternatives rejected, accepted consequences, implementation follow-ups, and a condition for revisiting the choice. Leave missing owners or dates explicit.”
  3. Review the draft against the structure below. Confirm that Driver has recorded the team’s choice rather than silently selected an option or filled in an unanswered question.
  4. Copy the reviewed record into the architecture document or engineering issue, link the cited sources, and use your team’s normal review process to approve it.
Record sectionWhat the team should establish
ContextProblem, constraints, and codebase branch or revision examined.
DecisionChosen option, decision owner, and date.
AlternativesOptions rejected and the reason each was rejected.
Evidence and assumptionsSource references, supplied measurements, and questions still unverified.
ConsequencesAccepted risks, migration work, compatibility needs, and follow-up owners.
Revisit conditionA measurable change or new fact that would justify reconsidering the choice.

The shared architecture record is what implementers and reviewers use later. Keep it in your team’s documentation or Jira; the private Driver conversation holds your working discussion.