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.
- 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.
- 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.”
- 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.
- 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 section | What the team should establish |
|---|---|
| Context | Problem, constraints, and codebase branch or revision examined. |
| Decision | Chosen option, decision owner, and date. |
| Alternatives | Options rejected and the reason each was rejected. |
| Evidence and assumptions | Source references, supplied measurements, and questions still unverified. |
| Consequences | Accepted risks, migration work, compatibility needs, and follow-up owners. |
| Revisit condition | A 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.