If constant interruptions are running your business day, the long-term answer is not better concentration. It is reducing the number of things in the business that require access to you. That means finding out: Who interrupts you. What they need. Why they need you. Why they need you now . Whether somebody else should handle it. And what needs to change so the same interruption does not return tomorrow. Because there is a big difference between: Protecting yourself from interruptions and: Building a business that produces fewer interruptions. Noise-cancelling headphones can help you concentrate. Turning notifications off can help. Blocking two hours in the diary can help. Closing the door can help. I do all sorts of things to protect attention. But if your Operations Manager still needs you to approve a £200 purchase, three employees need answers only you know, a customer rings you directly whenever something goes wrong and your finance team cannot resolve an issue without your decision, focus techniques are treating the symptom. The business has been designed around access to you. That is the system I would fix. Constant interruption has a real cognitive cost It is tempting to dismiss interruptions because most of them are tiny. "Quick question." "Got a minute?" "Can you approve this?" "Where is...?" "What do you think about...?" Most take less than five minutes. The problem is that the interruption itself is only part of the cost. You have to: Disengage from what you were thinking about. Understand the new issue. Switch context. Make a decision. Then reconstruct where you were before. Research on workplace interruption consistently identifies additional cognitive workload associated with switching and resuming tasks. A 2024 experimental study found interruptions increased mental workload, while research involving office workers describes the additional cognitive demands required to suspend one task, deal with another and then reconstruct the original goal. One well-known University of California study found that interrupted workers sometimes compensated by working faster afterwards, but at the cost of greater stress, frustration, time pressure and effort. So ten three-minute interruptions are not necessarily only thirty lost minutes. Your day becomes fragmented. And fragmentation is particularly expensive when the work you were trying to do required sustained thought. Strategic work gets hit hardest Routine administration is relatively easy to resume. Deep commercial thinking is not. You are halfway through: Pricing strategy. A difficult management decision. Capacity planning. Financial analysis. A major proposal. Recruitment structure. Then: "Quick question." You answer. Return. Where were you? This is why an owner can spend ten hours at work and leave feeling as though nothing important moved. They were busy throughout. They were simply never allowed to remain with anything long enough to create much leverage. A recent experimental study found that the impact of an interruption varies according to when it occurs during complex decision-making, with interruptions during an evaluation and selection phase producing poorer task performance in that experiment. Timing matters. Not every minute of your working day is equally interruptible. UK businesses already report lacking time to improve how they operate The ONS Management and Expectations Survey found that 36% of UK firms with ten or more employees identified having too little time to think about or implement changes as the biggest barrier to improving management practices. That is interesting because it creates a horrible loop. The business interrupts you because its systems and management need improving. Those interruptions prevent you spending time improving its systems and management. So the weaknesses continue. Which produces more interruptions. You become too busy maintaining the current system to create a better one. Do not start by blaming your employees This is important. If people constantly interrupt you, it is very easy to conclude: "They need to stop asking me everything." Maybe. But people normally behave in response to the structure around them. If asking you is: Fast. Safe. Normal. Rewarded. And routinely produces an answer. Why wouldn't they? Imagine an employee can spend twenty minutes trying to find information. Or ask you and get the answer in twelve seconds. From their perspective, asking you is efficient. The problem is that what is efficient for the individual employee can be horribly inefficient for the owner and the organisation. Your availability has become a shortcut. Every interruption is evidence about the business This is the mindset shift I would make. Instead of only thinking: "This person interrupted me." Ask: What did this interruption reveal? Perhaps: Information is hard to find. Authority is unclear. A manager is not managing. A process is broken. The standard exists only in your head. Nobody owns something. A customer relationship is overly dependent on you. The employee lacks capability. The issue genuinely requires owner judgement. Or you have accidentally trained everybody to ask you first. Now the interruption becomes diagnostic data. That is useful. Run an interruption audit before trying to fix anything For ten working days, capture meaningful interruptions. You do not need a complicated app. A simple note will do. Record: Who interrupted me? What did they need? What category was it? How urgent was it actually? Could someone else reasonably have dealt with it? Why couldn't they? Was this a repeat? How did it reach me? What would prevent this interruption next time? Do not initially obsess about the exact minutes. The pattern matters more. By the end of two weeks, your chaos often becomes surprisingly repetitive. Group interruptions into categories I would start with seven. 1. Information interruptions "Where is...?" "Do you know...?" "What did we agree with that customer?" These indicate knowledge or information dependency. 2. Decision interruptions "Can I do...?" "Which option should we choose?" "Can you approve...?" These often indicate unclear decision rights or insufficient authority. 3. Problem interruptions "This has gone wrong." "What should we do?" These may indicate weak problem-solving capability or management escalation. 4. Update interruptions "Just letting you know..." "Quick update..." These can indicate poor reporting rhythm or unclear expectations around communication. 5. Customer interruptions Customers contacting the owner directly because they believe that is the quickest way to achieve something. Commercial dependency. 6. Exception interruptions A genuinely unusual situation outside existing rules. Some of these should reach you. 7. Owner-created interruptions You saw something. Asked a question. Changed a priority. Jumped into a conversation. Checked something. Not every interruption starts with someone else. This category can be particularly illuminating. Count which category dominates Suppose over two weeks you record: 47 interruptions. Seventeen are approvals. Eleven are people asking where information is. Eight are customer issues. Six are managers bringing raw problems. Five are genuine owner-level decisions. Excellent. You do not have a generic interruption problem. You have: An authority problem. An information problem. A customer-routing problem. And a smaller management problem. That is much easier to solve. Fix information interruptions by moving knowledge out of your head If people repeatedly ask: How do we do this? Where is that? What did we agree? What do we charge? Which supplier do we use? then your memory is part of the operating system. Create a better source. That might be: CRM. Shared customer notes. Pricing rules. Process notes. Project system. Internal knowledge base. Simple FAQ. Shared folder. Standard templates. It does not need to be sophisticated. It needs to be easier than asking you. Searchability matters A thirty-page manual nobody can navigate does not solve: "Where is the answer?" Make recurring information easy to find. Logical location. Sensible naming. Searchable documents. Current version. Clear ownership. Then when someone asks you: "Where is...?" you can redirect them. Not answer it forever. The short-term response takes slightly longer. The long-term dependency falls. If information changes regularly, give someone ownership of keeping it current Otherwise documentation decays. Someone needs to own: Price list. Supplier information. Customer records. Procedures. Templates. Whatever matters. A stale information system simply drives people back to the person they trust. Usually you. Fix decision interruptions by defining authority This is probably one of the fastest wins available to many owners. For two weeks, note every decision somebody asks you to make. Then ask: Did this genuinely require ownership-level judgement? If not, create a boundary. For example: Managers can approve expenditure up to £2,000 inside budget. Customer complaints up to £500 can be resolved without owner approval. Sales can discount within agreed margin rules. Operations controls overtime inside a defined weekly limit. Project Managers may change suppliers from an approved list. Now routine decisions move. Exceptions remain. The aim is not removing the owner from every decision Some decisions belong with you. Major capital commitments. Serious legal or regulatory exposure. Strategic customers. Senior appointments. Shareholder decisions. Material risk. Fine. But the fact that some decisions require you does not mean every decision should climb to the same level. The owner should increasingly manage exceptions rather than normal operating decisions. If staff continually ask for permission, look at how you react when they don't This one matters. Perhaps an employee once made a decision without asking. You disagreed. Then said: "Why didn't you check with me first?" What did they learn? Check. Next time they check. Then you become annoyed because: "Nobody can make a decision without me." Be careful what behaviour you train. If you want independence, you need to tolerate reasonable decisions that differ from your preferred decision. Not reckless ones. Reasonable ones. Fix problem interruptions by requiring recommendations Manager arrives. "We've got an issue." Instead of immediately solving it: "What do you recommend?" If they have no recommendation: "What are the options?" Now the thinking stays with the person closer to the problem. You may still contribute. But the business begins building problem-solving capability away from you. This is one of the simplest interventions I know. Gradually increase the quality of escalation A weak escalation sounds like: "We've got a problem." Better: "We've got three options." Better still: "I recommend option B because of cost, customer impact and timing. It requires you because it exceeds my £10,000 authority." That last one is worth interrupting you for. The manager has already done the thinking. You provide the genuinely senior decision. That is leverage. Managers should filter interruptions before they reach you One major purpose of a management layer is compression. Ten employee questions should not automatically become ten owner questions. A manager should: Answer. Decide. Prioritise. Coach. Combine. Escalate only what genuinely needs moving upward. If your manager's primary role is forwarding other people's problems to you, Article #38 applies. You do not yet have enough management leverage. Fix update interruptions with a communication rhythm Some interruptions happen because nobody knows when else they will get your attention. So they tell you everything immediately. Create predictable review points. For example: Weekly operational review. Daily ten-minute huddle during a temporary high-pressure project. Fortnightly manager one-to-one. Monthly finance review. Now people can ask: Can this wait until Tuesday? Often it can. The issue still gets attention. It just stops hijacking whatever you were doing at 10:17 on Monday morning. Batch non-urgent questions One simple approach with managers: Keep a running list. Unless something meets the agreed escalation criteria, bring it to our scheduled conversation. This teaches discrimination between: Important. and: Important right now. Those are not the same thing. Not every interruption should be eliminated This is critical. Research into workplace interruptions is not completely one-sided. Daily interpersonal interruptions can carry social benefits alongside the cognitive cost of task switching, including interaction and belonging. Businesses need conversation. Spontaneity. Questions. Relationships. Learning. I would never want an organisation where nobody dares speak to the owner. The target is not silence. It is removing unnecessary dependency-driven interruptions . A good interruption can be worth the disruption Examples: Serious safety issue. Major customer risk. Someone has discovered a significant commercial opportunity. Important employee welfare issue. Material fraud concern. Critical equipment failure. A decision where delay creates substantial cost. Interrupt me. The goal is that the interruptions which remain are increasingly worth interrupting you for. Define what urgent actually means Without a definition, urgency becomes personal. Employee: "This is urgent." Why? "Customer wants an answer." When? "Today." It is 9:15am. Not necessarily urgent. Create escalation criteria. Perhaps urgent means: Safety or compliance risk. Customer operation stopped. Material financial exposure. Deadline inside two hours with no authorised solution. Major strategic customer risk. Something irreversible will happen before the next review point. Now people have a framework. Your communication channels should reflect urgency If everything comes through the same route, everything feels equally important. You might create simple rules. Phone call: Genuinely urgent and needs immediate decision. Instant message: Time-sensitive but not emergency. Email or task system: Normal work. Scheduled review: Issues requiring discussion but not immediate response. The exact channels do not matter. The architecture does. People need to know: How should this reach me? and: When can they expect a response? This is Availability Architecture Availability is not simply a personal preference. It shapes organisational behaviour. If you are: Always reachable. Always responsive. Always willing to decide. Always willing to rescue. then the business adapts. People route more through you because access is easy. Availability Architecture means deciding deliberately: Who needs access? Through which route? For what type of issue? At what times? With what expected response? What bypasses normal rules? That is very different from simply putting your phone on silent. Instant response creates instant escalation Suppose employees know you answer Teams messages in under thirty seconds. Why spend ten minutes solving something themselves? Ask Adam. You unintentionally create an economic incentive for interruption. This is not because employees are lazy. They are using the fastest available resource. If you want people to use managers, systems and their own judgement, those routes need to become normal. Your immediate answer should stop being the default shortcut. Sometimes being slightly less responsive improves the system Not irresponsibly unavailable. Simply not instant. Someone messages: "Can we use Supplier B?" Instead of immediate reply, they may spend five minutes checking the approved supplier list. Problem solved. You never knew it existed. Interesting. Your availability can suppress other people's problem-solving because it removes the need for them to exercise it. Fix customer interruptions by transferring relationships Customers can become trained too. Something goes wrong. They phone the owner. Owner fixes it. Next issue? Owner. Eventually your organisational structure is irrelevant because the customer's escalation process is: Call Adam. For important customers, transfer operational ownership deliberately. Introduce the account owner. Let them lead meetings. Route service issues there. Back them publicly. You may remain strategically involved. You do not need to remain the customer-service escalation point for normal issues. Watch where you undermine the transfer Customer emails you. Copies manager. Do you reply first? Then why would the customer bother with the manager? You need to redirect. "Sarah owns this. Sarah, can you pick it up please?" Over time the relationship moves. If you keep proving that the owner is the fastest route, nothing changes. Fix process interruptions at the source An interruption often appears as a people problem. "Why do they keep asking me this?" Look deeper. Perhaps the process creates ambiguity. Example: Every unusual quote comes to you. Why? Because pricing rules don't cover the work. Fine. Improve pricing logic. Every scheduling conflict reaches you. Why? Because priorities are unclear. Define priorities. Every customer refund reaches you. Why? No authority level. Set one. The interruption disappears because the ambiguity disappears. Repeated interruptions are process signals Once? Question. Twice? Interesting. Ten times? System. Do not spend your career answering the tenth version of the same question. Solve the question category. Watch interruptions at handovers Many owner interruptions occur between roles. Sales to operations. Operations to finance. Estimator to delivery. Manager to manager. Nobody quite knows who owns the gap. So the issue floats upward. You become the bridge. Map the handover. What leaves Role A? What must Role B receive? Who confirms it happened? Interdepartmental ambiguity creates enormous owner noise. Stop making yourself the interdepartmental translator Sales asks you what Operations meant. Operations asks what Sales promised. Finance asks what Operations completed. You carry information around the company. That may have worked when everyone reported directly to you. As the company grows, managers need to coordinate with each other. Otherwise you do not have a management team. You have separate spokes connected through the owner. Fix recurring questions with training Sometimes the employee genuinely doesn't know. Show them. But notice repetition. If someone asks the same category of question repeatedly, perhaps the issue is: Training. Confidence. Capability. Or the fact that you keep answering instead of helping them develop judgement. Your response matters. Use questions to build independent thinking Try: "What do you think the answer is?" "What would you do if I wasn't here?" "What have we done previously?" "What does the process say?" "What are the risks?" "What do you recommend?" You are still accessible. But the cognitive labour starts shifting. That is how interruptions gradually become better conversations. Do not turn every interruption into a coaching session either There is another extreme. Employee asks: "Where are the spare printer cartridges?" You respond: "What do you think?" Don't be ridiculous. Sometimes answer. The point is using judgement. The bigger the decision and the more recurring the dependency, the more useful it becomes to move the thinking. Owner-created interruptions deserve special attention This is often missed completely. You walk through Operations. Notice something. "What are we doing with this?" Manager stops. Explains. You see another thing. "Why is that there?" Someone else stops. Then: "Can we change this today?" You just interrupted three people's work. Owners often complain about being interrupted while simultaneously interrupting the entire company. Leadership attention has weight. Every casual question from the owner can sound like: Priority. Do not think out loud at employees unless you want action Owner: "Could we maybe change the vans next year?" Employee hears: Research vans. Owner has forgotten the conversation by lunch. Two days later someone produces three quotations. This happens. As the company grows, distinguish: Idea. Question. Instruction. Decision. Otherwise your thinking creates work. Stop changing priorities through interruption Someone is doing important work. You see them. "Can you quickly do this first?" Another request. Then another. By Friday you wonder why the important work isn't complete. Owners can create the exact fragmentation they experience themselves. Use managers and priorities. If something genuinely changes, consciously reset the priority. Do not add another one. Protect deep work after fixing the routes Once you have reduced structural interruptions, personal attention management becomes far more useful. Now create protected periods for work requiring sustained thought. Maybe: Two mornings a week. Ninety minutes a day. Whatever fits. During that period, only defined urgent issues interrupt. Everything else queues. The precise schedule is less important than the principle. Some work deserves uninterrupted capacity. Research supports protecting demanding work from poor interruption timing A 2025 experimental study found that interruptions during periods of higher mental workload produced different performance effects from interruptions at lower-load moments, supporting the idea that interruption timing matters rather than all interruptions being equivalent. That suggests a practical approach. Do not merely ask: Can people interrupt me? Ask: When is interruption particularly expensive? Protect those periods. But focus blocks cannot compensate for structural dependence This is why I would never begin with the calendar. Imagine you block: 9am to 11am. No interruptions. Great. Meanwhile: Five employees waiting for your decisions. Operations Manager cannot approve something. Customer waiting for your call. Work has stopped. At 11am you emerge and inherit a queue. You did not remove dependency. You delayed it. The business needs decisions to exist elsewhere where appropriate. Then focus time becomes sustainable. Track interruption volume as a management KPI for a while If owner interruption is a genuine business constraint, measure it. Not forever. For a month. How many significant interruptions reached you each day? How many were: Information. Decision. Problem. Customer. Update. Genuine exception. How many truly required you? Then work on the largest unnecessary category. If owner-routed interruptions fall from: Thirty a day to: Twelve, something structural changed. That is useful evidence. Track repeat interruptions separately This may matter even more. You had sixteen interruptions. How many were essentially the same issue as last week? Repeat interruptions indicate the business learned very little from the previous one. Article #34 made the same argument around firefighting. The principle holds here too. Repeated owner attention should trigger structural improvement. Use an Interruption Tax question For every recurring interruption, ask: What would have to change for this never to need me again? Sometimes the answer is: Nothing. This is genuinely owner-level work. Fine. Other answers: Manager authority. Training. Documented standard. Customer transfer. System change. Better data. Different employee. Clear process. That one question moves you from frustration to design. Fix one interruption category at a time Do not announce: "Nobody interrupt me anymore." Terrible idea. Take the largest category. Perhaps approvals. For thirty days: Map every approval. Set thresholds. Transfer decision rights. Track what returns. Then: Information questions. Then: Customer escalations. This creates controlled improvement. People understand what changed. A practical 30-day interruption reset Week 1: Capture Record meaningful interruptions. Do not judge people. Collect: Source. Reason. Urgency. Channel. Whether you were genuinely required. Week 2: Diagnose Group them. Information? Decision? Problem? Update? Customer? Exception? Owner-created? Identify the two largest avoidable categories. Week 3: Redesign For those two categories, change the mechanism. Maybe: Decision threshold. Manager ownership. Shared information. Scheduled review. Customer transfer. Escalation rule. Training. Week 4: Test Protect one or two focus periods. Route issues through the new structure. Count what still reaches you. Then ask: Why? Repeat. What if employees ignore the new boundaries? Check whether you reinforce them. Employee bypasses manager. Do you answer? Employee asks something documented. Do you give the answer anyway? Manager asks for approval inside their authority. Do you approve it? If yes, the old system is still easier. Boundaries become real through behaviour. Not announcements. What if managers keep interrupting you? Managers are allowed to need support. But look at the pattern. Are they bringing: Strategic exceptions? Or normal management? If normal management continually travels up, determine why. No authority? Weak confidence? Insufficient capability? Fear of being wrong? Owner history? Article #38 becomes relevant again. A management layer should reduce owner interruption. If it doesn't, something in the layer needs strengthening. What if you actually enjoy being interrupted? This is another uncomfortable possibility. Being needed can feel good. Someone appears. You solve something. Immediate usefulness. Strategic work feels slower. No instant praise. No dramatic resolution. An owner's day can become addictive precisely because interruption supplies continual evidence: I matter. Notice that. The goal is not becoming irrelevant. It is moving your relevance to work with greater leverage. Constant accessibility can become part of your identity "I'm always available for my team." Lovely intention. But what outcome does that create? Support? Good. Dependency? Less good. Your people can know you will support them without having unrestricted access to your attention for every small issue. Support architecture is different from permanent availability. Measure success by what happens when you are unavailable One of the best tests is controlled absence. Not disappearing irresponsibly. Choose a period. Perhaps: Two-hour protected block. Half day. Eventually full day. Normal operational issues should not reach you. Then review. What waited? What was solved? What went wrong? What information or authority was missing? Every absence becomes a stress test of the operating system. Do not celebrate zero interruptions That is not necessarily success. Maybe people are frightened to raise things. Maybe you created an enormous communication delay. Maybe important information is now hidden. The target is: fewer low-value, unnecessary, dependency-driven interruptions. Not silence. You still want meaningful communication. The best interruptions become higher quality Early business: "Customer is unhappy. What do we do?" Later: "Customer is unhappy. We have resolved the operational issue under my authority. I want your input because the relationship is strategically important." That interruption is worth your time. Early: "Can I order this?" Later: "Our main supplier has failed and the alternative creates a £35,000 exposure outside my authority. Here are the options." Worth interrupting. The volume falls. The level rises. That is what you want. How Evolve approaches constant owner interruptions If an owner tells me: "I cannot get anything done because everybody constantly interrupts me." I do not start with: Turn off notifications. We can do that later. I want to know: Who interrupts you? What do they need? What decisions require you? What information exists only in your head? Which managers are being bypassed? Which approvals could move? Which customers depend on direct owner access? What repeats? How quickly do you normally respond? What happens when you don't? How often are you creating the interruption yourself? Then we redesign the routes. That might involve: Decision rights. Availability Architecture. Management development. Better information. Customer transfer. Escalation rules. New meeting rhythm. Systems. Training. The result I want is not merely: "You feel more focused." It is: The business now needs less of your immediate attention to keep moving. Much stronger. This is another form of dependency removal If your business depends on: Your decisions. Your memory. Your immediate response. Your relationships. Your willingness to solve problems. then interruptions are simply the visible symptom of that dependency. Your diary is showing you the organisation chart. Every interruption says: This work still routes through you. Some should. Many probably shouldn't. That makes your interruptions one of the richest diagnostic datasets you already possess. So, how do you stop constant interruptions running your business day? Do not begin by hiding from everybody. Record the interruptions. Classify them. Find the repeat categories. Move information out of your head. Clarify manager ownership. Give people decision authority. Require recommendations rather than raw problems. Create scheduled communication rhythms. Define genuine urgency. Build deliberate communication channels. Transfer routine customer relationships. Fix weak handovers. Train people where capability is missing. Stop instantly answering everything simply because you can. And protect deep work once the organisation has somewhere sensible to route normal issues while you are unavailable. Because constant interruptions are not only an attention problem. They are often an organisational design problem. If the entire business has been trained to borrow your brain every time uncertainty appears, no productivity technique is going to give you a genuinely quiet day. You have to change where answers, authority and responsibility live. Do that, and you do not merely become better at concentrating. You build a business that can continue working while you do.

Making profit but always short of cash? Learn how debtors, stock, WIP, tax, growth and loan repayments can drain cash from a profitable business.

Worried standards will fall if you delegate? Learn how to transfer work, decisions and quality controls without becoming a micromanager.

Still doing everything as your business grows? Learn which tasks, decisions and responsibilities an owner should progressively stop doing and why.

Sales growing faster than your business can deliver? Learn how to diagnose capacity, management, margin, cash and systems before growth turns into chaos.