I Stopped Blaming Myself for Bad Days After Learning This Math

Bad days aren’t a personal failure—they’re often the predictable result of a work environment that mathematically starves deep focus. A systems-thinking framework attributed to engineer John Duruk reframes productivity around three measurable “dials”: how often interruptions hit (lambda), how long it takes to regain task focus after each interruption (delta), and the length of uninterrupted time needed for real work (theta). When these values combine poorly—such as frequent interruptions every couple of minutes and a long recovery time—deep work blocks effectively become impossible, which helps explain the familiar feeling of “I can’t focus” without blaming willpower.

Duruk’s model matters because it turns focus into an engineering problem rather than a moral trait. If someone’s day starts with zero realistic deep-work blocks, expecting a breakthrough is unrealistic. The framework also highlights nonlinear gains: small improvements to interruption frequency or recovery time can flip a day from “no deep work” to multiple meaningful blocks without adding more hours. Deep work becomes a design choice—either by lowering internal standards to match the environment, or more constructively by redesigning tasks so they fit the time you actually get. That redesign is where AI becomes practical.

AI fits this model because it can influence the same variables that govern deep work. Instead of treating AI as a generic productivity chatbot, the approach is to use it as a “focus system tool” that helps manage interruptions, reload context faster, and reshape work into smaller, executable chunks. AI can monitor and route messages—classifying urgency, bundling non-critical pings, and deciding what gets through—reducing lambda. It can summarize and recall past context so delta shrinks, letting someone re-enter a task without a full mental reload. It can also decompose large, fuzzy assignments into scaffolded steps, effectively changing the structure of work to better match theta.

The practical strategies follow directly from those dials. First, use AI to create fewer, smarter interruptions: auto-answer trivial questions across Slack, Teams, and email, bundle non-urgent pings, and rely on tools like Superhuman and Lindy.ai to reduce notification noise and meeting churn. The trade-off is slower responses for low-priority messages in exchange for more deep work and better mental recovery.

Second, shrink delta by making context retrieval effortless—asking models what someone was working on last, using chat history, and even converting handwritten notes into searchable summaries via AI handwriting recognition. Third, fit more work into realistic blocks by chunking: generating outlines, code scaffolding, tests, and first drafts so tasks can progress in 20–40 minute segments rather than requiring long uninterrupted stretches.

At the leadership level, the framework shifts from individual hacks to culture and measurement. Treat focus like engineering uptime: define service levels for deep work blocks, color-code calendars, and use AI to read and track deep-work time. Team norms matter too—Slack and meeting etiquette that reduces interruption, plus shared “resumption” patterns for handoffs (for example, a consistent “here’s where to pick up” section in specs and PRs). The core takeaway is empowerment through system design: attention isn’t mystical, and AI isn’t a magic add-on—it’s a lever for turning the dials more effectively for individuals and teams.