Handling an Engineering Manager's New Feature Push When You Have Zero Spare Capacity

You are a product manager. Your engineering manager wants the team to work on a new feature, but you have no bandwidth at all to take it on. How would you handle the situation? Explain how you would respond to the engineering manager, how you would decide what happens to the idea, and how you would protect the working relationship along the way. ```hint Two separate questions Whether the idea is worth doing and whether there is room to do it right now are different questions. Answer each one before you respond. ``` ### Clarifying Questions - Does "no bandwidth" mean your own time as the PM is fully booked, or that the team's engineering capacity is already committed to the roadmap? - What kind of work is it: a customer-facing capability, or something engineering-driven such as paying down tech debt, improving stability or building tooling? - Where is the engineering manager's motivation coming from: customers, their own leadership, or the team's morale and growth? - Who makes the final call on the team's priorities: you, the engineering manager, or a shared product and engineering leadership group? ### What a Strong Answer Covers - Hearing out what the engineering manager wants to build and why, instead of dismissing it because the plan is full. - Judging the idea on the same impact, effort and strategic criteria as the work already planned, including a fair way to value engineering-driven work such as stability or tech debt. - Making the capacity trade-off explicit: what would have to move, shrink or wait, and who agrees to that. - The range of outcomes between an immediate yes and a flat no, and how you would choose among them. - Communicating the decision so the product and engineering partnership stays strong. ### Follow-up Questions - The engineering manager says the feature fixes reliability problems that keep slowing the team down. How does that change your prioritization? - After hearing your reasons, they plan to have engineers build it on the side anyway. What do you do? - How would you set up planning so engineering-proposed work has a fair path onto the roadmap without a negotiation every time?