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 for Weekly Review.
Operations
Weekly Review
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.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.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 Tage1-2 h Setup, laufend30-60 min15-45 min
Participantsdifferent
1-4111-3
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewAction Lists, Project List, Review RoutineUpdated Task System, Weekly Focus, Next ActionsADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
ProductivityPlanningTasksExecution
ProductivityExecutionPlanning
ArchitectureRationaleDocumentationGovernance
Add more methods