You've built the People roadmap. Every item on it connects to something the business actually needs. You're ready to present it. Then the room goes quiet, or everyone nods and nothing changes six months later. Somewhere between building the plan and presenting it, you skipped the part where the people who need to say yes actually helped shape it.
Before you present the roadmap, work out what each stakeholder needs to believe before they'll commit to it. That answer is different for every person in the room.
Most People teams treat alignment as the last step: a presentation at the end of the process, meant to win support for something already decided. By the time you're presenting a finished plan, you're asking people to accept a decision they had no part in shaping. Even when they say yes in the room, that commitment tends to be thin.
The real cost shows up later. Months into execution, you discover the plan answers the wrong question, or a stakeholder you thought was on board never actually was. Fixing that mid-execution costs far more time and credibility than testing the plan before you finalized it would have.
Every stakeholder needs to believe something different, and pitching the CFO's case to the CEO, or the CEO's case to your team, lands flat even when the plan itself is right. Who's actually in these seats varies by organization, but the categories show up almost everywhere: the CEO (or whoever this needs to land with), the CFO (or whoever signs off on the spend), your own team if you have one, and the employees the plan will affect.
When you built this roadmap, you had real conversations with your leaders about the business. Go back to what each one told you mattered to them: their priorities, how their team contributes to the objectives, what they said they needed from the People team. That's your starting material for what each of them needs to believe, not a fresh guess.
Showing it looks different for each: plain commercial logic for the CEO, the financial case for the CFO, room to raise concerns and a resourcing commitment for your team, plain language focused on what changes for employees.
Before locking the roadmap, take it back to the people who'll live with it. Ask what's missing, what feels off, whether it actually addresses what they told you mattered. This is what turns a plan you're pitching into a plan people already recognize as theirs.
This tends to work better as individual conversations than a group review, especially where hierarchy shapes who feels free to speak up in a room. Find the one or two people whose support makes everyone else's easier, and work those conversations first.
If part of the roadmap needs budget, the CFO (or whoever signs off on the spend) needs more than a number. They need to believe two things: what it costs the business if this doesn't happen, and that you've already weighed the alternatives. Lead with the cost of inaction, not the ask.
By the time you're presenting a finished plan, you're asking people to accept a decision they had no part in shaping.
Pick one stakeholder on your roadmap you haven't actually spoken to about it yet. What do they need to believe before they see the plan? Go have that conversation before you present.