The Problem With Productivity Advice
Most productivity advice is written for people who have stable, predictable schedules and clear work scopes. You're told to time-block, use the Pomodoro technique, batch similar tasks, and implement an inbox-zero system.
None of this accounts for what actually runs a founder's day: unexpected client escalations, strategic decisions that need to be made with incomplete information, team members who need unplanned attention, deals that accelerate or stall without warning, and the general state of running a business where the definition of "important" changes faster than any calendar system can accommodate.
I run X Network while contributing to Entrepreneur Magazine, hosting a podcast, running national representation campaigns, and speaking globally. I had to develop a productivity system that works under conditions of high variability and competing priorities — not a system that assumes a controlled environment.
What I've learned: the goal isn't to do more. It's to protect the work that actually moves things forward while not dropping the obligations that are real.
The Foundation: Distinguishing Output From Activity
The most common productivity failure in early-stage businesses is optimizing for activity rather than output. You can stay extremely busy doing things that don't matter while the most important work — the work that actually determines whether the business succeeds — doesn't get done.
Before any system, I ask: what would need to be true for this quarter to be a success? The answer is usually three to five specific outcomes. Everything else is either a means to those outcomes or it isn't.
This sounds obvious. In practice, most of the tasks that occupy a founder's time — especially in a service business — aren't on that list. Answering emails feels urgent. Writing a blog post feels productive. Sitting in a status meeting feels responsible. None of these are the outcomes.
The discipline is weekly: every Monday, identify the three to five specific outcomes that would make this week a success, and protect time for those outcomes before allocating time to everything else.
Energy Management Is More Leveraged Than Time Management
Time is fixed: everyone has 24 hours. Energy is variable: an hour of high-focus work produces dramatically more output than an hour of depleted, distracted work.
My best thinking — the work that requires genuine strategic judgment, creative problem-solving, or synthesis of complex information — happens in the morning, before I've depleted my cognitive resources on communication and reactive tasks. I protect 9-11am for that category of work. No calls, no Slack, no email. If I move that work to the afternoon when I'm already depleted, it either doesn't happen or it produces worse output than it should.
Most founders I know have a similarly predictable energy distribution but haven't mapped their calendar to it. The result: their best cognitive resources go to meetings scheduled by other people, and their actual thinking work happens in the scattered hours that remain.
The practical question: when are you at your best? Block that time for work that requires your best. Use the remaining time for execution, communication, and logistics.
The Three Categories Everything Gets Sorted Into
I sort every task into one of three categories:
Do (only me, this week). Work that only I can do and needs to happen this week. Strategic client work. Content that requires my specific perspective. Key business decisions. These get calendar time before anything else.
Delegate (someone else, defined outcome). Work that someone else can do as well or better than I can, or work that would be done better if I invested time in building someone else's capability to do it. Delegation doesn't mean abandon — it means define the outcome clearly, identify who does it, and create a feedback loop.
Delete (this week, or permanently). Tasks that appear important but aren't producing the outcomes that matter. Recurring meetings that could be replaced by an async update. Reports that get produced but not read. This is the category most founders are reluctant to use and should use more aggressively.
Protecting Maker Time vs. Manager Time
Paul Graham's distinction between maker time and manager time is the most useful concept I've applied to schedule design.
Manager time runs on one-hour intervals. The day gets carved into 30-60 minute slots for meetings, calls, reviews. This is how most people's calendars look and how most organizations default to scheduling.
Maker time requires large blocks. Deep work — building something, thinking through a strategy, writing, coding — doesn't produce in one-hour windows. An interruption in the middle of a three-hour writing block doesn't just cost the time of the interruption; it costs the recovery time to get back to depth.
Running a service business requires both: client relationships and team management require manager-mode responsiveness; the actual strategic and creative work requires maker-mode protection.
My solution is temporal separation: Monday, Tuesday, and Thursday mornings for maker work; meeting time blocked into Tuesday/Thursday afternoons and Wednesdays. The discipline is not letting individual meeting requests erode the maker blocks.
The Systems That Reduce Cognitive Load
Beyond time and energy management, the other lever is reducing the number of small decisions and recurring tasks that consume cognitive resources that should go to important work.
Communication templates. For the recurring communication patterns in a service business — project kickoffs, status updates, scope discussions, invoice follow-ups — having well-crafted templates reduces the cognitive effort of each individual instance while maintaining quality. This isn't automation for its own sake; it's removing unnecessary reinvention.
Decision frameworks for recurring decisions. When the same type of decision recurs — which clients to take, which projects to say yes to, how to handle specific types of client situations — pre-built criteria reduce the cognitive cost of each individual instance. My criteria for whether to take on a new client haven't changed significantly in years. I don't relitigate them every time a prospect appears.
Capture systems for ideas and tasks. The cognitive cost of maintaining an unorganized mental list of things to do is higher than the cost of the tasks themselves. A simple, trusted capture system — I use a combination of Notion and a physical notebook — reduces the background anxiety of "what am I forgetting?" That anxiety is a persistent drain on focus.
Batch communication. Email and Slack processed in two 30-minute windows per day (late morning and late afternoon) rather than continuously throughout the day. This is the single change most people can make that most immediately improves focused work capacity.
Key Takeaways
- Protect outcomes, not activity — weekly: what three to five specific outcomes would make this week a success? Those get time before everything else
- Energy management is more leveraged than time management — identify your peak cognitive hours and protect them for work that requires your best
- Three categories: Do (only me, this week), Delegate (defined outcome to someone else), Delete (ruthlessly)
- Maker time vs. manager time: temporally separate them — morning blocks for deep work, meeting-heavy afternoons/days
- Communication templates and decision frameworks reduce recurring cognitive overhead without reducing quality
- Batch communication: two dedicated windows per day instead of continuous processing
- The goal is protecting the work that actually moves things forward — not maximizing the appearance of activity