Restoring Team Energy

Low team energy is easy to label as a motivation problem. That label can be too shallow. Before trying to inspire people, inspect the work itself: workload, work pace, role clarity, decision authority, conflicting priorities, support and the ability to see progress.

The goal is not to diagnose employees. It is to diagnose the conditions in which the work is being done.

The International Labour Organization identifies workload and work pace, limited job control, unclear roles, poor organizational communication and conflicting work demands among factors that can contribute to psychosocial risks at work.

That does not mean every tired employee has a workplace disorder or that every low-energy team has the same cause.

It means founders have concrete operating conditions they can inspect.

Ask:

• Are too many priorities active at the same time?
• Are priorities changing before work can finish?
• Does one person have responsibility without decision authority?
• Are roles unclear?
• Is work repeatedly being redone?
• Are people waiting for founder decisions?
• Is the team working longer because the system is poorly designed?
• Can people see what progress looks like?

These questions are more actionable than simply asking whether people feel motivated.

The ILO's guidance treats excessive or unmanageable pressure, workload, work pace, limited control and unclear roles as relevant workplace risks and recommends prevention through risk assessment, better communication, worker participation and greater control over tasks.

The American Psychological Association's 2024 Work in America survey found that 67% of workers reported at least one outcome often associated with workplace burnout in the previous month, including low interest, motivation or energy. The survey is not a diagnostic instrument for an individual team, but it is useful context for why founders should not dismiss sustained low energy as a character problem.

The management implication is straightforward:

Before asking people to give more energy, check whether the work system is consuming energy unnecessarily.

A team can look busy while making little progress.

A common pattern is:

1. A project receives a priority.
2. An urgent request interrupts it.
3. Another project becomes urgent.
4. Work is paused.
5. The original task resumes later.
6. Context has to be rebuilt.
7. Deadlines slip.
8. Management interprets the delay as low productivity.

A 2026 r/managers discussion describes a similar operator problem: one engineer reported being repeatedly pulled between production issues, compliance, product development and customer support, with multiple project switches making progress harder to maintain.

That is one person's experience, not proof of a universal productivity cost. It is nevertheless a useful example of why the operating system should be examined before the person is blamed.

Autonomy does not mean leaving people alone.

A useful role has:

• A clear outcome
• A defined owner
• A decision boundary
• Known constraints
• A feedback path
• A clear escalation point

If every routine decision returns to the founder, the team may appear slow because the decision system is centralized.

If people are given responsibility without the authority or information needed to act, accountability becomes frustrating rather than useful.

Do not solve a priority problem with a motivational speech.

For the next operating period, identify the few outcomes that genuinely matter.

When a new urgent request appears, ask:

What should stop or move to make room for this?

If the answer is "nothing," the team has not been given a priority decision. It has been given another demand.

This is where founder discipline matters. A team cannot create focus if leadership continually creates exceptions.

People should be able to answer:

• What are we trying to change?
• What does finished mean?
• Who owns it?
• What is blocking it?
• What changed this week?

Progress can be a shipped feature, resolved customer issue, completed sales stage, published research, reduced defect backlog or another concrete outcome.

Avoid turning activity into the only measure of contribution.

Someone attending eight meetings may be less valuable to the current objective than someone who removes one critical blocker.

A one-on-one should not become a status meeting.

Use a small set of questions:

1. What is taking more energy than it should?
2. What keeps getting interrupted or redone?
3. What decision are you waiting for?
4. Which priority is unclear?
5. What should we stop or simplify?
6. What do you need from me to move?

Then record the action.

If the same blocker appears repeatedly and nothing changes, the issue is no longer just communication. It is an operating-system problem.

Specific recognition can reinforce useful behavior. It should not be used to compensate for unreasonable workload, unclear expectations or poor management systems.

If the team is overloaded, saying "great work" while adding more work does not remove the cause.

Recognition is most useful when it is connected to the actual contribution: what changed, why it mattered and what behavior should continue.

Instead of launching a vague motivation initiative, change a few operating conditions for two weeks.

Priority: reduce active priorities.

Ownership: assign one clear owner to each important outcome.

Decisions: create a short list of decisions that no longer need founder approval.

Blocked work: review blockers twice a week.

Workload: identify repeated overtime, rework and context switching.

Progress: review outcomes rather than activity alone.

At the end of two weeks, ask whether the same friction remains.

If it does, investigate the underlying process rather than adding another motivational event.

Do not assume low energy means laziness.

Do not assume every problem is caused by the founder.

Do not diagnose burnout from a short conversation.

Do not assume a survey score tells you the cause.

Do not use a motivational program to hide a staffing, scope, process or priority problem.

Do not treat Reddit stories as representative evidence.

Use this sequence:

Low energy appears → inspect workload → inspect priorities → inspect role clarity → inspect decision authority → inspect support and recovery → change the system → measure again.

If the system is healthy and the problem remains, investigate other causes with the people involved rather than guessing from the outside.

This article connects to Restoring Team Energy, the One-on-One Template and the broader people-management problems around team structure, retention and feedback.

• International Labour Organization, "Psychosocial risks and stress at work": https://www.ilo.org/resource/psychosocial-risks-and-stress-work
• American Psychological Association, 2024 Work in America survey: https://www.apa.org/pubs/reports/work-in-america/2024
• APA 2024 Work in America report: https://www.apa.org/pubs/reports/work-in-america/2024/2024-work-in-america-report.pdf
• Reddit r/managers discussion on workload, context switching and competing priorities: https://www.reddit.com/r/managers/comments/1sbenlf/employee_trying_to_prevent_burnout_with_manager/

Reddit is used as qualitative operator experience, not as prevalence data or a diagnosis.

When team energy drops, first inspect the work system. Look at workload, priority changes, role clarity, decision rights, blockers and recovery. Then make a small operating change and observe whether the condition improves. Motivation is not something a founder can manufacture with a speech. The environment in which people work is part of the problem being managed.

Related reading: \2 · \2