Founders Delegate Effectively Without Handing Off a Half Decision
Founders delegate effectively when the other person can start without chasing you for the outcome, the limit, and the moment you want to see the work. This page is a handoff habit for a founder who still designs, writes, or sells. It is not a claim that delegation grows revenue, saves a number of hours, or fixes a team. It is not legal, financial, or management advice.
If the work is not written down yet, use the getting things done method notes. If the block of making is the problem, use the pomodoro technique deep dive. Delegation starts after you know the next action and still should not be the person who does it.
The note you send before anyone starts
Write four lines. If you cannot fill one of them, you are not ready to hand the work off. You are ready to make a decision.
- Outcome. What will exist when this is done, in a form someone can open. A file, a page, a sent message, a list of options. Not “help with the homepage.”
- Limit. What they must not change. The offer, the name, the deadline already promised, the parts of the layout a client already approved.
- Check. When you will look, and what you will look at. One review, named, not “keep me posted.”
- Done. The sentence that lets them stop. “The homepage is in review with the hero and the three sections we named.” If they can keep polishing forever, you did not name done.
Send those four lines in the place the work will live, not only in chat. Chat is where you said it. The task is where they will look tomorrow. Link the file. If there is no file yet, say so in the limit line: they are producing the first version, not editing yours.
Where founders delegate effectively, and where they should not
Hand off production once the outcome is stable. A founder can ask for a revised hero, a cleaned set of screens, a first draft of the about page, or a list of open questions from a call. Those end. They can be checked against the four lines.
Do not hand off the decision you have not made. “Make the homepage better” is a decision wearing a task name. “Should we change the offer” is a decision. “Pick our positioning” is a decision. If you pass those down, you will get work back and reject it, because the missing piece was your choice, not their craft. Make the choice in one sentence, then delegate the making.
Do not hand off the client relationship and keep the craft, or the reverse, without saying which. If you still want to be the person who talks to the client, say that in the limit. If you want them to send the file, say that in done. Mixed signals are how a task comes back to your desk with a question you could have answered in the note.
The check is part of the handoff
A handoff without a check is a disappearance. Put the check on your own list the day you assign the work. Open the file at that time. Comment on the four lines: outcome met or not, limit respected or not, done met or not. Do not add a new direction in the same breath unless you rewrite the four lines and reset done. A moving done line is why people stop trusting the handoff.
If the work is early, ask for a rough version at the check, and say “rough” in the outcome line. People polish when they think the check is a verdict. Tell them the check is a comparison to the four lines, not a score of their taste.
If you miss the check, say so and name a new time the same day. A missed check teaches the other person that the work was not real. They will either wait, which stalls the job, or guess, which brings you a version you did not ask for.
What comes back, and what you do with it
When the file returns, answer only the gaps against the four lines. “The hero is not the one we named” is a gap. “I would have done the type differently” is a new decision. If you want that new decision, own it, rewrite the limit, and send a new check. Do not imply they should have read your mind.
Keep a short record on the task: the four lines, the check date, and your note. You will need it the next time you assign similar work. The record is not a performance review. It is how the next handoff gets shorter, because the limit and the done line already exist.
If the same gap shows up on two handoffs, the four lines were vague, not the person. Tighten the outcome. Show one example of done. An example is part of the limit: “match this section, not the rest of the old site.”
A week of handoffs, not a new tool
You do not need a delegation app, a score, or a meeting named for this. Use the list you already have. Each morning, mark the tasks that are yours to decide and the tasks that are ready for the four lines. Write the four lines on the ready ones before you open design files of your own. Then do your own work. The check you promised is an item on your list, with a time, in the same way any other task is.
Protect one kind of work from delegation until you have written the outcome: naming the offer, accepting a date you cannot move, and telling a client yes or no. Those are founder decisions. After each one, the making around it can move. Before each one, delegating the making only creates a draft nobody can finish.
Talk to the person once about how you will hand work off, not in the middle of a file. Show them a finished four-line note. Ask what is still ambiguous. Fix the note. The conversation is about the note, not about their attitude. If the note is clear and the work still cannot start, the blocker is access: the file, the login, the client context. Fix access. Do not add a second meeting.
When two people could do the task, pick the one who will still be here at the check, and say the other person’s name is not a backup unless you write that down. A silent backup becomes a second founder. You will both edit, and nobody will know who owns done.
Signs the handoff failed, without a scoreboard
You are still the bottleneck if any of these are true. The person asks a question the four lines should have answered. You rewrite the work instead of naming the gap. The check arrives and you are seeing the file for the first time because you never put the check on your list. The task has a new outcome every time you comment. None of these need a metric. They need a cleaner note or a decision you still have to make yourself.
Do not collect these signs into a rating of the person. This page is about the handoff. A rating is a different conversation, and it does not belong in the task comment.
Founders delegate effectively by leaving a note the other person can finish against, then showing up at the check you named. Tomorrow, take one task you are about to do yourself, write the four lines, and send it only if all four are real. If one is missing, that missing line is your work today, not theirs.
If you run a design practice, the same note covers a screen, a deck, or a set of options for a client. The outcome is the artifact. The limit is what the client or you already locked. The check is the review before anything is sent outside the studio. Done is the sentence that stops the file from bouncing. Use that shape on the next client delivery you are tempted to keep on your own screen. That is another way founders delegate effectively without a new tool.
One last pass before you send the note. Read it as if you do not know the client. If a sentence only makes sense because you were in the room, replace it with the decision the room made. “They seemed unsure” is not a limit. “Do not change the price line” is a limit. “Look at the call” is not an outcome. “A one-page outline of the three sections we agreed” is an outcome. The note should stand without you in the chair.
