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 Outcome-Driven Innovation |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Getting Things Done |
|---|---|---|---|
Purposedifferent | 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. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. |
Complexitydifferent | High | Medium | Medium |
Timedifferent | Mehrere Wochen | 2–4 h review as a planning range; preparation and evaluation additional | 1-2 h Setup, laufend |
Participantsdifferent | 2-6 researchers plus sample | Designers, developers as users, and facilitation | 1 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | 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 | Action Lists, Project List, Review Routine |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureEngineeringFeedbackValidationTasks | ProductivityPlanningTasksExecution |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
