Delegation fails when authority and accountability separate.
I have recently started repeating something to my team: own outcomes, not tasks. I do not want people to define success by the fact that they attended the meeting, sent the email, completed the assigned activity or followed the process. I want them to understand the result the company needs and take responsibility for achieving it.
This is a demanding standard. If a leader consistently fails to produce the outcome the role exists to create, the company must eventually find someone else who can. A startup cannot carry important people indefinitely because they appear busy or can explain every constraint. The business survives through results.
However, a founder cannot demand ownership of outcomes while retaining the authority required to produce them. If every meaningful decision needs the founder’s permission, the employee does not own the outcome. The founder does.
You cannot delegate responsibility and centralise power.
Tasks make it easy to avoid the result
Tasks are attractive because they are easy to observe. A person either prepared the document or did not. The campaign was launched, the feature was released and the customer was contacted. These actions can be placed on a list and marked complete.
The problem is that completed tasks do not necessarily create valuable change.
A salesperson can make one hundred calls without producing a serious opportunity. A product team can release five features that customers do not use. A customer-success employee can close every ticket while customers remain disappointed. If performance is defined by task completion, people can succeed while the company fails.
Outcome ownership changes the question. Instead of asking whether the activity happened, it asks what the activity achieved. Did the work create revenue, improve adoption, restore a customer’s confidence, reduce risk or remove an obstacle preventing another team from succeeding?
This encourages people to adapt. When the first approach fails, an outcome owner tries another route rather than reporting that the assigned task was completed. The person remains connected to the purpose of the work, not merely to its original form.
Accountability without authority is theatre
For outcome ownership to be real, people need enough authority to make relevant decisions. They must be able to choose a method, allocate approved resources, coordinate with other teams and change an approach when evidence shows it is not working.
If the founder must approve every message, price, hire, vendor or product adjustment, the team’s supposed ownership is theatrical. The employee carries the pressure of the target while the founder controls the decisions that determine whether it can be achieved.
This structure also creates delay. The person closest to the problem sees what needs to happen, but action waits until the founder becomes available. By the time approval arrives, the opportunity may have passed or the problem may have become more expensive.
When founders complain that employees do not take ownership, they should examine whether the company has trained people to wait. An employee who is repeatedly corrected for acting without permission will eventually stop exercising judgment. The founder then interprets that learned caution as a lack of initiative.
Authority has to travel with accountability.
Delegation requires boundaries, not unlimited freedom
Giving a person authority does not mean allowing them to make any decision without limits. Delegation needs boundaries because different decisions create different levels of risk.
The leader should understand the objective, budget, time frame, legal constraints and values within which they can act. They should know which decisions they can make independently, which ones require consultation and which ones must be escalated because they could expose the company to serious financial, regulatory, security or reputational harm.
A marketing leader may have discretion over campaigns within an approved budget but require additional authority before making a public claim that creates a legal obligation. An engineering leader may select implementation methods but need security review before changing infrastructure that protects customer funds or data. A commercial leader may negotiate within a defined pricing range but escalate terms that materially affect margin or cash flow.
Clear boundaries make people faster because they remove uncertainty about routine decisions while protecting the company where mistakes could be fatal.
The objective is not permissionlessness. It is decision-making at the lowest responsible level.
The outcome must be genuinely ownable
Before holding someone accountable, the company should ensure that the outcome is clearly defined and substantially within the person’s influence.
“Grow the business” is not a useful delegation. Which customers, which product, which period and which measure of healthy growth? Does the leader own pricing, budget, hiring and the support needed from product? What assumptions is the target based upon?
An outcome may also depend on several teams. If sales cannot close an enterprise customer without a product capability, or marketing cannot launch without compliance approval, the dependencies must be visible. One leader should not receive full blame for an outcome while another team faces no consequence for failing to provide something essential.
Ownership does not remove interdependence. It requires the owner to identify dependencies early, pursue them actively and escalate when they threaten the result. At the same time, the performance system must hold every contributing leader responsible for commitments on which colleagues depend.
The company wins as one organisation, not as a collection of departments defending their individual scores.
“No excuses” should not mean “no reality”
I believe strongly that leaders should find a way. Restrictions are part of building a company, and a person who gives up at the first obstacle cannot own an important outcome. Strong leaders search for alternatives, negotiate for resources and keep moving when the first plan fails.
But “no excuses” should not become a refusal to examine reality. A target can be poorly designed. Market conditions can change. The company can withdraw a necessary resource or create a conflicting priority. A leader should not be punished for an impossible outcome that leadership itself made impossible.
The relevant question is not simply whether the target was missed. What did the person do when the target became threatened? Did they communicate early, propose alternatives, ask for a decision and keep testing possible routes? Or did they wait until the deadline and arrive with a polished explanation?
Accountability should distinguish between an unfavourable result and the failure to behave like an owner.
One missed outcome may produce learning. A repeated pattern of poor judgment, late communication and weak execution is different. When expectations, resources and authority are clear, and the pattern still does not improve, the company should act decisively.
Founders must tolerate decisions they would not have made
Delegation becomes emotionally difficult when a capable leader chooses a reasonable path different from the founder’s preference. If the founder overrides every decision that is not identical to their own, employees will learn that authority is only symbolic.
The test is not whether the founder would have made the same choice. It is whether the choice falls within the agreed boundaries, follows sound reasoning and moves towards the outcome without exposing the company to unacceptable risk.
Some decisions will be wrong. That possibility is inseparable from genuine authority. The company should use review mechanisms, limited experiments and clear risk thresholds to make mistakes survivable, but it cannot develop leaders while protecting them from every consequence of judgment.
Founders should intervene when a decision threatens the company, violates its values or falls outside delegated authority. They should not intervene merely because another competent person has a different style.
Review outcomes and decision quality
An effective review should examine both the result and the reasoning that produced it. A good outcome can occasionally come from a reckless decision, just as a thoughtful decision can produce a disappointing outcome because uncertainty cannot be eliminated.
Leaders should explain what they expected, which evidence informed the approach, what changed and what they learned. This allows the company to improve judgment rather than rewarding luck or punishing every intelligent risk that fails.
The review should end with clarity. What will happen next? Does the strategy continue, change or stop? Does the person require more authority, better support or a narrower objective? Is the problem a correctable gap, or evidence that the role needs another owner?
Accountability is useful only when it changes future behaviour.
Give people the whole responsibility
If you want people to own outcomes, give them the complete responsibility that makes ownership possible. Define the result, explain the constraints, provide reasonable resources and allow decisions to happen without unnecessary founder approval.
Then measure what changed, not merely what was done.
This is demanding for employees because they cannot hide behind completed tasks. It is equally demanding for founders because they must release control, tolerate different methods and accept that delegated authority includes the possibility of mistakes.
The company cannot have one without the other.
When authority and accountability remain together, delegation creates leverage. People act faster, develop judgment and become capable of carrying important parts of the business without the founder’s constant intervention.
When they are separated, delegation becomes blame with a job title.
Leave a comment