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 Architecture Decision Record |  Operations ABC Analysis |  Architecture arc42 |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-2 Tage | 15-45 min | 30-60 min | 1-2 Tage |
Participantsdifferent | 10-50 | 1-3 | 1-5 | 1-4 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | ADR File, Decision Log, Rationale | ABC Classification, Focus Rules, Control List | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | SatisfactionPrioritizationCustomer | ArchitectureRationaleDocumentationGovernance | PrioritizationOperationsPortfolio | ArchitectureDocumentationCommunication |