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) |  Business Strategy Strategy Map |  Operations Causal Factor 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. | A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results. | For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 2-4 h workshop plus review | 2-6 h |
Participantsdifferent | Designers, developers as users, and facilitation | 4-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Strategy Map, Objective Set, Cause-Effect Hypotheses | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | AlignmentExecutionGoalsCausality | CausalityIncidentRoot causeTimeline |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
