The Notification That Trained You to Drop Everything

Your phone buzzes. WhatsApp. A supplier asking if that rush order is confirmed.

You were halfway through reviewing the quarterly numbers. Now you're not.

Thirty seconds to answer the message. Forty-five minutes to get back to where you were — if you get back at all.

This happens eight, maybe twelve times a day. You've stopped noticing. It's just how work works.

Except it isn't work. It's reaction. And reaction has become your default operating mode.

The Pavlovian founder

Somewhere along the way, you got trained.

The ping means someone needs you. The reply proves you're responsive. The quick answer keeps things moving. Good founder behaviour, right?

Here's what actually happened: you became the router. Every question, every decision, every minor ambiguity — they all flow through you because you've proven you'll respond in minutes.

Your team learned this. Your suppliers learned it. Your customers learned it. Now they don't check the shared doc or search their inbox or make the call themselves. They just message you. Because you always answer.

You didn't delegate the decision. You delegated the question.

The real cost isn't twelve interruptions

Pick any day last week. Count the pings that pulled you out of something.

Now ask: how many of those actually required you?

Not "you were the fastest option." Not "you knew the answer off the top of your head." Actually required your specific judgment, your authority, your expertise.

For most founders who do this honestly, the number is somewhere between one and three. The rest were questions someone else could have answered — if they knew where to look, or felt authorised to decide, or had a system that didn't route everything through the boss.

The twelve interruptions aren't the problem. The problem is you've built an operation that generates twelve interruptions. Daily. Indefinitely.

What a ping actually represents

That WhatsApp from the supplier? It's not a question. It's a symptom.

It means one of these is true:

1. The information exists somewhere, but it's easier to ask you than find it
2. The information doesn't exist anywhere except your head
3. Someone could make this decision, but they're not sure if they're allowed to
4. There's no defined process, so every instance is a fresh judgment call

Each of those is fixable. None of them get fixed while you're busy being responsive.

The permission problem

This one's quieter, but it's everywhere.

Your warehouse manager knows the rush order is confirmed. Saw the email yesterday. But the supplier asked you directly, and your manager isn't sure if they should jump in on a thread with your name on it.

So they wait. You answer. The pattern continues.

Permission isn't just about job descriptions or org charts. It's about what you've demonstrated is acceptable. If you answer everything, you've demonstrated that answering everything is your job.

Breaking the pattern requires explicit, repeated, visible permission for someone else to handle it — and visible restraint from you when they do.

Building the buffer

The goal isn't to ignore your phone. It's to create a layer between the question and your attention.

This doesn't require fancy software. It requires deciding:

What can be answered without you? Supplier order status. Shipping ETAs. Return policy clarifications. Standard pricing. If it's the same answer every time, it shouldn't reach you.

Where does that answer live? A shared doc. A pinned message. A one-page FAQ your team can forward. The format matters less than the agreement: this is where we look first.

Who's authorised to handle it? Named person, named decisions. "James handles all supplier queries about orders under £500" is a policy. "Anyone can answer routine questions" is a hope.

What's the escalation path? Not everything can be handled without you. But the default should be attempting it first. Escalation should require a sentence: "I checked X and Y, but this needs your call because Z."

The withdrawal period

You will feel useless. For about two weeks.

Questions will go to someone else. They'll take longer to answer. The answers might be slightly less perfect. You'll itch to jump in.

Don't.

The team is learning. Your suppliers are learning. Everyone is recalibrating based on the new pattern you're demonstrating.

Two weeks of slightly slower responses. Then a permanent reduction in the number of things that require your brain.

What you're buying back

An uninterrupted hour. Then two. Then a morning where you finish what you started.

The quarterly numbers actually get reviewed. The pricing model gets rebuilt. The thing you've been meaning to think about for six months finally gets thought about.

That's what the ping costs you. Not thirty seconds. The clarity that only comes from consecutive, unbroken attention.

If this sounds like the kind of problem worth unpicking, that's exactly the work we do — figuring out what's actually generating the interruptions, and building the system that stops them reaching you.