You've got a page of things you believe the business needs from People right now: enhance organizational capability, increase talent density, refine the employee experience. These are your People implications, what the business context means for what the People team needs to work on. Directional, but not yet a plan. You don't know how to turn that page into something a manager could actually act on.
A People roadmap is not a list of implications. It's a series of specific answers to one question, asked once for every business objective: what can the People team do to increase the odds this objective gets hit.
Most People teams get stuck at exactly this step. They either stay too strategic, circling the implications without ever turning them into anything executable, or they jump straight to operational detail and end up busy on things disconnected from what leadership actually cares about. The first version shows up as a deck full of aspirational language and no action items. The second shows up as a long list of People activities nobody can trace back to a business priority.
Both look like progress. Neither is. The fix isn't more thinking time, it's going back to the specific business objectives your implications came from, and asking the same disciplined question against each one.
If you can't name the specific business objective a roadmap item serves, it doesn't belong on the roadmap yet. And the answer to "what should we do about this" is sometimes to add something, sometimes to remove something creating friction. Both count as progress.
Take one of your People implications and trace it back to the specific business objective it came from. For each objective, literally answer: what can we do from a People perspective to increase the odds this gets achieved? Say the objective is expanding into new markets. A People objective could be building the team's capacity and infrastructure to support that expansion.
Brainstorm the initiatives, programs, or projects that would move that People objective. For the expansion example, that could mean upgrading your HR systems to support a distributed team, or putting someone in charge of figuring out fair, consistent pay across the different countries you're hiring in.
If you're weighing several options, weigh them on the same three things: how fast you can stand it up, what it costs, and how directly it moves the objective. A roadmap where every initiative looks equally important usually means none of them were tested against those three.
In many businesses across Lagos, Nairobi, Kampala, or Accra, the highest-impact move is often not a program at all: it's a single hire, a policy change, or freeing up a manager's time, since budget and headcount are usually the tighter constraint than ambition.
Sometimes the answer isn't a new initiative. It's removing something that's slowing the business down. Here's the same objective producing two different kinds of answer, one additive and one subtractive:
You'll often need a combination of initiatives to hit one objective, not one silver bullet.
For each initiative, name what you'll track to confirm it did what you wanted, and that it moved the business objective it's tied to. Know what you're watching before you start, not after.
If you can't name the specific business objective a roadmap item serves, it doesn't belong on the roadmap yet.
Pick one thing you believe People needs to work on right now. Name the business objective it serves and the initiative that would deliver it. If you can't name both, that's the gap to close before it goes on your roadmap.