Clear delegation requires clear specification

The idea

Vague delegation produces vague results. Specify the outcome, constraints, and success criteria before handing anything off.

"Make it better." "Clean this up." "Handle the customer situation." "Write something compelling." "Fix the onboarding flow."

These are not delegations. They are wishes dressed in imperative grammar. Every one of them transfers a task without transferring the information needed to complete it. The delegate — whether a person, a system, or an AI — receives an action without an outcome, effort without direction, authority without criteria.

An example

A manager tells a designer: 'Make the landing page better.' The designer spends two weeks adding animations, rewriting copy, and restructuring the layout. The manager wanted the form conversion rate to improve. The designer delivered aesthetic polish. Neither was wrong — the specification was. If the manager had said 'Increase the form completion rate from 12% to 20%, without changing the navigation structure, by next Friday,' the designer would have focused on form UX from day one. The vagueness did not save time. It cost two weeks.

Where it goes wrong

Confusing thoroughness with rigidity. 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.

Make it stick

Before your next delegation — whether to a colleague, a contractor, or an AI — pause and write the specification before you communicate it. Use the five-part framework from this lesson. If you cannot write a clear outcome statement, you have not finished thinking. The specification is the proof that your thinking is complete enough to delegate.