Most business owners start the day with a plan and end it having done something else. A customer rings about a late delivery. A supplier misses a date. A staff member needs a price approved. A machine breaks down. A quote is due by five. Each issue is reasonable on its own. Together they consume the day, and the work the owner meant to do, such as winning better customers, improving a process or planning next year, waits for a quieter week that never arrives.
Management writer Henry Mintzberg, studying what managers actually do, found that their work is typically fragmented, varied and reactive, conducted in short bursts and often started by other people. That description fits most small business owners. In those conditions, the owner’s attention becomes the business’s scarcest resource, and how it is spent shapes the business as much as how money is spent.
This article explains why attention is a governance problem rather than just a time management problem, how to treat interruptions as evidence about the business, four tests for deciding what deserves the owner’s attention, why recurring problems need system fixes rather than repeated rescue, and how to protect time for the issues that matter but are never urgent.
Attention is an allocation decision
Every hour spent on one issue is an hour not spent on another. Unlike money, attention rarely appears in any report, so its cost goes unnoticed. But staff watch where the owner’s attention goes and learn from it. If the owner always jumps on urgent operational problems but rarely discusses customers, capability or future plans, the business learns that urgency matters more than importance.
Three common misreadings make this worse:
- Responsiveness is mistaken for effectiveness. An owner who answers every question immediately may look highly engaged while teaching the business to escalate rather than solve.
- Urgent is mistaken for important. Deadlines and pressure attract attention naturally. Ambiguous, long-term problems with no deadline are postponed, even when their consequences are larger.
- Overload is treated as a personal productivity problem. Better calendars and task lists help, but they do not fix a business that has more work, more decisions and more projects than its people can absorb. That is a problem of priorities and design.
Interruptions are evidence
A useful shift is to stop asking “how can I cope with everything?” and start asking “why does this kind of issue keep reaching me?” Each interruption says something about how the business is designed:
- Unclear decision rights: staff are not sure what they may decide.
- Missing standards: there is no pricing guide, approval limit or procedure, so each case comes to the owner.
- Weak information: people cannot see what they need to act.
- Conflicting priorities: two parts of the business want different things and nobody has set the rule.
- Too many initiatives: the business is running more change than it can manage.
- A culture of upward delegation: problems are passed up because that is what has always happened.
Recording interruptions for a week or two, by type, usually reveals that a handful of categories account for most of them.
Exceptions and recurring problems
Reacting is not always bad. Some problems genuinely need the owner: a serious safety incident, a major customer crisis, a decision that only the owner has the authority or knowledge to make. Those are exceptions, and handling them is part of the job.
The tenth occurrence of the same scheduling dispute is not an exception. It is evidence that the system has not been fixed. A useful habit after any significant intervention is to ask: was this a genuine exception, or did I just compensate for a design weakness?
Four tests for what deserves the owner’s attention
| Test | Question | Typical response |
|---|---|---|
| Consequence | What happens if this is handled badly or ignored? | Keep high-consequence matters with the owner |
| Reversibility | Can the decision be changed cheaply later? | Reserve the owner’s attention for hard-to-reverse choices |
| Recurrence | Is this a one-off, or a repeated system failure? | Fix recurring causes, not just each event |
| Delegability | What is the lowest level that can decide this safely? | Push authority there, with clear limits |
A fifth question applies across all four: does this issue relate to what the business is actually trying to achieve? A consequential issue may still not deserve continued attention if the work behind it no longer matters.
Fix the cause, not just the event
When an issue recurs, the solution usually lies in one of a few design changes:
- Delegate authority with clear limits, such as approving purchases or discounts up to a set amount. The delegating without losing control article describes how to do this safely.
- Create a standard: a pricing guide, a checklist, a default rule for common conflicts.
- Improve information: make schedules, stock or job status visible to the people who need them.
- Set a priority rule for recurring conflicts between functions, such as sales and production.
- Reduce the number of initiatives running at once.
Each takes some effort up front. Each removes a recurring demand on the owner for good.
Make escalation rules explicit
Staff escalate when they are unsure whether they are allowed to decide. A short, written set of escalation rules removes much of that uncertainty. For each common type of decision, state who decides, up to what limit, and what should come to the owner. For example: discounts up to 5% are approved by the salesperson, up to 10% by the sales manager and above that by the owner; any safety concern stops work and comes straight to the owner; any customer complaint involving more than a set amount is reported the same day.
Clear rules work in both directions. They reduce unnecessary escalation, and they make sure the issues that genuinely need the owner arrive quickly rather than being held back until they become crises.
Develop people who absorb problems
The long-term answer to owner overload is not just delegating tasks but developing people who can solve problems on their own. That means sharing the reasoning behind decisions, not just the answers; asking “what would you do?” before giving a view; and accepting that others will sometimes decide differently from how the owner would have. An owner who solves every problem personally becomes indispensable while the business stays small. An owner who teaches others to solve problems builds a business that can grow.
Relationships extend capacity
Mintzberg’s research also showed that managers spend a great deal of time with people outside their direct line: peers, customers, suppliers and contractors. This is not wasted time. Good relationships bring information early, make coordination faster and reduce the number of problems that arrive as crises. An owner with strong relationships with key customers and suppliers hears about problems while they are still small.
Protect time for the future
The hardest discipline is protecting time for questions with no deadline and no obvious owner: changing customer behaviour, new technology, succession, dependence on one customer or supplier, skills the business will need in three years. These questions always lose to today’s problems, because their consequences are uncertain and distant.
Practical ways to protect them:
- A regular, protected block of time for working on the business rather than in it, treated as seriously as a customer meeting.
- Separate meetings for running the business and for choosing its direction. If every management meeting is consumed by this week’s problems, nobody ever discusses the future.
- A short list of strategic questions reviewed monthly, so they are not forgotten between crises.
This does not mean more meetings. It means deliberately reserving some attention for what the normal rhythm of the business would otherwise crowd out.
Attention limits how much change a business can take on
Owners often approve initiatives one at a time, each sensible on its own. But each needs the owner’s attention to sponsor, unblock and decide. A business with eight improvement projects that each need the owner’s involvement may be unable to deliver any of them well, even if the money is available. Treat the owner’s attention, and that of key managers, as a limit when deciding how many initiatives to run. The where strategy is really decided article looks at capacity and attention as constraints on strategy.
A worked example
This is an illustration. The owner of a precision engineering workshop with 22 staff feels permanently overloaded. For two weeks, she records every interruption that needs her decision, by type:
| Type | Count |
|---|---|
| Approving prices on quotes | 18 |
| Scheduling conflicts between sales and the workshop | 14 |
| Purchasing approvals under $500 | 11 |
| Customer complaints about delivery dates | 9 |
| Genuine exceptions | 6 |
| Other | 6 |
| Total | 64 |
Only six were genuine exceptions. The rest pointed to four design problems, and she addresses each:
- Quote approvals: she writes a pricing guide with standard rates and margin rules. The estimator can approve quotes within the guide; only unusual jobs come to her.
- Scheduling conflicts: a weekly 30-minute planning meeting between sales and the workshop manager, with a simple priority rule for urgent jobs.
- Purchasing: the workshop manager is authorised to approve purchases up to $2,000.
- Delivery complaints: delivery dates are confirmed with the workshop before being promised to customers.
Two months later, she records interruptions again. The total has fallen to about 23 in a fortnight: the six exceptions, six other matters, about five unusual quotes, three scheduling escalations and three delivery issues. She uses the time recovered to block out Friday mornings for visiting key customers and planning, and the estimator and workshop manager both say they prefer having the authority to decide.
How this applies to a small Australian business
In small businesses, the owner is often the default decision-maker for everything, which limits how much the business can grow. Practical steps:
- Record interruptions for a week or two, by type.
- Separate exceptions from recurring problems.
- Apply the four tests: consequence, reversibility, recurrence and delegability.
- Fix recurring causes with delegation, standards, information and priority rules.
- Build relationships with key customers and suppliers so problems surface early.
- Protect regular time for working on the business.
- Hold separate meetings for operations and direction.
- Limit the number of initiatives that need your involvement at once.
The key-person dependence article covers what it costs when too much depends on one person.
Signals worth watching
- A calendar broken into dozens of short interruptions.
- The same issue reaching you repeatedly.
- Decisions made mainly because a deadline has arrived.
- Staff waiting for your approval on matters they understand better than you.
- Important, non-urgent issues discussed rarely or never.
- More initiatives than you can personally sponsor.
- Every management meeting consumed by this week’s problems.
Common mistakes
- Treating responsiveness as the measure of good leadership.
- Solving the same problem repeatedly instead of fixing its cause.
- Keeping approvals that could safely be delegated.
- Letting urgent work crowd out important work indefinitely.
- Approving initiatives without considering the attention they need.
- Mixing operational and strategic discussions in one meeting.
Frequently asked questions
How long should I record interruptions? One to two weeks is usually enough to see the pattern. Keep it simple: a tally by type is sufficient.
What if staff are not ready to take on more decisions? Start with low-risk decisions and clear limits, coach them through the first few, and widen the limits as confidence grows.
Won’t customers expect to deal with me? Some will, especially for important relationships. Keep those. Many routine questions are handled perfectly well by others once they have the information and authority.
How do I stop protected time being eaten by emergencies? Treat it like an appointment with an important customer. Move it only for genuine exceptions, and reschedule it rather than cancelling it.
What if the interruptions are mostly genuine exceptions? Then the business may be operating in a very volatile environment, or may need more capacity at management level. Both are worth recognising rather than absorbing indefinitely.
What about the problems only I can solve? Some genuinely are, at least for now: a relationship with a key customer, a technical judgement nobody else can make, a decision only the owner has the authority for. Keep those, but ask which of them could become someone else’s with training or documentation, so the business is not permanently limited by your hours.
Questions to ask
- Which three types of issue consumed most of my time this month, and what produces them?
- Which important, non-urgent issues keep being postponed?
- Which decisions reach me that could safely be made by someone else?
- Do we have more initiatives than I can personally support?
- Are our meetings dominated by this week’s problems?
- What would I stop doing if my time were treated as carefully as the business’s money?
Bringing it together
The owner’s attention is the scarcest resource in most small businesses, and it shapes the business as much as money does. Treat interruptions as evidence, separate genuine exceptions from recurring problems, fix the causes with delegation, standards, information and priority rules, and keep only the consequential, hard-to-reverse decisions at the top. Protect regular time for the future and limit the number of initiatives that need you. A calendar is not just a schedule. It is a record of what the business has trained its owner to care about.
Source: KEVOS notes, drawing on Henry Mintzberg’s research on managerial work and on teaching material on managerial roles and attention. Examples and figures in this article are illustrations.