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)Getting Things DoneExample MappingWeekly Review
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Getting Things Done |  Agile Example Mapping |  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. | 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 | Medium | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-2 h Setup, laufend | 30-60 min | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 1 | 3-7 | 1 |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Action Lists, Project List, Review Routine | Example Map, Acceptance Criteria, Open Questions | Updated Task System, Weekly Focus, Next Actions |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ProductivityPlanningTasksExecution | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ProductivityExecutionPlanning |