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 |  Architecture C4 Model |  Operations Scatter Diagram |  Operations 8D Problem Solving |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Low | Low | Low | High |
Timedifferent | 30–45 min | 1-4 h | 30-90 min | 1-6 Wochen |
Participantsdifferent | 1-10 | 1-5 | 1-4 | 4-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Context Diagram, Container Diagram, Component Diagram | Scatter Plot, Korrelationsnotiz, Hypothesenliste | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | FramingOpportunityIdeationQuestions | ArchitectureCommunicationVisualization | Root causeQualityVisualization | QualityProblem solvingRoot cause |