Ways of Working

Wellbeing & Sustainable Pace

Foundational

Building software is a long effort that runs over years. A pace you cannot keep up is not really fast. It borrows speed from next month and pays it back later through burnout, bugs, and people leaving. Protect your own wellbeing and your colleagues', because tired people build worse software and exhausted teams do not last.

A sustainable pace is an engineering concern, not a perk. Tiredness damages exactly the skills our work depends on: judgement, attention to detail, and care. In our work, a missed check can mean a compliance breach or a security hole, so a tired engineer is a risk. The rush to ship a feature this week often causes the incident next week.

Wellbeing is also a shared concern. A culture that quietly rewards overwork punishes the people who set healthy limits, and burns out the people who do not. Looking after yourself, and noticing when a colleague is struggling, is not laziness. It is how a team stays capable and humane over the long term.

Work sustainably

DoWork at a pace you could keep up for a long time. Steady and sustainable beats fast and short-lived.
DoTake real breaks, rest, and time off. Stepping away is part of doing good work, not time taken from it.
DoSet and respect limits around working hours. Do not make others feel they must always be available.
DoTreat ongoing overtime as a sign of a planning or scoping problem to fix, not something to celebrate.
ConsiderProtecting focus time and reducing context-switching. Scattered attention is its own kind of exhaustion.
Do notPraise overwork or self-sacrifice, or make people feel they must overwork to keep up. It only burns out the team and lowers quality.

Look after each other

DoNotice when a colleague is overloaded or struggling, and offer help or raise it. People under strain rarely ask.
DoMake it safe to say "I am at capacity" or "I need a break" without it being seen as weakness.
DoRespect that people have lives, time zones, and commitments outside work. Plan around them, not against them.
ConsiderDesigning on-call and incident response to be humane: enough people in the rotation, time to recover, and no one left to cope alone.
Do notReward the person who never logs off while ignoring the steady, sustainable contributor. You will lose the steady one.
Do notLet urgency become permanent. A team always fighting fires is a team about to lose people.

Self-review checklist

AskCould I keep up this pace for a year, or am I borrowing against next month?
AskAm I so tired that my judgement on this security- or compliance-sensitive work is weaker than it should be?
AskIs anyone on the team quietly overloaded or heading for burnout?
AskIs repeated overtime here a personal push, or a planning problem we should fix?

Why it matters: Burnout is costly and slow to undo. It costs us experienced people, hard-won knowledge, and the careful attention that safety-critical, regulated software needs. A sustainable pace keeps judgement sharp, defects low, and the team together. Over any real timeframe, that ships more and better work than crunch ever does.