Delegate the Outcome, Not the Steps
Success looks like this. How you get there is yours.
Next time you delegate, describe only three things: the desired end state, the constraints (budget, timeline, non-negotiables), and how you'll measure success. Then stop. Do not describe how to get there. If the person asks for steps, ask them to propose an approach first. Your job is the what and why — their job is the how.
You're assigning work to someone capable and you want them to take genuine ownership rather than just following instructions.
The person is genuinely new and needs process guidance to avoid costly mistakes.
Why it works
Prescribing the method kills initiative and makes you the bottleneck. Prescribing the outcome while freeing the method creates ownership, develops your team's judgment, and often produces better solutions than yours would have been.
When you tell someone how to do something, you get compliance. When you tell them what success looks like and let them figure out the how, you get ownership. Compliance produces exactly what you described, nothing more. Ownership produces solutions you didn’t think of and initiative you didn’t ask for. The instinct to prescribe steps comes from a good place — you know a method that works. But every time you do it, you trade their development for your efficiency. Give them the boundaries — budget, timeline, non-negotiables — and freedom to navigate within them. Their judgment grows with every problem you don’t solve for them.