View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Facilitation Consensus Workshop |  Facilitation Dot Voting |  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 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 workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. | 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 | Low | Medium | Low | Low |
Timedifferent | Half day initial, dann laufend | 1-3 h | 5-15 min | 60-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 5-30 | 3-20 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Consensus Clusters, Theme Titles, Priority Areas | Ranked list, Consensus signal, Shortlist | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | TeamAlignmentCommunicationService | FacilitationConsensusWorkshopAlignment | FacilitationVotingConsensusPrioritization | FacilitationDecisionProblem solvingWorkshop |