Why Change Initiatives Fail and How the Lippitt-Knoster Model Helps Leaders Succeed
Most change efforts do not fail because people dislike progress. They fail because the work of change is treated as an announcement instead of a system.
A leader shares a new direction. A slide deck explains the benefits. Teams nod along. Then the gaps appear. People are unsure what the change really means. Managers interpret the plan in different ways. Training arrives too late. Tools do not match expectations. Rewards still favor the old behavior. Three months later, leaders wonder why nothing has stuck.
This pattern is common because organizational change is complex. It involves priorities, habits, roles, budgets, skills, trust, timing, and pressure. A good idea can collapse if even one of those parts is missing.
The Lippitt-Knoster Model helps leaders see change as a set of connected conditions. It is simple enough to remember, but practical enough to diagnose why a change effort is stuck. The model says successful change requires five core components:
Vision
Skills
Incentives
Resources
Action plan
When one piece is weak or absent, people experience a predictable problem. Confusion, anxiety, resistance, frustration, or false starts are not random. They are signals.
Why Change Initiatives Fails So Often
Change usually starts with a business need. Costs are too high. Customers expect faster service. Technology has moved on. A merger changes the operating model. A new law forces a new process. The reason may be sound, but the plan often skips the human and operational work needed to make change real.
Here are the most common failure points.
Leaders mistake communication for alignment
Many organizations believe they have aligned people because they have communicated the change. Those are not the same thing.
Communication means people heard the message. Alignment means people understand the direction, believe the reason is credible, know their role, and can make decisions that match the new path.
A company might announce a shift toward customer self-service. The customer support team hears one thing. Product hears another. Finance focuses on cost savings. Sales worries clients will feel neglected. Without shared meaning, each function acts on its own version of the change.
That creates drift. The change does not fail in one dramatic moment. It weakens through small, inconsistent decisions.
The people doing the work are brought in too late
Change designed far from the day-to-day work often looks clean on paper and messy in practice.
Frontline teams know where systems break, where customers get confused, where handoffs slow down, and where old habits protect quality. If leaders do not involve them early, the plan can miss basic operating realities.
This does not mean every decision needs a committee. It means leaders need real feedback before a rollout, not only after employees start raising concerns.
The organization rewards the old behavior
People follow what the system rewards.
If leaders ask for collaboration but promote individual heroes, collaboration will fade. If they ask managers to coach employees but measure only short-term output, coaching will lose. If they ask teams to adopt a new platform but praise speed above accuracy, people will create workarounds.
Resistance is not always a mindset problem. Sometimes it is a rational response to the incentives in place.
Training is treated as an event
A single training session rarely changes behavior. People need practice, coaching, reference materials, feedback, and time to build confidence.
This is especially true when the change affects judgment, not just tasks. A new customer service philosophy, agile working model, safety practice, or performance management process requires repeated use. People need to learn what good looks like in real situations.
When skills lag behind expectations, anxiety grows. Some employees hide their uncertainty. Others push back. Many wait for the change to pass.
Leaders underfund the transition
Change costs time, attention, energy, and often money. Organizations may budget for software, consultants, or launch events, but forget the capacity needed to absorb the change.
People still have their regular jobs. Managers still face deadlines. Teams still serve customers. If the change is added on top of full workloads, frustration builds fast.
Under-resourced change creates a painful message: “This is critical, but we are not giving you what you need to do it.”
The plan lacks rhythm and ownership
A vague plan can create motion without progress. People attend sessions, form workgroups, discuss risks, and produce updates. Yet no one knows what must happen next, who owns it, or how success will be judged.
A strong action plan gives the change a rhythm. It defines milestones, decisions, owners, measures, and feedback loops. Without that rhythm, change efforts produce false starts. Teams begin, stop, restart, and lose trust.
How the Lippitt-Knoster Model Explains What Goes Wrong
The Lippitt-Knoster Model is often used to explain why complex change succeeds or stalls. Different versions of the model exist, and some include consensus as a separate element. The version many leaders use focuses on five practical requirements: vision, skills, incentives, resources, and an action plan.
The power of the model comes from its diagnostic value. It does not simply say, “Manage change better.” It helps leaders ask, “Which condition is missing?”
Component | What it gives people | When it is missing |
Vision | A clear picture of the future and the reason for change | Confusion |
Skills | The ability and confidence to work in the new way | Anxiety |
Incentives | A reason to support the change and keep using it | Resistance |
Resources | The time, tools, money, and support needed to change | Frustration |
Action plan | A practical path with ownership and timing | False starts |
This simple map helps leaders move from blame to diagnosis. If people seem resistant, the answer may not be another speech. The issue may be misaligned incentives. If teams seem slow, they may not be lazy. They may lack resources or a clear plan.
Vision prevents confusion
Vision answers the questions people ask first, even if they do not say them out loud.
Why are we changing?
What will be different?
What will stay the same?
What does success look like?
How will this affect customers, employees, and partners?
A good vision is not a slogan. It is specific enough to guide tradeoffs.
For example, “become more digital” is too vague. A clearer version might be, “Customers should be able to complete routine service requests online without calling support, while our support team focuses on complex needs that require human judgment.”
That description tells teams what to build, what to stop doing, and what not to sacrifice.
Skills reduce anxiety
People cannot commit fully to a change they do not feel able to perform.
Skills include technical knowledge, process knowledge, decision-making ability, and confidence. A warehouse team using a new inventory system needs hands-on practice. A manager moving from annual reviews to ongoing coaching needs conversation skills. A sales team selling a new offering needs product knowledge and new discovery questions.
Training should match the work. Short demos may help introduce a tool, but complex behavior needs practice and feedback.
Incentives reduce resistance
Incentives are not only bonuses. They include recognition, career impact, performance measures, peer approval, workflow ease, and personal meaning.
People ask a fair question during change: “What happens if I do this?”
If the answer is unclear, resistance grows. If the answer is “more work, more risk, and no recognition,” resistance is predictable.
Effective incentives make the desired behavior easier to choose. They also remove rewards for the old behavior when those rewards conflict with the change.
Resources reduce frustration
Resources include budget, tools, staffing, data, time, coaching, and decision access. They also include leadership attention.
A team can understand the vision, learn the skills, and care about the outcome, but still fail if they lack what the work requires. If a new process depends on clean data and the data is incomplete, frustration will rise. If a new service model requires more time with customers but staffing levels stay the same, teams will struggle.
Resource gaps often show up as cynicism. People stop believing leaders are serious because the support does not match the message.
An action plan prevents false starts
An action plan turns intent into movement. It should make the change visible and manageable.
A useful action plan includes:
Clear phases
Named owners
Near-term milestones
Decision points
Measures of progress
Feedback channels
Risks and responses
The plan should not be so rigid that it ignores learning. Complex change always brings surprises. The best plans create structure while allowing adjustment.
What Real Change Efforts Show Us
Real-world examples make the model easier to see. No public example is perfectly simple, and many factors shape success or failure. Still, well-known cases show how the pieces of the model work together.
Microsoft’s shift under Satya Nadella showed the value of vision and incentives
When Satya Nadella became CEO of Microsoft in 2014, the company was widely seen as needing a cultural and strategic reset. Microsoft had strong products and deep technical talent, but it also faced pressure from cloud computing, mobile devices, and faster-moving competitors.
The change that followed was not only about products. It involved a clearer direction around cloud services, a stronger focus on customers, and a cultural message often described through the idea of a growth mindset.
The Lippitt-Knoster lens helps explain why the change gained traction.
Vision was clearer. Microsoft placed major emphasis on cloud computing and subscription-based services. Teams had a stronger sense of where the company was going.
Skills were built and redirected. Engineers, sellers, and partners had to grow their ability to work with cloud platforms and new service models.
Incentives shifted. The company had to support collaboration across product groups and reward success in newer business areas, not only protect older revenue streams.
Resources were serious. Microsoft committed major investment, leadership attention, and talent to cloud growth.
Action plans became visible through products and business moves. Azure, Microsoft 365, and broader platform decisions showed that the direction was not only talk.
The lesson is not that every company should copy Microsoft. The lesson is that major change needs more than a charismatic message. It needs the system around the message to change too.
Netflix’s move from DVDs to streaming showed the power of acting before comfort disappears
Netflix began as a DVD-by-mail company, then moved aggressively into streaming. That shift required technology, licensing, customer education, new internal capabilities, and a willingness to reduce dependence on the original model.
This was not a smooth or risk-free path. The company made decisions along the way that drew criticism, including pricing and service changes that frustrated customers. Yet the broader change toward streaming proved decisive.
The Lippitt-Knoster Model highlights several strengths.
The vision was tied to how customers would consume entertainment in the future. The skills required new technical and content capabilities. The resources included investment in streaming infrastructure and, later, original content. The incentives aligned with gaining and keeping subscribers in a new model. The action plan unfolded over time through product changes, platform expansion, and content strategy.
Netflix shows that successful change does not require perfect execution. It requires enough clarity, capability, commitment, support, and sequencing to keep moving through discomfort.
Kodak showed what happens when vision and incentives conflict
Kodak is often used as a cautionary example in business change. The company had deep knowledge of photography and was aware of digital imaging long before digital cameras reshaped the market. Yet it struggled to shift its business away from film at the pace needed.
The story is more complex than “Kodak ignored digital.” The company explored digital technology, but its profitable film business created a hard conflict. Moving too quickly toward digital threatened the economics that had made Kodak successful.
Using the model, the problem becomes clearer.
There was not enough shared vision for a future where digital replaced the core profit engine. The skills existed in parts of the company, but they did not fully translate into a new operating model at scale. The incentives favored protecting film revenue. The resources and attention needed for a full transition competed with the existing business. The action plan did not overcome the pull of the old model.
Kodak’s case shows why incentives matter so much. A company can see the future and still fail to move toward it if the present rewards staying put.
J.C. Penney’s attempted retail reset showed the risk of moving without customer and employee alignment
In the early 2010s, J.C. Penney attempted a major change in its pricing and store strategy. The company moved away from its familiar coupon-heavy approach toward simpler pricing and a different shopping experience. The change was bold, but customers did not respond as hoped, and the retailer later reversed key parts of the strategy.
Through the Lippitt-Knoster lens, several issues stand out.
The vision may have made sense to leaders who wanted to refresh the brand, but many customers valued the old coupon experience. Store teams also had to manage shopper confusion. The incentives for customers changed abruptly. What once felt like a deal became less obvious. The action plan moved faster than customer habits could adjust.
This case highlights a point leaders sometimes miss: customers are part of the change system too. A new strategy must account for how customers understand value, not only how executives define it.
A hospital system adopting a new electronic health record shows why skills and resources matter
Consider a common example from healthcare: a hospital system adopts a new electronic health record. The goal is better documentation, safer handoffs, and easier access to patient information.
The vision may be sound. Yet the rollout can struggle if clinicians receive limited training, templates do not match the real flow of care, or staffing does not account for the temporary slowdown that comes with learning a new system.
In a better-managed rollout, leaders involve clinicians early, test workflows, provide role-based training, offer support during go-live, and adjust based on feedback. They also protect patient care by planning for the productivity dip.
The difference between success and failure is not whether the software is “good.” It is whether the change conditions are in place.
How leaders can apply the model before change stalls
The best time to use the Lippitt-Knoster Model is before rollout. The second-best time is when the warning signs appear.
Leaders can use it as a planning tool, a diagnostic tool, and a conversation guide.
Start with a plain-language change statement
A change statement should be short, specific, and useful. It should explain the shift without buzzwords.
A strong change statement includes:
What is changing
Why it is changing
Who will be affected
What outcome matters most
What will remain stable
For example:
“We are moving routine customer support requests to a self-service portal so customers can get faster answers and our support team can spend more time on complex cases. Phone support will remain available for urgent and high-risk issues.”
That statement gives people something concrete to respond to. It also exposes questions early.
Map the five components before launch
Use the model as a readiness check. Bring together a small group that understands strategy, operations, people, customers, and technology. Ask direct questions.
Vision
Can people explain the change in simple terms?
Do managers describe it the same way?
Have we defined what success looks like?
Have we named what will not change?
Skills
What new behaviors does this require?
Who needs training, practice, or coaching?
What will be hardest to learn?
How will we support people after the first training?
Incentives
What current rewards support the old way?
How will goals, recognition, and measures change?
What makes the new behavior worth the effort?
What risks do people take if they adopt the change early?
Resources
Do teams have enough time and staffing?
Are the tools ready?
Is the data reliable?
Who can remove barriers quickly?
Action plan
What happens first, next, and later?
Who owns each part?
What decisions are still open?
How will we track progress and adjust?
A readiness review should not become a ritual where everyone says green to avoid conflict. Its value comes from honest tension. If a component is weak, name it before the rollout exposes it.
Listen for the symptom, then trace it to the missing part
When change begins, leaders often hear complaints. The model helps translate those complaints into useful signals.
What people say | What may be missing |
“I do not understand why we are doing this.” | Vision |
“I am not sure I can do this well.” | Skills |
“This creates more risk for me.” | Incentives |
“We do not have what we need.” | Resources |
“The plan keeps changing.” | Action plan |
This does not mean every concern is valid in the same way. It means every concern deserves diagnosis before response.
If people lack vision, explain and clarify. If they lack skills, teach and coach. If incentives are misaligned, change the measurement system. If resources are thin, adjust scope or add support. If the plan is unclear, tighten ownership and timing.
Build manager capability early
Managers carry much of the burden in organizational change. They translate the strategy, answer questions, handle emotion, manage workload, and keep performance steady.
Yet managers are often briefed only shortly before everyone else. That leaves them underprepared.
Give managers time to understand the change before they have to lead others through it. Equip them with:
A clear explanation of the change
Expected questions and honest answers
Team discussion guides
Escalation paths for issues
Coaching on how to handle resistance
Permission to raise concerns without being labeled negative
Managers do not need scripts for every conversation. They need enough clarity and support to lead with confidence.
Pilot the change where learning will be fastest
A pilot can reduce risk, but only if it is designed for learning. Do not choose only the easiest team or the most supportive location. Pick a setting that reflects real complexity while still being manageable.
During a pilot, look for friction in the five areas.
Are people interpreting the vision correctly? Do they have the skills? Are old incentives pulling them back? Are tools and staffing enough? Is the plan clear at the task level?
Use the pilot to adjust the change before scaling it. A pilot that proves leaders were right is less useful than a pilot that makes the plan better.
Make incentives visible and fair
If the change asks people to behave differently, the organization must make that difference matter.
That may mean updating performance goals, recognizing early adopters, changing promotion criteria, revising team scorecards, or removing penalties that punish learning time.
Incentives should be fair. If only some teams receive resources or relief while others absorb the same change with no support, trust will suffer.
Also watch for hidden incentives. A leader may publicly support the change but privately praise managers who preserve old metrics at any cost. Employees notice that gap quickly.
Treat resources as a leadership decision, not an afterthought
A common leadership mistake is to approve the change but not the capacity required to carry it out.
Good leaders ask, “What must we stop, slow, or fund so this can succeed?”
That question matters because people cannot give full attention to unlimited priorities. If every change is urgent, teams will protect the work that feels safest or most measured.
Resources do not always require large budgets. Sometimes teams need a temporary reduction in reporting, faster access to decisions, better job aids, or a few hours each week for practice. The key is to match support to the real work.
Keep the action plan alive
An action plan should not disappear after kickoff. Review it often. Update it when facts change. Use it to keep the organization honest.
A living action plan answers:
What have we completed?
What did we learn?
What is blocked?
What decisions do we need?
What changes in the next phase?
What should we stop doing?
This rhythm turns change from a campaign into a managed effort.
The Warning Signs Leaders Should Not Ignore
Change trouble often appears early. Leaders can catch it if they pay attention to behavior, not only status reports.
Watch for these signs.
People can repeat the slogan but not explain the tradeoffs
This means the vision is too shallow. People may know the words but not how to use them.
Ask teams to describe real choices. What should they prioritize now? What should they stop doing? What customer problem should the change solve? If answers vary widely, the vision needs more work.
Training attendance is high but confidence is low
Attendance proves people showed up. It does not prove they can perform.
Check whether people can use the new process in realistic situations. Offer practice environments, peer support, and coaching. Ask managers what questions keep coming up.
Teams comply publicly and work around privately
Workarounds are valuable clues. They may show that the new process is too slow, tools are not ready, incentives conflict, or people do not trust the change.
Do not treat every workaround as defiance. Study it. The workaround may point to the fix that makes adoption possible.
The same blockers appear in every update
A blocker that repeats is not a status item. It is a leadership issue.
If teams keep saying they lack data, access, decisions, or staffing, the change plan needs adjustment. Repeated blockers drain belief because people see that reporting problems does not lead to action.
Early success depends on a few heroic people
Heroes can help a change get started, but they cannot carry it forever. If progress depends on a small group working nights, manually fixing data, or personally persuading every stakeholder, the system is not ready.
A sustainable change should become easier over time because the model supports it. Vision, skills, incentives, resources, and action plan must move from special effort to normal practice.
Practical Tips for Using the Model Well
The Lippitt-Knoster Model is simple, but using it well takes discipline. These practices help leaders turn it into better decisions.
Use it at three moments
Use the model before launch, during rollout, and after adoption begins.
Before launch, it helps test readiness. During rollout, it helps diagnose resistance and delays. After adoption begins, it helps keep the change from fading when attention shifts.
Ask different groups the same questions
Executives, managers, frontline employees, and customers may see different gaps. Ask each group about the five components, then compare the answers.
If executives rate vision as clear but employees do not, communication has not become understanding. If leaders believe resources are adequate but teams report overload, the plan may be unrealistic.
Make the invisible parts visible
Skills, incentives, and resources are often less visible than the launch message. Put them on the agenda.
For each component, assign an owner. Someone should be accountable for training quality. Someone should watch incentive alignment. Someone should track resource issues. Someone should maintain the action plan.
Avoid blaming resistance too quickly
Resistance is information. It may reflect fear, fatigue, poor design, lack of trust, or competing priorities. Some resistance is also valid criticism.
Leaders should not accept every objection as a veto. They should ask what the resistance reveals. If the model points to a missing component, fix the condition rather than arguing harder.
Communicate in layers
People do not absorb change all at once. Communicate in layers.
Start with the reason and direction. Then explain what changes for each group. Then provide the timing, support, and measures. Repeat the message through managers, team conversations, written guides, and live forums.
Repetition is not a weakness. It is how understanding forms across a complex organization.
Measure adoption, not just activity
Activity measures are easy to collect. Training completion, meeting attendance, and project milestones matter, but they do not prove the change is working.
Look for adoption measures too.
Are people using the new process correctly?
Are customers experiencing the intended benefit?
Are managers coaching to the new expectations?
Are old reports, tools, or rituals being retired?
Are outcomes moving in the right direction?
Measurement should help learning, not just inspection.
Close the loop when feedback changes the plan
When people give feedback and leaders act on it, say so. Name what changed and why.
This builds trust. It shows that participation matters and that the action plan is real. Silence creates the opposite effect. People assume their feedback vanished.
Structured Change is Slower At First and Faster Later
Unstructured change can feel faster in the beginning. Leaders announce the direction, set a deadline, and push for movement. The organization looks busy.
Then the hidden gaps appear. Confusion slows decisions. Anxiety slows adoption. Resistance drains energy. Frustration lowers trust. False starts waste time.
Structured change can feel slower at first because leaders do the preparation. They clarify the vision, build skills, align incentives, provide resources, and create an action plan. That work takes time, but it prevents avoidable rework.
The Lippitt-Knoster Model helps leaders succeed because it turns a vague challenge into a practical checklist of conditions. It reminds leaders that change is not only a message to send. It is a system to build.
When a change effort starts to struggle, ask five questions before blaming the people involved:
Is the vision clear?
Do people have the skills?
Are incentives aligned?
Are resources adequate?
Is there a real action plan?
The answer will usually point to the next right move. The organizations that handle change well are not the ones that avoid discomfort. They are the ones that give people enough clarity, ability, reason, support, and structure to move through it.
