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 notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for ALPEN Method
Operations
ALPEN Method
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.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 Tage1-2 h Setup, laufend15-45 min10-20 min daily
Participantsdifferent
1-411-31
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewAction Lists, Project List, Review RoutineADR File, Decision Log, RationaleDaily Plan, Time Estimates, Review Notes
Tagsno overlap
ArchitectureDocumentationCommunication
ProductivityPlanningTasksExecution
ArchitectureRationaleDocumentationGovernance
PlanningTime managementProductivityOperations
Add more methods