Decision Log

A decision log records important engagement decisions that may not need a full architecture decision record. It keeps alignment visible across technical, business, and governance stakeholders.

What to log

Log decisions about:

• Scope and non-goals.
• Runtime platform direction.
• Migration sequencing.
• Risk acceptance.
• Vendor or tool selection.
• Ownership boundaries.
• Compliance interpretation.
• Roadmap priority changes.

Decision fields

Track:

• Date.
• Decision.
• Context.
• Options considered.
• Decision owner.
• Stakeholders consulted.
• Consequences.
• Review trigger.
• Link to ADR or follow-up work.

Decision flow

Quality bar

A good decision log prevents the same debate from restarting every week. It should be easy to scan and clear enough that a new stakeholder can understand why the team chose a direction.

Watchouts

• Decisions without owners are unresolved preferences.
• Old decisions need review triggers when assumptions change.
• Decision logs do not replace ADRs for durable technical architecture.