View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Change Analysis |  Product Strategy DIBB |  Decision Making Force Field Analysis |
|---|---|---|---|---|
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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-120 min | 1-2 h | 45-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-6 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Change Matrix, Cause Hypotheses, Validation Questions, Action List | DIBB document, Belief list, Bet list, Learning report | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ChangeRoot causeTroubleshootingComparison | StrategyDecisionAssumptionsHypothesis | ChangeDecisionStrategy |