How to motivate a team

Motivation is not a mood you install in people. It is what happens when four things are true at once: the work matters to somebody, the person is getting better at it, they have some say in how it gets done, and the effort is noticed by a human who can name it. When a team goes flat, one of those four has broken. Work out which, rather than holding a rally.

This is also why most advice on the subject is useless. "Recognise your people" is not an instruction, it is a category. What follows is the actual sentences.

Start with the diagnosis, not the pep talk

Before changing anything, book twenty five minutes with each person and say up front what it is not. Otherwise they spend the whole conversation managing risk instead of talking.

The five questions, in order

1. Take the threat out first. "This isn't a performance conversation and nothing here goes in a review. I want to know what your week actually feels like."
2. Ask about the good days, not the bad ones. "Think of a week in the last few months when the work felt worth doing. What were you working on?" People describe what motivates them far more accurately from a real example.
3. Ask about friction. "What's the most annoying recurring part of your week that I could probably fix and haven't?"
4. Ask about the ceiling. "What are you getting better at right now? And what have you stopped getting better at?" The second half is where quiet resignations begin.
5. Close with one commitment. "Which single thing would make the biggest difference if I sorted it by the end of the month?" Then sort it, and tell them you did.

After each question, stop talking. The commonest failure here is the manager filling four seconds of silence with their own answer. Silence is the person deciding whether to tell you the real thing, not a problem to be solved. See active listening.

Wrong way, better way

The gap between these columns is specificity. The left one is about you and your feelings. The right one is about them and the facts.

Say the true thing before the motivating thing

Manufactured optimism reads as dishonesty or inattention, and both cost more than the bad news would have. Compare:

• Wrong: "This restructure is a great opportunity for all of us."
• Better: "This restructure is unsettling and I don't have all the answers. Here are three things I do know, one thing I've been told not to discuss yet, and when I'll know more."

Naming what everyone is already thinking buys you the right to be believed later. That is the practical end of psychological safety: people put effort into work they are allowed to be honest about.

Nobody has ever been motivated by a manager who appeared to think the situation was better than it was.

Recognition, in four sentences

Most praise fails because it is generic and immediately followed by a request. Recognition that lands has a shape:

1. Name the person. Not the team, not "you guys". A named person.
2. Name the specific behaviour. What they did, when, and what it cost them.
3. Name the effect. What became possible because of it.
4. Stop. Do not attach feedback, a new request, or the word "but" to the end of it.

Worked example: "Maya, in Tuesday's call you spotted that they'd moved their launch date, and you raised it in the room rather than letting it slide. That's why we're not rebuilding the plan next month." Four seconds, no budget. Then say nothing else.

The compliment sandwich ruins this. If praise is reliably the bread around criticism, people learn to brace at the first kind word. Keep the two apart, and use something like the SBI feedback model when the message is corrective.

Give people the two things they cannot give themselves

Control and visible progress. Nearly everything else you can influence is decoration.

• Delegate outcomes, not methods. Handing work over with the method attached is dictation with extra admin. Say: "You own this. The constraints are the budget and the date. How you get there is yours. Come to me as a sounding board, not for permission."
• Then hold your nerve. Take it back the first time it is done differently to how you would have done it, and you have taught the team that ownership is a loan.
• Make progress visible weekly. Three lines in a Friday note: what moved, what's stuck, what we learned. Teams on long projects go flat less because the work is hard than because nothing looks finished.
• Ask instead of answering. "What have you already tried?" and "what would you do if I were on leave?" build capability, which is itself motivating. The GROW model is a decent structure for it.

Motivating a team after a knock

A lost pitch, a cancelled project, a redundancy round. Sequence matters more than words here.

1. Day one: name it plainly. "We lost it. I'm disappointed and I expect you are. I'm not going to pretend otherwise." Do not schedule a motivational session the same week. It reads as a cover-up.
2. Within a week: debrief decisions, not outcomes. "Which of our decisions would we make again with the information we had at the time?" That separates bad luck from bad judgement, and stops people quietly concluding the fault was theirs.
3. Week two: one small, winnable thing. Confidence returns through completed work, not reassurance. A two-week piece that visibly ships beats any speech.
4. Within a month: report back. "Three of you said the review process was the problem. I've changed it. Here's what's different." Nothing flattens a team faster than input asked for twice and used zero times.

When it goes wrong

Four ways this fails in practice, and the recovery move for each.

1. You ask, and they say "everything's fine"

"Fine" is a reasonable answer to a question you have not yet earned. Do not push, and do not repeat it more slowly. Narrow it: "Fair enough. Different question: if I could delete one recurring meeting from your week, which one goes?" Small, low-risk questions are how you reach the large ones, about three conversations later.

2. You fix things and nothing improves

You probably fixed hygiene rather than motivation. Better chairs and free lunch remove irritation but do not create drive. If the work is repetitive, invisible or pointless, or the pay is under market, no perk touches it. Say so: "I've fixed what I can fix. The bigger issue is that this work isn't going anywhere for you. Let's talk about what would change that, including whether it's a different role." Pretending recognition compensates for a badly designed job loses you the person and their trust at once.

3. One cynic is setting the temperature

Privately, and name behaviour rather than attitude. Attitude is arguable, behaviour is not. "In yesterday's planning you said twice that it'll all be changed again in a month. You might be right. But it lands as a full stop, and people stop offering ideas. If you think the plan is wrong I want the argument, not the eulogy." If nothing shifts after two goes it is a performance problem, not a motivation one, and it needs proper feedback.

4. You promised something and got overruled

Go back first, before they hear it elsewhere. "I told you I'd get the extra headcount. I didn't. Here's what I asked for, the answer I got, and what I'm doing instead." Managers underestimate the credit earned by reporting their own failures accurately, and what they lose by going quiet and hoping nobody notices. Everybody notices.

What to do this week

1. Book three of the twenty five minute conversations. Not all of them, three.
2. Take one piece of friction you hear about and remove it inside two weeks.
3. Give one piece of named, specific recognition with no request attached.
4. Hand over one decision you would normally make, and do not take it back.

None of this is hard to understand, which is the problem. Managers read a page like this, agree with it, then revert to the pep talk in the real conversation, because the pep talk is what they have practised. This is a performance skill: it lives in what you say in the second after someone goes quiet. It shifts only through rehearsal and feedback, which is the whole reason experiential learning exists. Run the conversation badly where it costs nothing, get told exactly where you lost the person, run it again.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.