Getting headcount approved is only half the battle. The other half is deploying that headcount strategically. A common and powerful framework for visualizing how engineering investment is distributed is Run / Grow / Transform — sometimes called the Three Horizons model.
The Three Buckets
1. Run (Keep the Lights On — KTLO)
- Activities: Bug fixes, on-call rotations, security patches, dependency upgrades, compliance work.
- Goal: Stability and reliability.
- Danger: If this consumes 100% of your team's capacity, the company stops innovating and eventually loses to competitors who are shipping new value.
2. Grow (Incremental Value)
- Activities: New features for existing products, performance improvements, A/B tests, customer-requested enhancements.
- Goal: Retention, upsell, and customer satisfaction.
- Danger: Pure "Grow" work keeps existing customers happy but does not open new markets or revenue streams.
3. Transform (Innovation)
- Activities: New products, major architectural rewrites, entering new markets, platform bets.
- Goal: Future revenue that does not exist yet.
- Danger: Pure "Transform" work with no "Run" investment leads to production instability that kills customer trust.
Using This Framework to Win Headcount
The power of this model is that it makes your current allocation visible and your desired allocation concrete. Instead of saying "we need more people," you say:
"Currently, we spend 80% of capacity on Run and 20% on Grow. We have zero capacity for Transform. I am requesting 2 engineers to automate the highest-volume Run work, which will shift our ratio to 50% Run / 30% Grow / 20% Transform. This directly enables the platform modernization initiative that is on the executive roadmap for next year."
Executives respond to this framing because it connects headcount to strategy, not just workload.