Ask a room of candidates to describe a time they motivated a team and you will hear a lot of pep talks, team lunches and “I led by example”. Those answers are not wrong, but they are the weakest way to handle the question. The strongest answers are about changing the conditions people work in, not about giving a speech.
Here is the argument up front: interviewers are not scoring your enthusiasm. They are scoring whether you can work out why a team has stalled and fix the cause. The rest of this article sets out the reasoning, what the published evidence and employer frameworks say, and how to build an answer around it.
Why the pep-talk answer underperforms
A typical weak answer (illustrative) runs: “Morale was low before a deadline, so I organised a team breakfast, reminded everyone how important the project was and kept a positive attitude. We hit the deadline.” It is pleasant and it is believable, and it tells the interviewer almost nothing.
Three problems:
- No diagnosis. It never says why morale was low. Without a cause, any action looks like guesswork.
- No mechanism. There is no link between the breakfast and the deadline being met. The team might have hit it anyway.
- No transferable skill. The interviewer cannot picture you doing anything useful in their team, because the answer depends on mood rather than method.
Structured interviews make this worse for the candidate. The U.S. Office of Personnel Management, describing how structured interviews work, notes that “All responses are evaluated using the same rating scale and standards for acceptable answers.” If the scale rewards diagnosis and specific action, a warm but generic story will score in the middle at best.
What motivation actually depends on
One of the most widely used frameworks in motivation research is self-determination theory. Its account of basic psychological needs is a useful lens for this question, because it gives you a vocabulary for diagnosis. The Center for Self-Determination Theory describes three needs:
- Autonomy: “the experience of volition and willingness”. When it is frustrated, people experience “a sense of pressure and often conflict”.
- Competence: “the experience of effectiveness and mastery”. When frustrated, the result is “a sense of ineffectiveness or even failure and helplessness”.
- Relatedness: “the experience of warmth, bonding, and care”.
Look at a demotivated team through that lens and the useful questions become obvious. Do people have any say in how they do the work? Do they feel able to do it well, or are they set up to fail? Do they feel connected to each other and to the point of the work? A team breakfast touches the third need for a morning. Fixing an unclear brief, a broken tool or a rota nobody had a say in touches the first two for months.
There is no need to quote psychological theory in an interview. Use it privately to pick the right story and to explain what you did and why.
What employers say they are looking for
Employer frameworks back this up. In the UK Civil Service behaviour framework, the “Leadership” behaviour at Grade 6 and 7 asks people to “inspire and motivate teams to be fully engaged in their work and dedicated to their role”. That sounds like pep-talk territory until you read the indicators around it. Under “Delivering at Pace”, the HEO and SEO grades are asked to “allow individuals the space and authority to meet objectives”, and at Grade 6 and 7 to “ensure everyone clearly understands and owns their roles, responsibilities and business priorities”. At middle grades, “Leadership” includes “recognise and praise the achievements of others to drive positivity within the team”.
Read together, those are about clarity, ownership, space and recognition. None of them is about charisma.
Amazon’s leadership principle “Strive to be Earth’s Best Employer” says leaders “work every day to create a safer, more productive, higher performing” workplace, and frames that around empathy and employees’ growth. Again: conditions, not cheerleading.
Weak, better and strong answers compared
| Element | Weak | Better | Strong |
|---|---|---|---|
| Situation | “Morale was low.” | “Morale was low after a reorganisation.” | “Two people had asked to move teams, and our error rate had doubled since the reorganisation.” |
| Diagnosis | None | “People were tired.” | “In one-to-ones, three people said they no longer knew who signed off their work.” |
| Action | “I kept everyone positive.” | “I organised a team day.” | “I agreed a sign-off owner for each workstream with our manager and let the team choose who took which.” |
| Result | “We hit the deadline.” | “People seemed happier.” | “Errors returned to the previous level within six weeks and neither transfer request went ahead.” |
All rows are illustrative.
A better answer shape
Use STAR, but give the Action section an internal order. It should take up most of your answer, split across three beats.
- The signal (Situation and Task). What told you the team was not motivated? Use observable evidence: missed deadlines, quiet meetings, sick days, rework, people asking to move. Then say what you were responsible for.
- The diagnosis (Action, part one). How you found out why. Conversations, one-to-ones, looking at the workload data. This is where most answers are thin and where you can stand out.
- The change (Action, part two). The specific thing you changed to remove the cause. Ideally it gives people more say, more ability to succeed, or more connection to the purpose.
- The reinforcement (Action, part three). How you kept it going: recognition, regular check-ins, sharing results with the team.
- The result. Something observable, plus one honest reflection.
An illustrative answer built this way
Illustrative example. Retail assistant manager.
“After our store moved to a new stock system, the evening team’s mood dropped badly. Two people were late more often, and the closing checklist was regularly unfinished. I was the shift lead, so getting the evening team back on track was my responsibility.
I talked to each of them during quieter moments. The common thread was that the new handheld scanners kept freezing and nobody had been properly shown the workaround, so the last hour felt like failing in front of customers every night. They were not lazy; they felt incompetent at a job they had done well for years.
I asked the one colleague who had worked out the workaround to show the others in a fifteen-minute huddle, and I logged the scanner fault with head office with dates and times rather than just complaining about it. I also let the team decide the order of closing tasks, since they knew which ones the scanner problems hit hardest. Each Friday I shared how many closing checklists we had completed that week.
Within a month the checklist was being finished every night, and lateness was back to normal. The replacement scanners arrived later that quarter. My takeaway was that the drop in mood was a symptom; the cause was that a good team had been made to feel bad at their jobs.”
Notice what is missing: no speech, no prize, no “I stayed positive”. The candidate fixed competence (training from a peer), autonomy (choosing the task order) and recognition (the Friday update). That is the kind of story that sits well against a structured rating scale.
Morale versus motivation
Interviewers sometimes phrase this as “tell me about a time you boosted team morale”. The words are often used interchangeably, but it helps to treat them differently. Morale is how the team feels; motivation is whether people are willing and able to put effort into the work. You can lift morale for an afternoon. Lifting motivation usually means changing something about the work itself. If you are asked about morale, it is fine to tell a motivation story, as long as you show how the mood changed too.
If you were not the manager
You do not need authority to answer this well. Some of the best examples come from peers: the colleague who rebuilt a confusing shared tracker so people could see their progress, or the student who reorganised a group project so each member owned one section. At the Civil Service’s EO grade, the Leadership indicators include giving “praise and credit to colleagues and stakeholders where appropriate” and showing “positive, inclusive engagement with your team”. Those are open to anyone.
What matters is that you can show a diagnosis and a change you made within your own reach.
Where to draw the line
Two kinds of story are best avoided. First, anything where you “motivated” the team by adding pressure: longer hours, threats about performance reviews, comparisons with other teams. Even if it worked, it suggests you see motivation as something you do to people. Second, stories where the real fix was money or rewards you controlled. They can be valid, but they show budget rather than leadership, and the interviewer’s next question will be “what if you had no budget?”
If leadership is central to the job you want, make sure your CV tells the same story as your interview. The executive resume builder is set up for leadership-heavy CVs, and the resume questions hub covers how to phrase team results without overclaiming.
FAQ
What if my attempt to motivate the team did not work?
You can still use it, especially if you can show what you tried, why it did not work and what you changed. A misdiagnosis that you corrected is a better story than a generic success.
Should I say “I” or “we”?
Say “I” for what you did and “the team” for what they achieved. The interviewer is scoring your actions, so they need to hear them clearly.
Is a team-building event ever a good example?
It can be, if it addressed a real cause, for example a newly merged team that had never worked together. Explain why that event fitted that problem.
How is this different from a leadership question?
It overlaps, but it is narrower. A leadership question can be about direction or decisions; a motivation question is specifically about getting people willing and able to put effort in.
Sources
- Basic Psychological Needs, Center for Self-Determination Theory
- Success Profiles: Civil Service Behaviours, UK Government (GOV.UK)
- Structured Interviews, U.S. Office of Personnel Management
- Our Leadership Principles, Amazon