Winning Commitment From Several Teams for a Product Strategy You Own

You are the product manager for a product that several teams contribute to. You have set a strategy for it, and that strategy only works if each of those teams commits to it. How would you get every team on board, and how would you keep them committed once the work begins? ```hint Start from each team's goals Every team already has its own roadmap, targets and limited capacity. Before planning how to present the strategy, work out what each team gains, what it gives up, and who decides on its behalf. ``` ### Clarifying Questions - Which teams are involved, and do they report to me, to a shared leader, or to separate organizations with their own goals? - Is the strategy already approved by leadership, or can these teams still change it? - Are any teams known to be resistant, and is the resistance about the direction itself or about their capacity? - Would you like my general approach, an example of a time I did this, or both? ### What a Strong Answer Covers - Diagnosis before persuasion: each team's incentives, constraints, likely objections and real decision maker - Involving teams early enough that they shape part of the plan and own it - A clear written strategy with goals, non-goals and an explicit ask and owner for each team - A considered way to handle a team that still disagrees, including when and how to escalate - Mechanisms that keep commitment alive after kickoff, backed by a concrete example of doing this ### Follow-up Questions - A team lead agrees in the meeting but never staffs the work. What do you do? - How do you win over a team whose own metrics look worse if your strategy succeeds? - When is it right to escalate to a shared leader, and how do you do it without damaging the relationship?