View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Design ThinkingRisk StormingOutcome-Driven InnovationARID (Active Reviews for Intermediate Designs)
| Criterion | ![]() Innovation Design Thinking | ![]() Architecture Risk Storming | ![]() Product Discovery Outcome-Driven Innovation | ![]() Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. |
Complexitydifferent | High | Low | High | Medium |
Timedifferent | 1 Tag bis mehrere Wochen | 60-90 min | Mehrere Wochen | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 4-10 | 4-12 | 2-6 researchers plus sample | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Problem Statement, Prototype, Test Learnings | Annotated Diagram, Prioritized Risk List, Action Backlog | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | InnovationPrototypeResearch | RiskArchitectureWorkshopValidation | OutcomesInnovationResearchQuantitative | ArchitectureEngineeringFeedbackValidationTasks |



