LEAP for Transformation and Change
16 practical cards on spotting, planning and leading change, written for team leaders in food, manufacturing and logistics. A free resource from DevelopME.Today.
Change is now the normal state of a production or distribution site. New lines, new customers, new systems, new owners, new rules. Senior managers decide most of it, but the team leader is the person who makes it work on the floor, shift after shift.
These 16 cards cover four things a team leader needs: seeing when change is needed and whether the site is ready, planning the route, bringing people with you through the emotional side of change, and leading in a way that makes the change stick.
Every card follows the LEAP pattern: the idea in one sentence, how it works, a scenario from the shift, one thing to try in under 10 minutes, a warning, and a question for your coach.
A note on the evidence. Most change models come from consulting experience rather than controlled research. Use them as checklists and conversation starters, not as laws. Where a model’s history or evidence is disputed, the card says so.
Seeing the need for change
Good change starts with a clear view of what is wrong and what a change will touch. These five cards cover spotting the triggers for change, testing whether a change has enough energy behind it, and three models for seeing how one change ripples through a whole operation.
Card 1.1: Spotting the need for changeChange should start from a clear reason, and the biggest risk is assuming that what worked last year will keep working.
Practical guidance; not based on a single theory
| Triggers to watch for | Examples on site | |
|---|---|---|
| Inside the business | New technology, new senior managers, mergers, processes that keep failing | A new ERP system; a takeover; the same line stoppage every week |
| Outside the business | Customer demand, competitors, regulation, the economy | A retailer changes its spec; new allergen labelling rules; energy costs double |
- Look at the trend, not the day. Is waste, downtime or overtime slowly rising?
- Ask the floor. Operators often see a problem months before it reaches a report.
- Dig for the cause before choosing the change (see LEAP for Strategy 4.2).
- Compare your best shift with your worst. The gap shows what could change.
A warehouse team leader notices that mis-picks have crept up for three months. Nobody has flagged it because each week looks “about normal”. She plots the numbers, finds the rise started when a new product range arrived, and makes the case for re-slotting the pick faces.
Pick one measure your team tracks. Look at the last three months, not the last week. Is anything slowly getting worse?
Change for its own sake. A new manager’s pet project, with no clear problem behind it, burns goodwill you will need for the changes that matter.
What is your team still doing only because “that’s how we’ve always done it”?
Card 1.2: The Change EquationA change will only move if dissatisfaction with today, a clear picture of tomorrow and practical first steps together outweigh the cost of changing.
David Gleicher (early 1960s), published by Richard Beckhard and Reuben Harris (1977); the D × V × F > R wording comes from Kathleen Dannemiller and Robert Jacobs (1992)
| Letter | Means | Ask the team |
|---|---|---|
| D | Dissatisfaction with how things are now | What frustrates you about the way we do this today? |
| V | Vision of something better | Can you picture how it will work, and what it means for you? |
| F | First steps that are clear and doable | Do you know what we are doing on Monday? |
| R | Resistance, or the personal cost of changing | What will you lose or have to give up? |
The first three are multiplied, not added. If any one is close to zero, the change stalls, however strong the others are. It is a thinking tool, not a sum to score precisely.
A distribution centre brings in hand-held scanners. Everyone hates the paper system (high D) and the trainers are booked (clear F), but nobody has explained how the scanners will make their shift easier (low V). Adoption stalls until the team leader runs a ten-minute demo on the floor.
Think of a change coming to your team. Score D, V and F as low, medium or high. Which one is weakest? That is your first job.
Trying to beat resistance by pushing harder. Often the quicker fix is to reduce the real cost, for example by ending the double running of old and new systems.
Which of D, V or F is weakest in the change you are leading now?
Card 1.3: Leavitt’s DiamondTasks, people, structure and technology are linked, so a change to one always ripples into the other three.
Harold Leavitt (1965)
| Point of the diamond | What it covers | Ripple from a new automated case packer |
|---|---|---|
| Technology | Equipment, systems, software | The case packer itself |
| Tasks | The work that has to be done | Manual packing disappears; new checks and cleaning tasks appear |
| People | Skills, numbers, attitudes | Packers need retraining as operators; some fear for their jobs |
| Structure | Roles, reporting lines, shifts | Fewer people per line; a new technician role; changed rotas |
Before a change goes live, walk round all four points and ask: “If this changes, what else has to change too?”
A bakery installs a new slicer to speed up the line. Nobody updated the cleaning schedule or trained the night shift. Within a week, a hygiene audit fails. A ten-minute diamond check at the planning stage would have caught both.
Take one change coming to your area. Write one consequence for each of the four points.
Treating a change as “just an IT project” or “just a restructure”. The point you ignore is usually the one that causes trouble.
Which point of the diamond do you tend to forget?
Card 1.4: The McKinsey 7-SAn organisation is more than its structure chart: seven connected elements must line up for a change to work.
Robert Waterman, Tom Peters and Julien Phillips (1980), developed with Richard Pascale and Anthony Athos
| Element | At team level, ask | |
|---|---|---|
| Hard | Strategy | What are we trying to achieve? |
| Hard | Structure | Who reports to whom, and who decides? |
| Hard | Systems | Which procedures, reports and tools do we use? |
| Soft | Shared values | What do we really believe matters? (The centre of the model.) |
| Soft | Style | How do leaders actually behave? |
| Soft | Staff | Do we have the right people in the right places? |
| Soft | Skills | What is the team good at, and what is missing? |
The hard elements are easier to change on paper. The soft elements decide whether the change sticks. The model shows where things are out of line; it does not tell you how to fix them.
A site launches a “right first time” quality drive with new checks (systems) and a quality champion on each line (structure). But supervisors still praise output above all else (style). Quality barely moves until leaders change what they praise.
Pick the most recent change on your site. Which of the seven elements did it change, and which did it leave untouched?
Changing only the hard S’s. A new procedure that clashes with how leaders behave will lose.
Where does your own leadership style pull against the change your site wants?
Card 1.5: The Burke-Litwin modelChange usually starts outside the business, and it matters whether it hits the deep drivers of the organisation or the day-to-day machinery.
W. Warner Burke and George Litwin (1992)
| Level | Factors | What it means for you |
|---|---|---|
| Outside world | Customers, competitors, regulators, the economy | The usual starting point of big change |
| Transformational | Mission and strategy, leadership, culture | Deep, slow change, led from the top; your role is to explain it and model it |
| Transactional | Structure, management practices, systems, team climate, tasks and skills, individual needs and values, motivation | Day-to-day change; this is where team leaders have most influence |
| Performance | Individual and organisational results | The outcome that feeds back to the outside world |
Use it to diagnose: where did this change start, and which boxes will it pass through on its way to the floor?
Absence is rising on the night shift. A new rota (transactional) is tried and fails. Looking higher up the model, the team leader sees the real issue: since the takeover, people no longer trust that their effort is noticed (culture and leadership). He takes this to his manager with evidence.
Think of a problem your team has. Is it rooted in the deep drivers or the day-to-day machinery?
Fixing the wrong level. Retraining or new rotas will not solve a problem that really sits in leadership or culture.
Which problem have you been trying to fix at the wrong level?
Planning the route
Most changes fail in the doing, not the deciding. These three cards cover the two best-known step-by-step change models and a simple mapping tool that stops a process change causing problems up or down the line.
Card 2.1: Lewin’s three stages: unfreeze, change, refreezePeople have to let go of the old way before they can learn the new one, and the new way has to be locked in before it becomes normal.
Usually credited to Kurt Lewin (1947). Researchers have since shown that the tidy three-step model was largely built by later writers from a short passage of Lewin’s (Cummings, Bridgman and Brown, 2016)
| Stage | What happens | On the floor |
|---|---|---|
| Unfreeze | Show why the current way can’t continue | Share the data, the complaint, the audit result |
| Change | Move to the new way, with support | Train, coach, answer questions, expect mistakes |
| Refreeze | Make the new way the normal way | Update the standard work, check it, recognise it |
This is a different idea from Lewin’s three leadership styles (see LEAP Leadership Fundamentals 2.2). Treat the stages as a simple reminder, not a fixed sequence: on a busy site, change is rarely so neat.
A chilled foods site moves to electronic temperature probes. The team leader starts by showing two paper records that were filled in after the fact (unfreeze). She coaches each operator on the probe (change), then removes the paper sheets and adds the probe check to the shift audit (refreeze).
For a change your team is in now, ask: which stage are we really at?
Skipping the refreeze. It is the stage most often missed, and without it people drift back to the old way (see 4.4).
What would make the last change you led truly “frozen”?
Card 2.2: Kotter’s 8 stepsBig change succeeds when leaders work through eight steps in order and don’t declare victory too soon.
John Kotter, first set out in a Harvard Business Review article (1995) and expanded in his book Leading Change (1996)
- Create urgency: help people see why change is needed now.
- Build a guiding coalition: a group with enough influence to drive it.
- Form a vision: a clear picture of where the change is heading.
- Communicate the vision: often, simply, and through what leaders do.
- Remove obstacles: the systems, rules or people blocking the way.
- Create short-term wins: visible early successes that build belief.
- Build on the change: use early wins to go further, not to relax.
- Anchor it in the culture: make the new way “how we do things here”.
Team leaders do most of their work in steps 4 to 7: explaining the vision, clearing blockers on the floor, and spotting wins worth celebrating.
A logistics site moves to a new warehouse management system. The team leader can’t change the plan, but he can explain it in shift briefs, report every blocker he finds, and celebrate the first week with no paper pick lists.
Find one early win in a change you are part of, and tell your team about it at the next brief.
Declaring victory too early. Kotter found that many changes fail because leaders celebrate the launch and move on before the new way is embedded.
Which of the eight steps does your site tend to skip?
Card 2.3: SIPOC: mapping a process before you change itMap who supplies what, what happens, what comes out and who receives it, so a change doesn’t solve one problem by creating another.
The quality movement; in use in Total Quality Management by the late 1980s and now part of Lean Six Sigma. No single originator
| Suppliers | Inputs | Process | Outputs | Customers |
|---|---|---|---|---|
| Goods-in, the flour mill | Flour, recipe, labels | Weigh, mix, bake, cool, pack | Packed loaves, batch records | Despatch, the retailer, QA |
- Start in the middle: describe the process in four to six big steps.
- Then list the outputs and who receives them.
- Then the inputs needed and who supplies them.
- Mark every box your change will touch, and talk to those people before go-live.
A team leader plans to change the bread line’s label format. A quick SIPOC shows two customers she hadn’t thought of: the despatch team, whose scanners read the old barcode position, and QA, who file the batch records. Both are brought in early and the change goes live without a hitch.
Sketch a five-column SIPOC for one process your team runs. Who is on it that you rarely speak to?
Going into too much detail. SIPOC is a one-page overview; use a full process map if you need every step.
Who outside your team would be affected if you changed your process tomorrow?
Bringing people with you
A change only works when people change what they do. These four cards cover why change feels hard, the emotional journey people go through, the five things each person needs before they can change, and how to stay steady yourself.
Card 3.1: Why change feels hardPeople resist change for understandable reasons, and the reason tells you what kind of help they need.
Practical guidance; not based on a single theory
| Reason | What you might hear | What helps |
|---|---|---|
| They don’t understand it | “Nobody’s told us anything.” | Clear information, a chance to ask questions, and honest answers |
| They don’t agree with it | “This won’t work here.” | Listen properly; share the reasons; take good points back up the line |
| They think they’ll lose out | “What’s in it for me?” | Be honest about losses; show real benefits and new opportunities |
Many changes also take away something people value: a routine, a skill they were proud of, a role, a team. Name the loss; don’t pretend it isn’t there.
Experienced pickers push back against voice picking. The team leader learns their real worry: their speed, built over years, will count for nothing. She asks two of them to help train others, so their expertise still matters.
Think of the person most against a current change. Which of the three reasons fits them best?
Labelling people as “resistant”. Resistance is information; it often points to a real flaw in the plan.
What is the most useful thing a “resistor” on your team has ever told you?
Card 3.2: The change curvePeople often go through a dip of difficult feelings before they accept a change, and they move through it at different speeds.
Adapted from Elisabeth Kübler-Ross’s stages of grief (On Death and Dying, 1969); applied to workplace change from the 1980s onwards
| Phase | What you might see | What helps |
|---|---|---|
| Shock and denial | “It won’t happen.” Carrying on as normal | Clear, repeated information |
| Anger and resistance | Complaints, blame, every glitch held up as proof | Listen, stay calm, don’t argue |
| Low point | Low energy, mistakes, absence | Support, patience, small tasks |
| Exploring | Questions about the new way, trying it out | Training, coaching, space to practise |
| Acceptance | Using the new way, suggesting tweaks | Recognition and involvement |
A note on the evidence. Kübler-Ross herself said her stages were not a fixed sequence, and there is little research showing workplace change follows them neatly. Use the curve to stay patient, not to label people.
After a line closure merges two teams, a team leader notices one operator who was angry last week is now quiet and making mistakes. Instead of a disciplinary chat, she checks in, gives him a short-term buddy and a clear task. Two weeks later he is helping new starters.
Place each member of your team on the curve for a current change. Who needs support rather than more information?
Telling people where they are on the curve. “You’re just in denial” helps nobody.
Where are you on the curve yourself for the latest change on your site?
Card 3.3: ADKAR: five things each person needsAn organisation only changes when each person does, and each person needs five things in order.
Jeff Hiatt and Prosci (late 1990s), set out in Hiatt’s book ADKAR (2006)
| Letter | The person needs | What you can do |
|---|---|---|
| Awareness | To know why the change is happening | Explain the reason in plain words |
| Desire | To want to take part | Show what’s in it for them; listen to concerns |
| Knowledge | To know how to change | Train, explain, show |
| Ability | To do it for real, at full speed | Coach on the job; allow practice time |
| Reinforcement | Reasons to keep doing it | Recognise, measure, fix slips quickly |
When someone is stuck, find the first missing letter and work on that. Training (K) won’t help someone who doesn’t yet see why (A).
A new start-up checklist is ignored on one shift. The team leader works through the letters: everyone knows about it (A) and has been trained (K). The gap is D: they see it as extra paperwork. When she shows them the two breakdowns it would have prevented, use rises.
Think of one person struggling with a change. Which letter is missing first?
Jumping straight to training. Most change plans are heavy on K and light on A and D.
Which letter do you most often skip when you introduce a change?
Card 3.4: Resilience through changeLeaders who stay steady through change help their teams to do the same.
Practical guidance; for resilience in more depth see LEAP for Personal Effectiveness 1.2
- Stay curious. Ask “what could this make possible?” as well as “what could go wrong?”
- Know your strengths. Remind yourself what you bring that the change still needs.
- Hold your values, flex your methods. Be firm on what matters, open on how it is done.
- Use your network. Talk to peers who have been through similar changes; ask for help early.
- Plan and pace yourself. Break the change into steps, protect rest, and keep some routines steady.
For your team: keep what you can the same, be honest about what you don’t know, and check in more often than usual.
A team leader learns his shift pattern will change and his best operator is moving to another site. He is unsettled, but he talks it through with a peer who went through the same thing last year, writes down what he can still control, and keeps the daily brief exactly as it was. His team follows his lead.
Write down three things about the current change that are within your control. Act on one this week.
Hiding your own struggles completely. A little honesty (“this is new for me too”) builds trust; pretending all is fine does not.
Who do you turn to when change knocks you off balance?
Leading the change
Plans and processes are not enough on their own. These four cards cover the difference between managing and leading change, the core skills of a change leader, how to win people’s hearts as well as their heads, and how to stop the old way creeping back.
Card 4.1: Leading versus managing changeManaging change gives it structure; leading change gives people a reason to follow. Both are needed.
Builds on John Kotter’s distinction between leadership and management (1990)
| Managing change | Leading change | |
|---|---|---|
| Focus | Plans, processes, timelines, budgets | People, purpose, belief |
| Tools | Project plans, training schedules, checklists | Vision, conversation, example |
| Key question | Is it on time and on plan? | Do people understand it and want it? |
| Who does it | Usually people with the formal role | Anyone, at any level, with credibility |
A team leader rarely owns the change plan, but always has the chance to lead the change on the floor. For the wider difference between leading and managing, see LEAP Leadership Fundamentals 1.2.
A new labelling system is project-managed perfectly: every operator is trained on time. But nobody explains why, and the old labels keep appearing. A team leader on the late shift starts each brief with one customer complaint the new system will prevent. Her shift adopts it first.
Look at a change you are part of. Write one thing you could do to manage it better and one to lead it better.
Thinking leadership is someone else’s job because “I didn’t decide this”. Your team watches you, not the project plan.
In the change you are part of now, are you mainly managing it or leading it?
Card 4.2: The change leader’s toolkitChange leaders keep people behind a change by combining a clear view of the future with steady, honest, everyday behaviour.
Draws on Rosabeth Moss Kanter, Barry Stein and Todd Jick (1992) and John Kotter (1996)
| Skill | On the floor |
|---|---|
| See the future | Be able to explain where the change is heading in two sentences |
| Build allies | Win over respected people early; involve other teams that are affected |
| Communicate, then repeat | Say it at every brief, in plain words; say what you don’t know yet |
| Listen and involve | Ask for ideas and concerns; welcome challenge without dropping the goal |
| Keep energy up | Notice effort, share progress, celebrate small wins |
| Keep the goal in sight | Don’t let daily firefighting push the change aside |
| Walk the talk | Do the new way yourself, and keep every promise you make |
A team leader is asked to introduce a new start-of-shift safety huddle. She asks her two most respected operators to help design it, runs it herself every day for a month without fail, and shares one near-miss it caught each week. The huddle sticks.
Choose the one skill in the table you use least. Do one thing with it this week.
Saying one thing and doing another. Skipping the new process “just this once” tells your team it doesn’t really matter.
Which promise about the current change are you most at risk of breaking?
Card 4.3: Hearts, heads and handsTo win real support rather than reluctant acceptance, give people a reason to care, a reason to agree and a practical reason to make the effort.
Practical guidance; not based on a single theory
| Appeal to | What it means | Example |
|---|---|---|
| Hearts | Help people feel why it matters, to them and to others | “This is about everyone going home safe.” |
| Heads | Show it makes sense, with facts and examples | “The trial line cut rework by a third.” |
| Hands | Show real, practical benefits that make the effort worth it | “No more paper forms at the end of shift.” |
Facts alone rarely move people. Lead with the heart, back it up with the head, and make the benefit real for their hands.
A site wants operators to report near misses. Posters full of statistics change nothing. A team leader tells the story of a colleague hurt at another site, shows how few reports the site gets, and makes reporting a 30-second job on a tablet by the line. Reports triple.
For a change you need your team to back, write one sentence for the heart, one for the head and one for the hands.
Emotional appeals that aren’t true. Overselling a change wrecks trust when reality arrives.
Which of the three do you rely on too much, and which do you forget?
Card 4.4: Making change stickA change isn’t finished at go-live; it is finished when the new way has become the normal way and the old way has gone.
Practical guidance, bringing together Lewin’s refreeze, Kotter’s eighth step and ADKAR’s reinforcement
- Update the standard work: procedures, one-point lessons, start-up checks, training records.
- Remove the old way: take away old forms, tools and shortcuts, so slipping back is harder.
- Measure and show it: put the new measure on the team board and talk about it.
- Recognise it: thank people who use the new way well, by name.
- Check at 30, 60 and 90 days: walk the floor and look for drift.
- Coach, don’t blame, when someone slips; find out what made the old way easier.
- Build it into induction, so new starters only ever learn the new way.
Three months after a new allergen changeover routine, a team leader walks the line at 2am and finds the old paper checklist taped inside a cabinet. She finds out why (the new tablet is slow at night), gets the tablet fixed and removes the paper copy.
Pick a change from the last six months. Go and check whether any of the old way has crept back.
Moving on too fast. When leaders’ attention shifts to the next change, the last one often quietly unravels.
What is the one sign that would tell you a change has truly stuck?
Every card at a glance.
| Card | Model | Key idea | Reach for it when |
|---|---|---|---|
| 1.1 | Spotting the need for change | Watch inside and outside triggers; look at trends | Something is slowly getting worse |
| 1.2 | The Change Equation | Dissatisfaction × vision × first steps > resistance | A change has stalled |
| 1.3 | Leavitt’s Diamond | Tasks, people, structure, technology all connect | New kit or a new system is coming |
| 1.4 | The McKinsey 7-S | Seven elements must line up; shared values at the centre | A change looks good on paper but isn’t landing |
| 1.5 | The Burke-Litwin model | Deep drivers versus day-to-day machinery | Fixes keep failing |
| 2.1 | Lewin’s three stages | Unfreeze, change, refreeze | You need a simple shape for a change |
| 2.2 | Kotter’s 8 steps | Urgency through to anchoring in culture | A big site-wide change is starting |
| 2.3 | SIPOC | Map suppliers to customers before you change | You are changing a process |
| 3.1 | Why change feels hard | Don’t understand, don’t agree, or will lose out | Someone is pushing back |
| 3.2 | The change curve | A dip of feelings before acceptance | Morale has dropped after an announcement |
| 3.3 | ADKAR | Awareness, desire, knowledge, ability, reinforcement | One person is stuck |
| 3.4 | Resilience through change | Stay curious, flexible and connected | Change is getting to you |
| 4.1 | Leading versus managing change | Structure plus belief | The plan is on track but people aren’t |
| 4.2 | The change leader’s toolkit | Vision, allies, communication, example | You are asked to lead a change |
| 4.3 | Hearts, heads and hands | Feel it, believe it, see the benefit | You need real support, not compliance |
| 4.4 | Making change stick | Standardise, remove the old, check for drift | A change is “done” |
Sources and further reading.
All card text is original to DevelopME.Today. Each theorist’s ideas were checked against at least one independent source.
- Beckhard, R. and Harris, R. T. (1977) Organizational Transitions: Managing Complex Change
- Burke, W. W. and Litwin, G. H. (1992) A causal model of organizational performance and change, Journal of Management, 18(3)
- Cummings, S., Bridgman, T. and Brown, K. G. (2016) Unfreezing change as three steps: rethinking Kurt Lewin’s legacy for change management, Human Relations, 69(1)
- Dannemiller, K. D. and Jacobs, R. W. (1992) Changing the way organizations change, Journal of Applied Behavioral Science, 28(4)
- Hiatt, J. M. (2006) ADKAR: A Model for Change in Business, Government and our Community
- Kanter, R. M., Stein, B. A. and Jick, T. D. (1992) The Challenge of Organizational Change
- Kotter, J. P. (1990) A Force for Change: How Leadership Differs from Management
- Kotter, J. P. (1995) Leading change: why transformation efforts fail, Harvard Business Review, 73(2)
- Kotter, J. P. (1996) Leading Change
- Kübler-Ross, E. (1969) On Death and Dying
- Leavitt, H. J. (1965) Applied organizational change in industry, in March, J. G. (ed.) Handbook of Organizations
- Lewin, K. (1947) Frontiers in group dynamics, Human Relations, 1(1)
- Waterman, R. H., Peters, T. J. and Phillips, J. R. (1980) Structure is not organization, Business Horizons, 23(3)
Trademarks. ADKAR is a registered trademark of Prosci, Inc. Kübler-Ross Change Curve is a registered trademark of the Elisabeth Kübler-Ross Family Limited Partnership. Both are described here in our own words.
External links open in a new tab. We link to them as useful further reading and are not responsible for their content.
Want help using this on your floor?
The LEAP Pilot turns ideas like these into 10-minute huddle sessions your team leaders run themselves, measured against your own numbers.