View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Fault Isolation |  Product Discovery Kano Model |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
Purposedifferent | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 30-180 min | 1-2 Tage | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-6 | 10-50 | Designers, developers as users, and facilitation |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Kano Matrix, Feature Classes, Priority Themes | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | TroubleshootingDiagnosisEngineering | SatisfactionPrioritizationCustomer | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
