Balance Technical Debt and Feature Delivery

Project Context

Notion's Workspace Platform team is preparing a Q3 launch of a new enterprise permissions feature requested by several top customers. The feature is expected to help close $4.2M in annual contract value, but the underlying permissions service has accumulated technical debt: incident rates have increased, test coverage is low, and deploys now require manual rollback steps.

You are the program manager for a 10-person cross-functional team: 6 engineers, 1 engineering manager, 1 product manager, 1 designer, and 1 QA lead. Leadership wants the feature launched within 12 weeks, but engineering believes at least part of the quarter must be spent reducing technical debt to avoid a risky release.

Key Stakeholders

The VP of Product wants the customer-facing feature delivered this quarter to support enterprise sales commitments. The Engineering Director wants to reserve meaningful capacity for reliability and maintainability work. Sales is pushing for the full feature scope, while Customer Support is concerned that another unstable launch will increase ticket volume.

Constraints

• Timeline: 12 weeks, with a hard launch review in Week 10
• Budget: No additional headcount; only $60,000 available for contractor QA support
• Current debt: 14 high-priority bugs, 3 recurring Sev-2 incidents in the last 60 days, and only 58% automated test coverage on the permissions service
• Dependency: Security review must be completed by Week 8, and one senior backend engineer is allocated 30% to production support

Complications

1. A strategic customer has asked for one additional admin workflow that was not in the original scope.
2. Engineering estimates that ignoring two core debt items could increase launch rollback risk significantly.
3. The VP of Sales has already told two enterprise prospects the feature will be available by quarter end.

Deliverables

1. Propose a 12-week execution plan that balances technical debt reduction with feature delivery.
2. Explain how you would decide what debt must be addressed now versus deferred.
3. Define stakeholder communication and escalation points when trade-offs affect scope or launch timing.
4. Identify the top risks, mitigations, and fallback options if the team falls behind.
5. Specify success metrics for both the feature launch and technical health improvements.