The Minds Behind Architecture Decision Records – 7 People Redefining Software
Seven practitioners helped make architectural decision-making explicit, lightweight, versionable, and easier to understand through ADRs, decision models, and modern architecture documentation.
TL;DR
Seven practitioners helped make architectural decision-making explicit, lightweight, versionable, and easier to understand through ADRs, decision models, and modern architecture documentation. [1][2]
Why you should read it anyway
Architecture diagrams explain what a system looks like, but often fail to explain why it looks that way. ADRs preserve the context, alternatives, and consequences behind decisions so future teams can distinguish intentional constraints from historical accidents.
Imagine where Architecture Decision Records would be without them
Without ADRs and related decision-centered practices, architecture documentation would remain more diagram-heavy and rationale-poor, forcing teams to reconstruct old decisions from code, tickets, and institutional memory.
Time Estimate of how many years we would be hindered without them for human progress
Editorial counterfactual estimate: 2–5 years. This is not a measured historical fact. It is an editorial estimate of how much slower the field might have matured without this cluster of people, institutions, practices, and tools.
The 7 people behind Architecture Decision Records
1. Michael Nygard
Why they matter: popularized the modern Architecture Decision Record format, framing each ADR as a lightweight record of context, decision, status, and consequences.[1]
2. Michael Keeling
Why they matter: advanced practical architecture decision-making and documentation through books and talks focused on architecture leadership and collaborative design.[2]
3. Olaf Zimmermann
Why they matter: developed substantial research and practice around architectural decisions, decision models, and reusable architectural knowledge.[3]
4. Gregor Hohpe
Why they matter: emphasized decision-centric architecture and the importance of making architectural tradeoffs explicit rather than presenting architecture as static diagrams.[4]
5. Neal Ford
Why they matter: helped popularize lightweight architecture governance, evolutionary architecture, and practices that make decisions explicit and continuously testable.[5]
6. Rebecca Parsons
Why they matter: advanced pragmatic architecture governance and continuous architecture, reinforcing the idea that architectural decisions should evolve with evidence rather than remain frozen.[1]
7. Simon Brown
Why they matter: created the C4 model and advocated lightweight, understandable architecture documentation, complementing ADRs by separating structural views from recorded design decisions.[2]
How they each differ from one another
Nygard popularized the ADR format; Keeling focused on practical decision leadership; Zimmermann researched architectural knowledge; Hohpe emphasized decision-centric architecture; Ford and Parsons tied decisions to evolutionary governance; Brown complemented ADRs with lightweight structural documentation.
Final Take
Architecture Decision Records preserve the most perishable part of architecture: the reasoning that once made a design choice sensible.
Works Cited
- 01Michael Nygard — Documenting Architecture Decisions cognitect.com
- 02ADR GitHub organization adr.github.io
- 03
- 04C4 Model — Simon Brown c4model.com
- 05Gregor Hohpe — The Architect Elevator architectelevator.com
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead