When clients insist on working with you personally, the bottleneck is rarely about your team’s ability. It is about two separate problems: your team needs your method translated into real training, and your clients need a clear, confident message that your team delivers the same standard you do. Lia walks through the exact moves to solve both sides, from codifying your secret sauce to publicly edifying your team members in front of clients. This episode is most useful for founders, consultants, agency owners, and service-based business leaders who are stuck as the face of every client relationship.
This episode is part of the Delegation, Bottleneck & Getting Out of the Weeds series. Browse all episodes →
Mic drop moments
“Delegating isn’t a yes or no. It’s not one way or the other. There’s a real gradient that we can offload responsibilities and help people take on more and learn more within.”
“This is not a sink or swim moment where you go, well, it’s your project. You have to figure it out. This is where I would invite the person to shadow us and learn from us how we would solve that problem.”
“…nothing takes more time than having to redo a bunch of work because it didn’t get done right.”
Episode highlights
Delegating is a gradient, not a handoff
Lia opens with the framing that trips most people up: they treat delegation as binary. Either you own it or they own it. In reality, delegation lives on a spectrum. Handing something off does not mean you exit the picture completely. You stay aware, you check in, and when something starts to go wrong, stepping in is part of the process, not a failure of the delegation itself.
The question someone asked at a conference that kicked off this episode
After sharing her six-part Unstoppable Team framework at a conference, an attendee asked the question Lia hears constantly: if I have delegated something and I can see my team member is about to make a big mistake, do I let them fail and learn, or do I step in? Her answer is unambiguous. Step in, especially when there is a customer impact, a financial impact, or consequences for other team members or the timeline.
First move: check what the team member already sees
Before you jump in and fix anything, ask. Go to the person and say something like, “I noticed something starting to come up. Are you seeing that too?” Two good things can happen. They already know about it and have a plan, in which case you relax and let them run. Or they do not know, and your question opens the door to share the risk without making it feel like a takeover. Either way, you learn where they actually are before you act.
Second move: teach, do not just rescue
If the team member needs real support, this is not a sink-or-swim moment. Lia’s framing: invite them to shadow you. Say something close to, “We have a tight timeline, so let me take the reins on this, but I want to walk you through exactly what I do step by step so that next time you have totally got it.” You ask if that is okay. That language matters because it signals trust and investment, not a vote of no confidence.
The shadow time is not overhead, it is an investment
The most common objection Lia hears is “I do not have time for this.” Her counter is direct: nothing takes more time than redoing work that did not get done right, unwinding decisions that went sideways, or being pulled off high-priority work because something broke. A few hours spent walking someone through a fix, writing up the steps, or making a simple checklist pays back far more time on the other end.
Write it down while you are in it
As you work through the fix alongside your team member, do not just narrate what you are doing. Write it out. Send a follow-up email. List the steps. Name the vendors, templates, or contacts involved. That quick writeup becomes a lightweight SOP the person can use the next time without you in the room. The work of creating it is already happening because you are solving the problem anyway.
The grounding question for any delegation decision
Lia closes with the question she tells her clients to ask whenever they are unsure how much to let go: “How do I set this person up for success the next time?” When you answer that question honestly, you figure out exactly what they need to know to operate independently later. That is the standard that guides when to step in, how much to say, and what to document before you hand it back.
Related episodes in this cluster
- Ep 233: Why you’re still the point person for everything (and how to fix it). Being stuck as the final decision-maker on everything is almost never a delegation problem. Before delegation can work, three things have to be in place: the right people, clarity on where you as the owner should focus, and simple systems that reduce noise. This episode is most useful for business owners and team leads who have already hired and communicated expectations but are still buried in the weeds.
- Ep 231: Why delegating keeps failing (and the shift that actually fixes it). Delegation fails when leaders dispatch tasks instead of handing off outcomes, keeping themselves as the bottleneck at every step. The fix is shifting from fetch-the-answer assignments to giving a team member ownership of a full result, with clear context, defined success, and agreed checkpoints. This episode is especially useful for leaders who know they should delegate more but still find everything coming back to them.
- Ep 225: How to stop being the bottleneck on every decision your team makes. When your team brings every decision to you for final sign-off, you are doing two jobs at once and your team is never building real ownership. Lia’s fix is to articulate your own decision-making process, then deliberately offload specific decisions with a simple communication system so you stay informed without staying in the weeds. This episode is especially useful for founders and team leads whose capable people are still waiting on them before moving forward.
- Ep 221: Clients keep asking for you by name. How do you hand off work without losing their trust?. When clients insist on working with you personally, the bottleneck is rarely about your team’s ability. It is about two separate problems: your team needs your method translated into real training, and your clients need a clear, confident message that your team delivers the same standard you do. Lia walks through the exact moves to solve both sides, from codifying your secret sauce to publicly edifying your team members in front of clients. This episode is most useful for founders, consultants, agency owners, and service-based business leaders who are stuck as the face of every client relationship.
Want to go deeper?
The Unstoppable Team. How to build a team that runs without you in the room.
Full transcript (click to expand)
Delegating isn’t a yes or no, right? It’s not one way or the other. There’s a real gradient that we can offload responsibilities and help people take on more and learn more within. Welcome to the Managing Made Simple podcast, where you get a masterclass in managing your team with ease in 15 minutes or less. I’m Leah Garvin, your host and team operations consultant. Through this show and my programs with small businesses and corporate teams, I condense a decade of experience driving team operations in some of the most influential companies in tech into strategies to save you time, money, and most of all, stress.
It doesn’t matter if you’re a business owner who realized that running a team isn’t as easy as you thought it would be. Are a new manager learning the ropes or a seasoned manager ready to up their game? Everyone is welcome to hang out with Managing Made Simple. From conflicts to feedback to delegating and more, we leave no stone unturned when it comes to what makes us love managing, kind of hate it, and everything in between. Let’s go.
Welcome back to the show. So last week, I was doing a talk at a conference sharing the secrets of building an unstoppable team. And this is where I dove into my six-part formula, which is what my book The Unstoppable Team is about, where when you set clear priorities, you have a good onboarding process, you have clear working norms, you understand how to track work and get that bird’s eye view, you have processes around delegating and decision making, and all this comes together and how you measure performance.
When those six things are aligned, you can have yourself an unstoppable team. And so in the talk, I shared this framework and examples around how to implement these things really, really simply on teams. And at the end of the talk, somebody had an awesome question that I wanted to do an episode about today because this is something that comes up a lot. And so the question was, when I’ve delegated something, what if I see someone’s about to make a big mistake or cost the customer’s money or create a problem with our product or whatever it is?
Should I just let them fail and learn the lesson or should I step in? And this is such a great question because we can spend all this time trying to avoid being a micromanager, really building up our skills and delegating, and there’s still times when our team members aren’t quite ready for it. And my short answer is you should absolutely step in, especially if there’s an impact to the bottom line, there’s a customer impact, there’s an impact to other team members, to longer term consequences.
We definitely want to step in. Delegating isn’t a yes or no. It’s not one way or the other. There’s a real gradient that we can offload responsibilities and help people take on more and learn more within. And so I want to be clear, really at the outset of this, that it’s not you’ve delegated it too bad. It’s already, the fate is sealed. When you’ve delegated something, that’s an opportunity for someone else to take it on. But because delegating does involve you still being aware of what’s going on and in some degree of checking in, if someone is about to make a mistake that you can first see can be prevented or that you’ve been through before and you know exactly how to fix it, flagging it is a really important part of the learning of how to take something on.
And so there’s two things that I would do in this situation. First and foremost, once you see an issue that’s either about to happen or has started to happen, approach that team member and say, hey, I know you’re running with this thing, but I was curious, like I’m kind of seeing an issue starting to come up. Like, are you aware of that? Do you sense what that is? And it’s just to get a sense of, hey, they might already know what it is and they might have a plan of how to mitigate it.
And in that case, this will alleviate any concerns and you can go back to what you were doing. Now, when you ask them this, if they say, no, what do you mean? You say, oh, well, you know, last time we placed this order with this supplier and it ended up, you know, being really late and it costs like a big delay in our project. So I just wanted to flag that, right? So maybe you share then what the risk is.
And if the person’s like, oh, okay. Yes. Okay. I got it. Let me run with it again. Now you’ve planted that seed. You, you, you know, help them course correct. And then you can go back to your business. But a lot of the times we recognize something and the team member does need a little bit extra support. And so you say, hey, you know, um, wanted to just flag that using the supplier can cause some delays.
And they say, oh, well, I don’t know what to do. Like what other suppliers do we have? And then they get nervous and they need some support again. This is not a sink or swim moment where you go, well, it’s your project. You have to figure it out. This is where I would invite the person to shadow us and learn from us how we would solve that problem. And this is where you’re teaching them how to fish so that they can take on this project or process or task next time.
So in that case, I would say something like, all right, well, you know, we have a really tight timeline. So let me kind of take the reins on this, but I want to walk you through exactly what I do step-by-step so that next time this comes up, you’ve totally got it. Is that okay with you? And so you are volunteering your support and you’re asking if that’s okay. So the person doesn’t think like you don’t trust them or, you know, you you’re, you’re taking it back and, and, and it’s not their project anymore.
So you’re really just demonstrating, hey, I want to help you be successful. There’s a few things that I, you know, learnings I can impart on you. And then from there, you’ve got this. Did you know that I do team workshops on all of the stuff that I talk about on this show with large companies like Google and also with startups and small businesses like marketing agencies, law firms, and med spas, whether it’s making those feedback conversations a little less awkward, how to support your team through all of the change and uncertainty, making us all well, a little on edge right now, or delegating to empower your team to step up as owners.
I come into your teams and give you the tools you need to wrestle with all this tough stuff and feel like you’ve got it handled. Reach out at helloatleahgarvin.com or pass my info along to the decision maker in your company. And let’s make all this team stuff easier and a lot more fun. Okay. So that’s the framing. And then the second thing I would say is actually, you know, having them shadow you, talking through the reasoning behind things, letting them really understand and learn how to solve this for the next time.
I think when we jump back into a project, it can be easy to say, okay, I’ve got it from here. Go work on this. There’s another real high priority thing. You know, I’ll take this over and I’ll let you know when it’s done. But when we do that, now that person’s going to just make that same mistake again. We haven’t taught them anything about how to take it on in the future. So it is important. And you might, you know, take, you know, it might mean two of you doubling up on this task or project for a short period of time so that you can train that person on how to take that on.
But again, any amount of time of them shadowing you and learning this thing is time saved in the future. So it is worth it. And I say this about teaching our team members anything about building a relationship, about really getting clear on expectations, about mapping out, you know, how you approach a certain task, writing up a process or recording a loom video. All of these things take a few minutes, maybe a few hours. Okay. And a lot of times I hear people just like you saying, I just don’t have time.
I’m so buried. I’m drowning so much. I don’t even have time to do that. And I got to say, nothing takes more time than having to redo a bunch of work because it didn’t get done right. Having to go back to an earlier point and look at, well, where did stuff go wrong? And you’re like unwinding decisions that didn’t work. You have delayed projects because people didn’t have clear expectations and guidance set. You’re having to jump in and jump off your high profile work and your high, you know, high, high priority stuff because something went wrong here.
And now you’re pulled in anyway. Okay. So the more we figure this out upfront or the more, when we jump in, we explain exactly what we’re doing for a team member to be able to figure that out later, the more set up we are in the future. And again, this kind of thing I’m talking about, this takes a few hours at most, usually much less. So for example, if you, if you’re jumping in and you’re helping someone, you know, figure out how to complete a project and really get through something, you know, you figure out, well, what are those key meetings that you need to be having with that team member?
What are some of the things like, you know, communications that you’re sending out or whatever you’re doing to fix it and get it back on track. That’s the lesson you’ve got to impart on that person so that they can do that next time. And as you’re doing this, I encourage you not just to tell them, but write it out in an email, write the steps. This is going to be the lightweight, simple SOP or process for them to be able to do it next time.
You know, it’s probably as simple as having a checklist in many cases, right? Okay. Here’s we run through, here’s the way that we figure this out. Here’s the vendors or suppliers or contractors we use. Here’s the template, right? Just kind of getting it aggregated. So the person can really run with it later. And now doing that upfront, that’s going to save that person time on the other end. So this is really an upfront investment. Again, just a few hours, right?
At most to be able to get things humming along later. So this is what we do when we’re in a situation where we’ve delegated something, we recognize a risk that something’s going off track. And instead of just going, well, sink or swim or taking it over ourselves, we jump in. We first assess like, Hey, with a little bit of guidance, does the person understand what the risk or issue is? And can they take it over? And if not, that we have, we give them an opportunity to shadow us and learn from how we would solve it so that they can do it the next time.
All right. So delegating is something I think that’s a real challenge for a lot of us. I hear it every single day from my clients and in folks that I work with, um, both in the corporate world and small business owners, because it’s hard to know where to let go. And I would say the real, you know, the real question to ask ourselves that helps us really ground and well, what should I do here? What should I not is how can I set someone up for success for the next time?
When we ask ourself that question, then we figure out, okay, the next time I’m not going to be involved. And here would be the things that they’d have to know to be successful. All right. Give it a try and let me know how it goes. See you next time. That’s all I have for today. Thank you so much for tuning in to the Managing Made Simple podcast, where my goal is to demystify the job of people management so that together we can make the workplace somewhere everyone can thrive.
With that said, let’s spread the word. If you love this episode, please pass it along to someone who might benefit from it. See you next time.
Questions this episode answers
Should I let my employee fail and learn from their mistake or step in when I see something going wrong?
Step in, especially when there's a real cost involved. If the mistake will hit the bottom line, affect a customer, impact other team members, or create longer-term consequences, you absolutely should intervene. Delegating doesn't mean the fate is sealed and you wash your hands of it. It means you're still aware of what's happening and available to course-correct. The goal isn't sink or swim. The goal is to set that person up to succeed the next time without your help.
How do I step in when an employee is about to make a mistake without making them feel like I don't trust them?
Start by asking, not telling. Approach the team member and say something like, 'I noticed an issue starting to come up. Are you aware of it? Do you have a plan?' They may already know and have it handled, which puts your mind at ease. If they don't, share the risk clearly and offer to help. Frame it as, 'Let me take the reins on this one, but I want to walk you through exactly what I do step by step so you've got it next time.' Ask if that works for them. That way you're offering support, not taking over.
What's the best way to teach an employee how to handle a problem they've never dealt with before?
Have them shadow you while you fix it, and talk through your reasoning out loud as you go. Don't just solve it and hand it back when it's done. That teaches them nothing. As you work through the issue, write down the steps in an email or a simple checklist, including the vendors, templates, or resources you used. That becomes a lightweight process they can follow independently next time. A few hours of teaching upfront saves far more time than having to redo the work or bail them out again later.
How do I know if I'm being a micromanager or just appropriately checking in when I've delegated a task?
The key question to ask yourself is: how can I set this person up for success next time without me being involved? That framing keeps you focused on building their capability rather than controlling the outcome. Checking in to spot risks, flag known pitfalls, and offer guidance is part of good delegation. Jumping in to fix things without explanation, or taking work back permanently without teaching, is where it tips into micromanaging. Delegation is a gradient, not an all-or-nothing handoff.
Is it worth taking time to document a process when I'm already overwhelmed and behind?
Yes, because nothing takes more time than fixing work that went wrong, unwinding bad decisions, or getting pulled away from high-priority tasks because something broke. Writing up a quick checklist or sending a step-by-step email as you solve a problem takes a few hours at most, usually far less. That small upfront investment means the next time that situation comes up, your team member can handle it without you. The time you spend not documenting always comes back around as a bigger time cost later.