All decisions wait for the owner: why delegating tasks doesn’t free up the business owner

Assigning a task and transferring decision-making authority are two different steps. If the team is responsible for execution but must get approval for every deviation from the plan, the manager remains a bottleneck in the company’s operations.

Constant questions do not always indicate a lack of initiative. Often, an employee knows what needs to be done but does not understand which decisions they are authorized to make independently.

There can be several reasons. The manager may not have clearly defined the boundaries of authority or may have assigned several tasks with the same level of urgency. Sometimes, an employee avoids making independent decisions after the manager reacted harshly to a mistake. In other cases, the team has simply become accustomed to waiting for approval: the owner asks employees to take on more responsibility but then reviews every decision and changes it without explanation.

Start with specific examples. For one week, track the questions for which the team needed approval and how long they had to wait for an answer. This will make it clear what is actually slowing the work down: insufficient information, conflicting priorities, or a lack of authority to act.

Not every decision requires the same level of oversight. Useful guidelines include the potential consequences, the cost of a mistake, and how easily the decision can be reversed.

For example, the person responsible can change the sequence of internal tasks if it does not affect commitments made to clients. They can also make purchases within the approved budget without obtaining separate approval. However, changing the price for a key client, making significant expenditures, or launching a new line of work should be discussed with the manager.

The rule “get approval for everything important” does not work here. To an employee, any unusual situation may seem important, so they will turn to the manager for approval again. It is much more useful to define specific boundaries: a spending limit, the types of commitments that can be made to clients, and situations in which a decision cannot be easily reversed.

Autonomy starts with a clear assignment. People need to know the expected outcome, have access to the necessary information, and understand the boundaries within which they can choose how to proceed.

For example, an employee is responsible for preparing a proposal by Friday. They determine the workflow for the week and coordinate with the designer on a time to prepare the layout. If there is a risk of missing the deadline promised to the client, they notify the manager before confirming a new date. This makes it clear where the authority to change the internal plan ends and where approval is needed for an external commitment.

These rules are best discussed using examples from day-to-day work. For one role, the key boundary may be spending; for another, it may be contract terms or the impact on the customer experience. If a situation falls outside the defined boundaries, the employee will know when to ask for help rather than waiting for permission at every step.

A manager can stay informed about the progress of work without requiring approval for every action. It is enough to agree on the expected outcome, when progress should be reviewed, and which risks the team should report immediately.

During regular meetings, discuss decisions that have already been made: what worked, what consequences were unexpected, and which guidelines were missing. This allows the manager to monitor results and refine the boundaries of autonomy. At the same time, employees do not have to put their work on hold every time they face a choice.

Mistakes also need to be reviewed. If a decision was made within the agreed boundaries, determine what information was missing or what the team assessed incorrectly. Help address the consequences and clarify the rule for the future. When people are penalized for making a good-faith attempt, they are more likely to seek permission the next time, even for routine decisions.

Agreements about authority should be accessible during the work process. In a task in Uspacy, the manager assigns a person responsible, specifies the deadline, and describes the expected outcome. For example: “Prepare the proposal by Friday. Determine the order of internal tasks yourself, but get my approval before changing the deadline promised to the client.” These boundaries should be defined when assigning the task, so the employee can start working without unnecessary clarification.

The team can keep questions, proposed solutions, and the final agreement in the task comments. A key comment can be pinned so that the guideline does not get lost in the discussion. The manager monitors deadlines and statuses and enables the “Review after completion” option for results that genuinely need to be reviewed and accepted personally. This allows the manager to review completed work without approving every intermediate step.

Autonomy also requires access to the right tools and data. If an employee works with clients in the CRM, it is worth reviewing their access permissions: can they see the necessary deals and perform the assigned actions? At the same time, technical access does not replace agreements about authority. The team should separately define which decisions the employee can make independently and which require the manager’s approval.