Tuesday, October 27th, 2026

Last Wednesday I counted.

Not emails. Interruptions. Texts, calls, Slack pings, a client voice memo, two "quick questions" from a contractor, and a guy on LinkedIn who wanted to "hop on a call" about something he refused to describe.

By 2pm I had forty one tally marks on a legal pad.

Forty one. And I run a small operation. I don't have a sales floor or a staff of twenty. I have clients, a few contractors, and a phone that apparently thinks I work for it.

What bugged me most was the pattern. Almost none of those interruptions were emergencies. Most of them were people doing exactly what I'd trained them to do. I answer fast. So they ask fast. I reply at 9:40 at night. So they send stuff at 9:40 at night. I've spent years teaching everyone in my world that the quickest way to get anything done is to come find me.

They learned the lesson perfectly. That part's on me.

If you think this is a you problem, it isn't. It's an everybody problem, and it's getting worse.

Microsoft surveyed 31,000 workers, matched it against signals from its own software, and published what it called the infinite workday. The average employee in that data gets interrupted 275 times a day. That's once every two minutes during core hours. Forty percent are checking email before 6am. Nearly a third are back in their inbox by 10pm.

Gloria Mark at UC Irvine has spent two decades studying this. Her research found that the average time people stay on a single screen before switching has dropped to about forty seven seconds, and that getting back to a task after an interruption can take around twenty five minutes.

Forty seven seconds of focus. Twenty five minutes to recover. Do that math across a day and you start to understand why you can work ten hours and feel like you got nothing done.

And those studies are about employees. The owner isn't getting interrupted every two minutes. The owner is the thing everybody else interrupts to get unstuck.

I listened to a long conversation this month between Steven Bartlett and a Berkeley neuroscientist named Sahar Yousef, and one idea stuck with me. Every time you switch, a little bit of the last thing stays with you. Researchers call it attentional residue. You think you're on the proposal, but part of your brain is still on the text from the contractor. So you're not really working on anything. You're just hosting a bunch of half thoughts.

That's what forty one interruptions feels like by 2pm. A crowded room in your own head.

You've got about nine weeks left in the year, and they're the loudest nine weeks on the calendar.

Holiday promos. Year end deals. Clients spending budget before December 31st. Black Friday is a month away. Every single person in your world is about to get more urgent, and every single one of them already knows the fastest route to an answer is you.

If you don't change the rules before November, you'll spend the most important stretch of the year as a human switchboard.

So let's change the rules. Seven steps. None of them require new software, and most of them take less than an hour to set up.

You can't fix what you can't see, and you can't see your own interruptions. You'll remember the annoying ones and forget the rest.

Pick two normal workdays this week. Keep a pad next to you, or a note on your phone, and every time something pulls you off what you were doing, write one line.

Who it was. What channel it came through. What they needed. Whether it actually needed you.

If you want help with the laptop side, Rize tracks every app and context switch in the background and shows you exactly how fragmented your day was. The first time I looked at my own report I was embarrassed. I thought I'd been writing for two hours. I'd been writing in nine little pieces with my inbox in between each one.

At the end of two days, sort the log into three piles.

Real urgent. Something breaks or costs money if you don't respond within the hour.

Real, not urgent. It needs you, but tomorrow at 10am would've been fine.

Not yours. Somebody else could have answered it, or the answer already exists somewhere.

Most people I walk through this find the first pile is tiny. Five percent, maybe ten. The third pile is usually the biggest. That's your opportunity, and it's a lot bigger than you think.

One big reason you're buried. Every channel is treated as equally urgent. A text, an email, a Slack message, a voice memo, a DM, a comment on a shared doc. They all buzz the same way, so your brain treats them all as fires.

Fix that by deciding what each channel is for, and writing it down.

Mine looks roughly like this.

Phone call means something is actually on fire. If you call me, I'll pick up or call back fast.

Text is for people in my inner circle and for true time sensitive stuff from clients. Short answers only.

Email is for anything that needs thought, documents, approvals, or a paper trail. I answer it in blocks, not as it arrives.

Slack or the project tool is for the team, and it's where work questions live so they're searchable later.

DMs on social are for social. They are not a support line.

Yours will look different. The point is that a channel with a job is a channel you can ignore when it isn't doing that job.

This is the one that changed my week, and it's the one most owners are scared to do.

You tell people how fast you'll respond in each channel. Out loud. In writing.

Something like this, in your email signature, your client welcome doc, and your team handbook.

"I check email at 10am and 3pm on weekdays. Anything sent by 2pm gets a reply the same day. For urgent issues, call the office line."

That's it. Two sentences.

The fear is that clients will hate it. They won't. People don't need you to be instant. They need you to be predictable. A client who knows they'll hear back by 3pm stops sending three follow ups at 10:15, 11:00 and 11:40. A team member who knows you batch your questions at 4pm starts saving them up instead of tapping you on the shoulder every time one pops up.

Uncertainty is what makes people chase you. Remove the uncertainty and most of the chasing stops on its own.

Then the hard part. Keep the promise. Don't announce a 10am email block and then answer everything at 7:15 because you were up anyway. The first time you break your own rule, everybody learns the rule isn't real.

Go back to your log and look at the "not yours" pile. A lot of it will be the same questions on repeat.

Where do I send the invoice. What's the login for the portal. When's the next call. Did you get my file. What's the status on the thing. Can you resend the link.

Every one of those questions is a tiny tax. Two minutes to answer plus twenty five minutes to get back to what you were doing, if Gloria Mark is right. Answer the same question eight times a month and you just burned about three and a half hours on one sentence.

So answer it once, properly, in a place people can find without you.

