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 Concierge MVP
Product Discovery
Concierge MVP
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
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 idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution.When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.
Complexitydifferent
LowMediumMediumLow
Timedifferent
Half day initial, dann laufend1-4 Wochen1-3 h60-90 min
Participantsdifferent
Ein Team plus Stakeholder3-10 Kunden5-304-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Team API DocumentConcierge Learnings, Service Blueprint, MVP RisksConsensus Clusters, Theme Titles, Priority AreasProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
TeamAlignmentCommunicationService
MVPValidationServiceDiscovery
FacilitationConsensusWorkshopAlignment
FacilitationDecisionProblem solvingWorkshop
Add more methods