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 Problem Framing Workshop |  Facilitation Consensus Workshop |
|---|---|---|---|
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 team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | Half day initial, dann laufend | 60-120 min | 1-3 h |
Participantsdifferent | Ein Team plus Stakeholder | 4-10 | 5-30 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Team API Document | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Consensus Clusters, Theme Titles, Priority Areas |
Tags1 shared | TeamAlignmentCommunicationService | FacilitationAlignmentDiscovery | FacilitationConsensusWorkshopAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
