Step by step delegation guidefrom @jp.forno

Transcript

This is episode two of Delegation Maxing, how to delegate a task. Number one, provide context. Make sure they know why this matters and all the things that are going on around it. The military actually calls this the commander's intent, giving people the task, the purpose, and the end state. This is helpful because if the plan breaks, they can actually improvise in order to get to the end result instead of coming to ask you. Number two is to define the outcome. What is your definition of done? Make sure that you're describing the result and not the activity. Otherwise, you might just get a finished task that didn't solve the problem. Number three is provide resources. Make sure that they have the right tools and information to complete the task. Number four is agree on the process. Michael Hyatt has his awesome framework that's called the five levels of delegation. Essentially, he goes from do exactly as I tell you all the way to you decide, just don't tell me about it. Most delegation fights happen because you had a level two in your head and they heard a level four in theirs. So say the level out good. Either you show them through an SOP or a Loom video or just tell them the outcome and let them come up with a how. Number five is to set the parameters. Make sure you never delegate a task without a deadline, a time budget, and a definition of what good looks like. Time budget is actually very important. Think about Parkinson's law that says that work will fill the amount of time that you give it to be completed. So make sure that you give sufficient tier, but not more than you need to. Number six is to set up the communication plan. Where do they tell you it's done? How do they check-in with you? Where do they report if there's potential problems? This is how you prevent things falling through the rank. So make sure you save this clip for the next time you delegate something.