What actually causes it
Burnout gets discussed as an individual resilience problem, which is convenient and mostly wrong. On small teams it is usually produced by four structural conditions, none of which is about the person experiencing it.
Work that never finishes. A backlog that grows faster than it is cleared removes the sense of completion entirely. People can sustain hard work with an end in sight almost indefinitely, and struggle with moderate work that has none.
Responsibility without authority. Being accountable for an outcome you cannot influence is one of the most reliably corrosive situations in work. It is common in small teams because ownership gets assigned faster than decision rights do.
No boundary between on and off. Not the number of hours, but the absence of any hours that are reliably not work. Being mentally on call at all times is exhausting even when nothing happens.
Everything is urgent. When nothing is prioritised, everything carries the same weight, and people cannot down-regulate. Constant low-grade urgency does more damage over months than an occasional genuine crunch.
The distinction that matters
Tired is a state that a weekend fixes. Burnt out is a state where the weekend makes no difference. If time off is not restoring someone, adding more time off is not the intervention.
The early signals
Output is a lagging indicator. It holds up long after the person is struggling, because conscientious people compensate. By the time work quality drops, this has usually been running for months.
The earlier signals are all about withdrawal from the optional:
- Fewer questions, and less pushback in meetings
- Contributions become shorter and more transactional
- They stop suggesting things
- Cynicism appears where it was not there before
- Small, uncharacteristic errors in routine work
- Working more hours while completing less
The most useful of these is the disappearance of pushback. Someone who used to argue about decisions and now agrees with everything has usually not come round to your view, they have stopped having the energy to disagree.
Structural fixes that work
Cap work in progress, not just workload
A limit on how many things a person can have open at once, typically two or three. When something new arrives, something else has to move out of progress explicitly.
Most people are not overloaded on total volume, they are overloaded on simultaneity. Five half-finished things cost far more than five sequential ones.
Two or three open itemsMake finishing visible
A weekly note of what actually got completed, by name. Not a status report to a manager, a record for the team.
On small teams, everything is continuous and nothing is ever launched, so completion is invisible unless someone deliberately marks it. That invisibility is a direct cause of the never-finishes feeling.
Weekly, by nameGive a real priority order
Not three number one priorities. A ranked list where someone can drop item four this week without asking permission.
The point is not the list, it is that people can stop doing something without it feeling like failure. Without permission to drop, everything stays open.
Ranked, not groupedProtect off-hours by modelling, not policy
Use schedule-send for anything written outside working hours. Do not reply to messages at midnight even when you are awake.
A written policy that says nobody must work late, from a manager who visibly works late, teaches people what the real expectation is. They believe what you do.
Schedule-send is the whole fixMatch authority to responsibility
For anything someone owns, be explicit about which decisions are theirs to make without asking.
The most draining position is being held accountable while having to seek approval for every change. It is also easy to fix, and costs nothing.
Write down what they can decide
When someone is already burnt out
Time off alone will not do it. They return to the same conditions and the recovery is gone within two weeks, which is often read as proof that they were the problem.
What helps: reduce the load genuinely rather than symbolically, narrow the scope so there is one thing to finish rather than six to hold, remove whatever specific responsibility they have no control over, and stop expecting them to be the person who absorbs the overflow.
Then talk to them about it directly rather than tiptoeing. People deep in this generally know exactly what is causing it and have not been asked. Asking, and then changing something visible within a week, does more than any amount of concerned monitoring.
If it is beyond what a workload change can address, say so and point them at whatever health support exists. That is a limit worth recognising rather than managing through.
The founder problem
On small teams the pattern usually starts at the top, and it does not stay there.
A founder who works every evening is not just risking their own capacity. They are setting the observed standard, and everyone calibrates against what they can see. The team will not believe a stated policy that contradicts your behaviour, and the more loyal they are, the more closely they will match it.
The uncomfortable version of this: if your team is burning out and you are working eighty-hour weeks, the intervention that matters most is not a wellbeing initiative. It is you visibly stopping at a reasonable hour, often enough that people believe they can too.
Frequently asked questions
- Is burnout just working too many hours?
- No. Hours are a factor but not the main one. Work that never visibly finishes, responsibility without the authority to change anything, and constant context-switching all produce burnout at ordinary hours. Plenty of people work long weeks without burning out when the work resolves and they can affect the outcome.
- What are the earliest signs?
- Withdrawal from optional things first: fewer questions, less contribution in meetings, cameras off, quieter in chat. Output usually holds up for a while before it drops, so waiting for a performance signal means waiting months too long.
- Does time off fix burnout?
- A holiday helps someone who is exhausted. It does not help someone who is burnt out, because they return to the same conditions and the recovery is gone within a fortnight. Time off is worth combining with a change to the workload they come back to.
- How do I stop my team working late without banning it?
- Change what you model rather than what you mandate. If you send messages at 11pm, people read availability into it regardless of what your policy says. Schedule-send is the single most effective intervention available to a manager.
- Is burnout different in a startup?
- The intensity is often accepted, which makes the signals easier to miss and harder to raise. Small teams also have no slack, so one person struggling immediately loads everyone else, and the whole thing compounds faster than in a large company.