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 Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario.
Complexitydifferent
MediumMediumLowHigh
Timedifferent
1-3 h1-3 h45-90 minHalf day
Participantsdifferent
3-122-82-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanContext Map, Integration Patterns, Boundary NotesAssumption List, Critical Assumptions, Learning PlanStress Test Report, Action Plan per Scenario
Tagsno overlap
KnowledgeMappingRisk
Domain-Driven DesignBoundariesStrategy
AssumptionsRiskDecisionDiscovery
StrategyBusiness modelRiskDiagnosis
Add more methods