Free LEAP resources

LEAP for Strategy

15 practical cards on planning, seeing the bigger picture, improving and solving problems, written for team leaders in food, manufacturing and logistics.

How to use this guide

Strategy can sound like something that happens in a boardroom. But every plan the business makes lands on the shift eventually, as a new target, a product change, a capital project or a cost squeeze. The team leader is where strategy turns into action.

These 15 cards cover four things a team leader needs: planning the team's work and setting clear goals, understanding the bigger decisions above them, leading improvement and new ideas, and solving problems properly so they stay solved.

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 boardroom models. Theme 2 includes tools senior managers use to set strategy. You won't run a Boston Matrix on your line, but knowing how these tools work helps you understand why your site makes the decisions it does, and explain them to your team.

Theme 1

Planning and priorities

Good planning is what turns a target from the office into a shift that runs smoothly. These four cards cover planning and allocating the team's work, writing clear goals, deciding what matters most, and preparing for things going wrong.

Card 1.1: Planning the team's workA plan works when everyone knows the purpose, their part, the deadline and how progress will be checked.
Theory and originator

Practical guidance; not based on a single theory

How it works
  1. Agree the direction with your manager: what the team must deliver and why.
  2. Break it down into smaller pieces with dates.
  3. Prioritise by impact and ease (see 1.3).
  4. Allocate work by skill and current workload, fairly and consistently.
  5. Involve the right people: maintenance, QA, planning, anyone the plan depends on.
  6. Communicate so everyone knows what they are doing and why.
  7. Monitor and review: check progress during the work, support people who are stuck, and learn from it afterwards.
On the shift

A team leader is told to cut changeover time on Line 2 by a third before Christmas. Instead of trying everything at once, she breaks it into three trials, gives each a named owner and a date, and reviews progress at Friday's brief. The target is hit with a week to spare.

Try this today

Take one goal your team has this month. Write down who owns each part and when it is due.

Watch out for

Planning alone. A plan built without the people who must deliver it usually misses something they would have spotted.

Question for your coach

Which current plan does your team not fully understand?

Card 1.2: Setting goals with SMARTA goal everyone can act on is specific, measurable, achievable, relevant and time-bound.
Theory and originator

George Doran (1981), building on Peter Drucker's management by objectives (1954)

How it works
LetterAskBuilding the goal
SpecificExactly what?Cut film waste on Line 4
MeasurableHow will we know?from 3% to 2%
AchievableCan we do it with what we have?using the new splicer
RelevantDoes it matter to the business?to hit the site's cost target
Time-boundBy when?by the end of March

Drucker set out the idea of managing through agreed objectives in 1954. The SMART checklist came later, from George Doran in 1981. Doran's original A and R stood for "assignable" and "realistic"; versions vary. For a delegation version with two extra letters, see LEAP for Personal Effectiveness 3.3.

On the shift

A team leader's goal is "improve safety". Nobody knows what to do. She rewrites it: "Every operator completes the new lock-out training by 31 January, and near-miss reports rise from 4 to 10 a month." Both happen.

Try this today

Rewrite one of your team's goals so it passes all five letters.

Watch out for

Goals that are SMART but pointless. A perfectly measurable goal that doesn't matter to the business wastes effort.

Question for your coach

Which of your current goals would fail the SMART test?

Card 1.3: Prioritising effort and spendTime and budget are always limited, so put them into the work that matters most and stop the work that doesn't.
Theory and originator

Practical guidance, using a common impact and effort grid

How it works
Low effortHigh effort
High impactQuick wins: do nowBig projects: plan carefully
Low impactFill-ins: do if there's timeMoney pits: stop or avoid
  • List the jobs competing for time or money.
  • Place each on the grid, with the team.
  • Do the quick wins, plan the big projects, and actively stop the money pits.
  • Review the grid when priorities change.
On the shift

A team leader has eleven improvement ideas and no time. Placing them on the grid, she finds three quick wins (a new label printer position, a clearer changeover board, a spare-parts shelf). All three are done in a week. Two "money pits" are dropped.

Try this today

List five things competing for your team's time this week. Put each in one of the four boxes.

Watch out for

Only doing quick wins. The high-impact, high-effort projects are often where the real gains are; they just need planning.

Question for your coach

What are you still doing that belongs in the "stop" box?

