View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Weekly Review |  Operations Getting Things Done |  Innovation Lean Startup |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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 | Medium | Medium |
Timedifferent | 30-60 min | 1-2 h Setup, laufend | Wochen bis Monate je Lernzyklus | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1 | 1 | 2-8 | Designers, developers as users, and facilitation |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | Updated Task System, Weekly Focus, Next Actions | Action Lists, Project List, Review Routine | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ProductivityExecutionPlanning | ProductivityPlanningTasksExecution | LeanStartupValidationMVP | ArchitectureEngineeringFeedbackValidationTasks |