View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Force Field AnalysisGetting Things DoneWeekly Review
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Force Field Analysis |  Operations Getting Things Done |  Operations Weekly Review |
|---|---|---|---|---|
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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | 1-2 h Setup, laufend | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-12 | 1 | 1 |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Force Field Map, Change Levers, Risk Notes | Action Lists, Project List, Review Routine | Updated Task System, Weekly Focus, Next Actions |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ChangeDecisionStrategy | ProductivityPlanningTasksExecution | ProductivityExecutionPlanning |