Card 1.4: Types of plan, including contingency planningDifferent plans serve different jobs, and a good team leader always has a plan for when things go wrong.
Theory and originator

Practical guidance; not based on a single theory

How it works
Type of planTimescaleWho owns itExample
StrategicYearsSenior leadersGrow ready-meals volume by 20%
TacticalMonthsMiddle managersAdd a third shift on Line 6
OperationalWeeksManagers and team leadersShift rotas, training plan
ActionDaysTeam leadersToday's run plan
ContingencyWhen neededEveryoneWhat we do if the blast chiller fails

A contingency plan names the risk, the trigger that starts the plan, who does what, and what it will cost. Assumption-based planning lists what the plan depends on and watches for signs those assumptions are breaking.

On the shift

The only forklift driver on nights rings in sick. The team leader has no plan, and the dock backs up for three hours. Afterwards he writes a one-page contingency card: who else is licensed, which loads can wait, who to call. Next time, the delay is 20 minutes.

Try this today

Name the single failure that would hurt your shift most. Write three lines on what you would do.

Watch out for

Contingency plans that live in a drawer. If nobody knows the plan exists, it won't be used.

Question for your coach

What is your shift's biggest single point of failure, and what is the plan?

Theme 2

Seeing the bigger picture

These five cards explain the tools senior managers use to decide where the business is going. Each one ends with what it means for a team leader: how to read the decisions coming down, and how to turn them into action on the floor.

Card 2.1: Turning strategy into team actionA strategy only works if each team understands it, sees its part, and can say whether it is working.
Theory and originator

Practical guidance; not based on a single theory

How it works
  • Understand the why: ask your manager what the business is trying to achieve and what is driving it.
  • Map stakeholders: list who is affected or has influence (other shifts, maintenance, QA, customers) and how much.
  • Link team goals to business goals: show how your team's targets connect to the bigger plan.
  • Agree how success will be measured before you start.
  • Test it with the floor: ask experienced operators what could stop it working.
  • Protect what matters: keep the team's values and culture in mind as you change things.
On the shift

The site announces a move to 24/7 working. Rumours spread. The team leader asks his manager for the reasons (a new customer contract), maps who is affected, and explains it at the brief with the shift patterns on the board. He collects three practical concerns and takes them back. The change lands with far less resistance.

Try this today

Ask your manager, "What is the one thing the business most needs from my team this year?"

Watch out for

Passing on decisions without the reasons. "Because head office said so" breeds resistance.

Question for your coach

Could every member of your team explain why their main target matters?

Card 2.2: Ohmae's 3C modelA good strategy balances three things: what customers need, what the company does well, and what competitors offer.
Theory and originator

Kenichi Ohmae, The Mind of the Strategist (1982)

How it works
CQuestion
CustomersWhat do they really need, and how do different groups differ?
CorporationWhat are we strongest at, and what should we make or buy?
CompetitorsHow can we be different: better, cheaper or faster?

Ohmae's point is that strategy means using your strengths to meet customer needs better than competitors can. Ignore any one C and the strategy fails.

For a team leader: when the site chases a new customer or changes a product, the 3Cs explain why. Your team's quality, speed and cost are the "corporation" strengths that win or lose the work.

On the shift

A bakery site loses a supermarket contract on price. Management decides to compete on speed instead: same-day orders. The team leader explains to her shift that changeover speed is now the site's main strength against competitors, and gets the team's ideas on cutting it.

Try this today

Ask yourself: what does our biggest customer care about most, and how does my shift affect it?

Watch out for

Treating customers as one group. Different customers often need very different things.

Question for your coach

Which of the three Cs does your team understand least?

Card 2.3: The Boston MatrixA business can sort its products by how fast their market is growing and how strong their share is, to decide where to invest.
Theory and originator

Bruce Henderson, Boston Consulting Group, "The Product Portfolio" (1970)

How it works
Low market shareHigh market share
High market growthQuestion marks: invest selectively or dropStars: invest to keep the lead
Low market growthDogs: usually wind downCash cows: keep efficient, use the cash elsewhere

For a team leader: if your line makes a cash cow, expect pressure on cost and efficiency rather than new investment. If it makes a star, expect growth, new kit and more people.

On the shift

A team leader is frustrated that her line never gets new equipment while the line next door gets a new wrapper. Her manager explains: her product is a cash cow, stable and profitable, and the new line makes a fast-growing star. She refocuses her team on running the existing kit as efficiently as possible.

