Team Leadership: How Leaders Decide What to Delegate to Protect Focus

A full plate is a sorting problem before it is a time problem. In our online dispute resolution work, I have learnt that anything I can write down as a process leaves my list. If a task can be turned into a checklist, a workflow, and a clear owner, it should sit with the team. What stays with me is the judgement about which problems matter this month and which can wait.

My single rule is that repeatable work gets a system and one-off judgement gets me. A good example is payment follow-ups, where teams often chase each reminder by hand and lose whole days to it. Once you build the reminder sequence, set the timelines, and name who acts when it fails, the work runs without you. That is delegation done properly, you hand over an outcome and a process, and you free your own week.

The moment that taught me this came from watching a slow, manual process eat a team alive. In a past role I helped move an eight-week paper journey to about eight days by digitising each step. The lesson was that holding tasks close feels responsible and quietly becomes the bottleneck. The work only scaled once the process carried it and my hands came off.

What I refuse to delegate is the call on priorities, because that is where focus is won or lost. Everything that is repeatable, teachable, and recoverable should move to the person closest to it. Give them the outcome, the boundaries, and where to escalate, and let them run. A team that owns the process gives back the one thing you cannot make more of, your attention.

My rule is that anything I can write a one-page checklist for gets delegated, and anything I cannot stays with me until I can. The moment that taught me was the fit approval on first samples in our Los Angeles sewing operation. I was the go-to for every fit check because I was good at it, and for a stretch every first sample in the building waited three or four days for a twenty minute look from me, so launches slipped a week while everyone did their jobs correctly. I sat down and wrote what I actually check, measurements against tolerance, seam allowances, how the neckline sits, on one page, and the pattern maker now signs off on anything inside tolerance while I see only the exceptions. Samples stopped waiting, and my own list shrank to the two things that cannot be reduced to a page: pricing a difficult run and telling a founder no. The trade-off is that the first month of a handoff is slower than doing it yourself, and you have to accept a few judgment calls you would have made differently.

Coming from my role managing digital operations at a precision cleaning company where we juggle multiple high-stakes projects for aerospace and pharma clients simultaneously, I learned this the hard way: delegate anything that doesn’t require your unique decision-making authority or specialized knowledge. The turning point came when I was personally handling routine content updates while a critical client certification review sat on my desk. I realized I was protecting tasks I simply felt comfortable doing rather than focusing on what only I could resolve. Now I ask myself, “If this doesn’t get done perfectly, does it derail a major outcome or just create a minor hiccup?” Minor hiccups get delegated with clear guidelines. That single shift freed me to focus on strategic priorities that actually move our business forward, and my team grew stronger by owning more of the process.

Coming from three decades of building a distance learning organization, I learned this the hard way: if someone on your team can do the task 70% as well as you can, delegate it immediately. Early on, I held onto course content reviews because I convinced myself only I could maintain quality standards. The result? Bottlenecked launches and a burned-out team waiting on my approval. The turning point came when I handed curriculum development to our senior instructors and watched them bring fresh perspectives I never would have considered. Now my rule is simple: I only keep tasks that genuinely require my unique position or relationships, like strategic partnerships with universities or major policy decisions. Everything else goes to the person closest to the work. This freed me to focus on expanding our international programs, which has opened entirely new markets. The irony is that letting go actually improved quality because the people doing the work daily often see solutions I miss from 30,000 feet.

My rule is that I keep the work that actually requires my specific judgment, and I delegate almost everything else — even the tasks I’m good at. That last part is what took me years to learn. Being able to do something well is not a reason to keep it on your own plate. It’s usually the reason you should hand it off, because those are exactly the tasks that quietly eat the hours you needed for the decisions only you can make.

I learned this the hard way running a training team. I had built the curriculum myself, so when it came time to scale, my instinct was to keep reviewing everything personally — I told myself no one would catch the details the way I would. What actually happened was that I became the bottleneck, and my team stopped growing because I wasn’t giving them room to. The moment it clicked was realizing that if I trained someone to do a task at eighty percent of my standard, that was not a loss — it was eighty percent of my time back, and my people getting better every week. So I built out clear ownership and career paths and made myself review outcomes instead of every step.

