How do you allocate roadmap capacity across near-term delivery, platform and tech-debt investment, and longer-term bets when every group is pulling for more?
role-specific · Senior level · product-management
What the interviewer is really asking
Assesses whether a senior PM can manage the roadmap as a portfolio across time horizons and risk profiles, rather than over-indexing on whichever group is loudest in the room.
What to say
- Frame it as portfolio allocation across horizons — keep-the-lights-on and committed delivery, foundational/platform investment, and exploratory bets — and set rough target splits up front so the mix is a deliberate decision, not an accident of who lobbied hardest.
- Tie each bucket to its own success signal: delivery to committed outcomes, platform to engineering health and velocity metrics, bets to learning milestones — so you can defend why each gets the share it does.
- Revisit the allocation on a cadence and adjust to context: a stabilization quarter justifies more platform investment, a growth push justifies more delivery, and you say that trade-off out loud rather than quietly starving one bucket.
What to avoid
- Don't let the loudest stakeholder or the most urgent fire set the whole mix; that systematically starves the invisible work — platform and bets — that has no one shouting for it.
- Don't treat tech-debt and platform work as a residual you fund only with leftover time; framed that way it never gets funded and velocity quietly decays.
- Don't present a static allocation as permanent; refusing to adjust the mix as the business phase changes is just a different way of being wrong.
Example answers
Strong: I run the roadmap as three buckets with rough target splits — roughly 60% committed delivery, 25% platform and debt, 15% exploratory bets — and I make that split a visible decision the team and stakeholders sign off on. When velocity started slipping from accumulated debt, I temporarily pushed platform to 35% for a quarter and named exactly which delivery items would wait, with the data on how the debt was taxing every estimate. Being explicit meant the delivery stakeholders accepted the trade rather than feeling robbed.
Weak: I focus capacity on whatever's most urgent and customer-facing, and I fit in tech-debt and bigger bets when we have some slack between releases.