“A general rule is to follow an “inverted pyramid” style of writing, commonly associated with news stories. The key is to put the most important material at the start, and push details to later in the record.”

https://toot.thoughtworks.com/@mfowler/116284886338044351

Martin Fowler (@[email protected])

NEW POST ADRs are short documents that capture a decision, structured into logs that reveal a history of architectural thinking for a product https://martinfowler.com/bliki/ArchitectureDecisionRecord.html

Thoughtworks’ Mastodon instance

“ADRs contain not just the decision, but also a brief rationale for the decision. This should summarize the problem that led to this decision being needed and the trade-offs that were taken into account. A good way to think of them follows the notion of “forces” when writing a pattern.”

https://martinfowler.com/bliki/ArchitectureDecisionRecord.html

bliki: Architecture Decision Record

A short document that captures a single decision, structured into a log to provide a history

martinfowler.com
The post refers to Nygard’s 2011 “Document Architecture Decisions” post — which wasn’t the first to present a decision template (e.g., “Architecture Decisions: Demystifying Architecture,” by Jeff Tyree and Art Ackerman was published in IEEE Software in 2005), but it was the post that really had impact.

“ADRs are short documents that capture a decision, structured into logs that reveal a history of architectural thinking for a product”

— Martin Fowler

https://www.linkedin.com/posts/martin-fowler-com_adrs-are-short-documents-that-capture-a-decision-share-7442232936789213184-oUSA

bliki: Architecture Decision Record | Martin Fowler | 61 comments

ADRs are short documents that capture a decision, structured into logs that reveal a history of architectural thinking for a product https://lnkd.in/e9K7VHDE | 61 comments on LinkedIn

LinkedIn