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 | ![]() Product Strategy Counter Metrics | ![]() Engineering Goal Question Metric | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
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 a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. | 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 | Low | Medium | Medium |
Timedifferent | 1-4 h | 30-60 min | 90-180 min | 1-2 h |
Participantsdifferent | 1-5 | 2-6 | 3-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Counter Metric List, Guardrail Definitions | GQM Table, Metric Profiles | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureCommunicationVisualization | MetricsMeasurementStrategyExperiments | MetricsMeasurementEngineeringAlignment | AlignmentStakeholdersStrategyFacilitation |



