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 of Team API with its method-specific working model.
Team Design
Team API
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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
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.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
Half day initial, dann laufend30-90 min30-60 min45-90 min
Participantsdifferent
Ein Team plus Stakeholder2-82-83-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Team API DocumentConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesPower Interest Grid, Strategy per StakeholderExpectation Map, Alignment Notes, Agreements
Tagsno overlap
TeamAlignmentCommunicationService
ConstraintsDecisionPlanningOptions
StakeholdersFacilitationAlignmentPlanning
AlignmentStakeholdersTeam
Add more methods