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 of Team API with its method-specific working model.
Team Design
Team API
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.
Complexitysame
LowLowLowLow
Timedifferent
20–45 minHalf day initial, dann laufend30-60 min45-90 min
Participantsdifferent
Small cross-functional groupEin Team plus Stakeholder2-83-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Risk list, Mitigation plan, Assumption logTeam API DocumentPower Interest Grid, Strategy per StakeholderExpectation Map, Alignment Notes, Agreements
Tagsno overlap
RiskDecisionFailurePlanning
TeamAlignmentCommunicationService
StakeholdersFacilitationAlignmentPlanning
AlignmentStakeholdersTeam
Add more methods