LEAP for Building Teams
22 practical cards on forming, directing and growing a team, written for team leaders in food, manufacturing and logistics.
A shift is only as good as the team on it. The same line, with the same kit, can run well under one crew and badly under another. The difference is rarely skill alone. It is whether people know what they are aiming for, trust each other, speak up, and help each other out.
These 22 cards cover the whole life of a team: putting it together, pointing it in the right direction, building trust, getting the best from each person, and growing the team's skills so it copes when people are off, leave or move on.
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 evidence. Some models here are well researched (the Job Demands-Resources model, leader-member exchange). Others are popular practitioner tools with little formal testing (Cog's Ladder, the five dysfunctions, the nine-box grid). Each card says which.
Forming the team
Good teams start with the right people in the right seats. These four cards cover recruiting well, understanding how new teams settle in, and seeing the different strengths and roles each person brings.
Card 1.1: Recruiting the right peopleGetting a hire right first time saves money, time and team morale; getting it wrong costs all three.
Practical guidance; not based on a single theory
- Be clear on the role: update the job description, the shift pattern, the contract type and the skills that really matter.
- Describe the job honestly: include the early starts, the cold store or the heavy lifting. A realistic picture puts off the wrong people and keeps the right ones.
- Follow a fair process: screen, shortlist, interview and decide against the same criteria for everyone.
- Involve the team: let an experienced operator show candidates the line and share their view.
- Plan the first week: a good induction is part of recruitment, not an afterthought.
A site hires six agency pickers for peak. Three leave in the first week because nobody mentioned the minus 25°C freezer. The next round, the team leader shows every candidate the freezer and the kit before they accept. Retention through peak improves.
Read your team's current job description. Note one thing it leaves out that a new starter would want to know.
Hiring for "gut feel" or people like you. It narrows the team and can be discriminatory. Use the same questions and criteria for every candidate.
What do your best performers have in common that you could look for at interview?
Card 1.2: Cog's LadderNew groups climb five rungs before they work at their best, and a leader can help them climb faster.
George Charrier, Procter & Gamble (1972)
| Rung | What you see | What helps |
|---|---|---|
| Polite | People are friendly but guarded | Introductions, clear basics, quick wins |
| Why are we here? | Questions about purpose and goals | Explain the purpose and targets clearly |
| Power | Jostling for position and influence | Set fair ground rules, don't rush decisions |
| Cooperation | People start to work together | Involve them, share decisions |
| Esprit | Strong loyalty and pride | Stretch them, protect what works |
It is very similar to Tuckman's forming, storming, norming and performing (see LEAP Leadership Fundamentals 5.4), with an extra "why are we here?" stage.
A new night crew is pulled together from three lines. Week two brings arguments over who runs the best machine (power). The team leader agrees a rotation and explains the shift's targets again. By week five they are covering for each other unasked (cooperation).
Decide which rung your team is on. Pick one action from the "what helps" column.
Weak evidence. It was first written up in a company newsletter, not tested research. Use it as a conversation starter, and expect teams to slip back down when people change.
What has moved your team down a rung recently, and what did you do?
Card 1.3: Belbin's team rolesPeople tend to behave in a team in recognisable ways, and the best teams have a balance of those behaviours.
Meredith Belbin, Management Teams (1981), from 1960s research at Henley Management College
| Group | Roles | Brings |
|---|---|---|
| Action | Shaper, Implementer, Completer Finisher | Drive, turning plans into action, attention to detail |
| People | Co-ordinator, Teamworker, Resource Investigator | Organising others, harmony, outside contacts |
| Thinking | Plant, Monitor Evaluator, Specialist | New ideas, sound judgement, deep know-how |
- Most people have two or three preferred roles.
- Each role has strengths and "allowable weaknesses".
- Gaps and too many of one role both cause problems.
A line improvement team is full of Implementers and Completer Finishers: everything is done carefully, but no new ideas come. The team leader brings in an engineer who is a natural Plant and a buyer who knows suppliers (Resource Investigator). Two good ideas follow in a month.
Think about your team. Which of the three groups (action, people, thinking) is weakest?
Treating roles as fixed labels. People can adapt, and the full Belbin profile uses feedback from others, not just a self-test. Belbin is a registered trademark of Belbin Associates.
Which role do you play most, and which do you avoid?
Card 1.4: Spotting and using strengthsWhen people spend more time doing what they are good at, they perform better, feel more confident and are more likely to stay.
Practical guidance; not based on a single theory
- Start with yourself: know your own strengths and weak spots first.
- Watch and listen: notice what people do well and what they volunteer for.
- Ask: one-to-ones, quick questionnaires and feedback from colleagues all help.
- Name it: tell people specifically what they do well.
- Use it: where you can, match tasks to strengths.
A quiet operator is average on the line but always spots labelling errors others miss. The team leader asks her to own the end-of-line label check. Label complaints fall, and she starts speaking up in briefs.
Pick one team member. Tell them one specific thing they do well, and why it matters.
Ignoring weaknesses that matter. Playing to strengths doesn't mean letting safety or quality gaps slide.
Whose strengths are going unused on your shift right now?
Setting direction
Most team problems that look like personality clashes are really about unclear goals, roles or ways of working. These four cards help you set clear expectations, check the basics are in place, brief the team well, and measure what matters.
Card 2.1: Clear expectations and team chartersTeams work best when everyone has agreed, from the start, what good looks like and how they will work together.
Practical guidance; not based on a single theory
A team charter (sometimes called a team contract) is a short written agreement the team builds together and signs up to.
- Goals: what the team is aiming for this month or quarter.
- Roles: who does what, including who covers whom.
- Ways of working: handovers, breaks, phones, how disagreements are raised.
- Check-ins: one-to-ones and team reviews to keep it on track.
It works best with a new team, or when an existing team has slipped into uneven effort.
Two operators keep clashing over who cleans down at the end of shift. The team leader gets the whole team to agree a one-page charter, including a clean-down rota. The arguments stop because the rule is theirs, not his.
Write down three things you expect from your team that you have never actually said out loud.
A charter written by the leader and handed down. If the team didn't build it, they won't own it.
Which expectation causes the most friction because it isn't clear?
Card 2.2: The GRPI modelWhen a team struggles, check goals first, then roles, then processes, and only then relationships.
Richard Beckhard (1972), formalised by Irwin Rubin, Mark Plovnick and Ronald Fry (1977)
| Level | Question to ask |
|---|---|
| Goals | Does everyone know and agree what we're aiming for? |
| Roles | Does everyone know who does what, and who decides? |
| Processes | Do our handovers, meetings and procedures actually work? |
| Interpersonal relationships | Do people trust and respect each other? |
The model's key point is that many "personality clashes" are really caused by unclear goals, roles or processes higher up.
Day and night shift leads seem to dislike each other. Working down GRPI, the team leader finds the two shifts have different targets for the same line (goals). Once the targets are aligned, most of the tension goes.
Think of a current team problem. Ask the four questions in order and note where the answer is first "no".
Treating it as a one-off. GRPI is a snapshot; check it again when people, targets or processes change.
Which team problem have you been treating as personal that might really be about goals or roles?
Card 2.3: Team briefingsA short, regular team briefing keeps everyone pointing the same way and gives people a chance to be heard.
Practical guidance; not based on a single theory
- Same time, same place: the start-of-shift brief should be a habit, not an event.
- Look back: how did the last shift go against target, safety and quality?
- Look forward: today's plan, priorities and any changes.
- Pass on the bigger picture: share relevant news from the site or business.
- Ask and listen: invite questions, and make sure quieter people are heard, not just the loudest.
A team leader's brief has turned into ten minutes of her talking. She changes the format: two minutes on yesterday, two on today, then she asks one named person each day, "What would make today easier?" Small problems start getting raised before they cause downtime.
At your next brief, ask one quieter team member a direct, open question.
Briefings that only go one way. If nobody ever raises anything, people have learned it isn't worth it.
When did a briefing last change what you did that shift?
Card 2.4: Measuring team performanceMeasure a few things that matter, across more than one dimension, and use the numbers to help the team improve, not to blame it.
Practical guidance; not based on a single theory
| Dimension | Example measures on a production floor |
|---|---|
| Output | OEE (overall equipment effectiveness), units per hour, orders picked |
| Quality | Right-first-time, waste, customer complaints |
| Safety | Near-misses reported, accidents, housekeeping audits |
| People | Absence, turnover, training completed |
| Improvement | Ideas raised and implemented |
Look at trends over weeks, not single shifts, and share the numbers with the team.
A team is praised for record output, but waste has doubled and near-miss reporting has dropped to zero. Looking only at output hid the problem. The team leader adds waste and near-misses to the daily board.
List the measures you look at every shift. Note which of the five dimensions you are missing.
Measures that drive the wrong behaviour. A target on units per hour alone can push people to cut corners on safety or quality.
What does your team think you care about most, judging by what you measure?
Trust and relationships
Trust is what lets an operator admit a mistake, challenge a bad decision or ask for help. Without it, problems stay hidden until they become incidents. These four cards cover how trust is built, what happens when it is missing, and how a leader's relationships with individuals shape the whole team.
Card 3.1: Building trustTrust builds slowly through consistent behaviour, and the leader sets the tone.
Practical guidance, drawing on Stephen M. R. Covey, The Speed of Trust (2006)
- Share a little of yourself: people trust leaders they know.
- Do what you say: follow through on every promise, however small.
- Talk openly and often: explain decisions, share what you can, admit what you don't know.
- Live your values: be fair, honest and respectful with everyone, not just favourites.
- Be yourself: people spot an act quickly.
- Make time face to face: conversations on the floor build more trust than messages.
A team leader promised to chase a broken locker for weeks and never did. Small thing, big signal. She fixes it, apologises for the delay, and from then on writes every promise in her notebook. People start bringing her bigger problems.
Write down every promise you made to your team this week. Close one of them today.
Thinking trust is built by team-building days. It is built, or lost, in hundreds of small moments on shift.
What is one promise you haven't kept, and what has it cost you?
Card 3.2: The five dysfunctions of a teamTeams fail in a predictable chain, and the root is usually a lack of trust.
Patrick Lencioni, The Five Dysfunctions of a Team (2002)
| Dysfunction | What it looks like | What the leader does |
|---|---|---|
| Absence of trust | People hide mistakes and don't ask for help | Go first: admit your own mistakes |
| Fear of conflict | Polite meetings, then moaning in the canteen | Invite honest debate about the work |
| Lack of commitment | Decisions nobody really backs | Get to a clear decision and confirm it |
| Avoidance of accountability | Nobody challenges poor standards | Hold people to what was agreed |
| Inattention to results | People protect their own patch | Keep the shared results visible |
Each dysfunction feeds the one above it, so start at the bottom.
In shift meetings everyone agrees to the new changeover method, then half the team ignores it. The team leader realises nobody felt safe to object in the meeting. Next time she asks, "What's wrong with this plan?" and waits. The real objections come out and get fixed.
In your next meeting, ask "What's the weakest part of this plan?" and wait for an answer.
Weak evidence. The model comes from a business fable, not research. It is a useful lens, not a diagnosis.
Where does your team agree in the room and disagree outside it?
Card 3.3: The Johari WindowTeams work better when more is known openly, and feedback and sharing are how the open area grows.
Joseph Luft and Harrington Ingham (1955)
| Known to me | Not known to me | |
|---|---|---|
| Known to others | Open: what we all know | Blind spot: what others see but I don't |
| Not known to others | Hidden: what I keep to myself | Unknown: what nobody knows yet |
- Ask for feedback to shrink your blind spot.
- Share appropriately to shrink your hidden area.
- In new teams the open area is small; it grows with time and trust.
A team leader thinks he is approachable. Feedback from a trusted line lead reveals that he sighs and looks at his watch when people raise issues (blind spot). Once he knows, he stops doing it, and more issues come to him.
Ask one person you trust, "What do I do that I might not realise?"
Oversharing. Moving things from hidden to open should be relevant and appropriate to work.
What might be in your blind spot as a leader?
Card 3.4: Leader-member exchangeLeaders form a different relationship with each team member, and people who feel like outsiders get less trust, less information and fewer chances.
Fred Dansereau, George Graen and William Haga (1975), developed by Graen and Mary Uhl-Bien (1995)
- Role-taking: when someone joins, the leader sizes them up.
- Role-making: through early tasks, trust builds or doesn't, and people drift into an "in-group" or "out-group".
- Routinisation: the relationship settles into a pattern that is hard to change.
In-group members get more trust, information and opportunities. The aim is to offer that quality of relationship to everyone.
A team leader always gives the interesting jobs to the same three operators who started with him. The agency staff and newer starters notice. He starts rotating the improvement tasks and making a point of briefing everyone the same way.
List your team. Mark who you speak to most. Have a proper conversation with someone you speak to least.
Pretending you have no in-group. Almost every leader does. The skill is noticing it and widening it.
Who on your team might feel like an outsider, and why?
Getting the best from people
These five cards cover the everyday tools of a team leader: handing over ownership, giving feedback, coaching, recognising good work, and keeping the workload at a level people can sustain.
Card 4.1: Empowering without micromanagingSay what good looks like, give people the information and authority to get there, then step back.
Practical guidance; not based on a single theory
| Delegating a task | Empowering a person | |
|---|---|---|
| You decide | What, how and when | What and why |
| They decide | Very little | How, and many day-to-day calls |
| Best for | Urgent jobs, crises, new starters | Experienced people, ongoing ownership |
- Share the bigger picture: targets, costs and constraints.
- Set clear boundaries: what they can decide alone, what needs a check.
- Accept some mistakes as learning.
- Check in, don't hover: agree when you'll catch up.
A team leader checks every one of a line lead's decisions. The line lead stops making any. The team leader agrees a boundary: "Anything under a 20-minute stop is your call; tell me afterwards." Decisions speed up and the line lead grows in confidence.
Pick one decision you always make. Agree with someone that it's now theirs, within clear limits.
Empowering without support. Handing over authority without the information or skills to use it sets people up to fail.
Where are you hovering, and what are you worried will happen if you stop?
Card 4.2: Giving feedbackGood feedback is specific, balanced and about behaviour, not the person.
Practical guidance; not based on a single theory
- Know your point before you start.
- Describe, don't judge: "The last three pallets weren't wrapped to standard", not "You're sloppy."
- Use "I": "I noticed…" owns your view.
- Avoid always and never.
- Balance it: recognise what's going well as well as what needs to change. Too much criticism discourages; too much praise breeds complacency.
- One point at a time, and give the person a chance to respond before offering advice.
A team leader tells a picker, "Your accuracy is always rubbish." The picker gets defensive. Next time: "I noticed four mis-picks on aisle 12 this week. Your speed is great. What's happening on that aisle?" The picker explains the labels are faded. They get replaced.
Give one piece of specific, positive feedback before the end of your shift.
Saving feedback for appraisals. Feedback works best close to the event.
Who have you been avoiding giving honest feedback to, and why?
Card 4.3: Coaching with GROWCoaching means helping someone find their own answer through good questions, rather than telling them what to do.
Graham Alexander, Alan Fine and John Whitmore (1980s); first published by Whitmore, Coaching for Performance (1992)
| Stage | Ask |
|---|---|
| Goal | What do you want to achieve? |
| Reality | What's happening now? What have you tried? |
| Options | What could you do? What else? |
| Will (or Way forward) | What will you do, and by when? |
A GROW conversation can take five minutes at the end of a line. The skill is asking, listening and resisting the urge to jump in with the answer.
A line lead asks how to fix a recurring jam. Instead of telling him, the team leader asks: "What would good look like? When does it jam? What have you tried? What else could you try?" The line lead suggests a fix she hadn't thought of, and owns it.
Next time someone asks you for an answer, ask "What do you think?" first.
Coaching in a crisis. When the line is down or someone is at risk, tell. Coach when there is time to learn.
What stops you coaching instead of telling?
Card 4.4: Recognising and rewardingRecognition is one of the cheapest and most powerful tools a leader has, and it works best when it is specific and personal.
Practical guidance; not based on a single theory
- Say thank you: sincerely, specifically and soon.
- Know what each person values: some like public praise, others a quiet word, extra training or shift choice.
- Mix it up: recognition can be financial or not, formal or informal.
- Recognise the team too: agree a shared goal and celebrate together when it's hit.
- Be fair: recognise effort and behaviour across the whole team, not just the favourites.
A team hits a month with zero customer complaints. The team leader brings in breakfast, puts the result on the board and names the three operators who caught problems early. The next month, more people report near-misses.
Thank one person, by name, for something specific they did today.
Generic praise. "Good job, everyone" is quickly ignored. Say what was good and why it mattered.
When did you last recognise someone outside your usual few?
Card 4.5: Managing workload: demands and resourcesEvery job has demands that use up energy and resources that restore it; keep them in balance and people stay engaged, let demands outrun resources and they burn out.
Evangelia Demerouti, Arnold Bakker, Friedhelm Nachreiner and Wilmar Schaufeli (2001), the Job Demands-Resources model
| Job demands (cost energy) | Job resources (restore energy) |
|---|---|
| High volumes and tight deadlines | Support from the team leader and colleagues |
| Short staffing and overtime | Some control over how and when work is done |
| Shift work, noise, cold | Feedback, training and development |
| Change and uncertainty | Clear goals and recognition |
When demands are high, adding resources can turn pressure into engagement rather than burnout. Also: prioritise, share load with other teams, and say no, with reasons, to work outside the team's goals.
Peak season doubles volumes, and the team leader can't reduce demand. Instead she adds resources: an extra five-minute break, daily thanks on the board, a clear plan each morning and a promise of the first choice of January holidays. Absence stays lower than last peak.
List one big demand on your team right now. Name one resource you could add to balance it.
Only looking at demands. Cutting workload isn't always possible, but increasing support usually is.
Which of your team's demands could you not reduce, but could balance with more resources?
4.4 Recognising and rewarding, Also in LEAP: spotting and preventing burnout
Growing team capability
A strong team copes when someone is off sick, leaves or gets promoted. These five cards cover building skills across the team, spotting and growing talent, what high-performing teams do differently, how to get teams working together, and how management choices higher up shape all of it.
Card 5.1: Multi-skilling and a learning teamA team that keeps learning, and where people can cover more than one job, copes far better with absence, change and growth.
Practical guidance; not based on a single theory
- Build a skills matrix: list people down the side, tasks across the top, and rate each person's level.
- Spot single points of failure: tasks only one person can do.
- Plan cross-training: pair experienced people with learners, and track progress on the matrix.
- Learn from mistakes: treat problems as chances to improve, not to blame.
- Share knowledge: encourage experienced operators to teach.
The only operator trained on the labeller goes off sick for three weeks, and the line runs at half speed. Afterwards, the team leader uses the skills matrix to find four single points of failure and trains a second person on each within two months.
Look at your skills matrix, or sketch one. Find one task only one person can do.
Overloading people. Multi-skilling needs time for training, and output may dip while people learn.
If your best operator left tomorrow, which tasks would stop?
Card 5.2: Talent and the nine-box gridPlotting people on current performance and future potential can help plan development and succession, if it is used carefully.
Adapted from a 1970s McKinsey and GE business-planning grid; no single originator for its use with people
| Lower performance | Higher performance | |
|---|---|---|
| Higher potential | Support and develop | Stretch and prepare for promotion |
| Lower potential | Address performance, clear expectations | Value and keep: solid, reliable contributors |
The full grid has three levels on each axis, making nine boxes. Use it alongside regular coaching and clear performance conversations, and deal fairly but firmly with persistent poor performance, with HR's support.
A team leader assumes his fastest operator is his natural successor. Plotting the team, he sees she is high on performance but has never shown interest in leading. Another operator, average on speed, always organises others. He offers her the deputy role.
Think about who could cover your job for two weeks. What would they need to learn first?
Bias and fixed labels. "Potential" is hard to judge and easily skewed by who you like. Use evidence, review placements regularly, and never share a box as a label.
What evidence, not gut feel, do you have for each person's potential?
Card 5.3: High-performing teamsA real team is a small group with complementary skills, a shared purpose and goals, and mutual accountability for results.
Practical guidance, drawing on Jon Katzenbach and Douglas Smith, The Wisdom of Teams (1993)
- Shared purpose and specific goals: everyone knows what the team is for and how success is measured.
- Complementary skills: technical, problem-solving and people skills across the team.
- A common approach: agreed ways of working.
- Mutual accountability: the team holds itself to account, not just the leader.
- Learning: from both successes and failures.
- Leadership from everyone: people step up when they see something that needs doing.
A packing team hits its targets but only when the team leader pushes. Over three months she shifts the focus: the team sets its own weekly goal from the site target, reviews it each Friday, and calls out each other's slips. Output holds steady even on her days off.
Ask your team, "What is this team for?" See if the answers match.
Calling any group a team. A group that works side by side with individual targets is a working group. That's fine, but it needs managing differently.
What would your team do differently if you weren't there for a week?
Card 5.4: Collaboration and team-buildingCollaboration within and between teams has to be built deliberately, and team-building works best when it tackles real problems.
Practical guidance, drawing on Lynda Gratton and Tamara Erickson, "Eight Ways to Build Collaborative Teams" (2007)
- Model it: leaders who visibly help other teams get teams that help each other.
- Clear roles, flexible approach: define who does what sharply, but give the team room on how.
- Mix people up: rotate staff across lines or shifts so they know each other.
- Keep teams small enough that everyone can know everyone.
- Purposeful team-building: pick activities that solve a real problem or build real bonds, and avoid ones that pit people against each other.
Days and nights blame each other for every problem. Instead of a team-building day out, the two team leaders run a joint 30-minute session to fix the handover sheet together. Relations improve because they solved a real problem side by side.
Find one small problem that crosses two teams or shifts. Suggest fixing it together.
Team-building as a reward day with no link to the work. It can be fun but rarely changes how people work together.
Which other team does yours find hardest to work with, and what could you fix together?
Card 5.5: Birkinshaw's four dimensions of managementEvery organisation makes choices on four dimensions of management, each on a scale from traditional to alternative, and neither end is always right.
Julian Birkinshaw, Reinventing Management (2010)
| Dimension | Traditional | Alternative |
|---|---|---|
| Coordinating activities | Bureaucracy: rules and procedures | Emergence: people coordinate themselves |
| Making decisions | Hierarchy: the boss decides | Collective wisdom: the team decides |
| Setting objectives | Alignment: clear targets cascaded down | Obliquity: aim at a bigger purpose |
| Motivating people | Extrinsic: pay, bonuses, promotion | Intrinsic: interest, pride, purpose |
This is mainly a senior-management model, but it helps a team leader understand why their site works as it does, and where they have room to move.
A site runs on strict procedures and top-down targets, which suits food safety. But a team leader notices that improvement ideas never come from the floor. Within the rules, she shifts one dimension: the team decides how to hit its weekly target (collective wisdom). Ideas start to flow.
For each of the four dimensions, mark where your site sits. Pick one where you have some room to move.
Assuming the alternative end is always better. In a food or safety-critical environment, many procedures must stay fixed.
On which dimension do you have more freedom than you are using?
Every card at a glance.
Use this table to find the right card fast. Start from the "Reach for it when" column.
| Card | The idea in a line | Reach for it when |
|---|---|---|
| 1.1 Recruiting the right people | Be clear and honest about the job; follow a fair process | You're about to hire |
| 1.2 Cog's Ladder | Groups climb five rungs to their best | A new or merged team |
| 1.3 Belbin's team roles | Balance action, people and thinking roles | The team keeps getting stuck the same way |
| 1.4 Spotting and using strengths | Match tasks to what people do best | Someone's talents are going unused |
| 2.1 Clear expectations and team charters | Agree together what good looks like | Friction over who does what |
| 2.2 The GRPI model | Check goals, roles, processes, then relationships | A team problem looks personal |
| 2.3 Team briefings | Short, regular, two-way | Your brief has become a monologue |
| 2.4 Measuring team performance | A few balanced measures, used to improve | One number is hiding a problem |
| 3.1 Building trust | Consistent behaviour, kept promises | People aren't bringing you problems |
| 3.2 The five dysfunctions | Trust, conflict, commitment, accountability, results | Agreement in the room, resistance outside |
| 3.3 The Johari Window | Feedback and sharing grow the open area | You suspect you have a blind spot |
| 3.4 Leader-member exchange | Offer everyone in-group trust | Some people feel like outsiders |
| 4.1 Empowering without micromanaging | Set the what, let them own the how | You're checking everything |
| 4.2 Giving feedback | Specific, balanced, about behaviour | A conversation you've been putting off |
| 4.3 Coaching with GROW | Goal, Reality, Options, Will | Someone asks you for the answer |
| 4.4 Recognising and rewarding | Specific, personal, fair | Good work is going unnoticed |
| 4.5 Managing workload | Balance demands with resources | Pressure is rising and you can't cut the work |
| 5.1 Multi-skilling and a learning team | Skills matrix, cross-training, no single points of failure | One absence would stop a line |
| 5.2 Talent and the nine-box grid | Performance and potential, used carefully | Planning cover or succession |
| 5.3 High-performing teams | Shared purpose, goals and mutual accountability | The team only performs when you push |
| 5.4 Collaboration and team-building | Solve real problems together | Two teams or shifts don't get on |
| 5.5 Birkinshaw's four dimensions | Traditional or alternative, on four choices | You want to see where you have room to move |
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. Belbin is a registered trademark of Belbin Associates. The GROW model's originators' firm, Performance Consultants, licenses its own GROW materials; the generic four-step GROW sequence is widely used.
Original works
- Beckhard, R. (1972) Optimizing team-building efforts, Journal of Contemporary Business; Rubin, I., Plovnick, M. and Fry, R. (1977) Task-Oriented Team Development
- Belbin, R. M. (1981) Management Teams: Why They Succeed or Fail
- Birkinshaw, J. (2010) Reinventing Management
- Charrier, G. O. (1972) Cog's ladder: a model of group growth, SAM Advanced Management Journal, 37(1)
- Covey, S. M. R. (2006) The Speed of Trust
- Dansereau, F., Graen, G. and Haga, W. J. (1975) A vertical dyad linkage approach to leadership within formal organizations, Organizational Behavior and Human Performance, 13
- Demerouti, E., Bakker, A. B., Nachreiner, F. and Schaufeli, W. B. (2001) The job demands-resources model of burnout, Journal of Applied Psychology, 86(3)
- Graen, G. B. and Uhl-Bien, M. (1995) Relationship-based approach to leadership, The Leadership Quarterly, 6
- Gratton, L. and Erickson, T. J. (2007) Eight ways to build collaborative teams, Harvard Business Review, 85(11)
- Katzenbach, J. R. and Smith, D. K. (1993) The Wisdom of Teams
- Lencioni, P. (2002) The Five Dysfunctions of a Team
- Luft, J. and Ingham, H. (1955) The Johari window, a graphic model of interpersonal awareness, UCLA
- Whitmore, J. (1992) Coaching for Performance
Independent sources checked
- Johari window, Wikipedia
- GRPI model, Six Sigma Development Solutions
- Vertical dyad linkage and LMX, Ohio State Fisher College of Business
- The job demands-resources model of burnout, University of Johannesburg research portal
- The Five Dysfunctions of a Team, Wikipedia
- GROW model, Wikipedia
- Nine-box grid: origins and criticism, Egon Zehnder
- Belbin team roles FAQs, Belbin
- Cog's ladder, Wikipedia
- Birkinshaw's Four Dimensions of Management, Mind Tools
- The Discipline of Teams, Katzenbach and Smith, HBR 1993
- Eight Ways to Build Collaborative Teams, Harvard Business Review
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.