liveBook · Manning

Decision scribe

As explained in Grokking Software Architecture

A Decision Scribe is an architectural role responsible for recording significant team decisions and their rationale.

When a team forgets why it chose a design, the same debate can start all over again. A decision scribe records significant architectural choices and their rationale, preserving the reasoning for later and helping new developers catch up. The role is more than taking notes: it creates certainty and a lasting record. section 2.3

Capture the decision in an Architecture Decision Record (ADR), a short written record of:

  • The problem context and the significant choice made. section 2.3
  • Options considered, including reasons for rejecting alternatives. section 2.3
  • The rationale behind the choice, so the team can revisit it without repeating old arguments. section 2.3

How Grokking Software Architecture covers it

How deep it goes
Defines ADR contents and purpose, while deferring fuller treatment of ADRs.
Examples
Uses recurring “Why aren’t we using X?” debates to illustrate the value of recording rejected options and reasons.
What you can do after
Practice/perform: Record a significant architectural choice, its context, considered options, and rationale in an ADR.
How it connects
Connects the architect's role to Architecture Decision Records and defensible architectural decisions.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.