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 Kano Model |  Architecture C4 Model |  Operations A3 Problem Solving |  Operations ABC Analysis |
|---|---|---|---|---|
Purposedifferent | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | 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 complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-2 Tage | 1-4 h | 45-90 min | 30-60 min |
Participantsdifferent | 10-50 | 1-5 | 2-5 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Context Diagram, Container Diagram, Component Diagram | A3 Report, Action Plan, Root Cause Analysis | ABC Classification, Focus Rules, Control List |
Tagsno overlap | SatisfactionPrioritizationCustomer | ArchitectureCommunicationVisualization | LeanProblem solvingCoachingOperations | PrioritizationOperationsPortfolio |