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 Pretotyping |  Operations Getting Things Done |  Operations Weekly Review |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
Purposedifferent | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | 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. | In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable. | 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 | Low | Medium | Low | Medium |
Timedifferent | Stunden bis wenige Tage | 1-2 h Setup, laufend | 30-60 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-4 | 1 | 1 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Action Lists, Project List, Review Routine | Updated Task System, Weekly Focus, Next Actions | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ValidationDemandMVP | ProductivityPlanningTasksExecution | ProductivityExecutionPlanning | ArchitectureEngineeringFeedbackValidationTasks |