The Cost of Running Hot
Sustained high load is not a badge of honour. It is a system operating outside its design parameters. Eventually, something gives.
Every system has a thermal envelope.
Push a processor past it for long enough and it does not just slow down. It damages itself. The degradation is quiet at first: a few dropped frames, a slightly longer response time, occasional instability under load. Then, at some point, it fails in a way that is much harder to recover from than the original overload would have been.
This is not a metaphor for people in cyber and tech. It is a description.
The culture in security and operations has, for a long time, treated running hot as desirable. The person who works the most hours, responds the fastest, stays on incident the longest, these are marks of commitment, competence, seriousness.
But there is a difference between high performance and sustained overload. One is a capability. The other is a failure mode you have not hit yet.
What overload actually looks like
The problem with operating above your sustainable load is that the early signs are easy to rationalise. You are tired, but so is everyone. You are less sharp than usual, but the pressure is real and external. You are making slightly worse decisions, but who would not under these conditions?
This rationalisation is the feedback loop that makes burnout hard to catch in yourself. The very capacity you would use to assess your own state, your judgement, self-awareness, perspective, is what the overload degrades first.
You do not notice you are running hot because running hot has impaired your ability to notice.
The load you cannot see
There is a category of load in cyber and security work that never shows up in ticket counts or incident logs. It is sometimes called cognitive load or moral load or just the weight of the work.
It includes:
- Holding knowledge that most people cannot or do not want to hold
- Being responsible for things that, if they go wrong, affect other people’s lives and livelihoods
- Working inside environments where the threat is real, ongoing, and partially invisible
- The baseline stress of being one of the people who is supposed to know what to do
This load does not clock out. It does not get resolved at the end of a sprint. It accumulates.
What happens when it gives
System failures under sustained load tend not to be dramatic. They tend to be quiet and gradual until suddenly they are not.
In people, it looks like: a slow withdrawal from the parts of work you used to find meaningful. An increasing flatness in response to things that used to matter. A reduced tolerance for ambiguity or change. A growing feeling that the gap between the effort you are putting in and the meaning you are getting out has become permanent.
These are not personality changes. They are state changes in a system that has been running outside its envelope for too long.
Recovery is not rest
The common prescription for burnout is rest. Stop. Take time off. Disconnect.
Rest is necessary, but it is not sufficient. A machine that has run hot and been damaged does not recover to factory settings just by being switched off. It may need inspection, component replacement, recalibration.
For people, recovery from sustained overload usually requires:
- Identifying and removing or reducing the sources of load, not just stepping away from the output
- Processing what happened during the overload period, not just what you did but what it cost
- Rebuilding the elements of identity and purpose that got eroded
Rest gets you functional. The rest of it gets you back.
Running hot is not strength. It is a system under conditions it was not designed for, doing the best it can, spending reserves it did not know it had.
The breakpoint is not the failure. The breakpoint is the thing that could have prevented it.
Insert one deliberately.