The mindset piece underneath it is detachment. When I’m gripping a task tightly, it’s almost always because I’m attached to it being done a certain way, and that attachment is what keeps me from letting go. A regular meditation practice is what helps me notice that grip and loosen it — it’s genuinely been my best productivity habit, and it’s why I ended up building Walking Meditation, a free app for exactly that kind of steadying pause during a full day.

My one guiding principle is; as long as there is someone on the team who will be able to come up to speed quicker than me clearing the way, then they can take care of that task. In general, what I’m here for is to maintain ownership of the work that requires only context that only I have from being involved for three years. I am happy to give away everything else.

It wasn’t until I left my sales position in August 2025 and began working full-time on both of my business ventures that this became an issue. With two businesses now competing for every minute I had available, I simply couldn’t keep pace with all the tasks that were required. So, I determined what I would continue to be responsible for and what I could hand off. Client Strategy, Positioning Calls, etc., these were things that were valuable based solely upon my experience over three years of attempting to make The Investors Centre successful. Production, Reporting, Delivery Mechanics – all of these could be maintained by a new hire within a few weeks of employment.

We limit the amount of hours we each put into the company (we start at half six and leave at three), so we spend afternoons with our families. Once a project has been pushed beyond three onto my list of tasks to complete, that’s when I know I’ve taken responsibility for something that the team should ultimately handle.

The instinct to keep something because you can do it better is exactly what kills focus. I learned this when we hit about 8,000 brands on Pageloot and I was still reviewing every custom QR code design request myself. The review cycle stretched to three days, clients got frustrated, and my actual strategic work vanished into approval queues. I was the bottleneck pretending to be quality control.

The moment that shifted it: a client called asking why their campaign launch was delayed. I realized I couldn’t name a single reason their design needed my specific eye instead of our designer’s. The cost wasn’t just time, it was that I’d become a gatekeeper on work that didn’t need gatekeeping, and it meant strategic decisions about product direction weren’t happening at all.

The rule I use now is this: if the task has a clear output standard and someone on the team has seen you do it once, it’s delegatable. Not because they’ll do it identically. Because the standard is the standard, not your execution style. I documented the design review checklist, assigned it to the designer, and kept only the final sign-off if something broke the pattern. Work moved in days instead of weeks. The designer caught things I would have missed because she was closer to the work.

The protection piece matters more than the delegation piece. You’re not freeing up time to fill it with more work. You’re protecting space for the decisions only you can make. That’s the actual rule.

When my desk disappears under paperwork, I delegate anything I can answer four questions about: who owns it, what done looks like, when it’s due, and when to check back with me. For our eco-packaging launch, I talked to the big clients but gave the competitor research to Jen’s team with Friday updates. We launched fine and I wasn’t working until midnight anymore. Keep the stuff that needs your actual voice. Give the rest to good people with clear directions.

I’ve learned how to delegate by trial and error. If I can write something down as a checklist, it goes to my team. The legal judgment calls stay with me. Handing off work felt pointless at first. Then we had that nightmare week with bonded titles, and I finally saw what actually needed my attention. Now my team handles routine state transfers using our guides. I jump in when salvage paperwork looks questionable. Figure out what’s predictable versus what needs your eyes, then let the first category go.

I use a counter instead of a rule. First time a question lands on my desk, I answer it. Second time the same question shows up, I write down how I answered and hand the whole category over.

That switch happened because of support tickets at our company.

We run marketing with one person. Every customer pain point that comes through support turns into content, and early on I was the one deciding which ones were worth writing about.

Then the same categories kept repeating.

Once I wrote down what made a ticket worth covering, the choice stopped needing me. Our marketing lead runs it now and the content sounds more like our customers than anything I would have picked.

If you’re answering the same thing twice, you’re not doing work anymore. You’re a lookup table with a calendar, and that’s an expensive way to be useful.

