Knowledge Work Has No Arena
Why execution collapses under sustained disruption. And why the problem was never discipline.
And that’s not a personal failure. It’s a structural one.
1. What I believed
You already know how this goes.
A new system. A clean start. Time blocks, routines, the right tools finally arranged in the right order. It works for a week, maybe two. Then one thing shifts. A project gets complicated. Life gets louder. The system doesn’t bend. It evaporates.
And the conclusion you draw is the one almost everyone draws, is that you weren’t disciplined enough to maintain it.
I drew that conclusion for years. I was wrong about what the problem was.
2. What reality did
Between February and March 2026, I ran an extended stress test. Not on purpose, life just happened.
February 19th, Ramadan started. That means waking between 4:00 and 4:30am to eat and drink coffee before the Fadjr (dawn) window closes. Less sleep. Significantly less caffeine across the day. For someone with ADHD, that’s not just inconvenient. It’s a direct hit to the regulation system that makes focused work possible.
My chronotype makes it worse. According to Dr. Breus’s Chrono Quiz, I’m a Wolf. Biologically wired to peak late. Waking at 4:30am isn’t just early. It’s structurally wrong. My brain doesn’t want to go to sleep early and doesn’t want to wake up at that time, let alone function.
On top of that: a new client. Full days on-site, three days a week, two hours of commute each way. The client speaks Swiss-German. Not German, Swiss-German. For me, a Dutch guy two years into Switzerland? German already costs more cognitive energy than working in his native language. Swiss-German costs even more. Every meeting, every hallway exchange, ran on a higher-effort setting than it looked from the outside.
Meanwhile: Startup Campus every Wednesday evening until 21:45, with a full-day Saturday bootcamp in week one. My kids started Betreuung (after-school care). Their first weeks, their nervous systems stretched and mine absorbing the spillover. Betreuung closes at 18:00. Hard stop. This means stopping on time, before 15:50 to catch the train and pray that there’s no delay somewhere.
None of these things were catastrophic individually. Together they produced something I’ve experienced before but never named properly: sustained overlapping disruption. Not a hard week. A persistent state where every recovery window was consumed before it opened. Where every system I’d built assumed a baseline that no longer existed.
3. What broke
The belief that discipline was the variable.
Here’s what I noticed: the work I produced during this period wasn’t random. It clustered around two kinds of tasks. Things with hard external deadlines. And things so small they required almost no activation energy.
Everything else stalled. The blog post I meant to write. The landing page that still isn’t live. The outreach messages I drafted in my head on the commute and never sent.
Not because I lacked discipline. I was showing up for hard things every day. But those hard things had arenas. A client expecting a deliverable is an arena. A classroom with twenty other people is an arena. My laptop, alone, with a task only I know exists. That’s not an arena. That’s a void.
You’ve been in that void. You know what it produces. Not rest, not resistance you can name and push through. Just the low-grade hum of avoidance dressed up as preparation. Or scrolling… on Facebook, TikTok, Linkedin, or whatever it is you turn to to get that little dopamine hit.
Knowledge work, unlike almost every other performance domain, has no built-in arena. An athlete doesn’t invent the game before playing it. A surgeon doesn’t construct the operating room before operating. The context provides the container.
Knowledge workers have to build the container, maintain the container, and perform inside it. Simultaneously, every day, while life actively dismantles it. When the baseline collapses, there’s no structure left to catch you.
That’s not a discipline problem. That’s a structural absence.
4. What I decided
Two things.
First: the variable isn’t discipline. It’s environment. More specifically, the presence or absence of a witnessed commitment structure. An arena. When I had one, even a borrowed one, even an imperfect one, I executed. When I didn’t, I defaulted to work that felt like execution without the exposure of actually doing the thing that mattered.
Second: energy isn’t a soft consideration. It’s a scheduling constraint. The 18:00 hard stop, the cognitive drain of Swiss-German, the ADHD tax of disrupted sleep and reduced caffeine. These aren’t excuses. They’re inputs. Ignoring them doesn’t make them disappear. It makes the system fail silently instead of visibly.
I stopped trying to fix my discipline. I started asking two different questions. What is the minimum viable arena for this task? And when, given real constraints, does my energy actually support this kind of work?
5. What this changes
I’m building PEACH-Flow around the first insight.
Not because people need more accountability tools. The market is full of those. But because existing tools treat the arena as a feature. Something bolted onto a productivity system to make it stickier.
The arena is the product. Everything else is infrastructure.
If your system only works when life is stable, it was never a system. It was a fair-weather strategy.
The second insight, energy as a hard input rather than a soft preference, isn’t in the product yet. It’s the next thing to figure out.
I’m building PEACH-Flow in public. If this resonates, or if you’ve lived a version of this, I want to hear about it.