You Don't Need More Willpower. You Need a Map.
I’ve facilitated dozens of goal-setting calls before starting my social impact mastermind, and there’s something I kept hearing: “I really need to delegate more.”
It comes up as part acknowledgment, part sigh. They’re busy, stretched thin, trying to do everything themselves. They know delegation would help. They’ve probably known it for months.
And then life continues exactly as before.
I used to think this was a mindset issue. That people needed more willpower, better boundaries, clearer priorities. But lately I’ve been finding I’m curious about something else… the question is:
“How do you document your processes?”
The founders who say they need to delegate more? They’re almost always the ones who’ve never written down what they actually do. There’s no map of their work, no record of the decisions they make, no capture of the small details that matter. Just tasks living inside their heads, accumulating like sediment.
The ones who are actively growing are different - the ones who are successfully shifting from working in their business to working on it. They have something in place. It’s rarely perfect. But they’ve started.
Here’s what I think holds people back: documentation sounds like bureaucracy. It sounds like you need to create some elaborate standard operating procedure, complete with flowcharts and version control and formal language no one actually uses. It feels like extra work with no immediate payoff.
But that’s the wrong frame.
Documentation isn’t preparation for delegation. It’s a way of seeing your work clearly.
When you articulate your processes, something shifts. You start to notice things, such as steps that take longer than they should. You notice tasks you’re doing out of habit, not necessity.
Sometimes you realize you’re spending two hours on something that gives you almost no value. Sometimes you see that you’ve been avoiding a decision because you didn’t know the decision was yours to make. Sometimes the act of describing your process reveals that the process itself is broken.
Understanding your business process is self-reflection disguised as documentation.
And once you have it down, even as a rough draft, even as something imperfect… you can start to see what’s missing. You can refine it. You can test whether it still makes sense. And eventually, when you’re ready, you can hand it to someone else.
But here’s the part that matters: you don’t need to wait until it’s ready to hand off. You start by capturing what you know.
How do you do this? If I were sitting across from you with a blank piece of paper, I’d ask you seven questions:
What result does this process produce, and when should someone use it? This is about purpose. If you can’t name what success looks like, you can’t teach someone else to recognize it.
Who performs this process, who owns the result? This is about responsibility. Delegation fails when accountability is fuzzy.
What is needed for the process (tools, access, information, files)? This is where bottlenecks hide. If only you have access to the thing someone needs, the process can’t move without you.
What are the exact steps, in order, to complete this process from start to finish? This is the map. And it’s where most people realize they’ve been taking shortcuts they didn’t know they were taking.
What situations require doing something different, and what should be done in those cases? Real work isn’t linear. There are always exceptions. Naming them means someone else can handle them without asking you first.
How do you verify the process was completed correctly? This is quality control. It’s the difference between delegation and abdication.
What is the outcome when this process is finished? This is the endpoint. If you can’t describe what done looks like, you’ll end up redoing someone else’s work.
These aren’t academic questions. They’re the questions that live underneath every task you do, whether you’ve articulated them or not.
And the beautiful thing about writing them down? You don’t need a perfect system. You need a starting point. A rough draft you can improve. A way to get the work out of your head so you can see it.
I’ve watched founders resist this for months, convinced they don’t have time, convinced it’s too much overhead.
The ones who actually delegate aren’t the ones with more willpower. They’re the ones who stopped treating delegation like a mindset problem and started treating their work like something worth understanding.