Handling an Underperforming Launch When Engineering Has No Spare Capacity

A feature you shipped recently is falling short of what customers expected. Your engineering team is fully booked and the roadmap has no room. What would you do? ```hint Name the gap first Before asking for engineering time, work out what kind of shortfall this is and whom it hurts. Some shortfalls close without new code; the rest have to win their place against the planned work on evidence. ``` ### Clarifying Questions - How do we know it is falling short: support tickets, low adoption, renewal risk, or complaints from a few key accounts? - Is the gap a defect, a usability problem, a missing capability, or a difference between what was promised and what shipped? - Which customers are affected, and does any contract or public commitment depend on this feature? - Are roadmap dates fixed by outside commitments, or can they move if the case is strong? ### What a Strong Answer Covers - A diagnosis that sizes the shortfall, splits it by customer segment and identifies its type before a fix is chosen - Whether options needing little or no engineering are considered before asking for capacity - An explicit trade-off between fixing the feature and planned roadmap work, argued with comparable evidence - How the decision is agreed with engineering, leadership and customer-facing teams, and how customers are told - Success criteria for the fix and a process change that keeps the gap from recurring ### Follow-up Questions - Your largest customer says it will not renew unless the feature is fixed this quarter. What changes in your plan? - The data shows that only a small but vocal group is unhappy. Do you still act, and how? - How would you decide whether to fix the feature, rework it or retire it?