Team Architecture
Team Architecture Decision Records
Turn hallway agreements into durable ADRs that survive re-orgs and onboarding waves.
Overview
Built for leads who are tired of re-litigating the same topics. You will practice tight ADR formats, dissent capture, and sunset clauses that keep documents honest.
Included
- ADR templates with dissent sections baked in
- Live rewrites of three anonymized messy decisions
- Role-play reviews where product challenges engineering tone
- Cadence guide for when to fork vs supersede an ADR
- Pair edits on your own draft ADRs
- Facilitation tips for remote sign-off rituals
- Lightweight activity log hygiene for cross-org workflow
Outcomes
- Ship five ADRs your team actually references in PRs.
- Define who can mark an ADR as superseded.
- Capture one minority opinion professionally in writing.
Lead contact
Daniel Vance
Curriculum designer; previously documentation guild lead at a multi-region analytics SaaS.
FAQ
Tooling requirements?
Plain Markdown in git is enough. Optional modules cover Confluence exports if your policy requires them.
Legal review?
We discuss stakeholder sign-off patterns but do not provide legal advice; sensitive clauses stay with your counsel.
What if our culture resists ADRs?
We spend a full week on adoption tactics, including smaller pilot teams and low-friction starting prompts.
Recent notes
“Fork vs supersede flowchart alone was worth it—finally stopped duplicate ADRs for the caching layer.”
“Dissent sections made our RFC threads calmer. Would like a deeper example on mobile client contracts next time.”