Winning back engineers' buy-in after a new roadmap lowers team morale

Your new roadmap has left the engineers on your product team demotivated. What would you do to get them engaged with the product again? ```hint Find out which kind of demotivation it is Before deciding what to change, work out whether the engineers object to what is on the roadmap, to how it was decided, or to what it means for their own work. ``` ### Clarifying Questions - Did you set the roadmap yourself, or are you carrying out priorities that leadership chose? - How is the demotivation showing: open pushback in planning, quieter disengagement such as slipping estimates, or people asking to move teams? - Did the roadmap cancel or push back work the engineers had been building or had proposed themselves? - Does the engineering manager agree with the roadmap, and do they already know about the morale problem? ### What a Strong Answer Covers - Diagnosing the cause through direct conversations before acting, in partnership with the engineering manager. - Explaining the reasoning and customer evidence behind the roadmap, and changing it where the team's objections hold up. - Concrete ways to give engineers ownership, such as involving them in scoping and solution design or reserving capacity for technical work. - Handling what cannot change honestly, without blaming leadership or promising what the PM cannot deliver. - How the PM will tell that engagement has returned, and how the next planning cycle avoids a repeat. ### Follow-up Questions - A senior engineer says the roadmap ignores technical debt that will slow everything down. How do you respond? - Leadership will not change the priorities and the team still disagrees. What do you do next? - Tell me about a time you won over a team that disagreed with your plan.