How to motivate your team: why enthusiasm is not the answer

Knowing how to motivate your team is one of the most commonly misunderstood aspects of management. The instinct is to equate it with energy or enthusiasm — so when people seem disengaged, managers respond with pep talks, incentives, or team events.

These interventions often produce a short-term lift and then return to baseline. That is not because the people are difficult or unmotivated by nature. It is because the tools are aimed at the wrong target.

The research on how to motivate your team points somewhere different: not to the environment around work, but to the nature of work itself and the conditions under which it gets done.

This article covers Self-Determination Theory, Expectancy Theory, and the Job Characteristics Model — and what each means in practice for managers trying to build lasting team engagement.

Self-Determination Theory: the science behind how to motivate your team

The most research-backed answer to how to motivate your team comes from Self-Determination Theory (SDT), developed by psychologists Edward Deci and Richard Ryan, is one of the most robust frameworks for understanding human motivation at work.

The theory holds that people have three core psychological needs. When work satisfies all three, intrinsic motivation follows — people work because the work itself is meaningful. When these needs are frustrated, motivation declines regardless of perks, pay, or team culture.

Autonomy

Autonomy is the need to feel that you have meaningful control over how you do your work. It is not the absence of direction — it is the experience of acting from your own values and judgment rather than pure external compliance.

Practically, autonomy comes from: being trusted to determine your own approach, having genuine input into decisions that affect your work, understanding the why behind expectations rather than just receiving orders, and not being micromanaged.

Manager implication: The single highest-leverage thing most managers can do when thinking about how to motivate your team is to increase autonomy. Give people ownership over their methods, not just their tasks. Explain reasoning. Ask for input before deciding. Delegate more than feels comfortable.

Competence

Competence is the need to feel effective and capable — to be growing, to be challenged at the right level, and to do meaningful work well. People who feel stuck, bored, or chronically in over their heads experience competence frustration, and motivation drops.

This is why "easy" work demotivates skilled people just as much as impossible work does. The sweet spot is challenge calibrated to capability: work that stretches without overwhelming.

Manager implication for how to motivate your team: Regularly ask people what they find most engaging and what feels like wasted time. Assign stretch work deliberately. Invest in development conversations. When someone's competence clearly exceeds their role, address it — either by expanding their scope or being honest about the timeline for a change.

Relatedness

Relatedness is the need to feel meaningfully connected to the people around you and to a purpose larger than yourself. It is not about being friends with everyone on the team. It is about feeling seen, valued, and part of something that matters.

Teams with high relatedness recover from setbacks faster, share information more freely, and cover for each other more generously. They also tend to retain people better, because the social bonds become part of why someone stays.

Manager implication: Invest in the quality of relationships on your team — in 1-on-1 meetings, in how you create space for people to be known beyond their job titles, and in connecting work explicitly to the impact it has on others.

Expectancy Theory: another lens on how to motivate your team

Another powerful framework for how to motivate your team is Expectancy Theory, developed by psychologist Victor Vroom, models motivation as a rational calculation. According to Vroom, motivation is the product of three beliefs, each of which must be present:

Expectancy: "Can I do this?" — the belief that your effort will lead to successful performance. If people believe they will fail regardless of how hard they try, they stop trying.

Instrumentality: "If I do it well, will I be rewarded?" — the belief that good performance leads to a meaningful outcome. If the link between performance and reward is unclear, inconsistent, or absent, the incentive to perform well disappears.

Valence: "Do I actually care about that reward?" — the perceived value of the outcome. A reward that nobody values is not a motivator, regardless of its cost.

Manager implication for how to motivate your team: Motivation failures often trace back to one of these three beliefs breaking down:

• Low Expectancy: people need clearer development support, better-calibrated expectations, or more direct encouragement that they can succeed.
• Low Instrumentality: the link between performance and outcome is unclear or has been broken by inconsistent follow-through. Rebuild it by being explicit and reliable.
• Low Valence: the incentive on offer is not what people actually want. Ask what matters to them rather than assuming.

Designing motivating work: a key part of how to motivate your team

If you want to know how to motivate your team through the work itself, Hackman and Oldham's Job Characteristics Model (JCM) is the most practical framework identifies five features of a job that predict whether the person doing it will find it intrinsically motivating.

Skill variety

The degree to which the job requires using different abilities and skills. Highly repetitive work with narrow skill requirements tends to become demotivating over time, even for people who were initially engaged.

Manager action: Look for ways to expand the range of skills someone's role draws on. Cross-functional projects, new responsibilities, and stretch assignments all increase skill variety.

Task identity

The degree to which the job involves completing a whole, identifiable piece of work from beginning to end. People are more motivated by projects they own fully than by fragments of a larger process where their contribution feels invisible.

Manager action: Where possible, give people full ownership of an outcome rather than a narrow slice of it. Make the connection between their contribution and the final result explicit.

Task significance

The degree to which the job has meaningful impact on others — whether colleagues, customers, or the broader organisation. Work that feels consequential is more motivating than work that feels arbitrary.

Manager action: Regularly connect the work to its impact. Not just at strategy meetings — in 1-on-1s, in team check-ins, in the language you use every day. "This matters because..." is one of the most underused sentences in management.

Autonomy

The degree to which the job gives freedom and discretion in how it is done. This overlaps directly with SDT's autonomy dimension and is one of the most consistent predictors of motivation in the research.

Feedback

The degree to which doing the job itself provides clear information about how well you are performing — not just manager feedback, but feedback built into the work itself.

Manager action: Build feedback loops into the work wherever possible. Dashboards, regular reviews, visible metrics, and direct contact with the people affected by someone's work all increase motivation through the feedback dimension.

What does not work when you're thinking about how to motivate your team

Perks and amenities. Free lunches, gym memberships, and flexible hours reduce dissatisfaction when absent, but they are hygiene factors, not motivators. They address the environment, not the nature of the work.

Praise without substance. Generic positive feedback ("great job!") has minimal motivational effect. Specific, timely recognition of what someone did and why it mattered has a significant effect.

Competition between team members. Internal competition can increase short-term individual performance but tends to reduce relatedness, information-sharing, and team cohesion — particularly in complex, interdependent work where collaboration is required.

Motivational speeches. A one-off talk inspires for a day. Consistent management behaviour — autonomy, meaningful work, real feedback, genuine care — builds motivation that lasts.

How Lead-well helps you figure out how to motivate your team

Lead-well's coaching chat helps managers think through specific challenges around how to motivate your team: a team member who seems disengaged, a role that has become stale, a situation where effort and reward have become decoupled.

The weekly reflection prompts include questions about team energy — not just whether things got done, but whether your team seemed engaged, drained, or somewhere in between. Tracking this over time helps you notice patterns before they become retention problems.

10 things managers can do this week to improve team motivation

1. Ask one team member what part of their work they find most draining — then see if you can change it
2. Explain the why behind a decision you'd normally just communicate — autonomy starts with understanding
3. Give someone ownership of an outcome, not just a task — hand over the method too
4. Identify one person who's operating below their capability — give them something that stretches them
5. In your next 1-on-1, ask "what would make your work feel more meaningful?"
6. Connect the team's work to someone it affects — a customer story, a downstream impact, a result that matters
7. Check the reward link: does good performance visibly lead to anything the person values?
8. Name a specific contribution out loud — not "great work" but what they did, why it mattered
9. Ask: is there anything I'm doing that makes your work harder than it needs to be?
10. Review roles: is anyone doing the same thing for so long that competence has become boredom?

For more on the relationship layer underneath motivation, see our guide on building psychological safety — teams that feel safe also tend to feel more motivated.

Frequently asked questions