HR transformation roadmap: a practical 90-day template

What belongs in an HR transformation roadmap?

An HR transformation roadmap connects a business problem to changes in people services, working practices, information and technology. It should explain what will improve for employees, who owns the change, what must happen first and what evidence will show progress. A software implementation schedule is only one part of that picture.

The 90-day approach below is a suggested starting framework. Adjust it to your capacity and the complexity of your services. Its purpose is to produce a tested improvement and a defensible next decision, rather than promise that a whole HR function can be transformed in three months.

Days 1 to 30: understand one employee journey

Choose a service with a clear beginning and end. Onboarding is useful because a new starter experiences the combined work of HR, their manager and IT. Map a fictional or appropriately redacted example from accepted offer to the first useful day at work.

Record each handover, the information required and the person responsible. Ask where the employee has to chase progress or repeat information. Include exceptions: a changed start date, an unavailable manager or an accessibility requirement. Invite the people doing the work to correct your map.

Establish a baseline you can actually reproduce. For example, count how many starters receive their agreed essentials by the agreed date. Record the denominator and the definition of “essentials”. A percentage without either can improve simply because somebody changed the calculation.

Days 31 to 60: design and test the improvement

Choose a small change that addresses the observed problem. Perhaps the service needs a shared owner and a visible checklist before it needs an AI assistant. Define the system that holds each record and how another team learns that a task is ready.

Use a test environment and fictional records to walk through the ordinary journey and its exceptions. Check what happens when the same request arrives twice, information is missing or the workflow stops halfway through. An employee should have a clear route to a person when the digital journey cannot continue.

If an agent is part of the proposal, specify its allowed actions and review points. The HR automation checklist helps turn an idea into a bounded pilot.

Days 61 to 90: review evidence and decide

Compare the pilot with your baseline using the same definitions. Look at service quality, employee effort and the work transferred to another team. Faster HR handling is not a useful improvement if managers spend longer repairing the result.

Review a sample of completed cases as well as the dashboard. Document exceptions, staff feedback and unresolved dependencies. Decide whether to continue, revise or stop the pilot. Give the next phase a named owner and the resources it requires.

Copy this roadmap brief

• Employee problem: what is difficult today, and for whom?
• Service boundary: where does the journey start and finish?
• Baseline: what will you compare, using which definition?
• Proposed change: what will people do differently?
• Dependencies: which records, teams and permissions are needed?
• Owner: who can decide and who will operate the service?
• Pilot evidence: what would justify expanding the change?
• Stop condition: what would make you pause and investigate?

Keep this brief beside the delivery plan. When a feature request arrives, ask which part of the brief it improves. This gives HR, IT and business leaders a shared way to discuss priorities.

Build the capability to deliver

Use HR Transformation Strategy & Roadmap to develop the plan with a facilitator, or HRIS Selection & Connected People Systems when requirements and integration are the immediate challenge. Explore the HR academy for the wider team, or talk to Experrt about a programme shaped around your service.