LEAP for Managing Performance
16 practical cards on setting goals, measuring what matters, giving feedback and raising performance, written for team leaders in food, manufacturing and logistics. A free resource from DevelopME.Today.
On a production or distribution site, performance is visible every hour: cases per hour, right first time, on-time despatch, near misses reported. But numbers on a board are not the same as managing performance. That happens in the conversations a team leader has, and the fairness people see in them.
These 16 cards cover four things a team leader needs: setting clear direction, measuring what really matters, running feedback and reviews that people value, and raising performance, including when someone is struggling.
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 your site’s policies. These cards are about everyday leadership. Where a card touches on formal steps, such as capability procedures, ratings or pay, always follow your own site’s policy and involve HR early.
Setting direction
Good performance starts long before any review. These three cards cover the performance management cycle, linking each person’s objectives to the site’s goals, and when to set a goal that stretches people.
Card 1.1: The performance management cyclePerformance management is a year-round cycle of agreeing, supporting, reviewing and resetting, not a once-a-year form.
Draws on Michael Armstrong and Angela Baron (1998) and the cycle models used in many HR texts
- Agree: what good looks like, the objectives and the measures.
- Support: coaching, training, resources and regular check-ins.
- Review: look at results and behaviours together, with evidence.
- Recognise and develop: thank, reward where policy allows, and plan development.
- Reset: use what you learned to agree the next objectives.
Its purpose is shared: everyone knows what the site is aiming for, what is expected of them, what high performance looks like, and that they own their part in it.
A team leader used to see her operators’ objectives only at the annual review. She now spends five minutes with each person every month on one question: “How are you getting on with your goals, and what do you need from me?” The annual review becomes a summary, not a surprise.
Pick one person in your team. Which stage of the cycle are they at right now, and when did you last talk about it?
Treating the review as the whole cycle. If the only conversation is once a year, the cycle has stopped.
Which stage of the cycle do you spend least time on?
Card 1.2: Cascading objectives: MBO and personal objectivesPeople perform best when their own objectives clearly link to the team’s and the site’s, and when they help set them.
Peter Drucker’s management by objectives (1954), developed by George Odiorne (1965)
| Level | Example objective |
|---|---|
| Site | Cut customer complaints by 20% this year |
| Team | Zero foreign-body complaints from Line 3 |
| Person | Complete metal-detector checks on time every shift and log every test |
- Cascade: start from the site’s goals and work down.
- Involve: agree each objective with the person, don’t just hand it over.
- Make it clear: what, by when, and how it will be done (see SMART in LEAP for Strategy 1.2).
- Monitor and review: check progress during the year, not only at the end.
A warehouse team leader asks each picker to suggest one personal objective that would help the site’s on-time despatch target. One suggests learning the reach truck to cover peaks. It becomes her objective, and she owns it.
Pick one person’s objective. Can you draw a straight line from it to a site goal?
Too many objectives. Three or four that matter beat ten that nobody remembers.
Which of your team’s objectives were set for them rather than with them?
Card 1.3: Stretch goalsA goal that looks almost out of reach can spark new thinking, but only when the team has the energy, resources and safety to try.
Draws on Sim Sitkin and colleagues (2011), and Steven Kerr and Steffen Landauer (2004)
| Use a stretch goal when | Avoid it when | |
|---|---|---|
| The team | It is confident, stable and has recent wins | It is already stretched, short-staffed or struggling |
| The work | Small improvements have stopped working | The basics are not yet in control |
| The support | There is time and resource to try new ideas | People will be blamed if they fall short |
Celebrate progress as well as success. A team that gets 70% of the way to a bold target has often done better than one that hit a safe one.
A line has been stuck at 82% efficiency for a year. The team leader sets a stretch goal of 90% and gives the team two hours a week to test ideas. They reach 87%, with a new changeover method the whole site adopts.
Look at your team’s targets. Is any of them so safe that nobody has to think differently to hit it?
Cutting corners. Under pressure, people may skip safety or quality checks to hit a stretch target; make clear those are never the price.
What would a genuine stretch look like for your team, and what would they need from you?
Measuring what matters
What gets measured gets attention, so measure the right things. These four cards cover choosing good measures, and three wider models senior managers use to judge how a whole organisation is performing.
Card 2.1: Choosing the right measuresA good measure tells you whether you are winning and what to do about it; a bad one just fills a board.
Practical guidance, using the common idea of key performance indicators (KPIs)
| A good measure is | Ask yourself |
|---|---|
| Linked to a goal | Which site or team objective does this show? |
| Within the team’s control | Can the team actually move this number? |
| Balanced | Does it sit alongside quality, safety and people measures, not just output? |
| Timely | Do we see it soon enough to act? |
| Simple | Can every operator explain what it means? |
Keep the list short. Review measures regularly: drop the ones nobody acts on and add ones that would change decisions.
A team board shows 14 measures. Nobody can say which matter. The team leader cuts it to five (safety, quality, output, waste and attendance), agrees a target for each and reviews them at every brief. Within a month the team can explain every number.
Look at your team board. Which measure has not changed a single decision in the last month?
Gaming the number. Measure only output and you may get output at the expense of quality or safety.
If you could keep only three measures for your team, which would they be?
Card 2.2: The Balanced ScorecardJudge performance from four angles, not just the money, so problems show up before they hit the profit line.
Robert Kaplan and David Norton (1992)
| Perspective | Key question | Example on site |
|---|---|---|
| Financial | How do we look to the owners? | Cost per case; waste value |
| Customer | How do customers see us? | On-time, in-full delivery; complaints |
| Internal process | What must we excel at? | Line efficiency; right first time |
| Learning and growth | Can we keep improving? | Skills matrix coverage; ideas implemented |
The four are linked: skilled people improve processes, better processes please customers, and happy customers drive financial results.
A site hits its cost target every month, yet loses a major customer. Looking back, on-time delivery had been slipping for six months, but nobody was watching it. The next year’s scorecard gives customer measures equal weight.
Sort your team’s measures into the four perspectives. Which box is empty?
Too many measures in each box. A scorecard with forty measures balances nothing.
Which perspective does your site talk about least?
Card 2.3: The Triple Bottom LineA business should judge itself on its impact on people and the planet as well as on profit.
John Elkington, who coined the term in 1994 and set it out in Cannibals with Forks (1997)
| Bottom line | What it covers | On site |
|---|---|---|
| People | Employees, communities, suppliers | Safety record, fair pay, training, local jobs |
| Planet | Environmental impact | Energy use, food waste, packaging, water |
| Profit | Economic value, broadly | Margin, but also local suppliers and jobs supported |
In 2018 Elkington himself called for a rethink, warning that many firms used the idea for reporting rather than real change. Use it to guide decisions, not just to fill a report.
A team leader in a ready-meals plant shows his team that food waste costs money (profit), fills landfill (planet) and could feed people through a local charity (people). A waste-reduction project gets more support than any cost drive before it.
Name one thing your team does that helps each bottom line.
Box-ticking. Three tidy columns in a report change nothing if targets and decisions still only follow profit.
Which of the three bottom lines does your team have most influence over?
Card 2.4: The EFQM ModelAn excellent organisation links why it exists, how it delivers and what it achieves, and keeps reviewing all three.
The European Foundation for Quality Management, set up in 1988 by 14 European companies. The current model (2020, updated 2025) replaced the earlier nine-box version
| Part | Question | Covers |
|---|---|---|
| Direction | Why do we exist, and where are we going? | Purpose, vision, strategy, culture and leadership |
| Execution | How do we deliver? | Involving stakeholders, creating value, driving performance and change |
| Results | What have we achieved? | How stakeholders see us; strategic and operational results |
The model uses a review cycle called RADAR: decide the Results you want, plan Approaches, Deploy them, then Assess and Refine.
A site preparing for an EFQM assessment asks each team leader to show one improvement cycle. One shows how her team set a target for allergen errors, trained everyone, checked results weekly and refined the check sheet twice. It becomes the site’s example of good practice.
Take one improvement your team made. Can you describe it as results, approach, deployment, assessment and refinement?
Treating it as an award to win. The value is in the regular self-assessment, not the certificate.
Where in your team does the “assess and refine” step get skipped?
Feedback and reviews
Reviews only work when people feel they are fair and useful. These five cards cover self-appraisal, feedback from colleagues, the review meeting itself, a lighter monthly alternative to the annual review, and keeping your judgements fair.
Card 3.1: Self-appraisalAsking people to review their own performance first turns the review into a two-way conversation and builds ownership.
Practical guidance; not based on a single theory
- Give a simple form a week before the review: achievements, challenges, strengths, areas to develop, goals for next year, support needed.
- Encourage evidence. Suggest people keep a short log of wins and problems through the year.
- Read it before you meet. Note where you agree and where you see things differently.
- Start the review with their view. “Talk me through what you wrote.”
Some people rate themselves too harshly, others too generously. Both are useful starting points for a conversation, not final answers.
A quiet operator rates herself “meets expectations”. Her team leader points to three problems she solved that nobody else spotted. It is the first time she has heard that her work is noticed, and the conversation opens up.
Before your next one-to-one, ask the person to jot down one thing they are proud of and one thing they want help with.
Using the self-appraisal against people. If honest answers are used to mark them down, next year’s will be bland.
Whose view of their own performance is furthest from yours, and why?
Card 3.2: Peer, 180° and 360° feedbackColleagues and others see parts of a person’s work that a manager never sees, so feedback from several sources gives a fuller picture.
Multi-source feedback; see Manuel London, Job Feedback (1997)
| Type | Who gives feedback | Best for |
|---|---|---|
| Peer appraisal | Colleagues at the same level | Teamwork, reliability, helpfulness |
| 180° | Manager, peers and the person themselves | A rounded view without reports below |
| 360° | As 180°, plus the people they lead | Developing team leaders and supervisors |
- Keep it anonymous and confidential, and say how it will be used.
- Ask about specific behaviours, not personality.
- Use it mainly for development, with a coach or manager to help make sense of it.
A team leader’s 360° shows that his manager and peers rate his planning highly, but his own team says he rarely explains decisions. He starts each brief with “here’s why”, and his next 360° shows the change.
Ask two colleagues one question about yourself: “What’s one thing I could do that would make your shift easier?”
Using peer ratings to decide pay or discipline. Friendships, rivalries and fear of conflict distort the scores.
What might your own team say about you that your manager would never see?
Card 3.3: The performance review meetingA good review is a two-way conversation about the past and the future, with no surprises.
Practical guidance; not based on a single theory
| Before | During | After |
|---|---|---|
| Gather evidence from the whole period, not just last month | Start with their view (see 3.1) | Write up what was agreed and share it |
| Read their self-appraisal | Balance strengths with areas to improve, with examples | Book the first check-in |
| Book a quiet room and enough time | Listen more than you talk | Follow through on any support you promised |
| Plan two or three key messages | Agree objectives and development for the next period |
An operator expects a hard review after a difficult quarter. Instead, his team leader starts by asking what got in the way. They find that he had been covering a vacancy on two lines. They agree a fair target and a training plan, and he leaves motivated.
Think of your next review. Write down the two or three messages you most want the person to leave with.
Surprises. If the first time someone hears about a problem is at their annual review, the feedback has come too late.
What would make your next review the most useful conversation that person has all year?
Card 3.4: The Five ConversationsReplace the annual review with five short, themed conversations spread across the year.
Tim Baker, The End of the Performance Review (2013)
| Month | Conversation | Example question |
|---|---|---|
| 1 | Climate review | How do you rate your job satisfaction and morale right now? |
| 2 | Strengths and talents | What are you best at, and how could we use it more? |
| 3 | Opportunities for growth | Where could you improve, and how can I help? |
| 4 | Learning and development | What skill would you like to learn next? |
| 5 | Innovation and improvement | What is one thing we could do better as a team? |
Each conversation takes about 15 minutes. The five are completed every six months, with one month spare for busy periods.
A team leader with 20 operators can’t face 20 hour-long annual reviews. She switches to 15-minute monthly conversations at the start of shift. Within six months she knows more about her team than in three years of annual reviews.
Have a 15-minute climate review conversation with one person this week.
Letting the monthly slot slip. Once a few months are missed, the framework quietly turns back into an annual review.
Which of the five conversations would you find hardest to have?
Card 3.5: Judging fairly: bias in reviewsEveryone takes mental shortcuts when judging people, so build habits that make your reviews fair.
Draws on research into implicit bias, including the Implicit Association Test (Anthony Greenwald and colleagues, 1998)
| Common trap | What happens | Fair habit |
|---|---|---|
| Recency | The last few weeks outweigh the whole year | Keep notes through the year |
| Halo or horns | One strength or weakness colours everything | Rate each area separately, with evidence |
| Similar to me | We rate people like us more highly | Ask: would I rate this the same for anyone? |
| Stereotypes | Assumptions about age, gender, race, accent or shift pattern | Judge only on observed work and results |
| Leniency | Everyone gets “good” to avoid conflict | Be specific about what good and great look like |
A note on the evidence. Researchers still debate how well bias tests predict behaviour, and there is little evidence that one-off bias training changes it. Clear criteria, written evidence and a second opinion do more.
Reviewing ratings, a team leader notices that all his night-shift operators score lower than days. He realises he sees nights only at handover, when things are busiest. He asks the night supervisor for evidence before finalising any rating.
Look at the ratings you gave last time. Is there a pattern by shift, age, gender or how often you see people?
Thinking “I’m not biased”. Everyone uses shortcuts; the fair leader is the one who checks.
Who in your team do you see least, and how does that affect how you judge them?
Raising performance
Most people want to do a good job. These four cards cover telling performance levels apart fairly, dealing with poor performance early, the trap of setting someone up to fail, and five routes to a high-performing workforce.
Card 4.1: Telling performance levels apart, fairlyRecognising strong performance and tackling weak performance both depend on being clear and honest about the difference.
Practical guidance on performance differentiation
- Set clear expectations from the start: job profile, measures and the behaviours expected.
- Give feedback often, at least monthly on the floor and formally every quarter.
- Gather evidence through the year, not just at the end.
- Sort into broad groups: exceeding, meeting, or not yet meeting expectations.
- Act on each group: stretch and recognise, support and develop, or address the gap (see 4.2).
Be cautious about forced ranking, where a fixed share of people must be rated low. Many large firms have dropped it because it can damage teamwork and trust.
A team leader rates everyone “meets expectations” to avoid arguments. His best operator, who trains every new starter, leaves for a competitor. In his exit interview he says nobody seemed to notice the difference he made.
Write down who in your team is clearly exceeding expectations. Have you told them, and do they know why?
Favouritism, real or perceived. If people can’t see the evidence behind a rating, they will assume it’s personal.
What would your best performer say you do to recognise them?
Card 4.2: Addressing poor performanceTackle poor performance early, privately and supportively, after first finding out whether the cause is skill, will or something else.
Practical guidance; in the UK, see also the Acas Code of Practice on disciplinary and grievance procedures
| Step | What to do |
|---|---|
| 1. Spot it early | Notice the gap before it becomes a pattern |
| 2. Gather facts | Specific examples, dates, data; not impressions |
| 3. Talk privately | Describe the gap and ask why; listen for causes such as training, tools, health or home life |
| 4. Agree expectations | What good looks like and by when |
| 5. Support | Training, buddying, adjustments, more frequent check-ins |
| 6. Review | Recognise improvement; if it doesn’t come, follow your site’s capability procedure with HR |
Ask whether it is a can’t (skill or resources) or a won’t (motivation), and do not assume. Dismissal is a last resort, after fair support and a proper process.
A previously reliable picker’s accuracy drops sharply. Rather than issue a warning, the team leader asks what has changed. He has new glasses and struggles with the small print on labels. A larger-font scanner screen fixes the problem in a day.
Think of someone whose performance is slipping. Write down one specific example and one question to ask them about it.
Waiting and hoping. The longer poor performance goes unmentioned, the harder the conversation and the more the rest of the team resents it.
Which performance conversation have you been putting off, and what is stopping you?
Card 4.3: The set-up-to-fail syndromeA manager’s low expectations of someone can cause the very poor performance the manager expected.
Jean-François Manzoni and Jean-Louis Barsoux (Harvard Business Review, 1998; book 2002)
- An early slip makes the manager doubt the person.
- The manager watches more closely, gives routine tasks and takes over decisions.
- The person feels distrusted, loses confidence and stops taking initiative.
- Their performance drops, which seems to prove the manager right.
- The cycle repeats, often until the person leaves.
Breaking the cycle: notice the pattern, take your share of responsibility, have an honest conversation about how you have been working together, agree clear expectations and gradually hand back trust.
A team leader realises she checks one operator’s work three times a shift and never asks his opinion. She tells him she has been over-checking, asks what support he actually needs, and gives him ownership of the start-up checks. Within a month he is one of the most reliable people on the line.
Think of the person you trust least. Is that based on recent evidence, or on an early impression?
Thinking it only happens with bad managers. The research found it is common among good, well-meaning managers.
Who in your team might feel you have already made up your mind about them?
Card 4.4: Katzenbach’s five paths to peak performanceHigh-performing workforces are built on emotional commitment, and there are five proven routes to it.
Jon Katzenbach, Peak Performance (2000)
| Path | Energy comes from | On the floor |
|---|---|---|
| Mission, values and pride | A purpose people are proud of | “We feed thousands of families every day” |
| Process and metrics | Clear standards and visible results | A team board everyone understands and owns |
| Entrepreneurial spirit | Freedom, risk and reward | Teams own an improvement budget |
| Individual achievement | Personal growth and advancement | Skills ladders and clear routes to promotion |
| Recognition and celebration | Being noticed and thanked | Shout-outs, team wins celebrated |
Successful organisations usually follow one or two paths well, rather than all five half-heartedly. Pick the ones that fit your site.
A logistics team leader can’t change pay, but she can change how results are seen and celebrated. She builds a simple daily board (process and metrics) and ends each week by naming the person who made the biggest difference (recognition and celebration). Performance and morale both rise.
Which of the five paths does your site use most? Which one could you add in your own team?
Copying another site’s path. What energises a sales team may not suit a night shift on a chilled line.
What makes your team proud, and how often do you remind them of it?
Every card at a glance.
| Card | Model | Key idea | Reach for it when |
|---|---|---|---|
| 1.1 | The performance management cycle | Agree, support, review, recognise, reset | Reviews feel like a once-a-year form |
| 1.2 | Cascading objectives | Link each person’s goals to the site’s | Setting objectives for the year |
| 1.3 | Stretch goals | Bold targets, with support and safety | Small improvements have stalled |
| 2.1 | Choosing the right measures | Linked, controllable, balanced, timely, simple | Your team board has too many numbers |
| 2.2 | The Balanced Scorecard | Financial, customer, process, learning | Only cost is being watched |
| 2.3 | The Triple Bottom Line | People, planet, profit | Making the case for waste or safety work |
| 2.4 | The EFQM Model | Direction, execution, results; RADAR | Your site is self-assessing |
| 3.1 | Self-appraisal | Their view first | Preparing for a review |
| 3.2 | Peer, 180° and 360° feedback | Feedback from several angles | Developing a team leader |
| 3.3 | The performance review meeting | Two-way, evidence-based, no surprises | A review is coming up |
| 3.4 | The Five Conversations | Five short themed chats in six months | Annual reviews aren’t working |
| 3.5 | Judging fairly | Spot the traps; use evidence | Before you finalise ratings |
| 4.1 | Telling performance levels apart | Exceeding, meeting, not yet meeting | Everyone is rated the same |
| 4.2 | Addressing poor performance | Early, private, supportive; can’t or won’t? | Someone’s performance is slipping |
| 4.3 | The set-up-to-fail syndrome | Low expectations create low performance | You’ve stopped trusting someone |
| 4.4 | Katzenbach’s five paths | Five routes to emotional commitment | You want to lift the whole team |
Sources and further reading.
All card text is original to DevelopME.Today. Each theorist’s ideas were checked against at least one independent source.
- Armstrong, M. and Baron, A. (1998) Performance Management: The New Realities
- Baker, T. (2013) The End of the Performance Review: A New Approach to Appraising Employee Performance
- Drucker, P. F. (1954) The Practice of Management
- Elkington, J. (1997) Cannibals with Forks: The Triple Bottom Line of 21st Century Business
- Elkington, J. (2018) 25 years ago I coined the phrase “triple bottom line”. Here’s why it’s time to rethink it, Harvard Business Review (online)
- EFQM (2020) The EFQM Model (updated 2025)
- Greenwald, A. G., McGhee, D. E. and Schwartz, J. L. K. (1998) Measuring individual differences in implicit cognition: the Implicit Association Test, Journal of Personality and Social Psychology, 74(6)
- Kaplan, R. S. and Norton, D. P. (1992) The balanced scorecard: measures that drive performance, Harvard Business Review, 70(1)
- Katzenbach, J. R. (2000) Peak Performance: Aligning the Hearts and Minds of Your Employees
- Kerr, S. and Landauer, S. (2004) Using stretch goals to promote organizational effectiveness and personal growth, Academy of Management Executive, 18(4)
- London, M. (1997) Job Feedback: Giving, Seeking, and Using Feedback for Performance Improvement
- Manzoni, J.-F. and Barsoux, J.-L. (1998) The set-up-to-fail syndrome, Harvard Business Review, 76(2)
- Odiorne, G. S. (1965) Management by Objectives: A System of Managerial Leadership
- Sitkin, S. B., See, K. E., Miller, C. C., Lawless, M. W. and Carton, A. M. (2011) The paradox of stretch goals, Academy of Management Review, 36(3)
Trademarks. The EFQM Model is the intellectual property of EFQM and is 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.