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 |  Engineering Fault Isolation |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Eisenhower Matrix |
|---|---|---|---|---|
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. | 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. | 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. | It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 30-180 min | 2–4 h review as a planning range; preparation and evaluation additional | 15-30 min |
Participantsdifferent | 10-50 | 1-6 | Designers, developers as users, and facilitation | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Eisenhower Matrix, Action List, Delegation Notes |
Tagsno overlap | SatisfactionPrioritizationCustomer | TroubleshootingDiagnosisEngineering | ArchitectureEngineeringFeedbackValidationTasks | PrioritizationFocusTasks |