Leadership highlight
Taking a team from 25% to 100% delivery — in one quarter
How I diagnosed why a cross-functional team was chronically missing roadmap commitments, and restructured how engineering and product planned and executed work to fix it permanently.
25%→ 100%
On-time delivery rate after process changes
1 quarter
Time to stabilise and consistently hit commitments
Zero
Underpromising to hit the numbers — explicit team commitment
Engineering + product
Process design
Delivery transformation
Root cause
The team was estimating tasks, not investigating them
When I took over, only 25% of committed roadmap work was being delivered on time. The real cause was fundamental: engineers were accepting tasks at face value without breaking down what it would actually take to build them. Estimates were guesses. Commitments were optimistic by default.
Compounding this: engineers were simultaneously responsible for their main project work and handling day-to-day bugs across the product areas they owned. Interrupt-driven bug work was fragmenting focus and making it impossible to hold a reliable delivery schedule.
The roadmap wasn't unreliable because of bad priorities. It was unreliable because the team had no systematic way to know what they were committing to before they committed.
What changed
Three structural changes, one quarter to stabilise
1
Module-level breakdown before any commitment
I required engineering leads to decompose every project module by module before it entered the roadmap. No task got committed to until someone had actually investigated what building it would take. This single change made estimates trustworthy for the first time.
2
Scrum with structured sprints
Introduced sprint-based delivery — starting with four-week sprints to build the habit, then moving to two-week sprints as the team found its rhythm. This gave engineers a forcing function to plan their own work and a regular cadence to course-correct before a quarter slipped.
3
Rotating bug duty, separated from project work
Created a dedicated bug duty rotation so day-to-day issues were handled by a designated engineer each cycle — not spread across everyone. This gave the rest of the team protected focus time for their main deliverables, eliminating the biggest source of mid-sprint disruption.
How we knew it was working
Consistently hitting commitments — without gaming the numbers
Within a quarter, the team was consistently delivering what it committed to. The metric that mattered most to me wasn't just completion rate — it was making sure the improvement wasn't coming from the team lowballing its commitments to look good. That was an explicit conversation: we were not underpromising to hit these numbers.
The signal that it had genuinely worked was that the engineering team itself started owning the estimation process — insisting on breakdown before commitment, flagging when a task wasn't sufficiently understood, and holding each other to the planning standard.