View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  DevOps Blameless Postmortem |  Engineering Goal Question Metric |  Business Strategy Balanced Scorecard |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 30-90 min | 90-180 min | Halber Tag bis mehrere Wochen |
Participantsdifferent | 2-8 | 3-12 | 3-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Postmortem Doc, Action Items, Timeline | GQM Table, Metric Profiles | Balanced Scorecard, Strategic Measures, Initiative Map |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Site Reliability EngineeringIncidentLearningReliability | MetricsMeasurementEngineeringAlignment | StrategyMetricsExecution |