Why Productivity Advice Fails Founders
A lot of productivity advice is built for tidy jobs and predictable days. Founder life is neither.
Most productivity advice is wrong for founders because it assumes a level of control that founders rarely have. It assumes the day is predictable, the work is clearly scoped, and the main challenge is personal discipline. That may be true for some jobs. It is not usually true for someone building or running something real.
Founder work is structurally untidy.
The problem is not that founders are disorganised. The problem is that the work itself changes shape constantly. One hour you are making a strategic decision. The next you are dealing with an operations issue, a people problem, a cash question, or a customer signal that suddenly matters more than the thing you planned to do.
So when generic productivity advice says:
- wake up earlier
- batch your tasks
- protect your deep work block at all costs
- follow the same routine every day
it sounds clean.
It also ignores how business actually behaves.
What does most productivity advice assume?
It assumes that if you structure yourself correctly, the day will obey.
That assumption breaks down quickly in founder reality.
Businesses are not quiet enough for that.
A founder is often operating across multiple time horizons at once:
- today’s fires
- this week’s decisions
- this quarter’s priorities
- the longer arc of what the business is becoming
Those layers create tension. If you apply a rigid productivity model built for stable environments, you end up feeling like you are failing simply because the framework was wrong for the job.
I do not think founders need more guilt about not having the perfect system.
I think they need a system that respects volatility.
Where does generic advice go wrong?
Usually in five places.
| Advice | Why it sounds good | Why it breaks for founders |
|---|---|---|
| Time-block every hour | Creates order | The day rarely stays still long enough |
| Eliminate all interruptions | Protects focus | Some interruptions are the work |
| Say no to everything non-essential | Preserves energy | Founders still need exposure to reality |
| Build one ideal routine | Feels efficient | Founder work has different operating modes |
| Measure output by completed tasks | Looks objective | Important work is often ambiguous, not checklist-friendly |
The founder’s job is not just to execute planned tasks.
It is to interpret what suddenly matters.
That is a different kind of productivity.
Why are interruptions not always the enemy?
Because some interruptions are information.
A supplier issue might expose a structural risk.
A customer complaint might reveal something the dashboard has not shown yet.
A team tension might signal a leadership issue that will become more expensive if ignored.
If you treat all interruptions as enemies of productivity, you can accidentally build a very efficient relationship with irrelevance.
That does not mean every interruption deserves attention.
It means founder productivity cannot be designed around the fantasy of a sealed environment.
The real work is learning to distinguish between noise and signal quickly.
That is closer to operating judgement than classical productivity.
What has worked better for me?
I trust priorities more than plans.
Plans matter. But priorities survive contact with reality better.
That is one reason I wrote How I Decide What Matters When Everything Is Urgent. The point is not to create the perfect schedule. The point is to create a decision filter strong enough to keep the day from being owned by whatever arrives loudly.
What works better for me now is this:
I protect one meaningful move, not one perfect day.
If the day collapses into noise but one compounding thing still moved - a key decision, a hiring judgement, a piece of writing, a systems improvement, a real customer conversation - then the day was not lost.
That standard is more forgiving.
It is also more honest.
Why do founders get addicted to productivity theatre?
Because it feels controllable.
A tidy Notion board feels satisfying.
A colour-coded calendar feels satisfying.
An inbox at zero feels satisfying.
A perfect morning routine feels satisfying.
None of these are bad on their own. The problem is when the founder starts mistaking the management of work for the movement of work.
Productivity theatre creates the emotional sensation of control without always producing commercial progress.
I have fallen into this myself. Especially in periods where the real work felt heavy or ambiguous, it was tempting to optimise the system around the work instead of touching the difficult thing directly.
That temptation is understandable.
It is also expensive.
What should founder productivity actually protect?
Three things.
Judgement.
If the system makes you fast but mentally shallow, it is a bad system.
Energy.
Not comfort. Energy. The ability to keep showing up with enough steadiness to make good decisions over time.
Compounding work.
The work that improves the next hundred days, not just the next hundred minutes.
That is why I think founder productivity should be measured less by volume and more by trajectory.
Did today improve the business’s direction?
Did it clarify something that was previously muddy?
Did it solve something at the root instead of only at the surface?
Those are better questions.
What does a founder-friendly productivity model look like?
For me, it looks more like a rhythm than a rigid routine.
It has a few principles:
- Start by identifying the one thing that would make the day structurally better if it moved.
- Leave room for real-world signal. Do not schedule yourself so tightly that the business cannot speak.
- Separate reactive blocks from thinking blocks when possible, but accept that some days will refuse elegance.
- Protect energy before you optimise output. A burnt-out founder with a clean calendar is still burnt out.
- End by asking what actually changed, not just what got handled.
This is less aesthetic than most productivity content online.
It is also more useful for real operator life.
Why does founder work need multiple modes?
Because not all days are the same kind of day.
Some days are for strategy.
Some are for decisions.
Some are for repair.
Some are for building.
Some are for selling.
Some are for carrying more than you wanted to carry.
Trying to force one ideal template onto all of these creates friction. That is why many founders keep feeling like they “fall off” their system. The truth is usually simpler: the system was too brittle for the reality of the role.
I prefer flexible standards now.
Not sloppy. Flexible.
That difference matters.
What role does discipline still play?
A major one.
This is not an excuse for chaos.
Founders absolutely need discipline. But founder discipline is not the same as calendar perfection. It is the discipline to keep touching the real work. To keep facing the thing that matters. To keep returning to priorities when the day tries to fragment you.
The Power of Showing Up When It’s Boring was about this in a different form. Discipline is less about intensity than repetition. A founder who can keep returning to the important work, even imperfectly, will usually outperform the founder who keeps designing beautiful systems they cannot live inside.
So what do I believe now?
I believe most productivity advice fails founders because it was written for environments where stability is normal.
Founder life is not stable.
It is dynamic, interrupt-driven, emotionally mixed, and structurally uneven.
That does not mean founders should give up on systems.
It means they should build systems that respect the shape of reality.
Not systems that make them feel guilty for living inside it.
I do not want a productivity model that looks impressive from the outside.
I want one that helps me protect judgement, move compounding work, and survive the noise without letting the noise define the day.
That feels less clever.
And much more true.
Ashraf Hassan (Ashmo)
Founder, brand builder, and merchant philosopher. Read my story
Keep Reading
How I Decide What Matters When Everything Is Urgent
Urgency is noisy. Importance is usually quieter. The work is learning to tell the difference.
Patience Is Not Passive
There's a version of patience that looks like waiting. And there's a version that looks like doing the work every day while the results take their time.