Try this today

Ask your manager which box your main product sits in, and what that means for your line.

Watch out for

Weak evidence for big decisions. The matrix is a quick picture, not a full analysis. Real decisions need more data, and a "dog" can still be profitable.

Question for your coach

How does your product's position explain the decisions being made about your line?

Card 2.4: Scenario planningInstead of betting on one forecast, imagine several possible futures and make sure your plan works in most of them.
Theory and originator

Developed at Royal Dutch Shell by Pierre Wack in the 1970s; popularised by Peter Schwartz, The Art of the Long View (1991)

How it works
  1. Pick the question: for example, "What will our site look like in three years?"
  2. Find the driving forces: customer demand, energy costs, labour supply, regulation.
  3. Pick the two biggest uncertainties and combine them into four different futures.
  4. Describe each future as a short story.
  5. Test your plan against each one, and agree early warning signs to watch for.

For a team leader: the same thinking works on a small scale. What if volumes rise 30%? What if two key people leave? A team that has talked it through reacts faster.

On the shift

A logistics site runs a simple scenario session with its team leaders on two uncertainties: a big customer winning or losing a contract, and agency labour being easy or hard to find. In the "win plus hard to hire" future, the plan clearly fails. They start cross-training early. When the contract is won, they are ready.

Try this today

Ask your team, "What would we do if volumes doubled next month? And if they halved?"

Watch out for

Treating scenarios as predictions. The point is to prepare for several possibilities, not to guess the right one.

Question for your coach

Which future is your team least ready for?

Card 2.5: Weisbord's six-box modelWhen an organisation isn't working, look in six places, and check both the official version and what really happens.
Theory and originator

Marvin Weisbord, "Organizational Diagnosis: Six Places to Look for Trouble" (1976)

How it works
BoxQuestion
PurposesAre our goals clear and agreed?
StructureIs the work divided up sensibly?
RelationshipsDo people and teams work well together?
RewardsDo we reward the right behaviour?
LeadershipIs someone keeping the other boxes in balance?
Helpful mechanismsDo our systems, meetings and budgets help or hinder?

Weisbord's key point is to compare the formal (what's written down) with the informal (what actually happens). The gaps show where the trouble is.

On the shift

A site rewards team leaders on output alone, but says quality comes first. Output rises; complaints rise too. Looking at the rewards box shows the gap between what is said and what is paid for. The bonus is changed to include right-first-time.

Try this today

Pick one of the six boxes. Write down the official version and what really happens on your shift.

Watch out for

Using it to blame. The six boxes are linked; a problem in one usually has causes in others.

Question for your coach

In which box is the gap between "official" and "real" biggest for your team?

Theme 3

Innovation and improvement

Most improvement on a production floor is small and steady: a better changeover, a smarter pick path, less waste. These three cards cover building a culture where people offer ideas, testing ideas before rolling them out, and building on what already works.

Card 3.1: Building a culture of ideasPeople only offer ideas when they believe they'll be heard, won't be punished for failing, and will see something happen.
Theory and originator

Practical guidance, drawing on Clayton Christensen, The Innovator's Dilemma (1997)

How it works
  • Two kinds of innovation: small, steady improvements to what you already do, and bigger changes that do things a new way. Christensen calls these sustaining and disruptive. Most frontline improvement is the first kind.
  • Model it: share your own ideas, including the ones that didn't work.
  • Make it safe to fail: thank people for trying, even when the idea doesn't work.
  • Ask everyone: run a simple ideas campaign where each person offers at least one idea.
  • Close the loop: tell people what happened to their idea, even if the answer is no.
  • Get backing from above: ideas schemes fail without senior support.
On the shift

A site's suggestion box hasn't had a new idea in a year. The team leader replaces it with an ideas board at the line, reviews it at every Friday brief and marks each idea "trying", "done" or "not now, because…". Within a month, the board is full.

Try this today

Ask your team for one idea to make tomorrow's shift easier. Act on at least one this week.

Watch out for

Asking for ideas and then ignoring them. That is worse than not asking at all.

Question for your coach

What happened to the last idea a team member gave you?

Card 3.2: From idea to improvementTurn ideas into improvements by testing them small and cheap first, then scaling up the ones that work.
Theory and originator

