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 C4 Model |  Facilitation Stakeholder Mapping |  Product Strategy KPI Tree |  Engineering Goal Question Metric |
|---|---|---|---|---|
Purposedifferent | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1-4 h | 60–90 min | 90-180 min initial, dann laufend | 90-180 min |
Participantsdifferent | 1-5 | 2-8 | 3-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Stakeholder Map, Engagement Plan, Risk Notes | KPI Tree, Owner List | GQM Table, Metric Profiles |
Tagsno overlap | ArchitectureCommunicationVisualization | StakeholdersAlignmentFacilitationChange | MetricsStrategyAlignmentMeasurement | MetricsMeasurementEngineeringAlignment |