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
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Four paper collections for projects, responsibilities, resources and archives.
Knowledge Modeling
PARA Method
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Purposedifferent
When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.
Complexitysame
MediumMediumMediumMedium
Timedifferent
2-8 h1-3 h Setup, laufend1-2 h2-4 h
Participantsdifferent
5-1214-123-12
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsPARA Structure, Project Notes, Knowledge ArchiveAlignment Map, Open Issues, Decision Questions7S Assessment, Alignment Gaps, Change Actions
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
KnowledgeProductivityOrganization
AlignmentStakeholdersStrategyFacilitation
OrganizationStrategyAlignmentChange
Add more methods