Gary Hamel, Leading the Revolution (2000)

How it works
  1. Imagine: generate ideas.
  2. Design: shape the best ones into something you can try.
  3. Experiment: test on a small scale (one line, one shift, one week). Hamel saw this as the most important step.
  4. Assess: did it work? What did we learn?
  5. Scale: roll out what works; drop what doesn't.

The aim is to learn quickly and cheaply, rather than betting big on an untested idea.

On the shift

An operator suggests colour-coding the tool shadow board to speed changeovers. Rather than redo every line, the team leader tries it on one line for two weeks. Changeovers there drop by eight minutes. The site rolls it out everywhere the next month.

Try this today

Pick one idea your team has talked about. Plan a one-week trial on a small scale.

Watch out for

Skipping the experiment. Rolling out an untested idea everywhere risks a big, expensive failure.

Question for your coach

Which idea could you test this week, small and cheap?

Card 3.3: Appreciative Inquiry: the 4D cycleInstead of starting with what's wrong, start with what works at its best, and build more of it.
Theory and originator

David Cooperrider and Suresh Srivastva (1987)

How it works
StageQuestion
DiscoverWhen has this worked really well? What made it work?
DreamWhat would it look like if that was normal?
DesignWhat do we need to change to make it happen, and who's involved?
Destiny (or Deliver)Let's do it, learn and adjust.

It is a useful counterweight to problem-solving tools, which focus on what's broken.

On the shift

A team's weekend shifts always seem to run better. Instead of asking why weekdays are bad, the team leader asks the weekend crew what makes their shifts work. Answers: a proper handover, fewer interruptions, people choosing their station. Two of those are copied to weekdays.

Try this today

Ask your team, "Tell me about our best shift recently. What made it work?"

Watch out for

Ignoring real problems. Appreciative Inquiry complements root-cause analysis; it doesn't replace it when something is broken or unsafe.

Question for your coach

What does your team do brilliantly that you could do more of?

Theme 4

Solving problems

Most problems on the floor come back because the fix treated the symptom, not the cause. These three cards cover what gets in the way of good problem-solving, how to dig down to the root cause, and how to get a group to think a problem through from every angle.

Card 4.1: How we solve problems, and what gets in the wayMost bad fixes come from misreading the problem, so understand it properly before jumping to a solution.
Theory and originator

Practical guidance; not based on a single theory

How it works

A simple sequence:

  1. Define the problem clearly, with facts.
  2. Find the cause (see 4.2).
  3. Generate options.
  4. Choose and try one.
  5. Check it worked, and stop it coming back.

What gets in the way:

  • Jumping to solutions before the problem is clear.
  • Assumptions and bias: "It's always nights", "It must be the new starter."
  • Personality: some people decide fast, others need all the facts.
  • Limited skills, time, people or money.
  • Outside pressures: customers, regulation, suppliers.
On the shift

Seal failures rise on a packing line. The first fix is to blame the operators and retrain them. It doesn't work. Going back to the facts, the team leader finds failures only happen with one batch of film. The supplier changes the film; failures stop.

Try this today

Next time a problem comes up, write it down in one factual sentence before anyone suggests a fix.

Watch out for

Blaming people first. Most problems are caused by processes, materials or equipment, not by careless people.

Question for your coach

What assumption do you most often make when something goes wrong?

Card 4.2: Drilling down to the root cause: drill-down, 5 Whys and fishboneKeep asking "why?" until you reach a cause you can fix, so the problem doesn't come back.
Theory and originator

5 Whys: Toyota, described by Taiichi Ohno. Fishbone (cause-and-effect) diagram: Kaoru Ishikawa

How it works

Drill-down: write the problem, list its causes, then the causes of those, until you reach something fixable.

5 Whys example:

Why?Answer
Why did the line stop?The conveyor motor overheated.
Why did it overheat?The bearing was dry.
Why was it dry?It wasn't greased at the last service.
Why not?It isn't on the planned maintenance list.
Why not?The list wasn't updated when the conveyor was replaced.

Fishbone: when there may be several causes, draw the problem as the head of a fish and list possible causes along the bones: people, methods, machines, materials, measurement and environment.

On the shift

Labels keep peeling on chilled packs. The fishbone shows possible causes under materials (label adhesive), environment (condensation) and methods (labelling before packs are dry). A five-minute check confirms the packs are labelled too soon after the chiller. Moving the labeller fixes it.

