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 for Risk Storming.
Architecture
Risk Storming
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Weekly Review.
Operations
Weekly Review
Purposedifferent
Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
60-90 min1-2 h Setup, laufend1-2 Tage30-60 min
Participantsdifferent
4-1211-41
Formatdifferent
WorkshopAsyncWorkshop + asyncAsync
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogAction Lists, Project List, Review RoutineArchitecture Document, Context View, Runtime View, Deployment ViewUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
RiskArchitectureWorkshopValidation
ProductivityPlanningTasksExecution
ArchitectureDocumentationCommunication
ProductivityExecutionPlanning
Add more methods