How to Build a Transformation Roadmap Template: 6 Phases, Excel and Jira

11 min read ยท 2026-11-21

To learn how to build a transformation roadmap template, start with the columns and work outward. Set up nine columns: initiative, objective, phase, owner, start and end dates, dependencies, milestone, KPI and status. Then group every initiative into six phases: assess, define the target, prioritize, pilot, scale, and embed. The template is ready when a steering committee can read it on one page and every line has an owner and a date.

A transformation roadmap is not a project plan. A project plan lists the tasks for one deliverable. A transformation roadmap shows how several initiatives change the way a company works over a long period, and in what order. This guide gives you the six phases with durations, a fully filled example you can copy, the setup in Excel and in Jira, and a way to present the result to leadership.

The roadmap at a glance

Goal: Move the organization from its current way of working to a defined target state, with clear owners, milestones and measures at each phase. Duration: 12 to 24 months

  1. Assess the current state (4 to 6 weeks)

    Know where you start before you promise where you will land.

    • Interview the leaders of each affected department and list their top three pain points.
    • Map current processes, systems and data flows for the areas in scope.
    • Rate the readiness of each team: skills, capacity, appetite for change.
    • Record baseline values for the KPIs you plan to improve.

    Milestone: Current state assessment signed off by the sponsor.

  2. Define the vision and target state (3 to 4 weeks)

    Describe what "done" looks like in terms a business leader can check.

    • Write a vision statement of two or three sentences.
    • Turn it into three to five measurable objectives.
    • Describe the target processes, systems and roles at a high level.
    • Agree on what is out of scope.

    Milestone: Target state and objectives approved by the steering committee.

  3. Prioritize initiatives and map dependencies (2 to 3 weeks)

    Decide the order of the work, not just its content.

    • List every initiative needed to close the gap between current and target state.
    • Score each one on value, effort and risk.
    • Mark dependencies: which initiative must finish, or start, before another.
    • Assign one accountable owner per initiative.

    Milestone: Prioritized initiative list with owners and dependencies published.

  4. Run a pilot (2 to 3 months)

    Test the change on a small group before you commit the whole company.

    • Pick one team or site that is willing and representative.
    • Launch the new process or system with a support plan in place.
    • Collect feedback every week and log every issue.
    • Compare pilot KPIs with the baseline.

    Milestone: Pilot review completed, with a go, adjust or stop decision.

  5. Scale the rollout (6 to 12 months)

    Extend what worked, in waves, without breaking daily operations.

    • Plan rollout waves by department, region or product line.
    • Train managers first so they can coach their teams.
    • Retire old tools and processes on a set date for each wave.
    • Hold a monthly roadmap review to adjust dates and scope.

    Milestone: All waves live and legacy processes retired.

  6. Embed and sustain (Ongoing, reviewed quarterly)

    Make the new way of working the normal way.

    • Move ownership of each process from the program team to the business.
    • Add the new KPIs to regular management reporting.
    • Run a lessons learned session and update the template for the next cycle.

    Milestone: Final KPI review shows the objectives met or a reset plan approved.

What columns a transformation roadmap template needs

Each line of the template is one initiative. Keep the fields the same on every line, so you can filter, sort and roll up the data later.

A blank owner or a blank milestone tells you the initiative is not ready to go on the roadmap. Send it back to the prioritization phase until both are filled.

  • Initiative: a short name that starts with a verb, such as "Move invoicing to the new ERP".
  • Objective: the vision objective this initiative serves.
  • Phase: one of the six phases above.
  • Owner: one named person, never a team.
  • Start and end dates: month level is enough for leadership.
  • Dependencies: the initiatives that must come first.
  • Milestone: the check that proves the initiative is done.
  • KPI: the measure it moves, with its baseline and target.
  • Status: not started, on track, at risk, late, done.

A filled transformation roadmap template example

Here is a complete example for one common case: a mid-sized distribution company replacing spreadsheets and an old accounting tool with a cloud ERP. It covers one initiative per phase, plus one adoption line, so you can see how the fields work together. The months are relative to the program start.

