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 |  Business Strategy Business Model Canvas |  Facilitation Stakeholder 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. | The Business Model Canvas condenses a business model to its key building blocks and assumptions. It makes variants quickly comparable and reveals gaps before validation or implementation begins. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | Half day initial, dann laufend | 1-2 h | 60–90 min |
Participantsdifferent | Ein Team plus Stakeholder | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Team API Document | Business Model Canvas, Assumption List, Business Hypotheses | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | TeamAlignmentCommunicationService | Business modelStrategyValueInnovation | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
