Ezee Fiber

Making Readiness Part of the Change Process

A new process is scheduled to launch in two weeks. The decisions are made, the workflow is set and communications are nearly ready. Then someone asks do we need training?

Most Learning and Development (L&D) teams have lived some version of this, and so have most project leaders. It is usually not intentional. Projects move fast, teams focus on their own deliverables and the people side of a change often lands last.

Leading L&D at Ezee Fiber, I support sales, contact center, field tech and other operations teams. Each experiences change differently, but the readiness question is the same.

The problem is not that L&D needs more time to build a course. By then, many decisions that shape employee readiness have already been made. Training may happen downstream, but readiness starts upstream.

Start With Readiness, Not Training

When a business introduces a new product, system, process, or policy, the first question is usually, what training do we need? When a new initiative comes to me? I start somewhere else: what will people need to do differently on day one, and how will we see it?

Employees may need new knowledge, but they may also need to use a new system, explain something differently to a customer, make a different decision or practice before performing. Training might be part of the answer, but it is rarely all of it.

This is where information gets confused with readiness. An email, a slide deck, a job aid or an eLearning course can share information. None of them tells you whether someone can perform on day one.

Information tells people what changed. Training helps them learn it. Readiness means they can do it.

Give People a Purpose, a Process and a Payoff

Early in my career, a leader coached me to think about change through three questions: why are we doing this? How do we execute it? What does it look like when we get it right? I later saw the same idea framed as purpose, process and payoff.

Purpose explains why something is changing, not just that it is.

“Information only tells people what changed. Training helps them learn it. Readiness means they can do it.”

Process shows what people are expected to do and what good performance looks like.

Payoff connects the change to something tangible that matters, like a better customer experience, fewer errors, more sales, less rework or an easier job.

Payoff is the most often skipped piece, and frequently what separates remembering information from applying it. For the employee, it answers the question they are really asking: what's in it for me?

These questions are hard to answer when training is the last box checked before go-live, and much easier when L&D joins the conversation while the change is still taking shape.

Readiness Is Shared Ownership

Earlier involvement does not mean L&D owns the project or employee performance. It means L&D brings a different lens. While other teams focus on the technology, process or timeline, L&D focuses on the people and the behaviors the change depends on.

L&D can build knowledge, create opportunities to practice and provide tools that support performance. But after training, employees go back to their teams. Their managers and leaders determine whether the new behavior is coached, reinforced and expected.

The business owns the change. L&D helps prepare people for it. Leaders reinforce it. Employees put it into practice. When one piece is missing, even well-designed training struggles.

Move the Conversation Upstream

Most changes do not come with months of lead time, so even a short early conversation matters. I have found the most useful ones happen before anyone uses the word training.

Start with a simple trigger: if a change affects what employees need to know, say, do or demonstrate, bring L&D in early enough to assess the impact. Add two questions to project kickoffs: what will our people need to do differently, and how will we know they can? How will we keep that behavior consistent across teams and business groups? Then define readiness before go-live by asking employees to demonstrate the new behavior, not just complete a course.

Every level of leadership plays a part. Executives can make readiness a standard go-live question alongside system readiness. Project leaders can bring L&D in while the scope is still being defined. Frontline managers matter most after launch, when the new behavior either gets coached or fades. L&D leaders should show up asking about performance, not offering courses.

None of this requires L&D to be the approver of every change. It requires visibility early enough to have a conversation and decide, case by case, what support people actually need.

That shift moves L&D from receiving requests at the end to helping the organization prepare its people for what comes next.

The goal is not to deliver training. The goal is to make sure people are ready to perform.