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 Stress Test |  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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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 | High | Low |
Timedifferent | Half day initial, dann laufend | Half day | 60–90 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Team API Document | Stress Test Report, Action Plan per Scenario | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | TeamAlignmentCommunicationService | StrategyBusiness modelRiskDiagnosis | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
