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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Eat the Frog
Operations
Eat the Frog
A paper tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.The method protects energy and attention for the task that creates the largest progress and is often postponed.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.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
1-2 Tage15-90 min daily25 min Zyklen15-45 min
Participantsdifferent
1-4111-3
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewPriority Task, Completion Note, Daily FocusFocus Sessions, Task Progress, Interruption NotesADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
PrioritizationProductivityFocusExecution
FocusTime managementProductivityExecution
ArchitectureRationaleDocumentationGovernance
Add more methods