There is a particular kind of exhaustion that sleep doesn't fix.
It's the exhaustion that comes from carrying too many unfinished thoughts. None of them are emergencies by themselves. A sales forecast waiting for review. A dashboard that needs another metric. An executive meeting at ten. Someone asking why an order stalled. A spreadsheet with formulas that no one trusts but everyone depends on. An email marked 'urgent' that really means, 'I waited until the last minute.'
By themselves, they're manageable. Together, they become static. The kind of mental noise that follows you home, rides in the passenger seat on the drive to work, and quietly waits while you're trying to fall asleep.
For years I believed my job was to answer questions. Some days it felt as though people stood outside my office carrying invisible buckets, waiting for me to pour a decision into each one. 'Can you look at this?' 'Does this number seem right?' 'Can you build something that shows...?' 'Why did this happen?' 'Can we automate...?'
Eventually I noticed something uncomfortable. I wasn't simply solving problems anymore. I was becoming part of the machinery that kept every other process moving. Whenever work couldn't find somewhere else to go, it found me. I wasn't unique. Most operational leaders eventually become human routing tables. Information enters from every direction. Questions accumulate. Decisions leave. Tomorrow the cycle begins again.
My instinct was simple: work faster. Learn another shortcut. Build another report. Eliminate another repetitive task. Surely there had to be a way to create enough breathing room that I could finally get ahead instead of merely keeping up.
Then artificial intelligence arrived in a way that ordinary people could actually touch.
I wasn't skeptical. I was fascinated.
I still remember the feeling of typing a prompt and watching coherent ideas appear on the screen. It felt less like using software and more like holding a conversation with something that could keep up. Not perfect. Not magical. But astonishing. My curiosity immediately outran my caution.
I threw everything at it. Spreadsheets. Forecasts. Executive summaries. HTML dashboards. Formulas that had been haunting me for years. Emails I dreaded writing. Ideas that had been trapped in my head because I couldn't organize them quickly enough.
Sometimes the answers were wrong. Sometimes they were incomplete. But even then, I wasn't disappointed. I was amazed. For the first time in my career I felt like I had a collaborator that never got tired of thinking alongside me.
That excitement changed my relationship with work. I stopped seeing AI as software and started treating it like a whiteboard that talked back. Every successful experiment led to another question. What else could it do? What if I connected these two ideas? What if reports became conversations instead of documents?
The strange thing was that success didn't reduce my workload. Reports finished faster, but leadership wanted deeper analysis. Dashboards became interactive, so people wanted more dashboards. Processes improved, revealing weaknesses that had been hidden behind slower work. Every improvement uncovered another opportunity.
At first I assumed I simply needed to become better at using AI. Better prompts. Better workflows. Better automation. I kept building because every success felt like discovering another room in a house I didn't know existed.
One afternoon I stopped in the middle of a project and realized something that refused to leave me.
'Why does every improvement create another bottleneck?'
I didn't know it then, but that question would eventually lead me to a forty-year-old novel about a struggling manufacturing plant, a physicist named Jonah, and an idea that would quietly reorganize the way I thought about work, leadership, measurement, and eventually AI itself.
The surprising part is that none of those discoveries began with manufacturing. They began with curiosity. AI didn't give me all the answers. It gave me something even more valuable. It made asking better questions addictive.
Looking back, that's where this story really starts. Not with technology. Not with automation. With the moment curiosity became stronger than the desire for quick answers.
Author's Note
This chapter intentionally ends before introducing the Theory of Constraints. The next chapter starts exploring why increased capability doesn't automatically create increased throughput — the question the rest of this research tries to answer.
— end of excerpt —