Making a business less dependent on its owner: start with five bottlenecks

1. Record tasks that come back to the owner

During a normal working week, record what the team has to ask, missing information and waiting time. Choose specific situations such as approving a quotation template, handling an order with missing stock or confirming content before publication. “The team cannot work independently” is too broad to design a change around.

Separate work that genuinely requires the owner’s decision from work that only needs a clear standard. An unusual transaction differs from a routine order with complete conditions. The goal is to identify what can be clarified, rather than stop every question from the team.

2. Check information and contact responsibilities

Someone may be assigned to process orders without knowing the latest template, available stock or who confirms delivery times. Asking for more independence does not resolve missing information. Identify a reference location and update owner for each area.

For work involving several people, choose one contact to maintain the overall status and define each person’s contribution. Agree on complete-information handovers, especially between sales, warehouse and customer service. Do not include customer data in shared documentation accessible more widely than the work requires.

3. Define verifiable outputs

Replace a task such as “prepare a quotation” with a description: a proposal containing confirmed needs, scope, pricing basis, implementation conditions and a next step. The recipient must know what a good result looks like and what evidence demonstrates completion.

Standards should reflect actual needs, rather than appearance alone. For example, correct packing means the right SKU, quantity, condition and required labels, with a pre-delivery check. Do not add steps simply to lengthen documentation; each needs a clear purpose.

4. Choose a recurring task for concise instructions

Prioritize work with identifiable inputs and outputs that currently requires repeated questions or frequent revisions. The person doing the work should help write it, because they know what paper instructions can miss. Record start conditions, main steps and situations requiring a pause to ask.

An SOP is a standard operating procedure for a task with a defined scope. Its first version need not cover every situation. The next article provides a one-page template for checking orders before handover, with completion standards and exception handling.

5. Decision-making authority must accompany responsibility

State what the performer can decide independently, what must be reported and what requires prior approval. Limits may concern change types, commitment scope or permitted resource use. The owner must ensure the team has resources and a way to ask when situations exceed its authority.

An early checkpoint can detect misunderstanding before work goes too far. However, every action need not be reapproved once standards are clear. Select checkpoints with the recipient according to risk and experience.

Test, record exceptions, then expand

A hypothetical situation: a shop starts with an order-checking process before delivery. During the trial, the performer records missing information, points requiring clarification and instructions that do not match reality. The owner reviews outcomes and errors to revise the version.

Track clarification requests, waiting time, rework errors and handover quality. If work becomes faster but errors increase, it cannot yet be called an improvement. Once the process is usable, expand to other tasks and maintain a version with an accountable update owner.

Suggested actions