Delegation
How to delegate judgment, not just tasks
Delegation fails when you hand over the task but keep the thinking, so every decision comes back to you and you end up taking the work back. To fix it, hand over the outcome, the context behind it and clear decision rights, then check results on a fixed rhythm instead of watching the process.
Three ways a handover breaks
- You hover. You delegate but stay in every decision, so you free no time and add management on top. Fix: hand over the outcome and judge the result, not the steps.
- You disappear. No check-ins and no course correction, so the work drifts. Fix: a short written update every day and a weekly call.
- You keep the context. You know why it matters and what the trade-offs are; they do not, so they execute literally. Fix: write down how you decide, and share it before the first task.
Why founders fall into these traps is its own subject, covered in the trust vs control paradox. The rest of this page is the method.
Step 1: sort the work into technical and adaptive
- Technical work has a clear problem and a known answer: schedule a meeting, update the CRM, process invoices. Hand it over now, with a written procedure if it has steps.
- Adaptive work needs judgment and iteration: improve the sales process, resolve a client escalation, find out why a campaign is not converting. Solve it once yourself, write down how you thought about it, then hand over the running and the improving.
Technical work moves on day one. Adaptive work moves once you have written down how you solved it.
Step 2: write the outcome, not the task
A task says what to do. An outcome says what good looks like, why it matters and how you will know.
- Instead of “Update the CRM every day”, hand over “Keep the CRM accurate enough that sales can trust the pipeline report every Monday.”
- Instead of “Schedule my meetings”, hand over “Protect two mornings a week for deep work, and answer meeting requests within a day.”
- Instead of “Research these vendors”, hand over “By Thursday, recommend which vendors to shortlist, with sources and the reason for each.”
- Instead of “Post on LinkedIn”, hand over “Publish posts on the problems buyers raise on our calls, and tell me which ones start conversations.”
Step 3: set decision rights in three levels
- Decide alone. Act, no need to tell you first. Example: reschedule an internal meeting; reply to a routine vendor email.
- Decide, then tell. Act, and report it in the daily update. Example: move a deadline by a day; chase a late invoice.
- Ask first. Bring a recommendation and wait for your yes. Example: anything that commits money, changes scope or speaks for you on something new.
Start with most work in “ask first” and move items up a level as the results prove out. That is how trust gets built: on evidence, in small steps you can reverse.
Step 4: write down how you decide
One page is enough. What you check before you say yes. What you care about most this quarter. Which people and topics you always want to hear about. When you would rather be asked than surprised. This page is the context gap closed in writing, and it is the first thing a new operator should read.
Step 5: run a rhythm, not a watch
- Daily: a short written note: what was done, what is in progress, what is waiting on you.
- Weekly: a call to review outcomes, correct course and reset priorities.
- Escalation triggers: new information that changes priorities, a trade-off they cannot resolve, a decision above their level.
Review the result, not the steps. Correct early, before a small miss becomes a habit.
What this looks like with an embedded operator
A client asks for a feature outside the agreed scope. A task-based assistant asks: “The client asked for this. What should I tell them?” An embedded operator says: “The client asked for this. I checked the scope and the contract, and it is outside both. I have drafted a reply in your inbox; tell me if it works and I will send it.”
How a handover runs at Chief Nest
Chief Nest places embedded operators, called Chiefs, inside remote, founder-led companies. The method above is built into how a Chief starts:
- Intro call. We learn how you work and what is eating your week.
- Match. A Chief who was trained before you met them is matched to your scope, in days, not weeks, because there is no recruiting period.
- Onboarding. A short onboarding covers your tools, your rules, your priorities and the first handovers.
- Every day. You get a short end-of-day note, so you always know what moved.
- Ongoing. A Chief Nest account manager supervises your Chief, checks in with you and is your escalation route. You contract with Chief Nest, so we stay responsible for the result.
- Over time. Work that repeats is written up as documented systems your company keeps.
If the fit is wrong in the first two weeks, we replace your Chief free, for any reason.
Keep reading
You do not need more hands. You need someone who thinks.
Book a 30-minute intro and we will look at what you could hand over first.