View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Value Chain Analysis |  Team Design Team API |  Facilitation Expectation Mapping |
|---|---|---|---|
Purposedifferent | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | High | Low | Low |
Timedifferent | Half day | Half day initial, dann laufend | 45-90 min |
Participantsdifferent | 3-8 | Ein Team plus Stakeholder | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Value Chain Map, Lever List | Team API Document | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | StrategyBusiness modelDiagnosisAnalysis | TeamAlignmentCommunicationService | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
