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 Domain Context Map
Domain Modeling
Domain Context Map
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
When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.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
MediumMediumLowLow
Timedifferent
1-3 h1-2 h Setup, laufend1-2 Tage30-60 min
Participantsdifferent
3-1011-41
Formatdifferent
WorkshopAsyncWorkshop + asyncAsync
Outputdifferent
Domain Context Map, Boundary Notes, Ownership MapAction Lists, Project List, Review RoutineArchitecture Document, Context View, Runtime View, Deployment ViewUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
Domain-Driven DesignContextBoundaries
ProductivityPlanningTasksExecution
ArchitectureDocumentationCommunication
ProductivityExecutionPlanning
Add more methods