Change Readiness Findings Are In. Now What? Turning Gaps Into Action

by Panorama Consulting Group | Oct 23, 2026

Two business professionals walking toward a white line drawn across the sand, representing how to address change readiness gaps before kickoff

Key Takeaways

  • Knowing how to address change readiness gaps matters because findings that stay in a report rarely impact how the project is staffed or sequenced.
  • A change readiness action plan translates each finding into a specific decision, with an accountable owner and a deadline, and builds it into the implementation plan itself.
  • Backfilling employees during ERP implementation protects daily operations while giving process owners the dedicated time that design workshops and testing cycles require.
  • Process remediation and targeted employee engagement close the gaps that technology cannot.

A change readiness assessment may flag thin process documentation in the sales department and an overextended finance team, but no one really cares. The ERP project proceeds as planned.

While many stakeholders might care less about how to address change readiness gaps, readiness findings are actually a powerful tool that should do more than simply predict project problems.

A recurring question from our clients is what to do with readiness findings once the decision to proceed has already been made. Today, we are exploring how to convert those findings into a change readiness action plan that shapes the project from kickoff onward.

Change Management Case Study

The client recognized their need for more comprehensive change management, so they asked us to fill in the gaps. We developed a robust communication plan to supplement the vendor’s communication approach.

What Happens to Readiness Findings After the Green Light?

A change readiness assessment measures how prepared an organization’s people are for shifts in daily work. Through surveys, interviews, and focus groups, organizations can pinpoint where confidence in the change is low among employees and their managers and where current workloads might impede project participation.

While leadership may accept the findings, these insights don’t always translate into changes to the project timeline or the staffing model.

A finding that says the warehouse team has low confidence in the coming change is simply an observation. A decision to schedule warehouse training after peak season is an action that can actually facilitate project success.

Where Change Readiness Gaps Usually Hide

Readiness gaps tend to cluster in a few predictable areas:

  • Capacity gaps: Process owners and subject matter experts already carry full workloads, so the project hours assigned to them exist only on paper.
  • Process gaps: Current-state processes are undocumented or inconsistent across sites, which leaves design workshops without a reliable baseline to build from.
  • Leadership gaps: Managers support the project in principle but have not explained to their teams why the change matters or what it will ask of them.
  • Engagement gaps: Employees have heard little about the project, and that silence is quickly filled with assumptions about job security and workload.

These gaps compound when an organization runs several initiatives at once.

For example, a production plant that is implementing ERP while also rolling out new supply chain software or piloting an AI implementation risks change saturation (the point at which the volume of change exceeds what people can absorb).

Case Study

Panorama served as the organizational change management advisor to a pulp manufacturer during its SAP S/4HANA implementation. Our team treated readiness as an ongoing discipline throughout the project.

We developed business readiness criteria and conducted readiness assessment focus groups, then paired those findings with a change impact analysis focused on shifts in roles and responsibilities. A change champion network that met monthly carried the findings into each phase of the rollout.

Because the engagement was phased to align with other implementation activities, readiness work informed the training strategy and communications plan as the project progressed.

Read the full manufacturing change management case study.

How to Address Change Readiness Gaps

A useful test for any readiness finding is whether it changes something in the project plan. Every gap should be routed into one of the four decision categories below:

Sequencing Decisions

Sequencing decisions determine when each department meets the change. A distribution center with a heavy peak season may need its cutover scheduled for a slower quarter, while a finance team facing conversion during year-end close may need its go-live moved to the following month.

Phasing by site or business unit also allows the best-prepared departments to go first, which gives later waves a proven model and a group of experienced peers to learn from.

Staffing Decisions

Capacity gaps require a staffing response. Backfilling employees during ERP implementation is often the most direct way to protect both the project and daily operations. Backfill can mean hiring temporary staff for routine transactional work or temporarily elevating an internal analyst to cover a supervisor's daily duties.

Our previous post about why ERP implementation risk starts with team capacity covers the planning side of this decision in more depth.

Process Remediation Decisions

Where the assessment finds undocumented or inconsistent processes, remediation should begin before design workshops start.

For plants moving onto new manufacturing ERP software, that might mean replacing informal practices, such as manually recording scrap at the end of a shift, with a documented standard that employees understand well before go-live.

Employee Engagement Decisions

Engagement gaps call for targeted communication that reaches each department through the managers its employees already trust. A change champion network gives every site a named contact who can relay concerns upward and explain project decisions in operational terms. Pulse surveys at key milestones can then measure whether confidence is improving before training begins.

