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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
Purposedifferent
In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.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.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
LowMediumMediumHigh
Timedifferent
20–45 min1-3 h1-3 hHalf day
Participantsdifferent
Small cross-functional group3-102-83-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Risk list, Mitigation plan, Assumption logDomain Context Map, Boundary Notes, Ownership MapContext Map, Integration Patterns, Boundary NotesStress Test Report, Action Plan per Scenario
Tagsno overlap
RiskDecisionFailurePlanning
Domain-Driven DesignContextBoundaries
Domain-Driven DesignBoundariesStrategy
StrategyBusiness modelRiskDiagnosis
Add more methods