Question
Why does delegation specification fail?
Quick Answer
Confusing thoroughness with rigidity. Over-specifying method and micro-managing every step is not clear specification — it is the opposite problem addressed in the next lesson. The failure mode here is specifying *how* when you should be specifying *what* and *when*. Another common failure:.
Confusing thoroughness with rigidity. Over-specifying method and micro-managing every step is not clear specification — it is the opposite problem addressed in the next lesson. The failure mode here is specifying how when you should be specifying what and when. Another common failure: believing that a smart delegate should 'just figure it out.' Intelligence does not compensate for missing information. The smarter the delegate, the more confidently they will solve the wrong problem.
The fix: Identify one task you've recently delegated or plan to delegate — to a person, a tool, or an AI system. Write a specification for it using the five-part framework: (1) the desired outcome in concrete terms, (2) the constraints that must not be violated, (3) the success criteria you will use to evaluate the result, (4) the resources available, and (5) the deadline. Now compare this specification to what you actually communicated. The gap between the two is the ambiguity you injected into the delegation.
The underlying principle is straightforward: Vague delegation produces vague results. Specify the outcome, constraints, and success criteria before handing anything off.
Learn more in these lessons
Go beyond the answer
This topic is part of Delegate to AI Without Losing Judgment — a guided sequence of 16 lessons.
After completing this path you will run a working delegation boundary: a criteria framework for what goes to AI versus what stays with your judgment, specifications clear enough that AI output comes back usable, a verification practice that catches errors without redoing the work, and the warning signs of over-delegation before your judgment atrophies.
Start the path →