Our reading notes

Architecture Decision Record

A compact explanation of recording one consequential architectural decision, its context, consequences, and later superseding decisions.

How to use it

  1. 01

    Write down why the decision made sense, not only the selected technology.

  2. 02

    Preserve accepted decisions and link a new record when the approach changes.

Keep in mind

A record needs to be accessible to the people affected. A source repository may not suit every cross-company decision.

Put it to work

Try this next

Write a short record for a recent decision whose reasoning currently lives only in a meeting or chat thread.

Get the architecture template

Notes and exercises by Awesome CTO. The original work belongs to Martin Fowler.

Work through the bigger question.

Our architecture guide connects the reading to a practical approach and a template.

Open guide
Esc

Type to search every entry. ↑↓ to move, Enter to open.