LevelUpWith

Explore / Leading Change: The People Side of Transformation / Lesson 2

Lesson 2: Building the Case for Change

Learn to write a clear, honest case for change that explains why the change is needed, why now, and what happens if nothing changes.

Free to read, no account needed. Part of Leading Change: The People Side of Transformation.

By the end of this level you'll be able to

  • Write a case for change that covers the problem, the vision, the risk of standing still and what it means for people
  • Change the emphasis of the case for different audiences without changing the facts
  • Spot a weak case for change, such as one that is vague, focused only on the solution or overstated

Why a Case for Change Matters

In Level 1 you saw that many change efforts fail long before go-live. A common reason is that people never understood why the change was happening. A case for change fixes this. It is a short, honest explanation that people can repeat in their own words.

Think of it as a diagnosis given before treatment. A patient is far more likely to follow a treatment plan when the doctor has explained what is wrong, why it needs treating now and what happens if it is left alone. Your team needs the same thing.

John Kotter's 1995 Harvard Business Review article "Leading Change: Why Transformation Efforts Fail" reported that well over half of the companies he observed failed at the first hurdle: they did not create enough sense of urgency. A clear case for change is how you build that urgency honestly.

Step 1: Write the Five Parts of the Case

A strong case answers five questions. Draft one or two sentences for each.

  1. The problem. What is going wrong today? Use evidence: numbers, incidents, customer feedback.
  2. Why now. What has changed that makes this urgent? For example, a contract ending, a new regulation, rising costs or a competitor moving.
  3. The risk of standing still. What happens if nothing changes? Be specific and realistic.
  4. The vision. What will be better afterwards? Describe the outcome, not just the tool.
  5. What it means for people. How will daily work change? What will people gain, what will they lose and what support will they get?

DO: Write each part in plain language. If you cannot fill in a part, you have found a gap in your own thinking. Fix it before you communicate.

Worked Example: A CRM Roll-out

Priya manages a 25-person sales team that tracks customers in shared spreadsheets. She is introducing a CRM (customer relationship management) system.

  • Problem: "Last quarter, 14 customer enquiries were lost or answered late because records were split across six spreadsheets."
  • Why now: "Our spreadsheet tool's support contract ends in March, and two key clients have complained about slow responses."
  • Risk of standing still: "We risk losing those clients, and every new joiner adds another spreadsheet to keep track of."
  • Vision: "One shared record for every customer, so anyone can pick up an enquiry within a day."
  • What it means for people: "You will log calls in the CRM rather than in spreadsheets. Expect some extra effort for the first month. We will provide training and a help desk, and you will stop spending time chasing other people's files."

Notice that Priya admits the cost (extra effort at first). That honesty builds trust.

Step 2: Adjust the Emphasis for Each Audience

Different groups care about different parts of the same case. Change the emphasis, never the facts.

  • Senior leaders: lead with business risk, cost and client retention.
  • Sales staff: lead with what changes in their day and what they gain, such as less chasing and faster answers.
  • IT team: lead with the end of the support contract and the integration work.
  • Finance: lead with costs avoided and the cost of doing nothing.

DO: For each audience, ask "Which of the five parts matters most to them?" Open with that part. Keep the same numbers and the same honest statement of costs for everyone. If staff hear "no extra work" while leaders hear "a demanding first month", trust collapses once people compare notes.

Also think about the messenger. Research by Prosci, a change management research firm, found that most employees want to hear the business reasons for a change from the CEO or senior leaders. A majority (58%) prefer to hear about the personal impact from their own supervisor. In practice, a senior leader explains the "why" and each manager explains the "what it means for you".

Step 3: Test the Case for Weaknesses

Before you share the case, check it against these common weaknesses.

  • Vague: "We need to modernise and be more agile." There is no evidence and nothing anyone can act on.
  • Solution-only: "We are implementing a new CRM." It names the tool but never explains the problem it solves.
  • Overstated: "If we don't adopt this, the company will close." People will notice an exaggeration and stop believing the rest.
  • No "why now": the problem is real, but nothing explains why it needs fixing this quarter rather than next year.
  • Silent on people: it covers the benefits to the business but not what changes for staff or what support they will get.

DO: Ask someone who will be affected to read your draft and tell it back to you in their own words. If they cannot explain the problem and why it matters now, rewrite it.

A Note on "Burning Platforms"

The "burning platform" metaphor comes from change consultant Daryl Conner. He drew on the 1988 Piper Alpha oil platform disaster in the North Sea, where a worker survived by jumping from the burning rig into the sea. The phrase is often used to mean "create fear to force change". Fear without facts tends to backfire: it is overstatement by another name. Use real evidence about the risk of standing still, and pair it with a credible vision so people have somewhere to move towards.

Key Takeaways

  • A case for change covers five parts: the problem, why now, the risk of standing still, the vision and what it means for people.
  • Support every claim with specific evidence, and be honest about costs.
  • Change the emphasis for each audience, never the facts.
  • Senior leaders are usually best placed to explain the business reasons, and direct managers to explain the personal impact.
  • Watch for weak cases: vague, focused only on the solution, overstated, missing "why now" or silent on people.
  • Test your draft by asking an affected person to explain it back to you.

A 6-question knowledge check follows this lesson in the app, free and without an account.

Keep going: levels 3 and 4 are free

Create a free account to open the next two levels, try the AI tutor, save your progress and pick up where you left off. No card needed.

Next: Level 3, Process Models: Lewin and Kotter.

Create a free account →See the whole course

More like this