- Limits and Humility — Learning to Be Finite
- Designing Within Constraints
- Blessed Are the Poor in Spirit (Matt 5:3)
- Avoiding Tech Arrogance: A Posture of Learning
- The Strength Found in Weakness
- When to Say “No”: Project Limits & Sanity
- Humbling Ourselves Before God (1 Pet 5:6)
- Burnout & Overwork: The Cost of Ignoring Limits
Burnout is often treated as a personal failure.
Someone could not cope.
Someone lacked resilience.
Someone needed to manage their time better.
But burnout rarely begins with one person making one poor choice. More often, it grows within systems that repeatedly demand more than people can sustainably give.
In technology, this can be easy to normalise.
Long hours are praised as commitment. Late-night releases become stories of dedication. Being permanently available is treated as professionalism. Teams celebrate the person who rescues the project, while quietly ignoring why the project needed rescuing.
Yet human beings are not infinitely scalable resources.
Ignoring that limit carries a cost—not only for individuals, but for quality, security, judgement and the long-term health of the organisation.
Burnout Is More Than Tiredness
Everyone becomes tired after demanding work.
Rest usually restores ordinary tiredness.
Burnout is deeper. It can involve emotional exhaustion, detachment, reduced effectiveness, irritability, difficulty concentrating and a growing sense that even simple tasks require enormous effort.
People may continue working while burnt out. From the outside, they may still appear productive. But the work often costs more internally, and recovery becomes harder.
This is one reason burnout can remain hidden.
The person still attends meetings.
Still answers messages.
Still completes enough work to avoid immediate concern.
But their capacity is gradually shrinking.
Technology Encourages Limitless Expectations
Software runs continuously.
Cloud services remain available day and night.
Automated systems process work without rest.
It is easy to allow these characteristics of technology to shape expectations of the people maintaining it.
Because the service is always available, the team is expected to be always available.
Because messages can be sent instantly, replies are expected instantly.
Because deployments can happen at any hour, someone is expected to be ready at any hour.
Technology can extend human capability. It should not erase human need.
A twenty-four-hour service requires planned coverage, sufficient staffing and genuine recovery time. It cannot safely depend upon the same small number of people remaining permanently alert.
Heroics Hide Weak Systems
Many organisations have a hero.
The person who knows every part of the system.
The person called whenever something fails.
The person who stays late, cancels plans and gets the release over the line.
Their contribution may be real and valuable. But the system around them may also be dangerously dependent.
Hero culture disguises structural weakness as individual excellence.
If one person cannot take leave without causing concern, knowledge is too concentrated.
If every incident requires the same expert, documentation and training are inadequate.
If deadlines are met only through repeated overtime, planning is unrealistic.
The goal should not be to find more heroic people.
It should be to build systems that do not require heroics as normal practice.
Overwork Reduces Quality
Extra hours may appear to create more output.
Sometimes, over a very short period, they do.
But technical work depends upon attention, judgement and memory. As fatigue increases, these begin to deteriorate.
People overlook edge cases.
Misread requirements.
Skip documentation.
Make risky assumptions.
Introduce defects that require later repair.
The organisation may gain several hours of visible activity while creating days of hidden rework.
This is particularly dangerous in work involving security, permissions, financial data, health information or critical infrastructure. A tired decision can have consequences far beyond the individual who made it.
Sustainable working is therefore not merely a wellbeing benefit.
It is a quality-control measure.
The Endless Urgent Queue
Burnout grows easily where everything is urgent.
When every request has the highest priority, teams lose the ability to distinguish genuine emergencies from ordinary pressure.
The result is constant interruption.
Long-term work stalls because urgent tasks repeatedly displace it. Maintenance is postponed. Documentation remains unfinished. Staff spend their time reacting rather than improving the conditions that create the emergencies.
A healthy system needs a clear definition of urgency.
What requires immediate response?
What can wait until the next working day?
Who decides?
What work will be displaced?
Without these answers, urgency becomes a way of transferring poor planning onto whoever is most available.
On-Call Work Needs Real Recovery
On-call responsibilities are sometimes necessary.
Systems fail outside office hours. Users may depend upon essential services. Security incidents cannot always wait.
But on-call work must be designed honestly.
Being on call affects rest even when no alert arrives. The possibility of interruption changes how a person sleeps, travels and spends time with family.
When an incident does occur, the hours worked should not simply be added to an ordinary working day as though nothing happened.
Teams need adequate rotation, clear escalation paths, useful runbooks and recovery time after significant incidents.
An on-call arrangement that depends upon goodwill rather than structure will eventually consume the goodwill.
Burnout Is Not Solved by Resilience Training Alone
Resilience can be valuable.
People benefit from healthy routines, supportive relationships, boundaries and practical strategies for managing stress.
But resilience should never become a way of teaching people to endure conditions that should change.
A breathing exercise cannot repair chronic understaffing.
A wellbeing webinar cannot compensate for permanent overtime.
A time-management course cannot solve a workload that exceeds the available hours.
When organisations respond to structural overwork only with individual coping advice, responsibility is placed on the person experiencing the harm.
The question should not only be, “How can this person become more resilient?”
It should also be, “Why does this work require such resilience to survive?”
Warning Signs in Teams
Burnout may appear gradually across a team.
Warning signs can include:
- increasing irritability or cynicism,
- repeated mistakes from experienced staff,
- people working while ill,
- reluctance to take leave,
- constant messages outside normal hours,
- falling participation in meetings,
- unresolved conflict,
- growing dependence upon a few individuals,
- and good staff quietly leaving.
No single sign proves burnout. But patterns should not be ignored.
Leaders need to create conditions where people can speak honestly before reaching crisis.
If admitting overload is interpreted as weakness, people will continue hiding it until they can no longer do so.
Boundaries Need Organisational Support
Individuals are often advised to set boundaries.
Do not answer emails late at night.
Take lunch breaks.
Use annual leave.
These are sensible practices, but they work only when the surrounding culture respects them.
A person cannot maintain a boundary if promotion depends upon breaking it.
Annual leave is not restorative if work accumulates untouched and returns as punishment.
A no-message policy is meaningless if senior leaders continue sending urgent requests at midnight.
Healthy boundaries need visible support from leadership.
Managers must model them, not merely recommend them.
Sustainable Pace Does Not Mean Low Standards
Some people hear “sustainable pace” and imagine reduced ambition.
But sustainability is not the absence of hard work.
There will be demanding periods. Launches, migrations and incidents may temporarily require extra effort.
The key word is temporarily.
A sprint cannot remain a sprint forever.
After an intense period, teams need recovery, reflection and improvement. Otherwise exceptional effort becomes the new baseline.
Sustainable teams can still achieve difficult things. They do so by planning capacity honestly, prioritising carefully and refusing to treat exhaustion as evidence of commitment.
Recovery Takes Time
Burnout is easier to prevent than to repair.
A weekend may not be enough.
A short holiday may provide relief without restoring full capacity.
Recovery can require reduced workload, medical support, counselling, changed responsibilities and a longer period of rest.
Returning too quickly to the same conditions often restarts the cycle.
Organisations should resist the temptation to ask when someone will be “back to normal” without examining whether normal was the problem.
Recovery is not only about helping a person return.
It is about ensuring they are not returned to the same machinery that exhausted them.
Designing Healthier Technical Work
Healthier systems are built through practical choices.
Document important knowledge.
Share ownership of critical services.
Limit work in progress.
Plan for leave and sickness.
Build realistic contingency into deadlines.
Review on-call demand.
Track repeated incidents and remove their causes.
Give teams uninterrupted focus time.
Make after-hours communication exceptional rather than routine.
Ask what should stop before adding new work.
These practices may appear less dramatic than rescuing a failing release at midnight.
But they create something more valuable: reliable work that can continue without consuming the people who perform it.
The Invitation
Look honestly at the way your work is organised.
Does success depend upon people regularly exceeding healthy limits?
Are the same individuals repeatedly rescuing projects?
Does every deadline become an emergency?
Can people take leave without anxiety?
Are mistakes being treated only as personal failures, or also as signs of overloaded systems?
Burnout should not be accepted as the natural price of working in technology.
People are not replaceable components.
Their attention, experience and creativity are gifts that require care.
Respecting human limits does not weaken technical ambition.
It protects the judgement needed to achieve it.
The strongest teams are not those that can survive endless pressure.
They are those wise enough to recognise that endless pressure should never have become normal.
