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 arc42 |  Business Strategy Balanced Scorecard |  Engineering Goal Question Metric |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | 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 | Low | High | Medium | Medium |
Timedifferent | 1-2 Tage | Halber Tag bis mehrere Wochen | 90-180 min | 1-2 h |
Participantsdifferent | 1-4 | 4-12 | 3-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Balanced Scorecard, Strategic Measures, Initiative Map | GQM Table, Metric Profiles | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureDocumentationCommunication | StrategyMetricsExecution | MetricsMeasurementEngineeringAlignment | AlignmentStakeholdersStrategyFacilitation |