View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation How Might We |  Team Design Team API |  Facilitation Expectation Mapping |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction. | 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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30–45 min | Half day initial, dann laufend | 45-90 min | 45-90 min |
Participantsdifferent | 1-10 | Ein Team plus Stakeholder | 3-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Team API Document | Expectation Map, Alignment Notes, Agreements | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | FramingOpportunityIdeationQuestions | TeamAlignmentCommunicationService | AlignmentStakeholdersTeam | Systems thinkingFramingStakeholders |