Employee Experience Roadmap: 12-Month Template With Owners and Metrics
8 min read ยท 2026-10-25
An employee experience roadmap is a time-based plan that shows which parts of working at your company you will improve, in what order, who owns each change and how you will know it worked. It covers the whole journey, from the first job ad to the exit interview, but it focuses your effort on the few moments that matter most to your people right now.
Most employee experience plans fail because they try to fix everything at once or start with a tool purchase. The 12-month template below starts with listening and journey mapping, then picks three priority moments, pilots fixes with one or two teams, and only then scales what worked. Every phase has a milestone you can check, and the guide covers owners, a filled-in example, metrics and how to get leadership behind it.
The roadmap at a glance
Goal: Improve the three employee journey moments with the biggest gap between importance and satisfaction, and show the change in survey scores and related metrics within 12 months. Duration: 12 months
Set the scope and sponsor (Weeks 1-4)
Agree on why you are doing this and who will back it.
- Name an executive sponsor, such as the COO or CEO, not only the HR lead.
- Write the business problem in one paragraph, for example new hires leaving in their first year or low internal mobility.
- Gather the data you already have: engagement survey results, exit interview notes, turnover by team and tenure, onboarding feedback.
- Set up a working group with HR, IT, facilities, internal communications and two or three line managers.
Milestone: A one-page charter with the problem, the sponsor, the working group and the baseline data, approved by the sponsor.
Listen and map the journey (Weeks 5-10)
Find out where the experience breaks, in employees' own words.
- Run focus groups or short interviews across roles, locations, tenure and work arrangements (office, hybrid, remote, frontline).
- Map the employee journey stages: attract, hire, onboard, develop, perform, grow, exit.
- For each stage, note the key moments, the people and systems involved, and the pain points you heard.
- Send a short pulse survey asking how important each moment is and how satisfied people are with it.
Milestone: A journey map with pain points by stage and importance against satisfaction scores for each key moment, shared with the working group.
Prioritize and plan (Weeks 11-14)
Choose three priority moments and write a clear plan for each.
- Plot each moment on a grid: importance on one axis, satisfaction on the other, and pick the high importance, low satisfaction ones.
- Score the candidates on effort and cost, and pick three to work on this year.
- For each priority, write the target outcome, the metric, the owner and the first fix to test.
- Agree on the budget and the people who will deliver each fix.
Milestone: Three priority moments with a target metric, an owner and a first fix each, approved by the sponsor.
Pilot the fixes (Weeks 15-26)
Test each fix with one or two teams before rolling it out.
- Pick pilot teams that feel the problem and have a manager willing to try something new.
- Launch the fix, such as a new onboarding plan, a manager one-to-one guide or a single IT request portal.
- Collect feedback at two and six weeks with short surveys and a few conversations.
- Compare pilot results with a similar team that did not get the change.
Milestone: A pilot report for each priority with results against the baseline and a go, change or stop decision.
Scale what worked (Weeks 27-42)
Roll out the successful fixes across the company and make them part of normal work.
- Write a rollout plan by department or location, with a date and an owner for each wave.
- Train managers on any new process before their team gets it.
- Update policies, the intranet and HR systems so the new way is the default.
- Tell employees what changed and why, and connect it to what they said in the listening phase.
Milestone: All go-decision fixes rolled out to every target group, with managers trained and systems updated.
Measure and plan year two (Weeks 43-52)
Show what changed and decide what comes next.
- Rerun the pulse survey on the same moments and compare with the baseline.
- Pull the related metrics: early turnover, time to productivity, internal moves, ticket resolution time.
- Present the results to the sponsor and leadership team.
- Pick the next priorities from the journey map for year two.
Milestone: A year-end report with before and after scores for each priority moment and an approved plan for year two.
Example: a filled-in roadmap for a growing company
Picture a company with about 600 people across two offices and a remote team. Turnover in the first year is higher than leaders want, and the engagement survey shows low scores on growth. The listening phase finds three pain points: a messy first week, unclear career paths and slow IT support for remote staff.
The team does not try to fix pay, benefits and the office layout in the same year. It sticks to three moments, which keeps the work small enough to deliver.
- Q1, listen and prioritize: journey map, pulse survey, three priorities chosen. Owner: HR business partner lead. Milestone: charter and priorities approved by the COO.
- Q2, pilot: a 30-day onboarding plan with a buddy in two teams, a career conversation guide for managers in one department, a single IT request portal for remote staff. Owners: talent lead, learning lead, IT service manager.
- Q3, scale: onboarding plan rolled out companywide, managers trained on career conversations, IT portal live for everyone. Owner: each priority owner, coordinated by the HR business partner lead.
- Q4, measure: pulse survey rerun, early turnover and internal moves compared with the baseline, year-two priorities picked. Owner: people analytics.
Who owns what
Employee experience is not only an HR project. A large part of what people feel at work comes from their manager, their tools and their workspace. If HR owns the whole roadmap alone, fixes that depend on IT or facilities stall.
Give each priority moment one owner, even if several teams contribute. Use a RACI chart if many groups touch the same moment.
- Executive sponsor: removes blockers, approves budget, presents results to the leadership team.
- HR lead or employee experience lead: owns the roadmap, runs the working group, reports progress.
- People analytics: owns the survey design, baseline data and before and after comparison.
- IT: owns fixes involving tools, access and support.
- Facilities or workplace team: owns fixes involving space, equipment and on-site services.
- Line managers: deliver many of the changes day to day and give feedback from their teams.
- Internal communications: explains changes and closes the loop with employees.
How to map the employee journey
Start with the stages most companies share: attract, hire, onboard, develop, perform, grow and exit. Under each stage, list the moments that shape how people feel, such as the offer call, the first day, the first performance review, a promotion decision or a parental leave return.
Build the map from what employees told you, not from what HR thinks happens. Use a whiteboard, Miro or a simple spreadsheet with one column per stage and rows for moments, people involved, systems used, pain points and quotes from interviews. Build separate versions for groups whose experience is very different, such as frontline workers and office staff.
Metrics to track
Pick one main metric for each priority moment, plus one or two company-level numbers. Measure the baseline before any pilot starts, and use the same questions and method every time you remeasure.
Do not judge the roadmap on the annual engagement score alone. It moves slowly and depends on many things you are not changing. Moment-level scores and operational numbers show progress much sooner.
- Moment satisfaction: the pulse score for each priority moment, from the same question asked before and after.
- Employee net promoter score (eNPS): how likely people are to recommend the company as a place to work.
- Early turnover: share of new hires who leave in their first year, by team.
- Time to productivity: how long new hires take to reach agreed first goals, as reported by their manager.
- Internal mobility: roles filled by internal candidates.
- Service metrics: IT or HR ticket resolution time, if a priority involves support.
How to present it to leadership
Leaders back employee experience work when it is tied to a business problem they already care about, such as hiring costs, early turnover or slow ramp-up. Open with that problem and the baseline, then show the three priorities and why they were chosen.
Keep it to one slide: the problem, the three priority moments, a 12-month timeline with the six phases, the owner and metric for each priority, and what you need from leadership. Leave out the full journey map and the survey details. Put them in an appendix for anyone who asks.
How to adapt the roadmap
A company of 50 people does not need a working group and a formal journey map. One HR lead can run a short survey, talk to a dozen people, pick two fixes and test them in a quarter. The phases stay the same, but each one takes days instead of weeks.
In a large company with many locations, run the listening phase by region or business unit, because the problems differ. Keep the priorities global if possible and let local teams adapt the fixes. If your workforce is unionized, involve employee representatives early, especially before changes to schedules, policies or tools.
Common mistakes to avoid
- Starting with a new HR platform before you know the problem leads to a tool nobody asked for, so listen and pick priorities first.
- Trying to fix every stage of the journey in one year spreads the team too thin, so limit the roadmap to three priority moments.
- Making HR the only owner leaves fixes that depend on IT or facilities stuck, so give each priority one owner from the team that controls the fix.
- Surveying people and never reporting back makes the next survey less honest, so share what you heard and what you will change within weeks.
- Rolling out a fix to everyone without a pilot spreads mistakes widely, so test with one or two teams first and compare with a similar group.
- Judging success only on the annual engagement score hides real progress, so track moment-level scores and operational metrics too.
Frequently asked questions
What is an employee experience roadmap?
It is a plan that shows which parts of the employee journey you will improve, in what order, who owns each change and how you will measure it. It usually covers 12 months and focuses on a few priority moments. It turns survey results into dated actions with owners.
What are the stages of the employee journey?
A common set of stages is attract, hire, onboard, develop, perform, grow and exit. Some companies add alumni or split onboarding into pre-boarding and the first 90 days. Use the stages that match how your company works.
Who should own the employee experience roadmap?
An HR or employee experience lead usually owns the roadmap, with an executive sponsor who can unblock decisions and budget. Each priority moment should have its own owner, often in IT, facilities or a business unit. Line managers deliver much of the change day to day.
How do you measure employee experience?
Use pulse surveys on specific moments, eNPS and your annual engagement survey, plus operational data such as early turnover, time to productivity and internal mobility. Measure the baseline before you change anything. Ask the same questions the same way each time so the numbers are comparable.
How long does it take to improve employee experience?
Pilots of focused fixes can show results within one or two quarters. Wider measures such as turnover or engagement scores often take a year or more to move. That is why the roadmap tracks moment-level scores along the way.