View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Outcome-Driven Innovation |  Innovation Brainwriting |
|---|---|---|---|
Purposedifferent | 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. | 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. | When loud voices or hierarchy distort the idea search, the method creates a quiet entry into joint development. It gives everyone thinking space and gathers contributions without social brakes, making diversity more visible and easier to build on. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Mehrere Wochen | 15-30 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-6 researchers plus sample | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Idea sheets, Expanded concepts, Prioritized list |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | OutcomesInnovationResearchQuantitative | BrainstormingCollaborationInclusionIdeas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
