View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Jobs to Be Done |  Architecture C4 Model |  Operations Scatter Diagram |  Operations 8D Problem Solving |
|---|---|---|---|---|
Purposedifferent | When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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 | Medium | Low | Low | High |
Timedifferent | 1-3 Wochen | 1-4 h | 30-90 min | 1-6 Wochen |
Participantsdifferent | 5-12 Interviews | 1-5 | 1-4 | 4-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Context Diagram, Container Diagram, Component Diagram | Scatter Plot, Korrelationsnotiz, Hypothesenliste | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | CustomerOutcomesNeeds | ArchitectureCommunicationVisualization | Root causeQualityVisualization | QualityProblem solvingRoot cause |