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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Purposedifferent
When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-3 h60-90 min60–90 min2-4 h
Participantsdifferent
2-84-102-83-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Context Map, Integration Patterns, Boundary NotesProblem Cluster, Prioritized Challenge, ExperimentStakeholder Map, Engagement Plan, Risk Notes7S Assessment, Alignment Gaps, Change Actions
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
FacilitationDecisionProblem solvingWorkshop
StakeholdersAlignmentFacilitationChange
OrganizationStrategyAlignmentChange
Add more methods