methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
Paper illustration for ALPEN Method
Operations
ALPEN Method
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitysame
LowLowLowLow
Timedifferent
20-60 min45-90 min10-20 min daily15-45 min
Participantsdifferent
1-42-811-3
Formatdifferent
AsyncWorkshop + asyncAsyncAsync
Outputdifferent
Runbook, Checklist, Escalation PathRACI Matrix, Responsibility Map, Decision NotesDaily Plan, Time Estimates, Review NotesADR File, Decision Log, Rationale
Tagsno overlap
OperationsReliabilityDocumentation
RolesResponsibilityGovernanceOperations
PlanningTime managementProductivityOperations
ArchitectureRationaleDocumentationGovernance
Add more methods