The Week Was a Data Point, Not a Verdict.
There is a version of collapse that looks like failure. There is another version that looks like information. Learning to tell them apart, and to stop doubling down when stopping is the more honest response, is some of the most important work an ADHD brain can do.
There was a week last year where everything fell apart at the same time.
Three major client deliverables, all of them real and all of them due. An important launch on a software platform that kept falling over at the worst possible moments. An HR problem that had been building quietly for weeks and chose that week to become urgent. A relationship that needed more than I had available, and knew it, and wasn’t wrong to need it. A body that had been running on four hours of sleep for longer than I’d admitted and had quietly, without announcement, stopped cooperating.
It was the kind of week that, in retrospect, was inevitable. Not because of bad luck or unusual circumstances, but because of arithmetic. The math just stopped mathing. I had made commitments that, in aggregate, exceeded the capacity of the system making them. The week was the bill arriving.
The old version of me knew exactly what to do with a week like that.
Double down. Push harder. Sleep less, or not at all. Tell myself to do better, absorb the cost personally and attempt to recover ground over the weekend through sheer force of continued effort. Treat the collapse as a failure of will and respond with more will.
I have done this many times. I know what it produces. A few days of borrowed output, followed by a longer and harder crash, followed by the slow reassembly of a system that is slightly more fragile than it was before. The arithmetic doesn’t change. The debt compounds.
What I did instead, that week, was something I am still, honestly, working out how to do reliably.
I stopped.
What stopping actually looked like
Not gracefully. Not according to any plan. The stopping happened because I finally, partway through a Wednesday that was going nowhere, recognised the pattern rather than just experiencing it.
This was the crash. The one that always followed the sprint. The inevitable consequence of months of operating on urgency and adrenaline and the particular ADHD skill of producing things at the last possible moment through sheer pressure-generated focus. I had been running the sprint model, which works, up to a point, and the point had arrived.
Recognising it as a pattern rather than as an isolated catastrophe changed what felt possible. A catastrophe requires pushing through. A pattern requires understanding.
I cancelled what I could cancel. Not everything. Some commitments were real and had real people on the other side of them. But some of the urgency I had been operating under was manufactured, or at least negotiable, and I had been treating negotiable urgency as fixed because challenging it would have required an honest conversation I had been avoiding.
I had those conversations. They were uncomfortable and shorter than I’d feared. Most people, when told honestly that something needs to move, respond to honesty better than to the increasingly strained performance of having everything under control.
I communicated honestly about the rest. Not with excessive apology or elaborate explanation, but with enough transparency that the people affected could make informed decisions about what they needed to do. Honesty, I have found, is almost always less costly than the energy required to maintain the fiction that everything is fine when it isn’t.
And then I slept. Properly, for several nights in a row, which sounds like the most basic thing imaginable and which I had not done in longer than I wanted to count.
“A catastrophe requires pushing through. A pattern requires understanding. Recognising which one I was in changed what felt possible.”
What I did with the week after
When I had slept enough to think clearly, I did something I had not done with previous versions of this week.
I looked at the conditions that had produced it. Not to allocate blame, not to generate a punishing post-mortem about everything I had done wrong, but to understand, as specifically as possible, what structural features of the preceding months had made that week inevitable.
This is a different activity from the self-criticism that usually follows a collapse. Self-criticism is often thorough about identifying that something went wrong and useless about identifying what. It produces shame, which is not actionable, rather than information, which is.
What I was looking for was the design flaw. The thing about how I had been operating that, continued, would produce the same result again. Not my personal failings but the structural conditions: the commitments I had said yes to when the honest answer was not yet or not without something coming off, the warning signals I had read as temporary and turned out to be directional, the recovery time I had not built in because building it in would have required admitting the sprint was a sprint.
Several things were visible from that vantage point that had not been visible during the weeks that produced them. The pattern of taking on work when the novelty of the ask was high and the actual delivery date was far enough away to feel abstract. The way certain kinds of professional obligation had been expanding quietly into time I had notionally protected for other things. The body signals, the particular quality of exhaustion that meant the system was running on reserve, that I had been overriding for weeks.
None of this was new information exactly. But it was newly useful, because I was approaching it as a question about design rather than a question about character.
The honest part about the cycle
There is something I want to be honest about, because my LinkedIn post on this a while back said it briefly and I think it deserves more space.
There is something perilously thrilling about the sprint-and-crash cycle. Not the crash itself, which is genuinely awful. But the sprint. The particular quality of focus that crisis-driven urgency generates in an ADHD brain. The way everything else falls away and the work becomes the only thing. The output that emerges in those conditions, which is often genuinely good, sometimes better than what more measured working produces.
This is not imaginary. The ADHD brain under genuine urgency accesses a mode of engagement that is real and productive and, in the moment, feels like exactly what the brain is built for. Which is, in a limited sense, true. Urgency does generate dopamine. The focus is neurologically real. The work is often worth something.
What is also true: this mode is expensive. It runs on cortisol and sleep debt and the depletion of relational and physical reserves that accumulate cost over time. The crash is the invoice. And the invoice gets larger with each cycle, because the recovery is never quite complete before the next sprint begins. For women specifically, that invoice can grow faster in midlife, as fluctuating oestrogen withdraws some of the neurological support the sprint has been relying on, which is part of why so many women are only diagnosed with ADHD in perimenopause.
I am not free of the appeal of the cycle. I would be lying if I said the sprint holds no attraction. But I have updated my understanding of what it costs, and that update has changed my relationship with it. The question is no longer ‘can I sustain this’ in the moment of the sprint. It is ‘what is the cost of this’ before I begin.
“The question is no longer can I sustain this, in the moment of the sprint. It is what is the cost of this, before I begin.”
Why the distinction matters: data point versus verdict
The most useful shift in that week, and the one I have returned to many times since, was the reframe that the week was a data point rather than a verdict.
A verdict is a conclusion about character. It says: this is who you are, this is what you are capable of, this is the pattern that will always emerge. Verdicts are static. They close things down. They generate shame, which produces avoidance, which makes the pattern more likely rather than less.
A data point is information about conditions. It says: under these circumstances, this is what happened. It leaves open the question of what different circumstances might produce. It is specific rather than global, actionable rather than merely painful.
The ADHD brain is particularly vulnerable to the verdict interpretation of collapse, partly because collapse tends to happen in visible ways that other people notice, and partly because a lifetime of being told you are inconsistent or unreliable or a bit of a disaster gets internalised into a story about who you are that the difficult week seems to confirm.
Resisting the verdict interpretation requires a specific kind of discipline that has nothing to do with working harder. It requires asking, in the aftermath of something going wrong, not ‘what does this say about me’ but ‘what does this tell me about the system and what it needs to be different.’
Those are genuinely different questions. They produce different things. The first produces shame and the impulse to double down. The second produces information and the possibility of a better design.
Working on the right problem
I said in my LinkedIn post that I am still working on building a life where the sprints don’t require the crashes. This is true. I want to be clear that still working on it is not the same as making no progress.
The change is not that the sprint-and-crash cycle has disappeared. It is that I recognise it earlier, respond to it differently, and use the aftermath as design information rather than as evidence of personal failing. That is genuinely different from where I was.
The other change is that I am asking more honest questions at the front end. Before saying yes to something, before adding a commitment to a system that is already carrying what it can carry, before telling myself that this particular urgency is manageable when the honest answer is that it will cost something I haven’t accounted for. The questions are: what does this require, what does it displace, and is the arithmetic honest.
This sounds more straightforward than it is for an ADHD brain. The novelty of a new commitment activates exactly the neurological systems that make honest capacity assessment difficult. The interesting thing is always more compelling than the accounting. I know this about myself, which means I have built some external structure around the yes, a pause, a conversation, a specific question asked of someone who knows the system well enough to see what I might be missing.
None of this is a cure for a brain that runs hotter than the culture expects and needs more recovery than the culture allows. It is a better design. Built not around the person I thought I should be, but around the person I actually am, with the brain I actually have, operating in the conditions I can actually sustain.
The week was a data point. I’m still using it.
REFLECT
“When things collapse, do you tend to push through or stop, and has that changed over time?”
If the sprint-and-crash cycle is a pattern you recognise, coaching is a useful place to examine what the arithmetic actually is and what a different design might look like. A free 25-minute discovery session is the place to start.