Saturday mornings have, at various points in my career, been the most accurate diagnostic of the week that preceded them. Not because anything significant happened on Saturday mornings — they were largely unremarkable, domestic, ordinary. But because the quality of a Saturday morning — the specific texture of how it felt to have nothing required of you for a few hours — reflected something precise about the preceding five days that the working week itself had not made visible.
There is a specific kind of exhaustion that does not come from overwork. It is not the tiredness of having done too much. It is the tiredness of having done a great deal and felt, at the end of it, that not enough of it mattered. That is a different fatigue entirely, and it requires a different response.
What It Is Not
It is not burnout in the clinical sense, though it can precede it. It is not overwork — the hours may be reasonable. It is not unhappiness, exactly, because the work is being done competently and the outputs are being delivered and by most external measures things are fine. It is not a crisis. That is partly what makes it hard to address: there is no obvious point of intervention.
I have experienced it most acutely in the middle of large programmes — not at the beginning, when the challenge is new and the stakes feel real, and not at the end, when the proximity of completion provides its own energy. In the middle, when the work is substantial and the end is not yet visible and the days have a certain sameness, and Saturday morning arrives and you realise that you are not sure, looking back at the week, what you actually built. What exists now that did not exist on Monday. The work happened. Something is hard to locate.
The absence of visible output is not the same as the absence of value. But at a certain level of abstraction — governance, programme management, strategy — the connection between the effort and the thing that exists because of it becomes genuinely difficult to see. That difficulty has a cost that accumulates quietly.
What Sustains People Who Last
The people I have observed sustaining genuine engagement and effectiveness over long careers in technology leadership share certain habits that I have come to think are not incidental. They maintain a direct connection to the technical work — not managing it from a distance, but staying close enough to understand it, to have a view on it, to be genuinely curious about it. They protect time for the work that feels like progress, not just the work that is required. They notice the Saturday morning problem early, before it has compounded, and they treat it as a signal rather than something to push through.
They also, almost universally, have things outside the work that are unambiguously theirs — where the connection between effort and outcome is immediate and visible. A physical practice. A creative pursuit. Something that produces something you can see or hold. I have noticed that the people who go longest without anything like this tend to be the ones for whom the Saturday morning problem becomes most acute.
What to Do With It
The honest answer is that there is no single solution, and the people selling one should be regarded with some scepticism. What there is, instead, is a set of practical adjustments — each small in itself — that address the underlying disconnection. Seeking out the work that has visible output even in senior roles. Being deliberate about the proportion of the week spent in meetings versus in actual technical engagement. Recognising, at programme level, the points where the work becomes abstract enough to require deliberate grounding in concrete reality.
And, for people at the level where the Saturday morning problem most commonly presents: accepting that the feeling is information. Not a crisis. Not a failure. Information about something that needs attention — and attending to it before it becomes a crisis, which it eventually will if it is ignored long enough.
A fifty-year career in technology is not built by being impervious to this kind of exhaustion. It is built by developing the capacity to notice it, to name it accurately, and to make the specific adjustments — small, practical, often counterintuitive — that reconnect the work to the thing that made it worth doing in the first place.
The Saturday morning problem is not a problem to be solved. It is a signal to be read. The people who last longest are the ones who learned to read it early.