Kirk Baker: Task Delegation Deep Dive : Making It Stick in Your Agency (Part 2)
Hosts of The Insurance Dudes Podcast. 1,000+ episodes helping insurance agents build elite agencies.
Delegation sticks when the owner debriefs instead of intervening, makes performance metrics visible, and builds redundancy across the team. Kirk Baker also flags the hard call: when a team member won't take ownership, the long-term cost of keeping them is bigger than the transition out.
Task delegation sticks when the owner runs structured debriefs instead of stepping back in to fix things, makes performance metrics visible, and builds real redundancy across the team. Kirk Baker covers what to do when a team member will not take ownership and the call has to be made.
Why does delegation break down weeks after the handoff?
Most delegation failures don't happen during the handoff. They happen in the weeks that follow, when the new arrangement gets stress-tested by real situations. An unusual client complaint comes in and the owner jumps back in because it's faster. A renewal slips through a crack and the owner decides it's just easier to handle renewals themselves. The team member makes a decision the owner wouldn't have made, and the owner overrides it.
Each one of these interventions sends a message to the team: "I don't actually trust you with this." And each message erodes the team member's confidence and initiative until, eventually, they stop trying to handle things independently because they've learned that the owner is going to get involved anyway.
Kirk's diagnosis is that most owners delegate the task but not the trust. They intellectually believe their team can handle things, but they react to imperfection with intervention rather than coaching. The standard they're holding their team to is "do it exactly the way I would do it the first time", and that standard is unreasonable. It takes time to develop judgment. It takes reps. The owner's job during that learning curve is to coach and debrief, not to take back the ball.
How does a structured debrief replace intervention?
One of the most underused tools in the delegation toolkit is the structured debrief. Instead of intervening when something goes sideways, the owner holds a debrief conversation: What happened? What decision did you make and why? What would you do differently? What do you need from me to handle it better next time?
This approach accomplishes several things simultaneously. It preserves the team member's ownership of the task, you're coaching them to get better, not rescuing them from failure. It surfaces the gaps in training or authority that need to be addressed systemically, rather than handling each situation as an isolated incident. And it builds the kind of judgment in your team that eventually makes them capable of handling situations you haven't explicitly prepared them for.
The debrief also changes the owner's role. Instead of being the person who fixes problems, you become the person who develops people. That's a fundamentally different, and more scalable, way to spend your time.
What accountability structures actually work without becoming micromanagement?
Delegation without accountability is abdication. The distinction matters. Accountability means the team member knows what success looks like, knows you're going to check, and understands the consequences of consistent underperformance. It doesn't mean micromanagement, it means regular, structured check-ins where performance data is reviewed honestly.
Kirk's approach to accountability centers on making the metrics visible. If a team member owns the renewal retention rate, that number should be visible to them and to the owner on a regular cadence. If someone owns the service response time, they should see that metric weekly. Visibility creates ownership. When people can see their own performance data, they self-correct without needing the owner to point out every slip.
The structure that works: short weekly check-ins focused on metrics and blockers, monthly deeper reviews where patterns are discussed, and quarterly conversations about development and growth. This isn't bureaucracy, agencies that skip this infrastructure end up with the owner doing informal, inconsistent oversight that generates more anxiety and less improvement than a simple structured process would.
What do you do when a team member is not working out?
Not every delegation attempt succeeds because not every team member is capable of or willing to take real ownership. Part of Kirk's framework is recognizing the difference between someone who is underperforming because of a training gap versus someone who is underperforming because they don't actually want the responsibility.
Training gaps are fixable. Unclear expectations are fixable. Missing authority or tools are fixable. An unwillingness to take ownership, a preference to always escalate, always defer, always avoid the decision, is much harder to fix. At some point, the agency owner has to make the hard call that the team and the role aren't aligned, and that keeping someone in a position they're not suited for is costing the agency more than the transition out would.
This is uncomfortable. It's one of the reasons agency owners default to doing things themselves, the calculus of "hire, train, wait for them to develop, potentially let them go and start over" feels more expensive and painful than just handling it yourself. But that calculus ignores the long-term cost of an owner who can't get out of the weeds.
Why should you build redundancy into the agency on purpose?
The ultimate goal of delegation is redundancy, not redundancy in the sense of unnecessary positions, but in the sense that the agency can function at a high level even when any one person, including the owner, is unavailable. That means cross-training. It means documentation of processes that lives outside any individual's head. It means team members who know enough about each other's roles to cover gaps without everything grinding to a halt.
Agencies with strong redundancy are dramatically more resilient. They handle staff transitions better. They handle the owner's absence, for vacation, illness, or growth-related travel, without the client experience deteriorating. They're also dramatically more attractive to potential acquirers, because a business that runs on the owner is worth much less than a business that runs on systems.
How do you hand off one task fully this week?
Pick one Tier 2 task from your delegation backlog, something you identified in Part 1, and this week, fully hand it off. Document the process, train the right person, give them the authority to make decisions within clear boundaries, and resist the urge to intervene unless something truly irreversible is about to happen. Schedule a debrief for the end of the week. One task, fully delegated, is worth more than ten tasks half-handed-off.
What is the bottom line on making delegation stick?
Delegation is a skill, not a personality trait. It can be built, practiced, and improved. Kirk Baker's experience running a successful agency is proof that the new frontier, service delivered by a team, not by the owner personally, is achievable. The framework is in Part 1. The execution is what Part 2 is about. Start with one task. Build the muscle.
Catch the full conversation:
This is Part 2 of a 2-part conversation with Kirk Baker.
Level up your agency:
Listen to The Insurance Dudes Podcast
Get more strategies like this on our podcast. Available on all platforms.
Related Episodes
Kirk Baker: The New Frontier of Agency Service and Task Delegation (Part 1)
Always Be Recruiting: Why Your Agency's Hiring Pipeline Is More Important Than Your Sales Pipeline
Square Peg, Round Hole: Why Your Best Employee Might Be in the Wrong Seat
Teach Your Team How to Fish: Why Doing It Yourself Is Killing Your Agency
Lackluster Leadership: The Failures That Are Quietly Killing Your Agency