Engineering Leadership
Building a Measurable Engineering Operating Model
Enterprise Engineering Organisation
DORA + system health
Measure the engineering system — not individuals
Metrics create conversations, not surveillance
At a glance
- Challenge
- Delivery predictability, technical health and continuous improvement were difficult to measure across teams.
- My role
- Introduced and strengthened engineering practices without adding process theatre.
- Team scale
- Applied across multi-team delivery with shared readiness and health rituals.
- Technical landscape
- DORA metrics, engineering health signals, Definition of Ready and Done, refinement and planning discipline.
- Complexity
- Making the engineering system observable without turning metrics into surveillance.
- Outcome
- Engineering became more observable and improvable, with clearer practices, healthier conversations and stronger ownership.
The challenge
Engineering teams were delivering software, but inconsistent engineering practices made delivery predictability, technical health and continuous improvement difficult to measure.
Context
Teams were shipping, but the engineering system itself was hard to see, improve or govern consistently.
The real problem
Without shared practices and signals, delivery predictability, quality and improvement depended too much on local habit and individual heroics.
My role
Introduced and strengthened engineering practices designed to create predictable delivery, stronger quality and greater ownership while avoiding unnecessary process overhead.
The decision
Strengthen an operating model that makes engineering health observable: readiness, quality, coaching, debt management and system-level metrics.
Philosophy
Measure the engineering system—not individual developers.
Approach
Introduced and reinforced practices that create clarity and ownership without process theatre, and used metrics to find constraints rather than assign blame.
What this involved
- Definition of Ready
- Definition of Done
- Refinement discipline
- Sprint planning
- Technical decomposition
- Architecture discussions
- Engineering health reviews
- Structured 1:1s
- Technical coaching
- Technical debt management
- Delivery governance
- Retrospectives
- Continuous improvement
How progress was observed
DORA
Deployment Frequency Lead Time for Changes Change Failure Rate Mean Time to Recovery
Additional signals
Cycle Time Escaped Defects Security Findings Platform Reliability Technical Debt Developer Experience Team Health
Proof points
- Shared Definition of Ready and Done used in planning and completion
- DORA and system-health signals reviewed as conversation starters
- Refinement, coaching and debt management treated as operating habits
- Continuous improvement loops tied to observable constraints
Outcome
Engineering became more observable and improvable — with clearer practices, healthier conversations and stronger ownership.
- Clearer Definition of Ready and Done
- Stronger refinement and planning discipline
- Visible engineering health signals
- Continuous improvement loops
Lesson
Metrics should help leaders improve systems. When they become surveillance, they stop telling the truth.