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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Purposedifferent
For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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.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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-90 min45-90 minHalf day initial, dann laufend30-90 min
Participantsdifferent
1-63-12Ein Team plus Stakeholder2-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Decision Tree, Option Map, Assumption ListExpectation Map, Alignment Notes, AgreementsTeam API DocumentConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
DecisionTreeOptions
AlignmentStakeholdersTeam
TeamAlignmentCommunicationService
ConstraintsDecisionPlanningOptions
Add more methods