Expert Insight

Our organizational change management team has found that readiness findings drive results only when each gap has a named owner and a due date inside the master project schedule. When findings live in a separate document, they lose priority the moment the first milestone slips. This is why our organizational change management consultants often build readiness actions directly into the implementation plan, depending on the scope of the engagement.

Building a Change Readiness Action Plan Before Kickoff

The following steps turn readiness findings into a change readiness action plan that leadership can track alongside budget and schedule.

1. Rank Every Finding by Business Impact

Score each gap by its potential effect on operations so that executive attention goes first to the findings that carry real financial exposure.

2. Assign an Owner and a Decision Deadline

Each finding needs one accountable leader who will decide how it is resolved, and that decision should carry a date that precedes the project phase it affects. For example, a capacity gap in finance must be resolved before finance design workshops begin.

3. Free Up Time Before Asking for It

Ask department leaders to identify how each person's daily responsibilities will be covered before their strongest people are assigned to the core team. Coverage might come through delegation, backfill, or an adjusted timeline. In terms of backfilling employees during ERP implementation, we advise clients to have replacements start several weeks early so that knowledge transfer is complete before project demands peak.

4. Write Readiness Actions Into the Project Plan

Readiness actions belong in the master schedule with the same visibility as configuration and testing tasks. When the steering committee reviews project status, it should see readiness progress in the same report. This keeps the findings in front of the leaders who have the authority to act on them.

5. Reassess Readiness at Key Phase Gates and Milestones

Readiness shifts as the project moves forward. A department that felt confident during design may lose confidence once testing reveals how much its daily work will change. A short readiness check at key phase gates or other major milestones shows whether the action plan is working and where it needs adjustment.

Follow-up readiness checks are especially valuable for organizations deploying manufacturing ERP systems across multiple plants. For example, they can reveal when a plant running three shifts has fallen behind its sister sites, even when every plant started from the same baseline.

Learn More About Change Readiness Action Planning

Readiness findings earn their value only when they impact how a project is managed. Organizations that convert each gap into a decision with an owner protect both the implementation and the business that has to keep running while it happens.

Panorama's independent ERP consulting services help organizations translate readiness assessments into implementation plans their teams can sustain. Contact us below to learn more.

FAQs About Addressing Change Readiness Gaps

What is the first step in deciding how to address change readiness gaps?
The first step is ranking each finding by its operational impact and assigning one accountable owner to it. From there, each gap should become a specific project decision with a deadline that precedes the phase it affects, which keeps the resolution visible in the master schedule.
What should a change readiness action plan include?
A change readiness action plan should list each finding alongside the decision it requires and the leader who owns that decision. It should also include due dates tied to project milestones and a method for reassessing readiness at key phase gates or other major milestones, because the gaps that matter most often shift once testing begins.
When is backfilling employees during ERP implementation worth the investment?
When a process owner or subject matter expert will spend a substantial share of their time on the project during design and testing, making that time available is nonnegotiable. Backfill is worth funding when it is the best way to free up the required time, but other options include delegation, new hires, consultant support, or a revised timeline. The cost of temporary staff is usually small compared with the cost of a delayed go-live, particularly when that delay extends the implementation partner's contract and postpones expected benefits.
Should an organization delay kickoff if readiness gaps are significant?
A short delay is reasonable when critical process owners cannot be named or when another major initiative will consume the same people during design. In many cases, phasing the rollout or changing the order in which departments go live addresses the gap without moving the overall timeline. This preserves momentum while giving less-ready teams more preparation time.
How can leaders keep employees engaged while they continue running the business?
Engagement improves when employees hear about the project from their own managers and see their concerns reflected in project decisions. Change champions at each site help relay questions upward, and designated training time shows employees that leadership understands the pressure of learning a new system while meeting daily operational targets.

Explore All Categories

Resource Center

2027 top erp report

 

2027 top scm systems

About the author

Panorama Consulting Group is an independent, niche consulting firm specializing in business transformation and ERP system implementations for mid- to large-sized private- and public-sector organizations worldwide. One-hundred percent technology agnostic and independent of vendor affiliation, Panorama offers a phased, top-down strategic alignment approach and a bottom-up tactical approach, enabling each client to achieve its unique business transformation objectives by transforming its people, processes, technology, and data.

Avatar photo