Customize this training

Get a certificate — $12

Leading Change and Continuous Improvement for Managers

Leading Change and Continuous Improvement for Managers

A premium course for managers who must make change happen in their team: why change efforts fail, planning a change with Kotter’s steps, the people side of change with Prosci’s ADKAR model, continuous improvement with PDCA and the Toyota Production System, and making changes stick without change fatigue. It draws on Kotter’s research, Prosci, CIPD guidance and ISO 9001. Not an accredited qualification.

What you will learn

  • Explain the common reasons change efforts fail and the manager’s role in change.
  • Plan a team-level change using Kotter’s steps and a stakeholder map.
  • Support individuals through change using ADKAR and treat resistance as information.
  • Run small improvement cycles with PDCA and lean principles.
  • Make changes stick and avoid change fatigue.

Modules

  1. Why change fails, and the manager’s role
  2. Planning a change
  3. The people side of change
  4. Continuous improvement with PDCA
  5. Making change stick

Course facts

Estimated study time
about 1.5 hours
Final assessment
10 questions · Pass mark 80%
Available in
English, Français, العربية
Price
Free. Optional verifiable certificate: $12
Last updated
Published by
AMAADOR ACADEMY

Who this course is for

Line and middle managers, team leaders and improvement leads who implement changes decided above them or start their own.

Prerequisites

No formal prerequisite.

Course content

1. Why change fails, and the manager’s role

In his 1995 Harvard Business Review article “Leading Change: Why Transformation Efforts Fail”, John Kotter described errors he had seen in many organisations: not establishing a great enough sense of urgency, not creating a powerful guiding coalition, lacking a vision, under-communicating the vision, not removing obstacles, not planning for and creating short-term wins, declaring victory too soon and not anchoring changes in the culture. These errors still explain many failed reorganisations, system launches and process changes.

Middle and line managers sit where change succeeds or fails. Senior leaders decide the direction; managers translate it into what changes for each person on Monday morning, carry concerns back up, and adjust the detail so the change works in practice. If managers do not understand or believe in a change, their teams quickly notice.

Your first job is therefore to understand the change yourself: what is changing, why, what will not change, and what is still open. Ask your own manager the questions your team will ask you. Be honest about what you do not know yet, and avoid passing on messages you cannot explain. A manager who says “I don’t know yet, and I will tell you by Friday” keeps more trust than one who guesses.

Key point: Understand the change yourself first, then translate it into what changes for each person.

2. Planning a change

Kotter Inc. now presents eight steps: create a sense of urgency; build a guiding coalition; form a strategic vision; enlist a volunteer army; enable action by removing barriers; generate short-term wins; sustain acceleration; and institute change. At team level these become practical questions: Why must we change now? Who, besides me, will help lead it? What will good look like? Who is keen to help? What is in the way? What can we show working within weeks? How will we keep going? How do we make it the normal way of working?

Map your stakeholders. List the people and groups affected, rate each on how much the change affects them and how much influence they have, and note their current view. Involve high-influence, high-impact people early — often the experienced team members others listen to. Many changes fail not because of open opposition but because people with informal influence were never asked.

Plan communication as a series of conversations, not a single announcement. Explain the reasons, what changes and what stays the same, and what support people will get. Repeat key messages through several channels, and create ways for questions to come back. Kotter’s research found that leaders typically under-communicate their vision by a large factor; managers can close much of that gap in team meetings and one-to-ones.

Key point: Answer the eight questions for your team, map stakeholders, and plan many conversations, not one announcement.

3. The people side of change

Organisations change only when individuals change. Prosci’s ADKAR model describes five outcomes a person needs: Awareness of the need for change, Desire to take part, Knowledge of how to change, Ability to apply new skills and behaviours, and Reinforcement to sustain the change. The model is useful for diagnosis: if someone is struggling, ask which element is missing. Training (knowledge) will not help a person who still does not see why the change is needed (awareness).

Resistance is normal and often useful. People may resist because they fear losing status, skills or income, because the change adds work, because previous changes failed, or because they see a real flaw in the plan. Treat resistance as information: ask what worries people and what would make the change work for them. Some concerns will improve the plan; others need clear answers and support.

The CIPD notes that involving employees in change, consulting properly and paying attention to well-being improve outcomes. Where changes affect jobs, hours or contracts, there may be legal duties to consult employees or their representatives before decisions are final; check with HR. Simple practices help everyone: explain early, involve people in designing the detail, give time and training to learn, and recognise effort during the dip in performance that usually follows a change.

Key point: Diagnose the missing ADKAR element, listen to resistance, and involve people in the detail.

4. Continuous improvement with PDCA

Not all change is a big project. Continuous improvement means many small changes made by the people who do the work. ISO 9001 requires organisations to continually improve the suitability, adequacy and effectiveness of their quality management system, and the Plan–Do–Check–Act cycle, associated with Walter Shewhart and W. Edwards Deming, is the standard method: plan a change based on a clear problem and a prediction, do it on a small scale, check the result against the prediction, and act — adopt, adapt or abandon.

The Toyota Production System, which Toyota describes as built on two pillars — jidoka (stopping to fix abnormalities so defects are not passed on) and just-in-time (making only what is needed, when it is needed, in the amount needed) — made kaizen, or continuous improvement by everyone, part of daily work. Its lessons for any manager are practical: make problems visible, go and see the work where it happens, ask why several times to find causes, and treat each improvement as an experiment.

Once a change works, standardise it: update the procedure, train people and check it is followed. Standard work is not bureaucracy; it is the baseline that makes the next improvement possible. Without it, improvements fade as people return to old habits or as new staff learn the old way.

Key point: Test small with PDCA, go and see, ask why, and standardise what works.

5. Making change stick

Kotter warned against declaring victory too soon: a new system going live, or a first good month, is not the end. Changes stick when they are reinforced — the R in ADKAR — through measures that show the new way works, recognition of people who use it, removal of the old option where possible, and managers who keep asking about it. Build checks into routines: include the new measure in your monthly review, and audit the new process after three and six months.

Watch the risk side of change. Changes to staffing, shift patterns, equipment or procedures can introduce new hazards or remove safeguards that were never written down. Many organisations use a management-of-change review for this reason: before implementing, ask what could go wrong, who needs training, and which controls must stay in place during the transition.

Too many changes at once cause change fatigue: people disengage, mistakes rise and good initiatives fail along with bad ones. The CIPD recommends attention to workload and well-being during change. As a manager, keep a list of all changes landing on your team, sequence them where you can, stop or delay low-value ones, and be honest with your own manager about capacity.

Key point: Reinforce and measure after go-live, review the risks of change, and protect the team from too many changes at once.

The full lesson, case studies, scenarios and templates continue in the interactive course on this page.

Sources and references

Management education only, not an accredited qualification and not a Prosci or Kotter certification. Changes to jobs, hours or working conditions may require consultation with staff or their representatives under local law; take HR advice. Models are summarised from the public sources cited.

All courses · Leadership & Professional Skills