The Founder Time Audit:Four Modes of Work, and Only One Builds Equity
Track one week of your calendar and sort every hour into Doing, Deciding, Delegating, or Designing. The ratio you find will predict whether your firm can ever run without you.
Open your calendar from last week. Every entry on it belongs to one of four categories, and the proportions between those categories say more about the future of your firm than your pipeline, your pricing, or your headcount. Mike Michalowicz gave the categories names in Clockwork: Doing, Deciding, Delegating, Designing. Three of them keep your business alive this month. Only the fourth gives it a life beyond you.
Founders of consultancies, agencies, and coaching practices rarely measure this. They measure revenue, utilization, win rates --- everything except where their own hours go. Which is why the same founder who can quote every client's budget from memory has no idea that almost none of their week is spent building anything that outlasts the week.
This article is an audit, not a pep talk. By the end you'll have a number --- and a plan for moving it.
01 — Start With the Exit Question
Could Your Firm Survive a Month Without You?
Before any framework, ask the question Michalowicz uses as his ultimate diagnostic: if you vanished for four weeks, what would happen? Would clients still get served? Would revenue still arrive? Would your reputation still be intact when you returned?
Notice that this isn't a question about whether you deserve a holiday. It's a structural X-ray. A firm that degrades within four founder-free weeks isn't really a firm --- it's a job with letterhead. And the gap between those two things isn't talent, effort, or even team size. It's how the founder's hours have been allocated, year after year.
You don't have to book the flights to run the test. Just answer honestly: which deliverables would slip? Which decisions would queue up unmade? Which clients would quietly start looking elsewhere? Each honest answer is an arrow pointing at a missing system.
"The four-week question isn't about rest. It's about ownership. If the business stops when you stop, you don't own a business --- the business owns you."
Most founders fail this test. The reason is hiding in their time allocation, and the 4D vocabulary makes it visible.
02 — The Four Buckets
Michalowicz's Vocabulary for Founder Time
In Clockwork, Michalowicz sorts every founder hour into four modes, each with a target ratio. The targets are not gentle suggestions --- they describe a business that can pass the four-week test.
- Doing --- keep it under 20%. Personally producing the deliverable: leading the workshop, drafting the report, taking the client call. Doing generates today's invoice and nothing else. The hour cannot be reused, resold, or repeated by anyone but you.
- Deciding --- keep it under 10%. Answering questions other people bring you because they lack the authority, training, or rules to answer them alone. Which template, which deadline, which colour. Each one feels tiny; collectively they make you the chokepoint every piece of work must squeeze through.
- Delegating --- keep it under 20%. Handing work out, briefing it, checking it. An upgrade on Doing, but the engine is still you: you assign, you verify, you restart anything that stalls. Remove you and the queue freezes.
- Designing --- get it to 50% or more. Writing the process, building the template, training the person, planning the strategy. Designing is the only mode whose output keeps working after you go home. It's the only founder hour that accumulates instead of evaporating.
Look at what those targets imply. Michalowicz is asking the typical expertise-business founder to flip their week upside down: half of all time on building the machine, less than a fifth on operating it. For most founders reading this, that ratio is currently inverted --- or worse.
The framework only becomes useful when you stop nodding at it and start measuring against it.
03 — Run the Audit
Five Days, Four Columns, One Honest Number
The exercise Michalowicz prescribes is almost insultingly simple: log your time for one working week and file every hour under one of the four D's. Use whatever captures reality --- a timer app, a spreadsheet, a notebook on your desk. What matters is that you record as you go rather than reconstructing from memory on Friday, because memory flatters.
Classification rules, so you can't cheat:
- It's Doing if the output required your hands. You typed the proposal, you ran the session, you replied to the email. No you, no output.
- It's Deciding if someone could have resolved it without you, given a clear rule or a bit of training. The fact that they came to you anyway is the data point.
- It's Delegating if you spent the time assigning, briefing, reviewing, or correcting someone else's work. The work isn't yours, but the momentum still is.
- It's Designing only if today's output reduces tomorrow's dependence on you: a documented process, a reusable asset, a person trained to operate without escalating.
One trap deserves a warning label. Founders love to file client strategy sessions under Designing because the conversation feels strategic. It isn't Designing. If you are in the room making it happen, it's Doing --- full stop. Designing would be codifying your methodology so a colleague can run that same session next quarter. Apply the absence test: had you not shown up, would the activity have happened anyway? No means it's not Designing.
On Friday, total the hours, compute the four percentages, and write them down. That set of numbers is your real org chart.
04 — Reading the Result
The Default Ratio, and the Tuesday That Produces It
When service founders run this audit honestly for the first time, the typical pattern lands somewhere around 70-80% Doing, 15% Deciding, 5% Delegating --- and effectively zero Designing. Not low. Zero.
The number shocks people because the days that produce it feel excellent. Walk through an ordinary Tuesday:
- 8:00 AM: Results review call with a client. Doing.
- 9:30 AM: Drafting a proposal for a prospective engagement. Doing.
- 11:00 AM: Marking up an associate's deliverable before it ships. Deciding.
- 12:00 PM: Lunch with a referral partner. Doing --- it's business development, and it's yours alone.
- 2:00 PM: Running a client workshop. Doing.
- 4:30 PM: Sign-offs on invoices and expenses. Deciding.
- 5:30 PM: Inbox. Doing.
Nothing on that list was wasted. Everything earned money or protected a relationship. And yet the day contributed exactly nothing to the firm's ability to function without its founder. Stack two hundred such Tuesdays in a row and you have a thriving practice and a non-existent business.
"A full calendar and a scalable business are not the same achievement. The audit exists to stop you confusing them."
If the ratio is this destructive, why does it survive? Because three psychological forces actively defend it.
05 — Why the Ratio Defends Itself
Three Forces That Keep Founders in Doing Mode
Michalowicz names three patterns that hold the broken mix in place. Each one feels like sound judgment from the inside.
First: the Doing Addiction.
Delivery produces instant, visible proof of usefulness --- a finished session, a sent report, a thanked client. System-building produces nothing you can point to today. So the nervous system votes for delivery every time, and the founder mistakes motion for momentum.
Second: the Hero Complex.
Being the one everybody calls in a crisis is flattering, and "no one can do this like I can" may be the most expensive belief in professional services. Every time you rescue a situation personally, you reinforce the structure that requires rescuing --- and guarantee the next crisis routes to you too.
Third: the Efficiency Illusion.
Repetition has genuinely made you fast. Faster than anyone you'd train. So handing the task over looks wasteful --- in the short run, it is. But speed at work you shouldn't be touching isn't efficiency; it's polishing the bars of your own cage. The illusion is the most seductive of the three precisely because the underlying fact is true. You really are quicker. That's the trap, not the defense.
Name these forces out loud when you catch them operating. They lose most of their power the moment they're labeled.
06 — The Lineage
Gerber Drew the Line; Michalowicz Added the Gradient
The 4D Mix didn't appear from nowhere. Its ancestor is Michael Gerber's famous split in The E-Myth Revisited: working ON the business versus working IN it. Gerber saw three characters fighting inside every owner --- the Technician who craves the craft, the Manager who craves order, the Entrepreneur who craves the future. In expertise businesses the Technician usually wins, not by being right but by being urgent. Client work shouts; systems whisper.
Gerber's great contribution was reframing scale as a question of where hours go rather than how good you are. The founder who can't grow isn't short on capability --- they're spending all of it directly on clients instead of encoding it into something a team can run.
But ON/IN is a binary, and real weeks aren't. Michalowicz's contribution was the gradient: Doing and Deciding sit at the IN end, Designing at the ON end, with Delegating as the awkward middle rung that founders mistake for arrival. Map the four-week test back onto the modes and the gradient becomes vivid: a Doing-heavy firm produces nothing in your absence; a Deciding-heavy firm freezes awaiting verdicts; a Delegating-heavy firm finishes what's in flight and then stalls; only a Designing-heavy firm keeps assigning, deciding, and delivering through its systems.
Alan Weiss compresses the whole argument into one line: "Process expertise is more valuable than content expertise." The knowledge in your head is the raw material; the system that delivers it without you in the room is the asset. The 4D Mix is simply the conversion schedule between the two.
Which leaves the practical question: how do you move from the ratio you measured to the ratio you need?
07 — The Migration
Sixteen Weeks From Operator to Architect
You cannot jump from 80% Doing to 50% Designing in a fortnight without torching revenue. The migration has to be staged, and the early stages are funded by the Doing work you're gradually retiring.
Weeks 1-4: carve out the first 10%. Reserve two hours each day --- mornings, before client gravity takes hold --- for pure Designing. One documented process, one template, one person trained on one task per session. You're not cutting delivery yet; you're layering construction on top of it. Days get longer for a month. That's the price of the foundation.
Weeks 5-8: drain the Deciding bucket. Pull up every decision that reached you during the audit week and write a rule that makes the next one not reach you. Deadline extensions below a week: project manager approves. Proposals under your chosen threshold: associate sends. Each rule is a small permanent gift of velocity to the whole organization --- and a small permanent reduction in your bottleneck role.
Weeks 9-16: trade Doing for Delegating, then Delegating for systems. The processes from the first phase now become handoff vehicles. The first transfer will wobble; the fifth will land at roughly 80% of your quality, which for most work is plenty. As your Doing hours fall, refill them with Designing, not with more Doing. And as delegated work matures into work that runs on documented process without your initiation, it stops being Delegating at all --- it becomes the machine operating.
"You are not trying to work less. You are trying to move your hours from work that pays once to work that pays indefinitely."
One financial caveat, stated plainly: as your personal delivery hours drop, your directly billed revenue may dip before the systems pick up the slack. That trade is acceptable on exactly one condition --- every Designing hour must eventually out-earn the Doing hour it displaced, through work delivered by others. If it doesn't, you're not building leverage; you're just billing less.
Re-run the audit monthly and keep the four percentages somewhere you'll see them. Then keep asking the four-week question until the honest answer changes. The day it does, you'll have stopped being your firm's most expensive employee and become its architect.