Try this today

Take one problem that keeps coming back. Ask "why?" five times with the people who work there.

Watch out for

Stopping at a person ("She forgot") or a single cause. The 5 Whys can be too simple for complex problems; use a fishbone when several causes might be at work.

Question for your coach

Which of your recurring problems has never had a proper root-cause check?

Card 4.3: Six Thinking HatsGet a group to look at a problem one way at a time, together, so every angle is covered without arguments.
Theory and originator

Edward de Bono, Six Thinking Hats (1985)

How it works
HatThinkingAsk
BlueManaging the processWhat are we thinking about, and what's next?
WhiteFactsWhat do we know? What do we need to find out?
RedFeelingsWhat's your gut reaction?
BlackCautionWhat could go wrong?
YellowBenefitsWhat's good about this?
GreenCreativityWhat else could we try?

Everyone wears the same hat at the same time, so the group thinks in parallel instead of arguing from fixed positions.

On the shift

A team argues for weeks about moving to four-on, four-off shifts. The team leader runs a 30-minute Six Hats session: facts first, then feelings, then risks, then benefits, then new ideas. A trial on one shift is agreed, with clear checks on fatigue.

Try this today

In your next team discussion, ask everyone to spend two minutes on "what could go wrong?" and then two on "what's good about it?"

Watch out for

Letting one hat dominate. Teams that only use the black hat kill every idea; teams that only use yellow miss real risks.

Question for your coach

Which hat do you wear most, and which do you skip?

Quick reference

Every card at a glance.

Use this table to find the right card fast. Start from the "Reach for it when" column.

CardThe idea in a lineReach for it when
1.1 Planning the team's workPurpose, parts, owners, dates, reviewsA new target lands on your team
1.2 Setting goals with SMARTSpecific, measurable, achievable, relevant, time-boundA goal is too vague to act on
1.3 Prioritising effort and spendImpact versus effort; stop the money pitsToo many jobs, not enough time
1.4 Types of planRight plan for the job, plus a plan BOne failure would stop your shift
2.1 Turning strategy into team actionExplain the why, link the goals, test with the floorA big change is coming down
2.2 Ohmae's 3C modelCustomers, corporation, competitorsYou want to know why the site is chasing a market
2.3 The Boston MatrixGrowth and share decide where to investYour line isn't getting investment
2.4 Scenario planningPrepare for several futuresThe future is uncertain
2.5 Weisbord's six-box modelSix places to look, official versus realSomething isn't working and you don't know why
3.1 Building a culture of ideasSafe to try, everyone asked, loop closedIdeas have dried up
3.2 From idea to improvementTest small, then scaleYou have a promising idea
3.3 Appreciative InquiryBuild on what worksSome shifts run much better than others
4.1 How we solve problemsUnderstand before fixingA fix didn't work
4.2 Drilling down to the root causeDrill-down, 5 Whys, fishboneThe same problem keeps coming back
4.3 Six Thinking HatsOne kind of thinking at a timeA group discussion has become an argument
References

Sources and further reading.

All card text is original to DevelopME.Today. Each theorist's ideas were checked against at least one independent source.

Trademarks. Six Thinking Hats is a registered trademark of Edward de Bono Ltd.

Original works

  • Christensen, C. M. (1997) The Innovator's Dilemma
  • Cooperrider, D. L. and Srivastva, S. (1987) Appreciative inquiry in organizational life, Research in Organizational Change and Development, 1
  • de Bono, E. (1985) Six Thinking Hats
  • Doran, G. T. (1981) There's a S.M.A.R.T. way to write management's goals and objectives, Management Review, 70(11)
  • Drucker, P. F. (1954) The Practice of Management
  • Hamel, G. (2000) Leading the Revolution
  • Henderson, B. D. (1970) The product portfolio, BCG Perspectives
  • Ohmae, K. (1982) The Mind of the Strategist
  • Ohno, T. (1988) Toyota Production System: Beyond Large-Scale Production
  • Schwartz, P. (1991) The Art of the Long View
  • Weisbord, M. R. (1976) Organizational diagnosis: six places to look for trouble with or without a theory, Group & Organization Studies, 1(4)

Independent sources checked

External links open in a new tab. We link to them as useful further reading and are not responsible for their content.

Put it to work

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.