Research Governance

Decision Log

A decision log is a structured record of important decisions, including the decision made, context, evidence, alternatives, rationale, owner, date, and consequences.

Concept facts

A decision log is a structured record of important decisions, including the decision made, context, evidence, alternatives, rationale, owner, date, and consequences.

Also known as
Decision register, decision record, decision history, architecture decision log, design decision log.
Used in
UX governance, product management, design systems, research operations, implementation planning, public-service delivery, vendor coordination, and release governance.
Interpret with
Design rationale, evidence matrix, research finding, UX insight, recommendation prioritization, UX governance, and implementation risk.

Plain-language explanation

A decision log helps teams remember why important decisions were made. It records more than the outcome. It captures the context, evidence, alternatives, and expected consequences.

Why it matters

In long-running projects, decisions are often lost in meetings, chat threads, presentations, or individual memory. This can lead to repeated debate, inconsistent implementation, or reversal of important decisions.

Use contexts

  • projects involve multiple stakeholders or vendors
  • research findings influence product or service decisions
  • design system patterns require governance
  • teams need to document why recommendations were accepted or rejected
  • public-service or regulated systems require decision traceability

Application guidance

Record decisions close to when they are made. Include context, evidence, alternatives, decision, rationale, owner, and consequences. Link decisions to research findings, evidence matrices, design rationale, or release-readiness criteria where relevant.

Practical example

A digital education grant system debates whether to show eligibility rules before or after account creation. The team decides to show basic eligibility first because research shows many applicants are unsure whether their institution qualifies. The UX consequence is reduced wrong applications, clearer applicant expectations, lower support burden, and better decision traceability.

Interpretive boundaries

A decision log is not a complete project history. It should focus on decisions that affect users, service meaning, risk, implementation, or governance. It should not become a tool for blame.

Applied at Userhub

Userhub uses decision-log thinking to preserve the reasoning behind UX recommendations, design system choices, content architecture, accessibility decisions, and service design trade-offs.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

Tyree, J., & Akerman, A. (2005). Architecture decisions: Demystifying architecture. IEEE Software, 22(2), 19–27. https://doi.org/10.1109/MS.2005.27

Nygard, M. (2011). Documenting architecture decisions. Cognitect. https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions

MacLean, A., Young, R. M., Bellotti, V. M. E., & Moran, T. P. (1991). Questions, options, and criteria: Elements of design space analysis. Human-Computer Interaction, 6(3–4), 201–250. https://doi.org/10.1080/07370024.1991.9667168

Cite this entry

APA

Userhub. (2026). Decision Log. UX Reference. https://userhub.com.bd/reference/decision-log/