The Business Link between Strategy, OKR, and DORA
The core link between corporate strategy, OKRs, and DORA is a vertical alignment chain: strategy sets the destination, OKRs translate that destination into measurable quarterly intent, and DORA provides the engineering-level signal that tells you whether execution is actually tracking toward that intent. Without this chain, each layer operates in isolation — strategy stays on slides, OKRs become performance theatre, and DORA metrics are engineering navel-gazing.
Preconditions for measurement
Never build a metrics framework for an organisation that can’t use it. Before instrumenting anything, ask three questions:
- Is there one accountable owner for user‑facing delivery?
- Do delivery teams share the same goal, budget, or executive sponsor?
- Has leadership ever acted on technical metrics before?
If the answers are no, stop. The problem is organisational, not technical. You will need to fix the organisation first.
The Conway constraint
Delivery pipelines mirror organisational structure. Twelve independent teams yield twelve services and twelve pipelines, with friction at every boundary. Lead time isn’t about build speed; it is about queues and handoffs between teams. Team‑level metrics mislead — each team looks fine while overall delivery drags. The cure is structural: reduce dependencies, align around product value streams, and give one group end‑to‑end ownership. Until then, DORA measures local efficiency in a system designed for systemic delay.
What the research says
Accelerate analysed six years of self‑reported DevOps data. Four metrics correlate with high performance — correlation, not causation. Good organisations show good metrics; However, metrics don’t make them good. Treat DORA as diagnostic framing, not a specification.
Measuring under constraint
In most enterprises, bottom‑up instrumentation hits walls — locked JIRA, restricted repos, platform gatekeeping. Workarounds:
- Git timestamps → lead‑time approximation (commit → merge → deploy).
- Manual handoff tracking for two sprints to expose waiting and transfer delays.
- Slack or PagerDuty timestamps → MTTR and CFR.
Rough, honest data beats perfect, permission‑bound data. Start with what’s reproducible, real, and expressible in business terms.
The minimum viable sequence
Conway first. Sponsor second. Definitions third. Instrumentation fourth. OKRs last. Most organisations invert this and start with dashboards. That’s why they get theatre instead of feedback.
- Accelerate: https://abinoda.com/book/accelerate
- DORA: https://dora.dev/research
- DORA and DEVOPS: https://cloud.google.com/blog/products/devops-sre/dora-2022-accelerate-state-of-devops-report-now-out
- Conway’s Law: https://www.melconway.com/research/committees.html
- Article researched using AI’s Claude and Perplexity, Wikipedia, and Grammarly-assisted for writing.