A Calendar Stat Worth Taking Seriously
This week's WAM log reveals an unsettling contrast: time labeled as "work" on the calendar occupies 72% of the week's available hours, yet within that same week, the number of decisions advanced on core product direction stands at zero. This isn't a productivity problem—it's a signal that your sense of direction is breaking down. When you manage to keep yourself occupied every minute of the day but stand completely still on the most important question, it means you're using some high-intensity behavior to replace the one thing you actually know you should be doing but haven't.
In Deep Work, Cal Newport points out that modern knowledge workers are prone to falling into a cycle of "low-cognitive-demand tasks": answering emails, sitting in meetings, tweaking document formats—these behaviors satisfy the brain's need for the reward of "having completed something," while requiring no real engagement with the ambiguous, uncomfortable, uncertain core problems. This mechanism explains why busyness itself can be a form of avoidance.
Why Busyness Is a Low-Risk Psychological Comfort Zone
Why are founders especially prone to this trap? There are three layers to it.
The first is the illusion of immediate feedback. Answering emails, replying to instant messages, hopping from one short meeting to the next—these behaviors deliver feedback on the spot. You immediately know the thing has been handled, and your brain releases a small hit of satisfaction. But whether the product direction is right, whether you should cut a feature, whether the business model holds up—feedback on questions like these may take weeks or even months to arrive. The brain is wired to prefer immediate feedback, so it keeps pulling you back toward tasks that make you feel like you're doing something.
The second is the misguidance of visibility. Founders carry expectation pressure from their team, investors, and partners. When you show up to every meeting and reply to every message quickly, others see you as "all in." But if you spent that same time in deep thought on a question with no standard answer, there's no external signal proving you're working. Busyness thus becomes a displayable form of output, used to hedge against the ever-present uncertainty of the founder's journey.
The third, and most fundamental, layer is confirmation bias at work. Research shows that when facing decisions with uncertain outcomes, people tend to favor information that makes them feel good while avoiding evidence that might disprove their own assumptions (see: Daniel Kahneman, Thinking, Fast and Slow). Keeping an unvalidated product hypothesis alive in your head costs far less than formally testing it and watching it fail. And busyness conveniently provides exactly that protective shell.
The Real Lesson: Output Volume ≠ Forward Direction
The core insight from this week isn't discovering that I'm "not working hard enough"—it's recognizing that "being busy" has itself become a mechanism of avoidance. That distinction matters a great deal: it reframes the problem from "time management" to "attention management." Time management assumes you already know where to direct your hours; but when busyness itself becomes the goal, time turns into a consumable used to fill the cognitive space that should have gone to decision-making.
Another key lesson: "no time" is often a selective narrative. When 72% of a week is filled with tasks and core decisions still tally to zero, the issue isn't insufficient time—it's that time has been mis-prioritized. More precisely, it's that certain tasks, because of their low threshold and low friction, have been systematically queued ahead of high-value tasks—and that whole queuing process tends to be automatic and unexamined.
An Adjustment You Can Make Starting Tomorrow
Beginning next week, I'm implementing a "Single Focus Block" system: every day from 9:00 to 11:00 AM is designated as the "Core Decision Window," during which only work tied to the week's single Most Important Objective (MOT) is allowed. All emails, instant messages, and non-essential meeting invites are paused for those two hours. This isn't a productivity hack—it's a structural attention-protection mechanism. It transforms "two hours where you don't have to do anything" into "two hours where only one thing can be done," dramatically reducing the brain's opportunity to drift toward low-friction tasks.
Two keys to execution: first, the MOT must be specific—specific enough that a concrete set of action options can be produced within an afternoon. An example: "Decide whether to cut the payment feature and focus on subscriptions." A vague MOT (like "optimize the product") leaves the brain plenty of room to slide back toward the placebo of busyness. Second, you must track "decision count" rather than "task completion count"—the former is the real indicator of forward motion.
"Busyness isn't always the ladder to the goal—sometimes it is the ladder itself, making you forget you never wanted to climb that wall in the first place." — 12W Field Notes, Week 2 Reflection