I’ve spent years coaching CEOs of companies between $50M and $2B, and delegation is honestly one of the hardest things I see them struggle with — not because they don’t trust their teams, but because they’re using the wrong comparison.

Here’s the rule I give every CEO I work with: if someone on your team can do a task at 70% of your level, delegate it immediately. You don’t need a perfect handoff — you need a good enough one. The moment you stop asking “are they as good as me?” and start asking “are they good enough?”, your list gets a lot shorter fast.

The moment that crystallized this for me was watching CEOs insist they couldn’t free up time for high-stakes strategic work because they were “already at 70 hours a week.” The real problem wasn’t the workload — it was that they were holding jobs they should have handed off. I wrote an entire book (*Great CEOs Are Lazy*) around this: your goal is 15-20 hours on your highest-leverage constraint. Everything else either gets delegated, deferred, or dropped entirely.

One thing people miss — delegation isn’t binary. You don’t just hand something off and disappear. Sometimes you say “investigate and bring me options, I’ll decide.” Other times it’s “own it completely.” Matching the delegation level to the risk and dollar amount involved is what separates thoughtful leaders from ones who either micromanage or abdicate entirely.

Having led CABEM Technologies since 2002 delivering software across regulated sectors like healthcare and government, I constantly face the challenge of prioritizing high-stakes oversight against technical execution.

My core rule is that foundational compliance architecture and high-level strategic alignment stay on my desk, while technical implementation and system adaptation belong to my team.

A defining moment came when scaling deployments for platforms like our Competency Manager and CJIS Audit Tracking software. I stepped away from direct technical customization and delegated system builds to our U.S.-based engineering team, trusting them to leverage our proprietary library of AI-enhanced modules.

Letting go of direct software development protected my focus for strategic growth and regulatory roadmaps, while allowing our engineers to rapidly deliver secure, tailored enterprise solutions.

I run a full-arch implant practice in Corsicana, and after 18 years, 10,000+ implants, and roughly 200 full-arch treatments a year, delegation is survival. My rule is simple: I keep the decisions that change the treatment plan; I delegate the steps that can be standardized, checked, and repeated.

The turning point was “no bone” patients needing zygomatic/pterygoid remote-anchorage planning and same-day teeth. I realized my focus belonged on the CBCT review, implant strategy, and patient conversation — not every scan, design step, or milling task.

So we built a 100% in-house digital workflow with trained team members handling scans, smile design setup, CAD/CAM production, 3D printing, and guide preparation. I still review the critical points before treatment, but I’m not the bottleneck for every handoff.

The practical test I use is: “If this goes wrong, does it change the patient’s health investment, safety, or trust?” If yes, it stays with me; if no, it gets a system, an owner, and a final quality check.

I will say one key moment when this became apparent for me, it was when I realized I was evaluating each article we publish in detail from start to finish while simultaneously running the commercial side of the business. It was clear something needed to be dropped; however, I consistently chose the wrong thing to let go of.

Rule: Delegate the “doing”, but do not delegate the method. A method (or process) is equal to a product. For us in our industry, as the original founding team, the method includes opening live accounts using our own money, placing actual trades, making real-time withdrawal requests and documenting everything we experience. If I were to delegate these processes to someone else, then I would have delegated the product itself. I would now be a manager over others’ opinions. All operational activities, including scheduling, website development, etc., are things which those people can do much better than I could. However, the editorial standards and testing methodology cannot be delegated.

It has been quiet since I made that decision. People no longer ask if our articles/reviews are paid for. That fact alone being eliminated from our audience’s questions regarding my company is worth significantly more than any individual agreement we have signed.

My Rule:

If you’re simply doing something I have already created as part of your processes — then it should not be on my To-Do List. That is why we create a process — to take care of those types of things. I will still make judgments about what needs to happen — but that can all go to our Team Members.