Read the example from top to bottom and you can see the logic of the whole program. Every line points to an objective. Every line after the first depends on another. The at risk status on line 4 tells leadership exactly where to look. To adapt it, keep the structure and replace the initiatives with your own. A digital transformation fills it with systems and data. An agile transformation fills it with pilot teams, new team rituals and coaching.

  • 1. Map current finance and order processes: objective, close the books faster. Phase, assess. Owner, program manager. Dates, month 1 to month 2. Dependencies, none. Milestone, process maps and pain point list signed off by the CFO. KPI, days to close the month, baseline recorded. Status, done.
  • 2. Define the target finance operating model: objective, close the books faster. Phase, define the target. Owner, CFO. Dates, month 2 to month 3. Dependencies, line 1. Milestone, target processes, roles and out of scope list approved by the steering committee. KPI, target set for days to close. Status, done.
  • 3. Clean and migrate customer and supplier data: objective, one reliable source of customer data. Phase, prioritize, then delivered before the pilot. Owner, data lead. Dates, month 3 to month 5. Dependencies, line 2. Milestone, duplicate records removed and test load accepted by finance. KPI, share of records passing validation rules. Status, on track.
  • 4. Move invoicing to the new ERP for one business unit: objective, close the books faster. Phase, pilot. Owner, finance operations lead. Dates, month 6 to month 8. Dependencies, line 3. Milestone, one full month of invoices issued from the ERP with no manual rework. KPI, days to close the month for the pilot unit, against the baseline. Status, at risk, data load delayed two weeks.
  • 5. Roll out invoicing and purchasing to all units in three waves: objective, close the books faster. Phase, scale. Owner, finance operations lead. Dates, month 9 to month 18. Dependencies, line 4 pilot review with a go decision. Milestone, all three waves live and the old accounting tool switched off. KPI, days to close the month, company wide. Status, not started.
  • 6. Train managers before each wave: objective, new process used every day. Phase, scale. Owner, HR business partner. Dates, two weeks before each wave. Dependencies, line 5 wave dates fixed. Milestone, every team in the wave processes its orders in the ERP for four weeks in a row. KPI, share of invoices issued in the ERP, by wave. Status, not started.
  • 7. Hand ERP process ownership to finance: objective, new process used every day. Phase, embed. Owner, CFO. Dates, month 19 onward, reviewed quarterly. Dependencies, line 5. Milestone, process owners named in finance and KPI added to the monthly management report. KPI, days to close the month, tracked every month. Status, not started.

How to set up the template in Excel

Excel works well when a small program team owns the roadmap and leadership expects a file. For a transformation, the timeline chart is not the point. The point is keeping objectives, phases and adoption measures linked, so you can answer "how far are we on each objective?" at a glance.

Excel does not draw dependencies as arrows and does not notify owners. Keep one master file in a shared folder and put the date of the last update in the top cell, so nobody works from an old copy.

  • Initiatives sheet: one row per initiative, with the nine columns above, formatted as an Excel table so new rows inherit the formatting.
  • Objectives sheet: one row per objective, with a count of initiatives per status pulled from the Initiatives sheet with COUNTIFS. This is the sheet the sponsor reads.
  • Lists sheet: the allowed values for phase, status and owner, used as dropdowns through Data Validation, so status labels never drift.
  • Change log sheet: date, initiative, what moved and why.

How to build a transformation roadmap in Jira

Jira suits a transformation where most initiatives are delivered by teams that already work in Jira. Keep the roadmap level separate from delivery. The roadmap shows initiatives, priorities and milestones, while sprints and boards hold the stories and tasks. To reproduce the template in Jira, follow the setup below.

