Why DORA and SPACE Changed How I Think About Engineering Metrics
Measuring What Actually Matters in R&D
For a long time, I thought I understood engineering metrics.
I’ve seen velocity charts, delivery dashboards and productivity reports across many teams and systems. They looked precise. They felt reassuring. And yet, they often failed to explain what was actually happening on the ground.
That disconnect is what eventually pushed me toward frameworks like DORA and SPACE. Not because they were trendy, but because they helped replace gut feel with something more honest.
tl;dr (for exec readers)
Most engineering metrics measure motion, not progress
DORA shows how work actually flows through the system
SPACE shows what that system does to people
Using both together improves delivery without burning teams out
Metrics should help teams learn, not make them defensive
For years, engineering productivity was judged by proxies.
How busy teams looked.
How fast tickets moved.
How confident leaders sounded in reviews.
From experience, I’ve learned this the hard way: activity is easy to measure, effectiveness is not. And once systems get large, distributed and automated - intuition stops scaling.
That’s where DORA and SPACE changed how I think about metrics.
DORA: When Delivery Stops Being a Personality Debate
DORA focuses on four things:
Deployment frequency
Lead time for changes
Change failure rate
Mean time to recovery
On paper, these look technical. In practice, they expose organizational truth.
Scenario (anonymized)
I’ve seen two teams deliver similar features with very different timelines. One shipped weekly. The other took months.
The difference wasn’t talent or effort. It was structure.
More approvals. More handoffs. Testing pushed late. Releases treated as events instead of routines.
DORA didn’t blame anyone. It made friction visible.
Once that happened, the conversation changed from “why is this team slow?” to “why does the system make safe change so hard?”
That’s when automation gets funded and ownership becomes clear.
SPACE: When “High Performance” Starts to Crack
DORA tells you how software moves.
SPACE tells you what it feels like to build it.
SPACE looks at:
Satisfaction and well-being
Performance
Activity
Communication and collaboration
Efficiency and flow
Scenario (anonymized)
I’ve worked with teams that looked excellent on paper. Strong delivery metrics. Fast releases. Quick recovery.
And yet, people were tired. Senior engineers disengaged. Attrition crept in.
SPACE helped explain why.
Engineers were spending more time coordinating than building. Context switching never stopped. Collaboration increased, but focus disappeared.
Without SPACE, those signals would have been easy to ignore.
Why One Framework Wasn’t Enough for Me
DORA alone can push teams faster than the system can safely support.
SPACE alone can protect teams without fixing delivery problems.
The real value showed up when both were used together.
I’ve seen teams improve deployment frequency and satisfaction at the same time, simply by clarifying ownership, reducing cognitive load and making recovery predictable.
Velocity improved because stress went down.
Metrics Are Mirrors, Not Weapons
One lesson experience teaches quickly: metrics change behavior the moment people believe they’re being judged by them.
Used poorly, metrics make teams defensive.
Used well, they make teams honest.
DORA and SPACE only work when they’re treated as learning tools, not performance sticks.
Closing Thoughts
Engineering excellence today isn’t about heroics.
It’s about systems that don’t require them.
DORA helped me see how software really moves.
SPACE helped me see what that movement costs.
Used together, they shifted my thinking from intuition-driven management to calmer, evidence-based leadership.
That’s where real improvement sticks.
If this resonated, I’ll be writing more about engineering leadership, AI-assisted development, and building sustainable systems. Subscribe if you want future posts in your inbox.
— Suren