Notes
Most business owners who sit down with Eric for a consultation open with a people problem. “This one person never gets it done right.” “This department just doesn’t follow through.” Nine out of ten times, that is not what is actually broken. Something upstream failed first, and the person is wearing the blame for it. This episode exists to help you find what actually broke before you decide who to blame.
Eric opens with a story about a PHP security scare that had his financial planner, a client, his wife, and his sixteen-year-old daughter all talking, while he, the owner of a web hosting company, knew nothing about it. His director of web services had already handled it, because Eric had delegated a responsibility, not a task. From there he walks through the four reasons delegation fails, in the order he checks them: clarity (single statement job descriptions, measurable KPIs, a clear picture of done), trust (delegating outcomes instead of process, and “trust but verify” without surveillance), systems (one channel for every delegation, feedback loops, and the QUACK quality assurance checklists his team runs nine times per website build), and finally people, including a hard story about a camp staffer he promoted too fast and had to fire.
By the end you will have scored yourself on all four and have a simple rule to carry forward: never blame the person first. Always start with the system. Eric also points you to the Real Bottleneck Assessment on the homepage of EricDingler.com, a short AI-backed diagnostic that tells you which of the four is holding your team back and what to do next.
Key Highlights
- Delegating doesn’t mean giving tasks. It means giving responsibilities.
- To be clear is to be kind. Clarity is the first thing that breaks in delegation, and the first thing to check.
- If every emergency lands on your desk, you haven’t developed a team. You have helpers.
- Trust but verify means checkpoints and quality control systems, not micromanagement or surveillance.
- Nine out of ten times it isn’t a people problem. Never blame the person first. Always start with the system.
Key Takeaways
Okay, here we go. In today’s episode, if delegation is something that you’ve struggled with or want to learn more about, you’re in the right place, because we’re going to unpack the four reasons delegation fails, how to go about diagnosing which one you’re struggling with, and how to fix them. Welcome to the Remote Team Leadership Podcast, a show designed to help you lead better to live better.
If you’re new to the show, my name is Eric Dingler and I am the host, because it’s my show, and I’m excited you are here. I work to put this podcast together because I want to help business owners build and lead teams that allow the business owner to stay out of the weeds and lead the business, work on the business. If you’re looking for a show that helps you build a team so you only have to work an hour a day, well, you’re not going to like this show, because I like to work, and I think leaders are the people that show up and work.
But what I do want to help you do is make sure that you’re working on the right things, and help you if you’re not able to work on the right things right now. Well, how do you set a team up and develop them so, as you delegate to them, they’re able to stay in the weeds as the team, enjoy being in the weeds, and keep the business going? They’re all busy working and doing the in-the-business things, allowing you more time to work on the business.
So this isn’t about getting away. This isn’t about exiting. This is about being a leader of a team that you are working with to grow your business. Now, I want to share a story with you to tee up a little bit about delegation, where we’re headed with this, and what’s possible.
With this story, I’m hoping to paint a picture, if you will allow me for just a moment, of what’s possible. So two weeks ago, I was having a coffee with our financial planner, Nathan. In fact, Marissa and I were hanging out with him, and we talked shop a little bit. His wife was there and their little one. These are people we’ve known for a long time, and it was just great. In fact, Nathan used to work for me at the summer camp I ran. He started working for me when he was like fifteen. So this was a long time ago. Oh my goodness, I don’t know, maybe twenty years ago or so. It’s been amazing to just be a part of Nathan’s life, and now Nathan and his wife’s life, and their little one who’s just two. I actually got to officiate their wedding when I was pastoring. I was in Virginia and got to fly up to Ohio, and they got married at the camp that I used to run where Nathan used to work. So we just have this great history together.
And so we were meeting and then hanging out, spending some time together. And as we’re walking out of the coffee shop, Nathan goes, “So did this PHP thing this last week, did it really have you guys scrambling and busy?”
And I looked at him and I said, “I have no idea what you’re talking about.” And he goes, “Oh, it was in the news. This big PHP thing that was impacting websites all around the world.” He said, “I just assumed that it would be something that would impact your client websites.”
And I was like, “Well, it most definitely would. But I don’t know what you’re talking about.” I was like, “You know, Peter on my team is our director of web services. He didn’t say anything, but I’m sure that he’s handled it. So I just don’t know anything about it.”
Well, then later that night, I was talking to a client and we were just touching base. They had a massive Meta ad campaign launching, and they were having some issues with their site, and this needed to get resolved before their ad campaign started. And this client, she said, “Is this related to the PHP thing that was in the news?” And I was like, “Well, I can’t imagine how, but I’m going to get Peter and the guys on it right away, and we’ll get this resolved here real quick.” And sure enough, within twenty minutes, everything was resolved and working well. And it had nothing to do with this PHP thing that everybody keeps talking about.
So two different people bring this up. I have no idea. I own a web design, digital marketing agency. Part of our business is web hosting. We host a couple hundred websites. We’ve got a server administrator. Like, this is my industry. I own a company that does this as one of the things that we do, and I have no idea.
So the next morning, I say something to my wife about it, and I’m like, “You know, hey, this is kind of crazy. This whole thing was happening, and two people brought it up last night, and I’m going to have to look into this.” And she said, “Oh, yeah. It’s been in the news since the beginning of the week.” And I went, “You know about it?” And she’s like, “Yeah, Eric. It’s been news.”
And I was like, “Oh, I really haven’t read the news this week.” And then our sixteen-year-old daughter goes, “Dad. Yeah. It was in The Pour Over yesterday,” which is her favorite news source.
And I got to thinking about it and I thought, you know what? This is amazing to me. I love the fact that our friend and financial advisor knows about it. Clients know about it. My wife knows about it. My sixteen-year-old daughter knows about it. And I’m sitting there as the owner of a web hosting business, basically, and I have no clue what they’re talking about.
Now, here’s the thing. I didn’t need to know. I didn’t need to know, because Peter already took care of it. And I say that because I did talk to Peter about it at the beginning of this very last week. I brought it up and asked him about it, and he goes, “Oh yeah. Man, if I should have told you, I’m sorry. But you know, I worked all week last week with Alex, and we took care of it and deployed patches and let people know and monitored.” And he rattled some stuff off. And I was like, “Peter, I don’t need to know.”
I did not need to know that, because at the end of the day, it wasn’t an issue. They resolved it right away. Nothing was hacked. No websites were offline. Everything worked out well.
And here’s why I want you to lean in and listen to this. What got us to this point wasn’t me training the staff on how to respond to every foreseeable future. I’ve talked about that in past episodes. It’s about developing your team to handle responsibilities, to know what they’re supposed to do and why.
It took us time to get there. It took us years. When the team first started, when Peter first started, he was working two hours a week and I was just delegating tasks, and I had to show him a lot. And if there was anything super technical, or even kind of technical, he was reaching out to me, and he was regularly doing that. And then it was able to become less and less and less and less. And now I’m the last person that’s going to be called in for a technical thing. I’m no longer on the phone tree, if you will, for anything technical, because it’s just not what I do. Those technical things are in the weeds. They are the business of what we do. So anytime something has to be done related to that, that’s working in the business, and I’ve developed my team and set them up so that they enjoy working in the weeds and they spend their time in the weeds.
So I am no longer in the weeds. I’m able to work on the business. It’s not that I wasn’t working while all of this was happening. I was working. I was out at networking events and meeting with new clients and creating content. And we’re launching a new podcast in the town where we’re living as a lead gen, really, for our digital marketing agency. So I was busy working with the local chamber of commerce on that. I was working on the business. I was working on the core values that we’re going to instill into and make the bedrock of the AI that we’re using as a company. And so I was busy all week long working on the business, and I love working. I’m not trying to build a team where I only have to work one hour a day. I would be bored out of my mind. I don’t want to do that. I like to work.
But for the business to grow, I’ve got to be working on the right things. I’ve got to be working on the right things. And so when I was preparing for this episode and was thinking through this story, I thought, you know what? I want to unpack how I do some of this. But there’s too much to fit into one podcast episode. So I thought what I would do is walk through what I can fit in this episode, which is very clearly the four things that break when delegation isn’t working. And I want to unpack these in the order of likelihood that they break.
When I go in to do some consulting for a business, and I’m working with the owner and their team and there’s delegation issues, in every situation I always go through the diagnosing of the issue, and I go through it in this order. So I want you to listen as I unpack each of these four and score yourself as we go along. Just keep it real simple. I’m doing that right. I’m doing that wrong. It’s really kind of that simple. There’s no gray area for these. You’re either doing this well and right as a leader, or you’re not doing it well, you’re doing it wrong as a leader.
So let’s go ahead and go through the four things that break, the four reasons, I should say, that delegation fails.
Number one is clarity. Number one is clarity. One of my favorite leadership gurus, Dave Ramsey, says, “To be clear is to be kind.” So when we are delegating, we have to delegate with clarity. We have to delegate with crystal clear information. We have to make sure that we’re specific, that we’re detailed. Delegation doesn’t normally equal brevity. But we still need to be to the point. We can’t have a lot of extra information in here. We’ve got to make sure that when we delegate, there’s some very key things that we delegate. And I have a whole section in my book, Hire to Grow, where I talk about these. How do you build a delegation system? I unpack those in detail in that section of the book.
But as it gets into what we’re doing here, one of the things that works, that I want to connect back to this example of clarity, is this. Everybody on my team has a job description that’s one and a half to two pages long. Everybody’s got up to three key metrics, key performance indicators, that we’re measuring regularly. People have a growth plan. We are intentional to be leading our team, guiding our people so that they are growing, and there are metrics that we have in place to go along with this. Everybody’s got a very detailed job description, but one of the things that everybody also has is a single statement job description.
I spent a lot of time on this, because I had time. As my team was in the weeds running the business, working in the business, I was able to go out and work on the business. A year and a half or so ago, I spent about a week really honing down every role in the company, creating for them a single line, a single statement that I was able to give them and say, “This is the single most important thing for you. If the ship is sinking, this is your responsibility. If you want to know, when Eric looks at my output, what does he see as a win or a failure?”
And it’s okay. Some people are like, “Oh, I don’t like to use the word failure. That’s so harsh.” Well, it’s not. It’s just the opposite of being successful. You’re successful, you’re not successful. And it can be a failure. Now, there’s plenty of room for learning in that. I’ve shared on the podcast in the past that failure is not a courtroom. Failure is a classroom. Every time there’s a failure, there’s a place to learn. So failure doesn’t get people in trouble. Failure highlights a place that we can learn and grow and improve something in the company. We’ve created a culture where failure isn’t the end. Failure is a growth point.
And so I want my team to know, where am I successful and where am I not successful? Like I said, we have several things that everybody does. Everybody has two or three key performance indicators. These are always a number that we can measure. We look at that during their one-on-ones, and they have job descriptions.
Peter does a lot. Peter has a team that he has to lead. Peter builds automations for us in our CRM. Peter is really responsible for our project management systems. He also wears a double hat as our own company’s IT person, so he helps with all of that. If things break on a website and one of the support team needs help, Peter helps them with that. Peter communicates with clients. He’s responsible for our support ticket system. Peter has a lot of things.
And in that, for example, our support ticket system. Well, we have a KPI that measures that every ticket is responded to within one business day. Every ticket is responded to within one business day, except for urgent requests. They’re responded to within five minutes, twenty-four seven. Within five minutes of anybody submitting an urgent support ticket, they get a live response from somebody on the team, twenty-four seven. And so we look at these numbers and we measure them. I want a one hundred percent successful closed ticket count. We can never, ever have a support ticket that comes to us and we go, “Well, we just can’t fix it.” No. We fix one hundred percent of the tickets that come to us. Everything has to be resolved in a way that the client is happy with. So he’s got some big numbers that we look at.
But his main job is this. This is his thing. I’m not going to read all of these to you, because they’re very simple. Peter’s is: he is responsible to ensure all websites for our clients are accessible online at all times. They meet core web vitals, and that just means how fast they run. They meet basic SEO standards. They’re browser compatible, all these different things. He’s responsible for that, and that everything on them is functioning all the time. That’s what I want. I want you to keep all of our clients’ websites working, working fast, accessible to people with disabilities. They have to be online, and they have to be there all the time, and safe and secure. Getting hacked, getting malware in there, the server coming down, unacceptable. That would be a failure of that day.
So at the end of every day, Peter is able to go, “Was every client website online today, operating at optimum efficiency and effectiveness? Yes. Okay, this was a good day.” Or, “What happened? What broke? And how do we prevent it from breaking again?” Well, you know what, it was broken for too long. How do we fix it faster next time? Where do we need an SOP? Maybe it was impossible to keep this from happening, so what’s the SOP that gets us back there sooner? What quality control checklist would have caught that earlier?
So this is the number one thing Peter’s responsible for. Even though he’s responsible for a lot, I’ve made it very simple for him to know, at the end of every day, here’s the one question you’ve got to ask yourself. All the things still matter. But this is the one thing that absolutely matters to Eric, as the owner of the business, the most. And so when a thing hits the news and the European Union is telling countries to take their websites offline, well, that’s big news that could threaten our clients’ websites. Peter’s on it. Why? Because he is responsible.
Delegating doesn’t mean giving tasks. It means giving responsibilities. I am very clear with my team about who is responsible for what, and then I need to make sure that they have the resources they need to be successful. So when we delegate, we delegate with clarity. We delegate to them a clear definition, a simple definition, of what the project looks like when it’s done. We make sure we check that they have all the access and resources they need to get there. They have the tools. There are check-in times, milestones. There’s a lot to something when we delegate it, but it’s done in a way that ensures that there’s clarity. Nobody has to wonder, “I wonder if I should let Eric know. I wonder if I should let my leader know where I am on this.” That’s built into what we delegate. Because like Dave Ramsey says, to be clear is to be kind.
So the first thing that breaks the most often in delegation, in any company I consult with, or leader I coach, or my own company, or any leadership position I’ve had over the last twenty-five plus years, is clarity. I used to be a very unclear leader when I delegated things. I didn’t have clarity on what delegation was. I didn’t have clarity on what I was delegating. I delegated things and didn’t delegate the whole picture. I thought I had communicated clearly, and I hadn’t. There was so much wrong with how I used to delegate until I learned how to delegate with clarity. So clarity is normally the first thing that’s broken in any organization that’s having issues when it relates to delegation.
Now, the second thing that’s an issue is trust. Trust. There’s too many times I’ve seen it, I’ve heard it, I used to say it. “It’s just faster to do it myself.” “Nobody would do it as good as I will.” “Well, this is so important. I better take care of this. I’m important.” Or, when we delegate, we get into delegating process over outcome. We start to delegate more than just, “Hey, here’s what I need, and why I need it, and when I need it by, and here are the optimal times to ask questions, and I want to see this stage before it’s moved on.” A lot of times we’ll get into delegating where we say, “I need you to do this, and I want you to use this tool, and it should take you four hours, and don’t work on anything else until you do this.” We start delegating the process. We focus on process because we’re just wanting a helper. We’re wanting a helper. And that’s fine at a point, and you may start there, but you can’t live there.
In fact, the fastest way to diagnose this is this: if every emergency lands on your desk, then you haven’t developed a team. You have helpers. You may not be leading. You may be managing.
And so trust is, as a business owner, you know that problems are being taken care of because you’ve clearly identified who’s responsible for what. When you delegate an outcome, and you’ve clearly articulated what the final thing is going to look like, and you let them get there in the way that they get there best, well, that’s trust. You’re showing them trust, and over time, they’re going to trust you. If you are consistent in your delegation, if you’re consistent in your feedback, if you are consistent in how you lead them, that’s going to grow trust from their perspective.
There’s a lot that goes into building trust. And when you’re leading a remote team, when you’re leading a remote team, it is crucial that you spend time together, very intentionally, because when you’re leading an in-person team, a lot of this is built up by chance. A lot of this is built in the break room, and in the hallways, and the meeting after the meeting, and sitting around waiting for a meeting to start. It is easier to build trust in an in-person team than a dispersed remote team, which is why a lot of companies have gone to requiring people to come back to the office. They were never intentional to build in time to even be online together. So you have to spend time together.
Now, to me, honestly, this is probably the most exciting leadership opportunity that AI can create for you. The more we have AI do the work of the work we do, the more time we have to meet with people, the more time we have to be in relationship. We’re actually training our AI to look for and recommend times to connect with each other on the team, because trust is built in communication. Bad things grow in the dark. Mistrust grows in the absence of clear information. And so meeting together, working together, solving problems together is foundational, really, to building trust.
Now again, if you’re like, “I don’t have time to do that. I don’t want to do that. I just need somebody to do A, B, C,” well then, okay, fine. You’re going to be a very busy person who’s got some helpers who are helping you accomplish things, but they’re not making your life easier. They’re not taking things off of your plate. They’re taking things away and bringing them back to you. When you take something off your plate and give it to somebody else to take care of, it should never come back to your plate. You’re giving it away. “I used to have this that I was responsible for. I am now giving it to you as your responsibility.” Now, typically we don’t start there. Very, very few people are able to start there. So we don’t start there. We build up to that.
One of my favorite quotes from former President Ronald Reagan is “trust, but verify.” I do trust my team, but we also have ways to verify. Not check up on. Not micromanage.
For example, I was just talking to a buddy of mine recently who was very excited. He’s got a new role. He’s leading an in-person team, and they all work in the same room. They produce an output. I don’t want to get into the details of what it was. I’m trying to protect the innocent here. So this friend of mine has a new job leading a team that creates a widget that consumers come in and buy from them. And on Sunday he was telling me he’s very excited because he just got access to their security camera system that lets him keep an eye on everybody while he’s not there. He can just log in from his phone now, and he can zoom right in onto the hands of the person and what they’re doing.
And the thing that caught me off guard was, I guarantee you, four weeks ago, when this guy was one of those people doing that work, he’d have thrown a fit if his manager was logging in and watching them from afar. And he would have been right to be upset about it. I’m going to look for an opportunity to kind of call him out on this a little bit, because I want him to grow from being a manager into a leader. He has got phenomenal leadership opportunities in front of him, and I’m really excited for him.
But you can’t. You have to have trust with your team. When I say trust but verify, it doesn’t mean micromanage. It doesn’t mean surveillance. You shouldn’t have surveillance on your team. You have checkpoints. You have checkpoints.
In fact, this actually takes us to our third area, and the third area that fails as it relates to delegation is systems. Systems. We have to have delegation systems. Delegation is not, “I just take care of this.” If you’re delegating to your team via email, and Slack, and also in a project management software, and sometimes you might send them a text message, you don’t have a delegation system. You are creating chaos. You’re an agent of chaos. Delegation happens in a system. There are things that I would say are leadership systems. And one of the things that I love most when it comes to doing leadership is being a leadership systems engineer. I love engineering and building these leadership systems.
When you have systems, you have a way that’s tracking for you: check-in points, quality control checklists. Everything is going to your team the same way, through the same channel, and coming back to you, if it needs to come back to you for approval, in the same way. Eventually, hopefully, not coming back to you at all, because a lot of times approval can be handled through a quality control check system. You’ve got a system for feedback loops. You’ve got a system that is regularly bringing everybody to sit down one-on-one with the person leading them, where the leader is able to speak into the person they’re leading, but the people that are being led are also able to give feedback to the leader to help the leader grow. And so as your systems mature, delegation gets faster, it gets cleaner, and it supports trust.
So when we verify, we have systems that verify. For example, and I think I’ve explained this in past podcasts, one of the things that we do is we build websites. Before a project brief for a design goes to the designer, there’s a checklist. We call it a QUACK, a quality assurance checklist. We use ducks on them, and it’s this whole thing. So we have QUACK one that goes through and makes sure that everything is actually there, in the way it needs to be there, for the designer. It’s consistent. The designer is not going to have to be chasing people down. “Well, I didn’t get the logo. I didn’t get the brand colors.” Everything is there, and it’s always going the same way. And then when the designer is done with the design, before it goes back to the client for the client’s input, there’s another QUACK. We check that there’s no filler text, it’s the correct images, there’s consistency, it meets accessibility, the navigation lists all the primary pages. Everything is checked. Then it goes to the client, and then it comes back. I’m not going to go into all of it, but we have, I think, nine QUACKs that happen as a website is being built. And these QUACKs are part of our “and verify.” We trust that people are doing their systems, they’re doing their things, but people are people.
We ask a lot of our team, and our team gets busy. So we need to have this built-in system so I don’t have to worry about it, so I’m able to be out networking and bringing in even more business, knowing that I have a system and a team that is able to handle the things I sell. When I go out and say something is going to be done a certain way, I’m able to sell it with confidence, not because I’m the one doing it, but because I have a system that is operating, and our people are operating with it.
And here’s the thing. It creates less stress for the team, because they’re not having to guess. They know where to go. They’re not having to spend time chasing things down. So the cleaner the system is, the more enjoyable it is for the team, and in delegation, things don’t break. Things don’t get lost. So we have to have systems.
All right, so let’s recap real quickly. We’ve gone through three of the four things. You’re doing a great job, by the way, listening. I’ve seen a lot of people listen to the podcast, and you, my friend, are one of the best. So whatever you’re doing, just keep doing it. Okay. Now, back to the show.
We have four things that break when we find failure in delegation, and in order, they’re number one, clarity, two, trust, three, systems. And the fourth and final one is people. This is actually the one where most people start, where most people think the problem lies. Nine out of ten leaders that come to me and schedule a consultation call through my website, we get on a call, and I say, “So, what do you want to unpack today?” And they may not use the word delegation, but they’ll say something like, “Oh, I’m really just having a problem with this one person on my team. Every time we give them something, it’s never done right.” Or, “I’ve got this department, and people in this department are just…” Nine out of ten times, it’s presented as a people problem.
And I’m telling you right now, nine out of ten times, it’s not a people problem. We almost always start there. But within about twenty minutes of me asking them questions, we’re actually at a point where we’ve diagnosed it. “Oh wait, it’s not the people.” They want to do a good job. Or they sure did when they started, but they don’t know what the heck’s going on. There’s a lack of clarity. There’s a lack of trust. They’re being treated like children. There’s no clear system for them to work with. And you, as the leader, you, as the owner, you think these things exist, but they don’t. You keep changing directions. And that’s fine if you want to change directions, but you’ve got to be clear about it. You’ve got to be clear about it. Nobody on the team knows why they’re being asked to do the things they’re doing. And so there’s all of these things.
Now sometimes, though, occasionally, it is a person. Now, I will argue that even in this situation, where it’s the wrong person on the team, normally they got there because the recruiting system was broken. You hired too quickly. There weren’t enough interviews. You didn’t interview for the right things. Rarely do people change. I’m not saying it doesn’t happen. I’m not saying I haven’t had situations.
I remember very specifically, I had a young man on staff in his first year. Oh my gosh, he was phenomenal. Very responsible, great kid, and we hired him back the second year and put him in a leadership role. In fact, we hired him back for the second year as the waterfront director. And about the second week of camp, I had to fire him. It was awful.
I failed in that situation as a leader, because I rehired him at the end of the summer, before he went off to his freshman year of college. And I’m not going to pretend. I did this exact same thing my freshman year in college. Both of us, freshman year of college, discovered a little thing called marijuana. And we smoked a lot of it back then. I have no idea if this guy still does or not. But I was not living my life by my faith, and I was making decisions that I wouldn’t make today. If I could go back and do it over, knowing what I know now, I wouldn’t make those decisions back then. But I should have thought about it. I should have known. Hey, that freshman year of college, people do change.
So there are times when, yes, people will change, but generally people don’t. Generally, when somebody is in their sophomore or junior year in college and they come back to the camp, they were pretty much the same way they were the summer before. The change happens a lot for people from graduating high school to the next year, after being a freshman in college. And over those nine months he was gone from camp, he started partying a little bit and started smoking some pot. And a few weeks into camp, he got caught in the boathouse smoking pot. And so I had no choice but to fire him.
So I’m not saying that it’s impossible. I’m just saying it’s the rarity. It’s the rarity. And I learned from there. I learned, you know what? I’m going to be very cautious now. I’m not going to say never. I don’t want to overreact. So I didn’t say, “Well, that’s it. I’m never promoting somebody that’s going to be a freshman in college to a leadership role the next summer.” No, that’s not it at all. I did learn, however, not to make the decision so fast. To wait, to stay in touch, to monitor, to find out more about what you’re doing at college, visiting them at college, finding out their friend group, who they’re hanging out with. If I’d have done that with this young man, I’d have found out he stopped going to church, he was spending a lot of time on the weekends at parties, and all these things that, if I’d have taken the time to maintain a relationship with him in between the summers, I would have seen this happening, and I may have said, “You know what, let’s hold off on promoting you.”
So again, I’m not saying that there’s not the possibility that people change. But what I am saying is this. In general, people don’t change. And so it’s rare that you hire somebody, and they start out really strong, and then suddenly they change and become a different person. If that’s the case, it’s because their true character is coming out. Their true character is finally revealing itself. And nobody interviewed for character. Nobody interviewed for character. We didn’t do a deep enough dive into their history, or we would have seen, hey, there’s a pattern here. There’s a pattern in their past few jobs, and we could have asked about that in the job interviews.
If you have somebody that comes on, and you’re going to be the fourth or fifth employer, and you ask them in an interview, “Okay, so how long were you at Company A, and what was that like? Why did you leave there? How long were you at Company B, and why did you leave Company B? Why did you leave Company C?” If every single time it’s the other company’s fault, “Oh well, the people there…,” bull crap. There’s no way. And if they literally have chosen three or four places to work before you, and those three or four places were always bad places, and they now want to work for you, you should be really nervous. Maybe you should go, “Whoa, maybe we’re not that great of a company if this person wants to work here as well.” All right? But here’s the thing. I don’t think that’s true. I think you probably are a very great company. But look, seeing that pattern is going to help you go, “Oh, man.”
“But they interviewed so well, Eric.” And all I’m doing right now is sharing with you conversations I’ve had with people as I help them build a team. “Oh, but they interviewed so well.” And I’m like, “Yeah, but look at their history. What’s happening here?” “I don’t know, I didn’t ask.” Have another interview and ask. “Well, if I ask to have another interview, they might get really frustrated. They may not want the job.” Well, listen. If you ask somebody to do another interview and they get fed up with it, and they’re nasty or mean, “Oh gosh, I’ve already done two,” then you don’t want them on the job. You don’t want them on the team. Because what are they going to be like when they get the job? So don’t worry about that. And again, I’ve talked about this in the past, and I write about it in my book, Hire to Grow. We do multiple interviews. We do four interviews at minimum when we’re hiring somebody for the team, because we have a system that ensures we get the right people on the team.
Now, sometimes as the company grows and things change, we may have somebody that is no longer aligned to the work we have available for them, and we either need to find work that is properly aligned for them, or we come to a mutual conclusion. They don’t want to change. “I don’t want to do anything different or new.” And that’s fine, and we’re not going to have anything new or different for them to do. And so we come to what’s known as a necessary ending. There are times when there are necessary endings. But a lot of times you’re able to pivot and get the person working on the right things. So yes, you can occasionally have the wrong person, but generally it’s almost always a broken system.
In fact, I tell my team, and I tell people I lead, and I tell people I coach, I never blame the person. Always start with the system. Always start with the system. Never, never blame a person’s name. Look at the system. They’re not being developed. They’re not being coached. They weren’t being evaluated properly. Whatever it is, there’s a system in place. And if you’re like, “Well, I don’t have a system for that,” well, that’s a systems failure. So get a system in place. So sometimes it’s the right person, but they’re in the wrong seat. Sometimes they’re on the wrong team. Sometimes it’s the wrong company. But like I said, usually it’s a system. So look at the system. Look at the system.
And for you yourself, you need to be able to let go of things to your team, and let them take care of things, let them handle things, so you can see that they are the right person. So you can see that they’ll step into the role and they’ll grow up into it.
Back to the scenario with this PHP thing. I’m walking out of the coffee shop and Nathan asked me about it. In the past, I would have probably been embarrassed that I didn’t know what was going on. In the past, old me, a long time ago, would have felt like I had to know. And the reason I would have thought that is because I used to think being the guy that everybody came to is what made me important. I got my identity, I found value, in that. And I finally had to get to the point where I realized that’s not what makes me valuable as a human, as a person. It’s really in my faith, in my relationship with Jesus Christ, where my true value comes from. And once I got to that point, and had that realization for myself, and started to operate out of that, was I able to be a better leader and really let people step into their purpose and the fulfillment of their role on the job.
So these are the four things that, nine times out of ten… don’t stop listening. Don’t stop listening. I’m not done yet. This isn’t me winding things down. So don’t hit stop. These are the four things that break when there’s delegation issues. It’s clarity, trust, systems, and people.
Now, at the beginning I said, hey, I want you to listen to this and think through which one am I doing right, which one am I doing wrong. If there’s one that you’re doing wrong, or you’re not sure, I have built a very simple tool for you. It’s a few questions. It’s the Real Bottleneck Assessment. It’s right on the homepage of my website, EricDingler.com. Go there, click the button to take the assessment, and in a few questions, it’s going to help you very quickly diagnose if your delegation challenge is clarity, trust, systems, or people.
And not only that, and this is the cool thing about it, I’m really, really excited for this. We have connected this assessment with AI. And we have given AI access to a very large library of years of my content: written content, video content, podcast content, webinar content, my entire Google Drive of content. We have fed it this massive amount of information, and when it diagnoses this, it’s also going to give you some really clear ideas for next steps. And it’s going to be pulling it right from my experience, the things that I help people do. So I’m really excited about it. I think it’s going to help you out. So again, just go to EricDingler.com. Take the Real Bottleneck Assessment. It just takes like four or five minutes, and the results are going to be tailored specifically to you, which is really, really cool. It’s going to ask your team size. Even if it’s just you, that’s okay. It’s going to ask you a couple other questions, and we’ve really worked to build this in a way that helps you diagnose where you’re currently struggling and start to take steps to address it and fix it. So, EricDingler.com, right on the homepage, take the assessment.
Now, the other thing I want you to do is this. If you’ve already taken the assessment, I don’t want you to be like, “Oh, I’m all done. I’m going to move on to the next episode.” What I’d love for you to do is rate and review this podcast right now. Right now. If you’re driving, pull over. Okay, that’s a little ridiculous. But the next time you can safely do so, leave yourself a voice memo, do whatever you can to remember, but I need you to rate and review. If you’re on Spotify, leave a comment. I love the comments on Spotify. That’s really cool. Whatever you do, when it comes to podcasts, as long as it’s rate and review, do that for this one. It’s the price of listening.
So listen, you are my marketing plan for this podcast. Your ratings, reviews, feedback, you’re everything. You listening to this is the whole reason I make this podcast, so you can grow as a leader, because I believe your leadership capacity is the capacity of your business. As you grow as a leader, your business will grow, but you’ll find that this starts to trickle out into the other areas of life. You’ll be a better leader in your family. You’ll be a better leader in your community. Leadership is, as John Maxwell says, the tide that lifts all ships in the harbor. Everything rises and falls on leadership, he says, and I couldn’t agree with him more on that.
So remember, quick recap here for you. The takeaways: clarity, trust, systems, people, in that order. Those are the four things that break. Go find out what your bottleneck is. Take the assessment, get a next step. And until next time, just choose one of these things. Take action on it to help you lead better.