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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
A paper tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.For easily distracted solo work, the method sets clear time boundaries for concentrated work. It protects attention when large tasks would otherwise fall apart into small avoidance moves.The method protects energy and attention for the task that creates the largest progress and is often postponed.
Complexitysame
LowLowLowLow
Timedifferent
15-45 min1-2 Tage25 min Zyklen15-90 min daily
Participantsdifferent
1-31-411
Formatdifferent
AsyncWorkshop + asyncAsyncAsync
Outputdifferent
ADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment ViewFocus Sessions, Task Progress, Interruption NotesPriority Task, Completion Note, Daily Focus
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
FocusTime managementProductivityExecution
PrioritizationProductivityFocusExecution
Add more methods