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 Failure Mode and Effects Analysis |  Operations Scatter Diagram |
|---|---|---|---|---|
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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 30–45 min | 1-4 h | 2-6 h | 30-90 min |
Participantsdifferent | 1-10 | 1-5 | 3-10 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Context Diagram, Container Diagram, Component Diagram | FMEA Table, Risk Priority, Mitigation Actions | Scatter Plot, Korrelationsnotiz, Hypothesenliste |
Tagsno overlap | FramingOpportunityIdeationQuestions | ArchitectureCommunicationVisualization | RiskQualityOperationsRoot cause | Root causeQualityVisualization |