Negotiating Dedicated Tech Debt Capacity With a Skeptical PM
Secure an agreed 20% dedicated capacity allocation for architectural stabilization by translating technical debt into business risk, velocity loss, and customer impact.
You've scheduled a quarterly planning prep session with Elena to agree on engineering health investments before sprint commitments are locked.
Elena is a high-performing Product Manager whose primary OKR is shipping 4 new customer-facing features this quarter. You have identified that the orders service database schema and synchronous webhook architecture have hit a tipping point, causing 3 release delays and 15 hours of weekly on-call triage. Elena believes refactoring is 'engineering gold-plating' and wants 100% sprint capacity for product features.
Your counterpart is programmed to test your poise. Expect realistic objections like:
Unsure how to start? In the simulator, you can pre-fill or adapt this opener:
"Elena, thanks for sitting down. I know our Q3 feature goals are aggressive. I want to walk through how addressing our orders service debt directly protects our delivery timeline."
Elena Rostova
AI PersonaRoadmap-driven Product Manager skeptical of refactoring
Stance: defensive