The team has heard another encouraging speech. The backlog is still growing, priorities still compete and the same people still receive public credit. It is tempting to describe the result as a motivation problem. Sometimes it is a problem of workload, fairness or credibility. Start with conditions you can investigate rather than an attitude you think you can see.
Check capacity before enthusiasm
Ask what is on the team’s plate, what is genuinely urgent and what can stop. Include work that is easily overlooked: helping new starters, handling interruptions, maintaining documentation and repairing avoidable errors. A plan that counts only visible deliverables can make capable people look slow while they keep the system functioning.
When demand exceeds capacity, make the trade-off explicit: reduce scope, extend time, add appropriate resources or accept a clearly assessed risk. “Try harder” is not a capacity plan. If you cannot authorize the change, take a specific decision request to the person who can and explain what remains unresolved.
Offer autonomy with clear boundaries
Edward Deci and Richard Ryan’s self-determination theory highlights autonomy, competence and relatedness as important psychological needs. In workplace practice, autonomy does not mean leaving people without direction. It means offering meaningful choice within real constraints, with enough context to make a sound decision.
Clarify the outcome, non-negotiable requirements and points where approval is needed. Then ask where the person wants discretion: sequencing, method, collaboration or how progress is shared. Do not offer a choice that will be overruled for an unstated reason. Apparent autonomy followed by surprise correction can undermine trust.
“Just own it. I do not want to be involved.”
“You can choose the approach within this budget. Bring me any change affecting the customer commitment.”
Make competence easier to build
Repeated struggle can look like low effort when the actual issue is unclear standards or missing practice. Show what good work looks like, make examples available and create room for questions before a high-stakes deadline. Ask which part feels uncertain rather than whether someone is “confident enough.”
Support should match the task and experience level. A new colleague may need a demonstration and a short check-in; an experienced colleague may need access to a specialist or a blocked decision removed. Avoid turning every learning need into surveillance. Agree how support will taper as capability grows.
Notice progress without manufacturing positivity
Teresa Amabile and Steven Kramer’s The Progress Principle draws attention to the importance of progress in meaningful work. A practical application is to make small, real advances visible: a recurring error removed, a difficult handover improved or a customer problem understood more clearly.
Do not require a cheerful story when the week was difficult. A progress discussion can acknowledge a blocked task and still identify useful learning. Ask, “What moved forward, what got in the way, and what decision would help?” This keeps attention on the work rather than the performance of optimism.
Recognize contribution fairly
Recognition is information about what the team values. If only presentation work is celebrated, maintenance and coordination can become invisible. Look for whose contribution gets named and whose gets absorbed into someone else’s success. Credit specific work without implying that one person delivered a collective outcome alone.
Ask how people prefer to receive appreciation. Public praise, a private message, development opportunities and appropriate compensation are not interchangeable. Appreciation does not replace fair pay, reasonable workloads or access to advancement. Avoid praising repeated overwork as the standard everyone should follow.
Protect belonging without demanding sameness
Relatedness is not a requirement to socialize in a particular way. Teams can support connection through dependable handovers, respectful responses and access to information. Optional events should not become an unofficial test of commitment, especially when caring responsibilities, disability, religion or distance affect participation.
For remote and hybrid teams, write down decisions and share context where everyone can access it. People should not need to be near the loudest conversation to understand what changed. Check whether meeting times and informal opportunities consistently favor the same group.
“Which part of your work feels worthwhile, which part drains effort without helping, and what is one condition we could change?”
Take exhaustion seriously
Persistent exhaustion, distress or a marked change in functioning deserves care, not an amateur diagnosis. Ask about work demands, available adjustments and appropriate support. Respect privacy and avoid asking for unnecessary medical details. The World Health Organization describes burnout as an occupational phenomenon; that description is not a tool for diagnosing a colleague.
Where health, disability or leave issues arise, involve the appropriate organizational process and qualified support. If immediate safety is at risk, use local emergency or urgent support services. A manager’s task is not to become a therapist, but to respond responsibly within their role.
Try one change and review it honestly
Choose a condition you can influence, such as reducing competing priorities or making recognition more specific. Agree how you will know whether it helps and invite a candid review. Do not convert every check-in into a motivation score. The aim is better work and more sustainable effort, not a new way to monitor mood.
For background, explore self-determination theory, Amabile and Kramer’s work, Daniel Pink’s Drive, and the World Health Organization. Popular frameworks can prompt questions; they do not replace local evidence or individual preferences.