View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Design Thinking |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Problem Interview |
|---|---|---|---|
Purposedifferent | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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. | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. |
Complexitydifferent | High | Medium | Medium |
Timedifferent | 1 Tag bis mehrere Wochen | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min je Interview |
Participantsdifferent | 4-10 | Designers, developers as users, and facilitation | 5-12 Interviews |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Problem Statement, Prototype, Test Learnings | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Problem Evidence, Risk Notes, Customer Segments |
Tagsno overlap | InnovationPrototypeResearch | ArchitectureEngineeringFeedbackValidationTasks | DiscoveryInterviewsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
