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 | ![]() Decision Making Decision Rights 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 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | Half day initial, dann laufend | 1-3 h | 90-180 min |
Participantsdifferent | Ein Team plus Stakeholder | 5-30 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Team API Document | Consensus Clusters, Theme Titles, Priority Areas | Decision Rights Matrix, Agreement |
Tags1 shared | TeamAlignmentCommunicationService | FacilitationConsensusWorkshopAlignment | DecisionGovernanceAlignmentResponsibility |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






