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 |  Operations Runbook |
|---|---|---|---|---|
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. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-2 Tage | 15-45 min | 30-60 min | 20-60 min |
Participantsdifferent | 10-50 | 1-3 | 1-5 | 1-4 |
Formatdifferent | Workshop + async | Async | Async | Async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | ADR File, Decision Log, Rationale | ABC Classification, Focus Rules, Control List | Runbook, Checklist, Escalation Path |
Tagsno overlap | SatisfactionPrioritizationCustomer | ArchitectureRationaleDocumentationGovernance | PrioritizationOperationsPortfolio | OperationsReliabilityDocumentation |