[Ep 70] The Handoff Package: Delegation That Sticks

WEBVTT
00:00:00.560 --> 00:00:06.639
Delegation should not create more work, but unfortunately, for a lot of founders, it does.
00:00:06.879 --> 00:00:15.599
You hand something off, it comes back wrong, it comes back half done, or not just how you imagined it.
00:00:15.839 --> 00:00:17.600
So you fix it.
00:00:17.839 --> 00:00:22.640
What has happened is that you have ended up doing two jobs.
00:00:22.960 --> 00:00:29.440
The original task that you thought you had delegated and the cleanup after the mess.
00:00:29.679 --> 00:00:33.920
And I get it, it's not that you want to be a control freak.
00:00:34.079 --> 00:00:41.920
It's just that you've tried delegating and you've been burned before, and you're tired of paying that rework tax.
00:00:42.320 --> 00:00:46.240
So you tell yourself, I'll just do it myself next time.
00:00:46.479 --> 00:00:51.759
And this is how you become the bottleneck in your business yet again.
00:00:52.000 --> 00:01:01.679
In this episode, I'm going to show you how to delegate in a way that actually sticks so you can hand off tasks and stop taking them back.
00:01:02.560 --> 00:01:05.120
Welcome to the Systemized Business Podcast.
00:01:05.200 --> 00:01:14.079
I'm BK, a business manager and a workflow specialist who just loves all things systems and process improvement.
00:01:14.319 --> 00:01:21.599
And this episode is for the founder who wants the support but keeps taking tasks back.
00:01:22.159 --> 00:01:30.640
Maybe you've hired an assistant, maybe you've you're working with a contractor, or maybe you have a small team.
00:01:31.120 --> 00:01:43.200
You could still be solo, but occasionally ask one or two people to assist you with one or two things in your business, but you cannot keep scaling like this.
00:01:43.680 --> 00:01:52.560
By the end of this episode, you will know why delegation fails, even though you have good people on your team.
00:01:52.799 --> 00:02:06.079
You will know the exact handoff package you need to delegate without rework, and you will have two approval rules that protect your time and quality.
00:02:06.719 --> 00:02:12.159
And then I'll give you a simple challenge: one task, one page, one SOP.
00:02:12.400 --> 00:02:13.919
Let's get into it.
00:02:15.840 --> 00:02:20.080
Let's first get to the heart of why delegation fails.
00:02:20.560 --> 00:02:24.960
Um, and I have identified four main reasons.
00:02:26.159 --> 00:02:32.879
Most delegation problems are not people problems, they are handoff problems.
00:02:33.439 --> 00:02:43.439
And as I go through these, see if you can recognize where things have gone wrong for you, and later I'll give you some ways to fix them.
00:02:44.000 --> 00:02:57.120
More often than not, we don't need a better assistant, we actually need a better system for transferring the outcomes we are looking for.
00:02:57.919 --> 00:03:05.520
Okay, so the first reason that delegation fails is because there is no definition of done.
00:03:06.080 --> 00:03:09.439
We say things like, can you post this?
00:03:09.680 --> 00:03:11.199
Can you handle my emails?
00:03:11.360 --> 00:03:12.960
Can you update the website?
00:03:13.199 --> 00:03:15.280
Can you help me with onboarding?
00:03:16.080 --> 00:03:20.240
In your head, you know exactly what that means.
00:03:20.560 --> 00:03:23.680
But in their head, they're guessing.
00:03:23.919 --> 00:03:29.759
And people can't hit a target if you don't explicitly define it, right?
00:03:30.319 --> 00:03:47.360
This is why, as founders, we end up disappointed because the expectation lives in your brain, it never made it into the brief and it was never clearly communicated.
00:03:47.919 --> 00:03:54.159
Delegation without a definition of done is basically a setup for failure.
00:03:55.199 --> 00:04:02.560
The second reason that delegation fails is because there's no SOP, standard operating procedure.
00:04:03.120 --> 00:04:10.960
Or there is an SOP, but it is so long and so complicated that nobody actually uses it.
00:04:11.520 --> 00:04:16.079
A lot of founders will say, but I explained it in a voice note.
00:04:16.639 --> 00:04:17.839
Okay, well fine.
00:04:18.079 --> 00:04:22.399
Voice notes are great for relationships, but they are not a reliable process.
00:04:22.639 --> 00:04:25.120
A voice note is not an SOP.
00:04:25.439 --> 00:04:28.560
A scattered message thread is not an SOP.
00:04:28.959 --> 00:04:33.199
The goal of an SOP isn't to write a novel either.
00:04:33.439 --> 00:04:35.680
The goal is usability.
00:04:36.319 --> 00:04:40.959
Something someone can follow while they are doing the task.
00:04:41.279 --> 00:04:46.319
No SOP, unfortunately, um, it fails.
00:04:46.879 --> 00:04:51.120
The third reason delegation fails is because there are no checkpoints.
00:04:51.439 --> 00:04:52.800
So let me explain this.
00:04:52.959 --> 00:04:56.240
So you hand off a task and then that's it.
00:04:56.399 --> 00:04:59.199
You disappear, you don't see anything until the end.
00:04:59.759 --> 00:05:06.639
Only to find that it's either wrong or it is late or it's not even what you wanted.
00:05:07.360 --> 00:05:09.120
How about the other extreme?
00:05:09.439 --> 00:05:20.000
You uh hand off the task and then you check every five minutes, which means now you're micromanaging.
00:05:20.639 --> 00:05:29.199
So you are still doing the work mentally and frustrating the person the person that you have handed the task to.
00:05:29.519 --> 00:05:41.519
So the the solution here is not to delegate and forget, delegate it and forget it with zero checkpoints or the other extreme, the constant looking over the shoulder.
00:05:41.839 --> 00:05:50.480
It's to set up milestone checkpoints to give you the opportunity to give feedback to the person doing the work.
00:05:51.279 --> 00:06:04.160
And the last reason, reason number four, that delegation fails, and this one is is is not quite as obvious, is um is because you are delegating the wrong task first.
00:06:04.959 --> 00:06:21.040
If you delegate something that is high judgment, high risk, or brand sensitive before your delegation process is stable, it is likely going to feel and be a complete disaster.
00:06:21.360 --> 00:06:27.439
So the best first delegation tasks are repeatable and predictable.
00:06:28.000 --> 00:06:38.319
By and delegation doesn't mean that we're just dumping tasks that we don't want to do onto somebody else.
00:06:38.639 --> 00:06:50.079
What we are really doing by delegating is transferring outcomes, and so this needs to be done with as much clarity as we can.
00:06:51.120 --> 00:06:55.920
So, okay, we know now why delegation fails.
00:06:56.720 --> 00:06:59.600
So, how can we prevent that from happening?
00:07:00.079 --> 00:07:18.000
And that's why we need a simple handoff package, and every delegated task needs a handoff package, and it doesn't have to be complicated, it uh we're not creating a long document or a cumbersome process.
00:07:18.240 --> 00:07:24.959
All we need is something that makes the outcome clear, and I call it a package because it has four parts.
00:07:25.120 --> 00:07:28.879
Part one is the outcome and success criteria.
00:07:29.199 --> 00:07:34.800
This answers the question: when this task is done, what is true?
00:07:35.680 --> 00:07:37.600
Let me give you an example.
00:07:38.000 --> 00:07:41.680
Let's say you're delegating a social media post.
00:07:43.279 --> 00:07:48.560
Now, the outcome is not post on Instagram.
00:07:48.800 --> 00:08:02.639
The outcome is post is created, caption matches brand voice, it includes a clear call to action, and it is scheduled for the correct date and time.
00:08:03.839 --> 00:08:05.600
That's the outcome.
00:08:06.240 --> 00:08:09.519
Then we want to add success criteria.
00:08:09.759 --> 00:08:12.639
So these are three to five bullets.
00:08:12.959 --> 00:08:34.159
For example, the the uh caption is conversational but professional, it uses our tone guidelines, it includes a call to action, it uses correct hashtags, it's uh and it is scheduled inside whatever tool that we use.
00:08:34.879 --> 00:08:41.200
So that is how we measure that it's successful.
00:08:41.679 --> 00:08:53.600
The success criteria matters because it turns feedback from emotional to objective instead of this doesn't feel right.
00:08:54.159 --> 00:08:57.279
You can say, does it meet the criteria?
00:08:57.519 --> 00:09:03.440
Yes or no, and then go through the three bullets, three, five bullets and see if it does.
00:09:04.879 --> 00:09:10.720
Just these two steps can reduce rework immediately.
00:09:10.799 --> 00:09:11.919
Do you see that?
00:09:12.399 --> 00:09:16.799
Part two of our handover package is constraints.
00:09:17.120 --> 00:09:21.200
Constraints are the boundaries that protect the brand and protect the business.
00:09:21.360 --> 00:09:34.960
This is where you clarify things like your brand tone and your brand voice, the do's, the don'ts, the budget limits, the tools to use, uh, the access and permissions.
00:09:35.200 --> 00:09:41.600
And here's an example of simple constraints that really can save you a headache later.
00:09:41.840 --> 00:09:46.559
For example, no emojis on LinkedIn posts.
00:09:46.799 --> 00:09:49.919
Keep them conversational but corporate.
00:09:50.480 --> 00:10:03.840
Use Canva templates in this folder only, or keep captions under 150 words, or no refund language unless I approve.
00:10:04.639 --> 00:10:11.120
So constraints are putting the rules, the boundaries in place so that micromanagement is avoided.
00:10:11.279 --> 00:10:23.279
They give additional clarity, and clarity is what makes delegation feel safe for you delegating and safe for the person who the work is delegated to.
00:10:24.080 --> 00:10:35.679
Part three of the package is giving an example of good or what a finished version version looks like.
00:10:35.840 --> 00:10:38.159
And this just might be the magic ingredient.
00:10:38.240 --> 00:10:43.039
This is an example of what a good finished version looks like.
00:10:43.200 --> 00:10:57.440
So this can be in the form of a link to a post that performed really well, or a screenshot, or a loom video, a template, or a gold standard folder with examples.
00:10:57.759 --> 00:11:02.720
If you show somebody what good looks like, they can match it.
00:11:03.039 --> 00:11:11.600
But if you don't, they're kind of just guessing, and guessing can create rework in the future.
00:11:11.840 --> 00:11:18.080
And then finally, part four is uh deadline and check-in points.
00:11:18.639 --> 00:11:24.080
So we're the final part of the package is the deadline, the check-in points.
00:11:24.240 --> 00:11:31.679
Deadline is uh is obvious, but check-in points are what prevents surprises, right?
00:11:32.000 --> 00:11:35.840
So you don't need um to be checking constantly.
00:11:36.000 --> 00:11:42.159
Remember, we don't want to be micromanagers, um, but we want to check at milestones.
00:11:42.320 --> 00:11:54.960
For example, if you have dedicated a blog blog post, indicate that, for example, the outline should be due uh Tuesday at 2 p.m.
00:11:55.519 --> 00:12:00.159
First draft can be due Thursday, 12 p.m.
00:12:00.480 --> 00:12:04.240
And then final edits Friday, 10 a.m.
00:12:05.279 --> 00:12:10.399
That is clear, those are milestones that you give feedback at every milestone.
00:12:10.480 --> 00:12:17.519
If you're delegating a batch of content, you can request send me three caption drafts first.
00:12:17.759 --> 00:12:23.600
Once approved, create the rest, and then final review before scheduling.
00:12:24.240 --> 00:12:31.279
Doing this protects your quality, uh your quality, and it also protects your time.
00:12:32.000 --> 00:12:48.000
And one thing about um about approvals, because some this can also be where people can get stuck and spend a lot more time than necessary uh approving things.
00:12:48.159 --> 00:12:50.480
You can approve things all day.
00:12:51.279 --> 00:13:06.559
And I actually advise my clients to batch approvals, and the way this looks like is instead of a message coming in, you respond, a draft coming in, you check it, a question coming in, you answer.
00:13:06.879 --> 00:13:22.080
Uh um this being asked for approval, you you know, like I said, this can take all day, and your day ends up being just a series of reactive micro approvals.
00:13:22.720 --> 00:13:26.000
Instead, I suggest having an approval window.
00:13:26.159 --> 00:13:31.120
For example, I do approvals once per day at 3 p.m.
00:13:31.600 --> 00:13:35.440
Or approvals happen Tuesdays and Thursdays.
00:13:36.559 --> 00:13:40.639
And this is how we can protect our deep work blocks.
00:13:40.799 --> 00:13:47.919
Remember, your team can still move forward, but you don't have to be interrupted 20 times a day.
00:13:48.240 --> 00:13:52.159
Another approval rule actually goes back to the checkpoints.
00:13:52.320 --> 00:13:59.200
Remember, one of the examples I gave was uh send me three drafts and when I approve, send the rest, something like that.
00:13:59.360 --> 00:14:01.519
Well, this can be an approval stage.
00:14:01.759 --> 00:14:08.879
Show me the outline first, send me two options, complete one example first, then replicate.
00:14:09.200 --> 00:14:25.200
Another example uh would be if you are delegating, let's say, your podcast show notes, don't say do all these 12 episodes, rather say do one, let me approve the format, then you can do the rest.
00:14:25.679 --> 00:14:30.960
And so that's how we can prevent rework at scale.
00:14:31.440 --> 00:14:38.480
So what we are not um we don't we it's not that we're chasing perfection, by the way.
00:14:38.559 --> 00:14:45.919
The goal is to be confident that the outcome we are looking for is clearly communicated.
00:14:47.120 --> 00:14:58.480
So now you might still be wondering what to delegate first, because that was one of the things at the top of this episode that we talked about delegating the wrong thing.
00:14:58.559 --> 00:15:03.519
So you might be wondering: okay, so what do I delegate first?
00:15:05.120 --> 00:15:11.360
Um, we want to delegate repeatable tasks before judgment-heavy tasks.
00:15:11.519 --> 00:15:33.279
For example, you can delegate things like scheduling and calendar management, formatting and um scheduling content, repurposing a post into multiple formats, client onboarding steps, you know, the folders, the templates, the welcome emails, file organization, things like that that have a repeatable process.
00:15:33.519 --> 00:15:51.840
The things I do not recommend delegating at first would be high-stakes strategy decisions, sensitive client escalations, or anything that you have never consistently done yourself yet.
00:15:52.080 --> 00:15:58.639
So you start with what repeats because that's what makes systemizing it easy.
00:15:59.600 --> 00:16:22.159
Let me take a quick break and let you know that if you have support, if you have an assistant or a small team, but you find that work keeps coming back to you, you, as this episode has um hopefully communicated that you don't need more help, you need clearer processes.
00:16:22.480 --> 00:16:33.279
So I'm offering a free clarity call where we will identify what is breaking in your handoffs, your roles, and in your workflows.
00:16:33.519 --> 00:16:36.879
And I'll recommend for you the next best step.
00:16:37.120 --> 00:16:53.840
For a lot of founders, tightening role clarity and building those standard operating procedures and checklists and templates so tasks can be owned end-to-end, is exactly what they are looking for and what they need.
00:16:54.159 --> 00:17:01.360
So if that is intriguing to you, if you need that kind of uh support, the link is in the show notes.
00:17:01.840 --> 00:17:06.240
Alright, so here is your action step for this week.
00:17:06.559 --> 00:17:14.960
Plan one task that you redo every week and create a one-page SOP for it.
00:17:15.200 --> 00:17:20.559
One page, just one page, and here's the simple structure, the purpose.
00:17:20.799 --> 00:17:24.960
What is this SOP for and when do you use it?
00:17:25.680 --> 00:17:33.599
The tools and the access, what tools are used, and where do these files live?
00:17:34.000 --> 00:17:49.279
And then the steps, try to keep it to five to ten bulleted steps, step by step of what happens throughout the process, and then the definition of done, which is it might be a checklist.
00:17:49.519 --> 00:17:53.599
What must be true when this task is finished?
00:17:54.319 --> 00:18:04.960
If you need to add a section that notes what the common mistakes can be, what usually goes wrong, or what can go wrong, how do you avoid it?
00:18:05.119 --> 00:18:11.680
And then give an example link or screenshot what good looks like.
00:18:12.400 --> 00:18:13.440
And that's it.
00:18:13.599 --> 00:18:24.000
We want to create SOPs that are simple and usable, and once you have one SOP, delegation gets so much easier, and then you do the next one.
00:18:24.160 --> 00:18:33.359
And if you want the template of either the handoff package or the SOP template, you can download those in the show notes below.
00:18:33.599 --> 00:18:43.200
If this episode hit home, if you found it useful, I'd love for you to give us a subscribe or a follow so you don't miss future episodes.
00:18:43.359 --> 00:18:53.440
Uh, go ahead and share it with somebody who might need a little bit of guidance when it comes to delegating and encouraging and encourage them to subscribe as well or follow the show.
00:18:53.599 --> 00:18:54.240
Why not?
00:18:54.480 --> 00:18:56.559
Thank you for your time today.
00:18:56.799 --> 00:18:57.680
Thank you for listening.
00:18:57.759 --> 00:18:59.440
I'll talk to you in the next one.
00:18:59.680 --> 00:19:00.720
Bye for now.