Situation: Our engineering velocity had slowed down by nearly 40% due to an aging monolithic build system, but product leaders wanted 100% of engineering bandwidth focused on releasing quarterly sales features.
Task: I needed to establish a sustainable framework that balanced critical infrastructure modernization with vital revenue-generating product features.
Action: I partnered with our head of product to introduce an agreed 70/20/10 capacity allocation model across all engineering squads: 70% for customer-facing roadmap features, 20% for architectural reliability and technical debt, and 10% for exploratory innovation and tooling. To justify the 20% technical debt allocation, I translated engineering pain into business terms, showing that modernizing our CI build pipeline would save forty developer hours each week—effectively giving the company an extra engineer's worth of feature capacity every month.
Result: With leadership buy-in, we upgraded our build pipeline over two sprints using the 20% budget. CI test run times dropped from forty-five minutes to seven minutes, immediately accelerating feature shipping velocity for the entire company by 25% within the subsequent quarter.