When I finally made the decision to follow this rule was after taking 4+ years of freelance work for clients on Reddit and creating a productized version of that service in early 2026. When I worked as a Freelancer, I did everything myself because it seemed like an easier way to do business. With Productization, however, I had to write out each one of the Judgement Calls I made (i.e., What makes a thread worthy of engagement? How many times do you need to ignore something before you walk away from it even though it appears to be relevant at first glance? And how does tone shift based upon the community?) — so another person could carry them out. Once a Decision becomes a Documented Pattern — It is removed from My To-Do List.

I will still own:

Client Strategy Calls.

Positioning.

And the Edge Cases — Where there is No Playbook Yet. These are the decisions where If I am Wrong — I lose money. If I Am Right — that is Why they Hired Me instead of a Template

The rule I settled on years ago is simple: anything you can teach to a standard, the team should own. Anything that decides what the company stands for in front of a customer, I own. My crew leaders run the truck, the wrap, the stairwell read — that’s what our in-house training is built for, teaching foresight so a lead sees the tight turn before the sofa gets there. A repeatable piece of that: on move-in day the lead signs the door of each room so nothing lands in the wrong place. What I don’t hand off is the reply when something goes wrong. Bad reviews come back to my direct line — a landline, not a cell — and I answer them under my own name. I can train a crew lead to anticipate a tight stairwell. I can’t train someone else to decide what this company stands for when a move goes sideways in front of a customer. We’re four trucks and six drivers, so I don’t have the layers a bigger outfit has — but that’s why keeping judgment on my plate is the one thing that protects the brand.

I keep whatever is still unproven and hand off whatever already has a decided answer. If a task has one correct way to be done, someone else can own it. If the task is really a question about what we’re willing to bet on, it stays with me.

That sorting comes from how I work on products. Rethinking a category nobody pays attention to means sitting with raw customer feedback and arguing about a design choice until it either survives or dies. Nobody can do that argument for me, because the argument is the job. Once a decision is made, the execution around it becomes documentable, and holding onto it is just me being sentimental about work I already finished.

The delegation call that protected my focus most was giving away everything downstream of a design being locked. Files, follow-ups, coordination, and revisions against a spec that already existed. I stopped being the bottleneck on things where my opinion no longer added information.

When work floods in now, I ask whether my involvement changes the outcome or only slows it down. If a capable person with the context would reach the same conclusion I would, it isn’t mine anymore. That leaves my list short, uncomfortable, and full of the calls only I can make.

Effective leadership requires a shift from being the best problem-solver in the room to the best problem-allocator for the organization. Scaling a startup to 650 professionals forced me to realize that my own technical proficiency was becoming a primary bottleneck for the company. I now manage my capacity using a strict Repeatability Rule: if a task has a predictable workflow and I have performed it successfully more than three times, it no longer belongs on my list. I reserve my focus for unmapped strategic pivots, high-stakes cultural navigation, and the direct mentoring of my leadership team.

This rule solidified during a period of rapid international expansion. I was still attempting to review every complex enterprise software architecture for our largest clients, convinced my personal oversight was the only way to maintain our standards. When I eventually audited our delivery metrics, I saw that project starts were stalling for weeks specifically because they were waiting for my approval. I was the single point of failure. By clinging to my identity as the technical expert, I was failing as a CEO. I had to delegate the final architectural sign-offs to my delivery managers and shift my energy toward creating the quality frameworks they would use to make those decisions.

Protecting your focus is about ensuring your energy is spent on unique activities that cannot be replicated by a system or a process. If you are handling a task that a well-documented process could resolve, you are not leading your company-you are simply filling a seat. True delegation is not just offloading work; it is empowering your team to own outcomes while you focus on the horizon.

With over 31 years in the insurance and risk management industry, my single rule is delegating anything where our team’s dedicated focus gives the client a clearer, more thorough advisory experience than my divided attention.

A defining moment occurred at Business Insurance Specialists when technical policy breakdowns were piling up alongside executive brokerage duties. Handing off those comprehensive risk walkthroughs to our in-house specialists allowed them to deliver the dedicated, step-by-step guidance our clients needed to understand their coverage options.

