"I delegated and it went wrong" is the universal complaint of the founder trapped in the Blue Belt who cannot move up to the Brown. But the complaint hides the real diagnosis: what the founder calls "delegating" is rarely delegating. It is assigning a task, withdrawing, and expecting results without having built the conditions for the other person to succeed.
The second section of the Brown Belt is brutal here: delegation without structure is not delegation, it is abandonment. And abandonment produces exactly the results the founder uses afterwards to justify taking control of everything again.
We go through the five conditions of the book in the three planes.
1. The 5 conditions of effective delegation
Condition 1: clarity of result
Delegation starts with what result, not with what process. Most founders delegate processes ("do these three things") instead of results ("get this number before this date"). The first format infantilizes the team. The second one elevates it.
Clarity of result means:
- What specific metric defines success
- By when (a closed date, not "as soon as possible")
- Under what restrictions (budget, quality, scope)
- What the priority is if there are tradeoffs
If the founder cannot articulate the four, he is not ready to delegate. He is ready to do it himself or to define the problem better before passing it to the team.
Condition 2: authority aligned with responsibility
This is the condition that 80% of founders violate. They assign responsibility ("you are responsible for sales") but they do not hand over the authority ("but I approve every decision"). The result is predictable: nobody wants to be responsible for decisions they cannot make.
The Brown Belt rule: authority must equal responsibility. If a person is responsible for result X, that person has to be able to make the decisions that lead to X. The founder reviews the result, not the path.
If the founder does not trust enough to hand over authority, the problem is not delegation, it is hiring or training. And delegating without solving that is setting the stage for failure.
Condition 3: sufficient resources
Delegating without resources is delegating the blame for the failure. If you ask for a result that requires $50K and you give $10K, you are not delegating, you are preparing an excuse for not assuming the responsibility of the resources.
Resources are not only money. They are:
- Access to complete information
- Access to the key people for deciding
- Access to the tools that accelerate the work
- Time not fragmented by another 12 simultaneous priorities
If the resources are insufficient, the founder has to say it explicitly and understand that the result is calibrated to that level. Honest delegation includes negotiating resources before, not after.
Condition 4: measurable success criteria
Without measurement, there is no possible delegation. There is confusion. The delegated person does not know whether they are complying. The founder does not know whether it is going well. He ends up intervening "just in case", and he breaks the delegation.
Success criteria include:
- Output metrics (sales, conversion, satisfaction)
- Input metrics (activities, process quality)
- Intermediate milestones (review points at 30, 60, 90 days)
- Alert triggers (when to escalate to the founder, when not to)
Condition 5: follow-up ritual without micromanagement
The last condition is the most subtle. Delegation is not disengagement. It is building a structured follow-up ritual that respects the delegated authority.
The concrete ritual:
- Weekly meeting (15-30 min) where the delegate reports progress
- Focus on results and obstacles, not on how the work is being done
- The founder asks more than he states, and the delegate's opinion carries weight
- If there is disagreement, the founder questions the reasoning, he does not impose his decision
The ritual without micromanagement is the Goldilocks zone: neither abandonment nor control. This is where the Brown Belt differentiates itself from the Blue Belt.
2. Structured delegation in automation
Automation as a low-cost delegate
Think of every automated system as one more collaborator. If you delegate something to an automatic system, you apply the five conditions the same way:
-
Clarity of result: what does the system have to produce? (not "automate invoicing", but "generate 95% of invoices in less than 30 seconds with zero tax errors")
-
Authority aligned with responsibility: what can the system decide without human intervention? (can it decline transactions? can it adjust prices? how much autonomy does it have?)
-
Sufficient resources: does it have the data it needs? the APIs? the compute? the adequate input quality?
-
Measurable success criteria: how do you monitor performance? what threshold marks an alert?
-
Follow-up ritual: who reviews the results? with what frequency? what is done when something degrades?
The founder who cannot answer the five for his automated systems did not delegate to automation, he installed software.
The system as an amplified bottleneck
Here a critical observation: a badly structured automated system becomes a permanent bottleneck. A badly delegated person can learn. A badly delegated system keeps failing identically thousands of times until someone intervenes.
The Brown Belt practice: every delegated system has a responsible human, not only a vendor. The responsible human reviews metrics, adjusts criteria, escalates alerts. If nobody is responsible for a system, the system ends up as property of the founder by default, which destroys the delegation.
The company with the greatest leverage is the one that applies the five conditions both to humans and to systems. A manager with real authority + a well-configured AI agent + measurable success criteria + a follow-up ritual beats a team of 10 with micromanagement. Structure is what produces the compounding, not the quantity of people or of AIs.
3. Structured delegation in AI
Delegating to AI is delegating to a brilliant junior collaborator
The most common error with AI: treating the agent as a tool. Treat it as a brilliant junior collaborator: capable, fast, without historical judgment about your business. With that frame, the five conditions apply naturally.
-
Clarity of result is the difference between a vague prompt, which produces vague output, and a prompt with a specific result, expected format and quality criteria, which produces useful output.
-
Authority has to be defined explicitly before implementing, not after. Can the agent publish content without review? can it send emails to clients? can it execute payments?
-
Resources are what the model can reach. Does it have access to your knowledge base? to your real-time data? to the tools it needs?
-
Success criteria are the outputs you accept, how you measure them, and what percentage requires human intervention.
-
The ritual settles who reviews the agent's outputs, with what frequency, and when you retrain or adjust.
The framework of progressive delegation with AI
The book proposes a gradual framework:
-
Level 1: the AI proposes, the human decides and executes: initial use. Minimum risk. Learning how the agent behaves.
-
Level 2: the AI proposes, the human approves, the AI executes: after months of Level 1 with consistent outputs. It reduces human work without losing control.
-
Level 3: the AI decides and executes inside a perimeter, escalates exceptions to the human: when trust is calibrated. Greater leverage.
-
Level 4: the AI decides, executes, and measures. It reports to the human by exception: only for low-risk decisions with well-established criteria.
Skipping levels produces the 95% failure pattern of AI projects. Companies that put AI in Level 3 without having gone through Levels 1 and 2 end up with quality problems, legal risk, loss of client trust.
The people who produce the best results are not the most controlled ones. They are the most clearly delegated, with real authority and measurable accountability. The same applies to intelligent systems.
Frequently asked questions
Abandonment is handing over a task without the five conditions: clarity of result, authority aligned with responsibility, sufficient resources, measurable success criteria, follow-up ritual. Delegation is handing over a task with the five. When a founder says "I delegated and it went wrong", 80% of the time he violated condition 2 (he assigned responsibility without authority) or condition 4 (he did not define how to measure success). The delegate did not fail, the delegation failed. Recognizing this is what separates the Brown Belt from the trapped Blue Belt.
One: clarity of result (what metric, by when, under what restrictions). Two: authority aligned with responsibility (if you are responsible for the result, you can decide the path). Three: sufficient resources (money, information, access to people, tools, unfragmented time). Four: measurable success criteria (output metrics, intermediate milestones, alert triggers). Five: follow-up ritual without micromanagement (short weekly meeting, focus on results, the founder asks more than he states). The five are non-negotiable. If any of them fails, you are not delegating, you are waiting for a miracle.
By applying the five conditions, treating the agent as a brilliant junior collaborator. Clarity: a prompt with a specific result, expected format, quality criteria. Authority: define explicitly what it can execute without human review. Resources: access to your knowledge base, data, tools. Criteria: which outputs are acceptable, how they are measured, what percentage requires intervention. Ritual: who reviews, with what frequency, when it is retrained. The framework of progressive levels: Level 1 (AI proposes, human executes), Level 2 (AI proposes, human approves, AI executes), Level 3 (AI decides inside a perimeter), Level 4 (AI decides and executes, reports exceptions). Skipping levels produces the 95% failure.
Diagnosis before reaction. Five questions: was the result clear? did the person have the authority to make the decisions that led to that result? did the person have the resources? were the success criteria measurable? did the follow-up ritual give the person a chance to ask for help before failing? If you failed on one or more, the problem was the delegation, not the person. If the five were fine, then the problem is indeed the person, and the solution is not to take back control, it is to train or to replace. The trap of the Blue Belt founder: when someone fails, he takes back control. That confirms to the team that the delegation was never real.
The third section of the Brown
Letting go of control + structured delegation produce a company that works without micromanagement. The third section is still missing: total governance. Designing the founder's dispensability as a conscious goal. How a company can prosper without the founder being present. Business, automation and AI with mature governance.
When the delegation includes hiring an external AI consultant, the 12 filters that apply are in How to Choose an AI Consultant. For the checklist that precedes delegating any AI initiative (47 questions in six dimensions), read AI Implementation Checklist for Executives.
Want the full method? Read AI Black Belt: Fundamentals Before the Prompt. For executive AI consulting or keynotes and workshops.
Go deeper
Want to bring your team to the next belt?
Book a discovery call or explore the full book.