For clients, that's a simple FAQ page or a welcome doc with the boring stuff in it. Billing, logins, timelines, how to reach you, what to expect in week one. If you run your clients through Go High Level, you can drop that into the onboarding sequence so it shows up automatically the day they sign.

For your team, it's a shared doc called "Before You Ask Me." Every repeat question gets added to the doc, and your reply is the link. It feels a little cold for two weeks. By week four, they check first.

This is the deeper version of step four, and it's where the real hours come back.

A lot of the interruptions in my log weren't questions about information. They were requests for permission. Can I refund this customer. Is it okay to move the call. Should I go ahead with the cheaper vendor. Can I give them an extra week.

Every one of those is a decision your people could make if they knew where the line was.

So draw the line. Literally.

Write down three or four decisions your team makes every week and set a limit for each. Refunds up to a certain amount, approved without asking. Rescheduling a client call, approved as long as it's within the same week. Vendor choices, approved if they're within budget and the vendor's already on the approved list.

Then add the sentence that makes it work. "If you make a reasonable call inside these lines and it goes sideways, I've got your back."

That sentence matters more than the limits. People don't interrupt you because they can't decide. They interrupt you because they're scared of deciding wrong and getting blamed. Take away the fear and the questions dry up fast.

No team? Give the decision to a system. An automation in Make.com can kill every "did you get my file" message by sending a confirmation the moment something lands in your folder.

Most people try to fix their notifications by turning a few off. That never works, because the defaults are designed to win.

Do it the other way around. Turn everything off. Every app. Then add back only what earns its place.

My rule: a notification gets to interrupt me only if a real person is waiting on me, right now, for something that can't wait two hours.

That means calls from favorites ring through. Texts from a short list of people break through my focus mode. Calendar reminders stay on. Almost everything else is silent, including email, which I check on schedule instead of on command.

Yousef had a tactic in that podcast I'd heard before but never tried. Switch your phone to grayscale. She said her lab saw people use their phones about an hour less a day once the colors were gone. I've been running it for a week. The phone just got boring, which turns out to be the point. All the little red badges and bright icons are built to pull you back in. Take the color out and a lot of the pull goes with it.

On an iPhone it's under accessibility, then display and text size, then color filters. Set it as the accessibility shortcut so a triple click flips it on and off. Five minutes, tops.

Now you put it all together.

Pick two or three windows a day where you handle messages. Late morning, mid afternoon, maybe a quick end of day sweep. Outside those windows, email is closed. Not minimized. Closed.

Inside the windows, move fast. Reply, delegate, file, or delete. Anything that needs real thinking becomes a task, not a draft that sits open all afternoon.

If a lot of your messages are follow ups from calls, get the call notes off your plate entirely. I record client calls with Fathom, and the summary and action items are sitting in my inbox when the call ends. That alone kills a whole category of "what did we decide" emails.

And when somebody tries to jump the line, which they will, don't punish them. Just gently point them back to the system. "Got this, I'll have an answer for you in my 3pm block." Do that three times and they'll stop testing it.

You could set all of this up by Friday. Most owners won't, and it isn't a time problem.

Being instantly available feels like being valuable.

When you answer in four minutes, you feel needed. You feel like the business can't run without you. Some of us built our whole identity on being the person who always picks up. I know I did. When the business was falling apart a few years ago, being reachable at every hour was how I proved to myself I was still in the fight.

But being reachable isn't the same thing as being useful. The most useful thing you can give your clients is your best thinking, and your best thinking can't survive being sliced into forty seven second pieces.

Somewhere in your week there's a version of you who could solve a problem nobody else can solve. He just never gets more than two minutes alone.

Announcing it without changing yourself. If you publish response times and then keep answering instantly, you just taught everyone the policy is fake. The behavior change has to start with you.

Going too strict too fast. Don't go from always on to two email checks a day overnight. Start with one protected two hour block each morning. Expand once it holds.

Forgetting the real emergencies. Keep one clear path for those, usually a phone call, and make sure people know they're allowed to use it.

Making it about you. Frame every change around what they get. Clearer answers at predictable times. That's a better deal for everybody.

I built out everything from today's letter so you don't have to rebuild it from an email.

It's called The Quiet Line Kit. Inside you'll find the two day interruption log with the sorting columns, a fill in channel map, response time templates for your email signature, client welcome doc and team handbook, scripts for telling clients and your team about the change without sounding like a diva, a "Before You Ask Me" doc template, a decision rights grid with spending and scheduling limits you can set, a notification rebuild checklist for iPhone and Android, an inbox batching schedule, and a fourteen day rollout plan to get it all live before Thanksgiving.

Free. Nothing to opt into. Duplicate the page into your own Notion and start tomorrow.

Get The Quiet Line Kit here

And if you run the log and realize the interruptions aren't really the problem, that the whole business routes through you because there's no structure underneath it, that's a bigger conversation. It's the exact kind of thing we work through at Pinnacle Masters. Hit reply and tell me how many tally marks you got.

Skip the full rollout for now. Two things.

Tomorrow, keep the interruption log. One day is enough to start. Who, what channel, what they needed, did it need me.

Then pick one channel and give it a published response time. Put it in your email signature before Friday.

That's it. One log and one sentence.

Nine weeks from now the year will be over. I'd love for you to look back on the busiest stretch of it and realize you actually got to think.

One step, one day. Grace over guilt. — Dan Kaufman

Tools I use and trust. If you sign up through these links I may earn a small commission at no extra cost to you. I only recommend things I actually use.

Rize.io, time tracking that makes you honest about your hours

Fathom.video, AI meeting notes that actually capture what matters

Go High Level, forms, CRM and follow up in one place

Make.com, automate your workflows without writing code

Beehiiv, where serious newsletter operators publish