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)Impact MappingWeekly ReviewBalanced Scorecard
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Strategy Impact Mapping |  Operations Weekly Review |  Business Strategy Balanced Scorecard |
|---|---|---|---|---|
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. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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. | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | 30-60 min | Halber Tag bis mehrere Wochen |
Participantsdifferent | Designers, developers as users, and facilitation | 3-8 | 1 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Impact Map, Outcome Hypotheses, Delivery Options | Updated Task System, Weekly Focus, Next Actions | Balanced Scorecard, Strategic Measures, Initiative Map |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | OutcomesStrategyBehaviorPlanning | ProductivityExecutionPlanning | StrategyMetricsExecution |