I tracked my time for 14 days. The result was embarrassing.
Six months ago I did a proper time audit. Not the "rough guess" kind where you estimate from memory and round everything in your favour. I actually logged every task, opened and closed the timer at the moment I switched.
The result was embarrassing.
4.5 hours a day on communication. Email, LinkedIn, Slack, DMs. Not building. Not selling. Not shipping. Just answering people.
That's more than half my working day. Gone.
My first move was to find faster ways to do the same things. Better templates. Keyboard shortcuts. Inbox systems. All the stuff productivity Twitter loves.
Helped a bit. Didn't fix the actual problem.
Then I changed the question. Instead of "how do I do this faster" I started asking "why am I doing this at all?"
Here's what changed:
Check-ins dropped from 6 to 2. I was checking email and messages six times a day. Each switch killed 15-20 minutes of context I had to rebuild. Cut it to 10am and 4pm only. Felt terrifying for a week. Nobody noticed. Nobody. Not a single person complained or chased me. The six check-ins weren't about email. They were about anxiety.
I stopped typing first drafts. I built Genie 007 partly for this reason. Voice input that actually understands intent, not just transcription. "Reply to the Manchester consultant, warm but professional, I'm open to a quick call next week." Get a finished reply back. Not a rough transcript to clean up. A finished reply. I process my afternoon email batch from my phone, walking around. No desk required.
Mornings became non-negotiable. No communication before 10am. One rule. I broke it every day for a week, then habit kicked in. Now it's automatic.
Three months later: under 90 minutes a day on communication. Down from 4.5 hours.
That's three hours a day recovered. Every day. Over three months that came out to about 180 hours that went into content and feature work instead.
The lesson I keep coming back to: the productivity industry sells speed. Most of us need elimination, not acceleration. You can't shortcut your way out of a process that shouldn't exist.
Audit before you optimise. Two weeks of real tracking. Then ask "should this exist" before you ask "how do I do this faster."
Curious what your biggest time sink looks like on a real audit. What does your day actually look like vs what you think it looks like?
The point about checking messages being an anxiety loop rather than a communication need is spot on. For your morning block, did you completely block notifications at the OS level, or did it just take raw discipline to build the habit?
The three-product problem is a lot more interesting than the email problem. Reconstructing the state of each business every time sounds like the real bottleneck.
I actually have a solution that could help with this. Happy to share if you're interested.
This is already a strong, detailed draft. What would you like me to do with it—polish it into a LinkedIn post, shorten it, make it punchier, or critique it for engagement?
The thing I'd add after doing audits like this: write the rule as something you can enforce, not just intend. "No comms before 10" works because it removes in-the-moment negotiation. If the rule still depends on willpower at 9:37, the system is probably leaking.
The six-to-two check-in change is the strongest part. Voice can make replies faster, but it won't stop the anxiety that keeps pulling you back to your inbox. I built DictaFlow to remove the need for typing, but the habit only sticks when the text appears in the app you already use. Your audit is a good reminder to cut unnecessary check-ins first, then speed up the ones that remain.
The anxiety point is right and I didn't name it clearly enough in the post. Cutting the check-ins was the fix that actually mattered. Voice was just multiplying what was left. The integration observation is sharp though — the reason voice drafts stuck for me was that the output landed in the same tool I was already sending from. Workflow continuity turns out to be most of the habit formation. How's DictaFlow handling the integration side — native connections or through clipboard?
Audit before optimize is right, but for founders running more than one company the fix isn't fewer check-ins, it's deciding which messages actually need you. Running four organizations, the only rule that's kept my inbox sane is: if a human can't make a real decision from my reply, an assistant or an agent handles it and I never see the draft. Worth adding to your audit: not how often you check messages, but what percentage of them actually needed you specifically.
The percentage framing is sharper than frequency. I was solving for time in my audit when the real question was whether it should have reached me at all. Four organizations is a fundamentally different problem though. Batching works when you have one context to hold. With four, the state reconstruction cost on each switch is the actual killer, not the check-in itself. How do you handle the context overhead when something needs immediate attention across two of them at the same time?
Reducing communication from 4.5 hours to 90 minutes is impressive. Did the two fixed check-ins also improve your focus, or mainly save time?
Both, but the focus part was the bigger surprise. I knew the time would drop. I didn't expect that batching check-ins would basically kill the anxiety loop. When I know there's a scheduled window, my brain stops running the "what if I've missed something" check in the background. The time gain shows up on the calendar. The focus gain doesn't, but it's probably the more valuable of the two.
That's the question that took me longest to answer honestly. The compounding activities I cut were the ones I couldn't measure yet. The rule I landed on: if cutting it causes no immediate pain but might matter in 6 months, keep it but timebox it. If you can't define what 'it worked' looks like in 12 months, that's not compounding, that's hope.
Great piece, Bill! The realization that 'checking email 6 times was solving for anxiety, not customers' is huge.
But I have a question regarding complete elimination. How do you evaluate whether a low-converting action truly has zero value versus a compounding effect that just hasn't hit its inflection point yet?
Sometimes consistent small efforts (like networking, light outreach, or content) look like a waste of time in a 14-day audit, but build non-linear momentum over 6–12 months. How do you distinguish between pure friction that needs to be cut and long-term compounding activity?
The shift from "how do I do this faster" to "why am I doing this at all" is pure measurement work. You didn't have a speed problem. You had an invisibility problem. The time audit made visible what your intuition couldn't: that email anxiety wasn't actually customer-driven, that batching communication was possible because the communication itself was optional.
Most productivity advice assumes the answer is already known: do it faster. What the audit does is let you ask a different question first. Instead of "what tools can I use," you get to ask "what would happen if this stopped?" Six check-ins became two and nobody noticed because the check-ins were solving for your anxiety, not for customer needs. That's information optimization can't touch.
The interesting part: once you had that measurement, the solutions became obvious and almost trivial. The batching windows didn't require productivity systems—they required one rule and a week of habit formation. Voice input didn't require perfect transcription—it required understanding intent instead of words. These solutions only make sense if you're starting from "this work is optional" rather than "this work is necessary but slow."
What's harder to measure downstream: whether the recovered time actually stayed in building, or whether new communication patterns quietly expanded to fill it. TCLeon511's question nails it—did the three hours stay or did something invisible expand? That's harder to see because you'd have to track it the same way you tracked the original problem. Most founders don't repeat the audit once the pain goes away.
That's exactly it. The number was the symptom. The diagnosis was what I didn't expect to find. I went in thinking I had a discipline problem and came out knowing I had an assumption problem. Those require completely different fixes.
The striking part is that the audit changed the diagnosis, not just the numbers. What looked like a communication-efficiency problem turned out to be a question about why the work was happening in the first place. That distinction makes the 4.5 hours/day figure much more interesting than the productivity gain itself.
The batching fix doesn't port, you're right. Email can wait four hours. Product state can't queue the same way. With one product I got lucky: the right answer was 'do less of this.' With three you'd need to solve the state problem differently. Probably by externalizing it so the context is readable, not reconstructed every time. I'd look at structured decision logs before anything else. Not sure they fix the problem but they make it smaller.
That’s helpful context. I appreciate you unpacking how you’re thinking about the problem.
I’d like to continue this conversation outside the thread. What’s the best email to reach you on?
Best place to find me is LinkedIn — search Bill Kiani. Happy to continue the conversation there.
Thanks, Bill. I appreciate that.
I don't use LinkedIn for these conversations, but I'd be happy to continue over email. What's the best email to reach you on?
The check-ins number is the one that'll stick with me. Six a day, 15-20 minutes of context each, and nobody noticed when you cut it to two.
Where it gets worse than your version: I run three separate products, so the switch isn't 15-20 minutes of task context, it's whole-business state. Which numbers, which customers, what I decided three weeks ago and why. And your fix doesn't port. You can batch email into two windows because email tolerates a four-hour delay. A product doesn't tolerate being thought about twice a week, so the cost compounds instead of batching away.
The elimination half travelled better. I killed a feature in one of my apps that had taken days to build and had its own landing page - four months live, not one visitor, ever. Cutting it also removed a health-data section from a privacy policy in fourteen languages and a tier of App Review scrutiny that had been slowing down releases with nothing to do with it. Nobody noticed that either.
Did the three hours actually land in building, or had something quietly expanded to fill them by the time you next measured?
Honestly, I don't know yet. I haven't re-run the audit. My intuition says yes because I'm shipping more. But intuition was the thing that got me to 4.5 hours a day in the first place. The real answer requires doing the same 14-day track again, which I haven't done. That's probably the follow-up post.