Jira keeps dates honest, because they move when the work moves. It is weaker at the parts of a transformation that are not software tasks: training, communication, policy changes, retiring old habits. Create those as epics too, even if the work behind them never touches a sprint. Otherwise the timeline shows the systems going live and leaves out the people side of the change.

  • Create one epic per initiative and use the initiative name as its title.
  • Fill in the start date and due date on each epic, so it appears on the timeline.
  • Record dependencies with issue links ("blocks" and "is blocked by").
  • Use a label or a custom field for the phase, and another for the objective, so you can filter by phase or objective.
  • Assign each epic to the initiative owner.
  • If initiatives span several teams or projects, use a cross-project timeline view in Jira, and check which Jira plan you need for it.

Plan change management and adoption inside the roadmap

Many transformation roadmaps list systems and processes, then stop. The change only counts when people actually work the new way. So give adoption its own initiatives, with owners and milestones, as line 6 of the example does. Add these lines to every phase from the pilot onward.

You check an adoption milestone by what people do, not by whether a message went out. "Training delivered" is an activity. "Every team in wave two processes its orders in the new system for four weeks in a row" is a milestone.

  • Stakeholder map: who is affected, how much, and who influences whom.
  • Communication plan: what each group hears, from whom, and when. Managers hear before their teams.
  • Training plan: role based sessions, scheduled before each rollout wave and not after.
  • Adoption KPI: a usage measure, such as the share of invoices issued in the new system, tracked by wave.
  • Feedback channel: one place where people report problems, reviewed every week.

Track progress and keep the roadmap alive

A roadmap that is not updated loses trust fast. Keep commitments firm for about six months, and show later work by quarter, without exact dates. Later phases depend on what the pilot teaches you, so precise dates two years out will only need to be withdrawn.

When a phase moves, record why in the change log. Six months later, nobody will remember why the pilot ran three weeks late. The log will.

  • Weekly: owners update status and dates on their own lines.
  • Monthly: the program team reviews risks, dependencies and slipping milestones.
  • Quarterly: the steering committee reviews KPIs against baseline and decides on scope changes.

Present the roadmap to leadership and clients

The full template is your working tool, not your slide. Build one view per audience from the same data. Executives need the six phases as horizontal bands by quarter, the major milestones as markers, and the status color of each objective. Team leads need their initiatives, owners, dependencies and next dates.

For the steering committee, prepare a one page summary and send it a few days before the meeting, so the session goes to decisions instead of reading. Show three things: what was completed since the last review, what is at risk and the decision you need, and what comes next quarter.

Common mistakes to avoid

  • Putting every task on the roadmap buries the direction, so keep initiatives on the roadmap and tasks in the delivery tool.
  • Skipping dependencies creates surprise delays, so link every initiative to what it needs before it can start.
  • Assigning initiatives to a team instead of a person leaves nobody accountable, so name one owner per line.
  • Promising exact dates two years out damages trust, so commit for about six months and show later work by quarter.
  • Leaving adoption out of the plan means systems go live without being used, so add training, communication and adoption KPIs as initiatives.
  • Updating the roadmap only before steering meetings makes it stale, so update status every week.

Frequently asked questions

What should a transformation roadmap template include?

It should include initiatives grouped by phase, each with an objective, owner, start and end dates, dependencies, a milestone, a KPI and a status. Add a short change log. Those fields let you build both a detailed working view and a one page leadership view from the same data.

How long does a transformation roadmap cover?

Most cover 12 to 24 months, split into phases. Commit firmly to the next six months or so, and plan the later phases at quarter level so you can adjust them after the pilot.

What is the difference between a digital transformation roadmap and an agile transformation roadmap?

A digital transformation roadmap centers on technology, data and the processes that change with them, such as moving to a new ERP or cloud platform. An agile transformation roadmap centers on how teams work: pilot teams, new rituals, scaling the framework and continuous improvement. Both use the same template, and only the initiatives change.

Should I build my transformation roadmap in Excel or Jira?

Use Excel when a small program team owns the roadmap and leadership expects a file. Use Jira when delivery teams already track their work there, so that dates update as the work moves. Many programs use Jira for delivery and keep a separate one page view for leadership.

Generate this roadmap with AI