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
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for Weekly Review.
Operations
Weekly Review
Paper illustration for Eat the Frog
Operations
Eat the Frog
Purposedifferent
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.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.In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.The method protects energy and attention for the task that creates the largest progress and is often postponed.
Complexitysame
LowLowLowLow
Timedifferent
15-45 min20-60 min30-60 min15-90 min daily
Participantsdifferent
1-31-411
Formatsame
AsyncAsyncAsyncAsync
Outputdifferent
ADR File, Decision Log, RationaleRunbook, Checklist, Escalation PathUpdated Task System, Weekly Focus, Next ActionsPriority Task, Completion Note, Daily Focus
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
OperationsReliabilityDocumentation
ProductivityExecutionPlanning
PrioritizationProductivityFocusExecution
Add more methods