How do you motivate an underperforming team?
It’s the wrong question, because it assumes the problem is motivation. Most of the time it isn’t. The team isn’t lazy. Something in their environment is getting in the way, and “motivating” them without removing that blocker just adds pressure to a broken system.
Why motivation is the wrong place to start
You can’t measure motivation. You can’t put “motivated” on a dashboard, and no one has ever fixed a team by asking them to try harder. Motivation is what Thomas Gilbert, author of Human Competence (1978), called the least observable box: a private state you can only infer from behavior. And the behavior you’re reading as “unmotivated” is usually a symptom of something upstream.
Gilbert’s rule: fix the environment before you blame the person. When a team looks lazy, disengaged, or checked out, you’re almost always looking at a broken box 1, 2, or 3 wearing a “motivation problem” disguise.
What are the six boxes?
| Information | Instrumentation | Motivation | |
|---|---|---|---|
| Environment | 1. DataCan they see what good looks like? | 2. InstrumentsDo they have the tools and time? | 3. IncentivesDoes good work pay off? |
| Person | 4. KnowledgeDo they know how? | 5. CapacityCan they sustain the pace? | 6. MotivesDo they want to? |
Gilbert (1978): six boxes in a 2×3 grid. Gilbert’s rule: fix the environment row (1–3) before touching the person row (4–6).
The environment (boxes 1–3) is what the world gives the team:
- Information & Feedback: do they know what “good” looks like, and how they’re doing?
- Resources & Tools: do they have the time, tools, and materials?
- Incentives & Consequences: does good work pay off and poor work cost?
The person (boxes 4–6) is what the performer brings:
- Knowledge & Skills: do they know how?
- Capacity & Aptitude: are they able, at a sustainable level?
- Motives & Attitudes: do they want to?
Notice where motivation sits: last. It’s the box you check after the other five.
What “unmotivated” usually means
When a team underperforms, the instinct is to replace the “lazy” people. But here’s what each box looks like when it’s actually the broken one:
- Box 1 (Information): they can’t see whether their work mattered. Months of shipping into a void reads as apathy. It’s blindness, not laziness.
- Box 2 (Resources): they’re overloaded and under-tooled. Permanent crunch reads as “not trying” when it’s actually “can’t.”
- Box 3 (Incentives): nothing happens when they do good work. When excellence and mediocrity pay the same, people conserve effort. You call it “no motivation.”
- Box 4 (Knowledge): they don’t know how, and won’t say so. “Unmotivated” is often “doesn’t understand the task.”
- Box 5 (Capacity): one person is carrying the team, so everyone else looks checked out.
- Box 6 (Motives): only here, last, does “they don’t want to” become a real answer. And even then it’s usually a response to one of the five boxes above.
Run the diagnostic
Gilbert's Behavior Engineering Model (1978) splits every performance problem into six boxes: three in the environment and three in the person. His rule: fix the environment before you blame the person. Answer each question honestly.
"Not sure" counts as a gap: uncertainty is data.
Do people know what "good" looks like, and how they are doing?
- I know what "good" looks like for my role. There is a shared, written definition.
- I get feedback often enough to know whether I am on track.
- I can see how my work connects to the outcome the team is after.
Do people have the tools, time, and materials to do the job?
- I have the tools I need to do the job to the standard.
- I have enough time. The workload is realistic.
- The process helps me; it does not fight me.
Does good work pay off, and does poor work cost?
- Good work gets noticed and rewarded.
- Poor performance has consequences, not just praise for good work.
- The incentives do not accidentally punish the behavior we want.
Do people know how to do the job?
- I have the skills to do my current work well.
- I know the next skill I need, and how to get it.
- I understand the "why" behind my work, not just the "how."
Are people able to do the job, at a sustainable level?
- My workload is sustainable. I am not permanently overloaded.
- The role matches my strengths and abilities.
- I have the mental and physical capacity the work demands.
Do people want to do the job?
- I want to do this work well.
- I find the work meaningful.
- I would keep going when it gets hard.
Answer every question, then select “Diagnose” to see which side, environment or person, is holding the team back.
Illustrative diagnostic based on Gilbert (1978), Behavior Engineering Model. It describes the system, not the people in it. Use it to decide where to intervene, not to blame anyone.
What to change instead of the person
If the diagnosis comes back “environment first,” stop planning pep talks and 1:1s about attitude. Do the concrete things:
- Write down what good looks like (box 1). A shared definition of done turns “I hope this is right” into “this is right, or we fix it.”
- Fix the tools and the pace (box 2). Remove the blockers and the permanent crunch.
- Make consequences match the behavior you want (box 3). Praise the outcome, fix the reward system, and make poor work cost something other than a heroic rescue.
The uncomfortable part: these are your boxes, not theirs. “The team is unmotivated” usually translates to “the environment I built isn’t one people can perform in.” That’s harder to hear, and easier to fix.
When it really is the person
Run all six boxes first. If, and only if, the environment checks out, then:
- Knowledge gap → train, pair, or move the work. That’s a fix, not a firing.
- Capacity mismatch → rebalance the load or the role.
- Motives → have the honest conversation. “Do you want this work?” is a fair question once the system isn’t the problem.
- Replacement is the last lever, not the first. It’s what you do when a person can’t or won’t perform in an environment that demonstrably works.
Most “motivation problems” are environment problems wearing a disguise. Fix boxes 1–3 first, and you’ll find the team you thought was lazy was actually stuck. Questions or pushback? s@spencervaradi.com.
Related: Your Engineers Aren’t Lazy. You’re Starving Them. · You’re Not Underpaying Your Engineers. You’re Under-Meaning Them.