HR roadmap template — editable, free
Most of a people team’s year is the same work at the same time: a review cycle, a compensation round, an engagement survey. This template marks every item as recurring annually or one-off, groups ten items across four programmes, and saves a view of only the things that come round again.
| View | Groups by | Visible fields |
|---|---|---|
The year (timeline) | Programme | Name, Recurs, Owner, Start, End |
Leadership (timeline) | Programme | Name, Programme, Start, End |
What repeats (board) | Recurs | Name, Programme, Owner, End |
All items (table) | Nothing — one flat list | Name, Programme, Recurs, Status, Owner, End |
Why does a people roadmap look different?
Because most of it repeats. A product roadmap is a list of things that haven’t happened before. A people roadmap is a review cycle, a compensation round and an engagement survey, in the same months every year, plus whatever one-off work fits between them.
Which means the useful field isn’t priority or status. It’s whether an item comes round again. The recurring items are a fixed cost on the calendar — you plan around them instead of deciding about them — and the one-off work only has the months they leave.
What is in this template?
Ten items across four programmes — hiring, onboarding, development and annual cycles — with every item marked as an annual cycle or a one-off, at month resolution.
The review cycle is six weeks long and it’s drawn at that length on purpose. A plan that leaves it off has two free months in it that don’t exist, and every one-off project scheduled there is competing with a company-wide process it will lose to.
One item is a one-off that makes a cycle cheaper: rebuilding the first week of onboarding. Those are the projects worth arguing for, and marking them so is most of the argument.
How does it stay current?
By being touched when something happens, not on a schedule, which is the argument in how to keep a roadmap up to date . It applies here with one twist: the cycles arrive whether or not the document is current, so the thing that actually goes stale is the one-off work in between.
Whether any of this is published beyond the leadership team deserves a real decision instead of a default. Should you have a public roadmap is about a customer audience, and the argument transfers exactly — publishing is a standing commitment to keep a forward-looking document current in front of people who didn’t agree to your replanning, and a stale people plan is read as a broken promise rather than a changed one.
For the funding view of the same year, an annual roadmap template groups by investment area. For the estate that runs alongside it, an IT roadmap template is organised by lifecycle. And for a design team’s version of planning in stages, a design roadmap template separates research from the work that ships.
Common mistakes
Leaving the annual cycles off because everyone knows about them. They take six weeks each and they land in the same months every year, so a plan that omits them counts time it doesn’t have.
Planning one-off projects into cycle months. A manager training programme scheduled across the review cycle competes with it and loses, every time.
Forgetting the work after a survey. Running an engagement survey is two weeks; acting on it’s a quarter, and only one of those usually makes it onto a plan.
Treating hiring as a single item. Four hires across two quarters is four different conversations, and one bar hides which of them has actually stalled.
Questions
Why mark items as recurring?
Because it changes what you do with them. A recurring cycle is a fixed cost on the calendar to plan around; a one-off is a choice you can move. Mixing them produces a plan that looks achievable and isn’t.
Does a people team need a roadmap at all?
It needs one for the same reason product does: several audiences are planning around the same work and getting different answers. The review cycle affects every manager in the company, and nobody should have to ask when it starts.
What about confidential work?
It doesn’t go on a shared view. Hiding a field is a view setting, so the values stay in the file and travel with the file — anything genuinely confidential belongs in a different document, not a hidden column.
Related
- Annual roadmap templateFour calendar quarters grouped by where the money goes, with confidence on every item and a board view.
- How to keep a roadmap up to dateStaleness is a copies problem, not a discipline problem. What to change so the update happens.
- Should you have a public roadmapThe upkeep is the real cost, the three conditions that justify it, and when to take it down.
Last updated