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 Learning Review |  Agile Sprint Retrospective |  Operations Getting Things Done |
|---|---|---|---|---|
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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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 | Low | Medium | Low | Medium |
Timedifferent | 30-60 min | 1-3 h | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 1-2 h Setup, laufend |
Participantsdifferent | 1 | 3-10 | Scrum Team | 1 |
Formatdifferent | Async | Workshop | Workshop | Async |
Outputdifferent | Updated Task System, Weekly Focus, Next Actions | Learning Review Notes, System Factors, Improvement Actions | Improvement actions, Team agreements | Action Lists, Project List, Review Routine |
Tagsno overlap | ProductivityExecutionPlanning | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementLearning | ProductivityPlanningTasksExecution |