Empowering our team to own that tailored advisory support consistently delivered better client outcomes while protecting my bandwidth for strategic governance and exclusive market access. Delegation succeeds when you assign tasks based on who can give the client the highest degree of focus.

I scaled multiple dog businesses from a solo walking service in Chicago to a full LA training and grooming facility before shifting into digital marketing for trainers and campaigns. That path forced me to figure out delegation fast or burn out.

The turning point came when I opened the LA location. Daily operations like scheduling walks, managing boarding rotations, and basic grooming flows were eating every hour. I handed those off to trained staff using clear checklists I built once, which freed me to focus on client programs and new service development.

My rule now is simple: keep anything that requires my direct judgment on brand voice or long-term positioning, and delegate every repeatable execution step that others can own after initial setup. Joel handles the technical SEO builds and graphics this way at So Fetch, while I stay with the S3 strategy sessions.

Between serving as a Cyber Operations Officer in the US Air Force and building my vending operations in San Antonio, I learned to filter tasks by operational leverage. I delegate execution that can be standardized and keep core partner relationships and high-level strategy on my own list.

The defining moment happened while scaling MM Healthy Vending and launching Vending Circle. I was spending valuable hours handling routine equipment troubleshooting instead of securing distributor relationships with suppliers like QinGo and Nayax.

My single rule is: delegate anything that can be resolved with a structured process, but own the relationships that create leverage. Passing daily operational Q&As and troubleshooting to our experienced mentors freed my focus to expand the business without dropping the quality of support.

I started Rise and Shine by handling every cleaning, call, and schedule with my wife, so I learned early which work builds lasting customer trust and which can be handed off once the right people are in place.

My rule is to keep anything tied to hiring for character and managing overall capacity, while delegating the day-to-day cleaning once someone has shown they fit the values and has the tools to succeed.

Early on, when we realized those first two clients were still with us after we stepped back from daily cleans, it showed that consistent results came from training and supporting the team rather than doing everything ourselves.

This keeps my focus on sustainable growth systems instead of getting pulled into every task that keeps piling up.

Balancing residential, commercial, and agricultural projects at Lassiter Roofing alongside my background as a Firefighter EMT taught me strict triage under heavy workloads.

My rule is to delegate tactical execution immediately and keep high-liability risk calls on my own desk. When weather backed up work across the Western Treasure Valley, I stopped managing daily schedules and handed direct installation workflows entirely over to the crew.

That freed my focus to handle custom site quotes and complex flat-roof structural inspections that directly protect our 5-year workmanship warranty. Trusting your team to execute keeps projects moving, while keeping high-stakes assessments on your list protects the business.

As founder of AL-Care and a tech investor with five exits, I’ve learned the hard way that being “needed” everywhere is usually a sign the system is too dependent on you.

My rule: I keep the work where my judgment, trust, or relationship materially changes the outcome. I delegate the work where a clear process, a caring person, and a fast check-in can get the family or project what they need.

That became real after my friend Steve Demas was diagnosed with stage 4 lung cancer. I could not personally solve every need, so I focused on the mission and relationships, while building a network that could help with referrals, counseling, financial guidance, events, and follow-up.

A practical test I use: if I am delaying the work by holding it, it probably belongs to someone else. Delegation is not dumping work; it is removing yourself as the bottleneck while staying accountable for the outcome.

I’ve had to learn this building multiple real estate ventures while also representing Dutch FC in Frisco. My rule is simple: I keep anything that defines the standard, and I delegate anything that can be executed inside that standard.

At Dutch FC, playing time and player placement can get emotional fast. Once we clarified the six factors — attendance, attitude, ability, game performance, position, and game significance — coaches could make consistent calls without every issue landing on one person’s desk.

The moment that shaped this for me was realizing a late-blooming player may be better served as an impact player in the right squad than a role player in the “highest” squad. That kind of philosophy stays with leadership; the weekly execution belongs to the staff closest to the players.

Delegation fails when you hand off tasks without handing off standards. If the team knows the values, the process, and what “good” looks like, you protect your focus without lowering the bar.