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) |  Architecture C4 Model |  Product Strategy KPI Tree |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 h | 90-180 min initial, dann laufend | 1-2 h |
Participantsdifferent | Designers, developers as users, and facilitation | 1-5 | 3-8 | 4-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 | Context Diagram, Container Diagram, Component Diagram | KPI Tree, Owner List | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureCommunicationVisualization | MetricsStrategyAlignmentMeasurement | AlignmentStakeholdersStrategyFacilitation |