How to hand over marketing to your team so it actually sticks

Aug 18
3 min read

Updated: 2 days ago

Introduction

Handover usually fails in the same way. Someone is shown how to do a task, agrees they understand, and three weeks later the task has quietly returned to whoever did it before.

That is not a people problem. It is a handover method problem, and the fix is mostly about testing rather than explaining.

1. How to hand over marketing to your team: separate what can be transferred

Not everything should move. Marketing splits into two kinds of work.

Operating work — scheduling, posting, requesting reviews, sending follow-ups, pulling numbers, updating listings. Repeatable, judgement-light, transferable.

Judgement work — deciding the offer, setting prices, choosing markets, approving what the business says publicly. Depends on knowing the business, and should stay with the owner for a long time.

Attempting to hand over judgement produces either paralysis or bad decisions. Hand over the operating half, which is usually most of the hours.

2. Transfer one task at a time

The instinct is to hand over everything at once, usually because the owner is overloaded. It reliably fails.

Move one task. Let it run for a few weeks until it is genuinely stable and requires no prompting. Then move the next.

Slower in appearance, and considerably faster to a working arrangement, because each task gets enough attention to actually take root.

3. Write the procedure before the conversation

Verbal handover does not survive. What is explained on Tuesday is half-remembered by the following week, and the gaps get filled with guesses.

Write each task down first: what triggers it, the numbered steps, where things live — which account, which folder, which login — what finished looks like, and who owns it.

Write it while performing the task rather than from memory. Documentation written afterwards skips the steps that trip people up, because those are invisible to whoever already knows them.

4. Test the handover properly

This is the step that determines whether anything transferred.

Have the person do the task from the documentation while you watch and say nothing. Every question they ask is a gap in the procedure — write it in rather than answering and moving on.

A procedure that has not been tested this way is a draft, whatever it says at the top. Most failed handovers skip this and discover the gaps weeks later.

5. Give it a slot and a name, not just an instruction

A transferred task needs a place in someone's week and one named owner.

Not a team. Shared responsibility for a recurring task reliably produces gaps, because everyone assumes someone else did it. One person, one recurring time in the diary.

Also make sure they have the access they need. A task handed to someone without the necessary login comes straight back.

6. Resist taking it back

The most common failure after a successful handover is the owner quietly resuming the task because it was done differently or more slowly.

Doing it yourself once is how a handover reverses. If the output is wrong, fix the procedure. If it is merely different, consider whether it matters.

Accept somewhat lower quality initially. Consistency by someone else beats excellence by you, because excellence by you does not scale and stops when you are busy.

7. Check in, then check the numbers

Review the first few cycles together, then step back to reviewing the output rather than the process.

After a month, look at whether the thing the task was supposed to affect actually moved — reviews arriving, enquiries followed up, content published on schedule. That is the real test of the handover.

Then add the procedure to a quarterly review, since platforms change and a procedure referencing a button that no longer exists teaches people to distrust all the documentation.

Conclusion

Hand over operating work and keep the judgement. Move one task at a time, write the procedure while doing the task, then test it by watching someone follow it without help.

Give each task one named owner, a slot in the week and the access it needs. Then resist taking it back, and judge the handover a month later on whether the outcome moved rather than on whether it was done your way.