Skip to content
Vol. 7 · Weekly edition
Economist Zone

The Hub for Economic Articles & Insights

This week

Q&A

Q&A

How Business Leaders Delegate Without Losing Control

EZEconomist ZoneNovember 18, 2026

§ How this was made

The perspectives in this article were written by the named contributors and submitted through Connectively. Connectively's automated system selected them and used AI to write the headline, introduction, section headings, summary sections, and illustration, and to make minor edits for clarity. Articles are assembled and published automatically. Report errors to corrections@connectively.us. How we make our content

Illustration generated with AI

Delegation can help a business move faster without leaving leaders out of the loop. Experts in management share practical ways to assign ownership, set clear limits, and review results without micromanaging. From spending caps to weekly decision logs, these methods keep teams accountable while giving leaders control.

What the experts said

25 contributors
LD

Louis Ducruet — Founder and CEO, Eprezto

Assign Owners and Review Weekly Results

I delegate the decisions where the person closest to the work has better information than I do, and I keep oversight through a fixed weekly checkpoint instead of approvals along the way.

At Eprezto we run a weekly, data-driven growth cadence. The rule is simple: whoever proposes an experiment owns it end to end. They design it, run it, and present the results to the team the following week. I do not sign off on each step in between.

What that removes is the queue. Ideas do not sit waiting for my approval, and nobody is confused about responsibility. There is one owner per experiment, and everyone knows who to ask. The oversight comes from the presentation itself. Results are shown with the data a week later, so a bad call surfaces quickly instead of quietly running for months.

There is a cultural side to it too. Ownership becomes a habit people practice every week rather than a value written on a wall, and in my experience culture comes from consistent habits like that, not from slogans.

So the practice I would recommend is one owner per initiative, a fixed day to show results, and the data on the table. You give up approving every step, and in exchange you get a regular, predictable moment where you see everything that matters.

JH

Jason Hennessey — CEO, Hennessey Digital

Pair Decision Owners With Dissent Owners

Scale exposes a leadership habit, keeping decisions because the founder once made them well. Expertise is not a permanent claim on every choice. Keep decisions that set standards across departments, protect trust, or determine where scarce resources go. Delegate decisions where speed, proximity to the customer, and knowledge matter more than consistency.

My practice was assigning a decision owner and a dissent owner. The owner advanced the recommendation, while the dissent owner had to identify blind spots, second-order effects, and evidence that would change the call. Both names appeared in the plan. This created friction before action and eliminated committee ownership. Oversight improved because disagreement surfaced early, not after disappointing results.

WM

Will Mitchell — Founder, StartupBros

Set Spending Ceilings and Read Friday Recaps

A while back I kept a running note on my phone of every decision someone brought to me in a single week. By Friday it was long, and most of it was refund approvals, ad copy tweaks, supplier follow-ups and which support reply to use. Almost none of it would have hurt the business if someone got it slightly wrong.

So I sorted the list by one question. Whether a bad outcome could be undone cheaply by the next week. Everything that passed went to my team with a written spending ceiling attached.

Under that number, they decided and moved on. Over it, or anything touching pricing, hiring or a long-term contract, still came to me.

What kept it from turning into confusion was a short Friday recap. Each person sent me a few lines on what they'd decided that week and why. I didn't approve anything in it.

I just read it, and if I spotted a pattern I didn't like, we talked Monday and adjusted the ceiling or the rules. Within a few weeks the interruptions dropped off, my mornings went back to the work only I could do, and my team stopped sitting idle waiting on me to answer simple questions.

RO

Ronald Osborne — Founder, Ronald Osborne Business Coach

Write Rules Before You Delegate

I delegate any decision that happens often, follows a clear rule and costs little to get wrong, and I keep the rare, expensive and hard to reverse ones. When I grew my NBN telecom contracting company in Australia to about 30 staff, I first thought five employees was my limit, because I was making every call myself and working until 2am. What broke that ceiling was writing standard operating procedures for the repeat decisions, like which crew took which job, what counted as a finished joint and when a job could be signed off. Once the rule was written down, a supervisor could make the call as well as I could. Oversight came from data rather than from hovering. Every job was captured in the field on our own software and checked by an office admin before it counted toward pay, so I could review the numbers each week instead of approving each decision. What I kept for myself was hiring, pricing big contracts and any decision about safety, which is why I turned down small cell tower work when I was not comfortable with the risk to my people. The practice that freed my time without confusion was simple: no decision got delegated until its rule was written, and every delegated decision left a record I could check later. People knew exactly what they owned, and I knew exactly where to look if something went wrong.

RS

Roman Surikov — Founder & CEO, Ronas IT | Software Development Company

Grant Authority Through Written Follow-Ups

I delegate a business decision when the person doing the work has the context to make it, its consequences are contained and we agree what would require escalation. A channel choice can go ahead without my sign-off. A decision affecting a client commitment or the company's direction deserves a separate conversation. The boundary gives the colleague room to act and gives me a specific reason to step in if the choice grows beyond it.

After a leadership meeting, I sent a written recap grouped by topic and assigned an owner to each item. I invited colleagues to correct anything I had missed or described inaccurately. In that same thread, I told a colleague the channel decision needed no approval from me. I also reported progress on my own items there, including work I hadn't finished. Everyone could see the owner and next step while the colleague retained authority to make the channel choice.

For me, the useful practice is pairing that explicit permission with a written follow-up. Taking my approval out of a bounded channel choice removes a decision from my queue; the recap still lets me check what happened and who is responsible. It avoids the confusion that comes from silently delegating a task while colleagues remain unsure whether the actual decision still belongs to me. I check whether a choice remains inside its agreed limits and whether anyone has surfaced a conflict. A change to a client promise, or a dependency another team cannot absorb, needs discussion before the person commits to it.

Write down one choice a colleague can make without asking you, identify its owner and the condition that brings it back for discussion. The ordinary leadership follow-up can then show its outcome alongside the other commitments.

JH

Jens Hagel — Founder & Owner, kjello

Draw Clear Lines for Management

I founded my IT company in 2004 and ran it for 21 years. In 2025 I handed day-to-day management to Philip, who had worked his way up from sales over almost ten years. I kept two things: most first meetings with new customers, and building kjello, our own IT support platform. Everything else is his call, and drawing the line that clearly is what kept it from getting messy. Jens Hagel, Founder & Owner, kjello (Hamburg, Germany)

DL

Dr. Laurence Schimmel DDS — Owner & Orthodontist, Schimmel Orthodontic Associates

Define Scheduling Authority Boundaries

As responsibilities grow, how do you decide which business decisions to delegate while retaining appropriate oversight?

Running an orthodontic practice means making decisions throughout the day, but not every decision needs to come through me.

I separate decisions based on their impact. Anything involving a patient's treatment plan, clinical safety, or a significant financial commitment requires my involvement. But routine scheduling changes, administrative questions, and day-to-day office coordination can be handled by team members who understand our procedures.

The key is making sure people know where their authority begins and ends. I want my team to feel confident making decisions, not worried that they'll get in trouble for handling something without asking me first.

What is one delegation practice that freed your time without creating confusion?

One practice that's helped is establishing clear guidelines for which scheduling issues the front desk can resolve independently and which ones need to be brought to my attention.

For example, the team can handle routine appointment changes, but if a scheduling request could affect the timing of a patient's treatment, that's something I need to review.

This keeps routine questions from interrupting patient care while making sure important decisions still receive the right attention.

I also believe in checking how things are working rather than checking every decision. If the schedule is running smoothly, patients are getting timely appointments, and the team knows when to involve me, the system is doing its job.

Delegation works best when employees know what they can decide, when to ask for help, and why those boundaries matter.

SB

Scott Brown — Founder, Focus Group Placement

Use Decision Briefs and Weekly Dashboards

I decide what to delegate by sorting decisions into two buckets: reversible decisions with a limited downside, which I hand off completely, and irreversible or high-stakes ones like pricing, compliance, and brand-defining choices, which I keep a hand in. Running several consumer services, I learned that if a mistake can be fixed in a week without hurting customers, it shouldn't be waiting on my approval. The one practice that freed up the most time without confusion was writing a short "decision brief" for each recurring area, covering the goal, the guardrails (budget limits, quality thresholds), and what triggers an escalation to me. Then I review a weekly dashboard of results instead of approving individual actions. People know exactly where their authority ends, and I stay informed without being a bottleneck.

BA

Brinda Ayer — Environment and Development Consultant, Founder and Principal Consultant, Urban Creative

Review Decisions Weekly Instead of Constantly

I decide by asking two questions about each decision: how costly is it to reverse, and does it touch a principle the brand stands on? Decisions that are easy to undo and low risk - such as how to word a customer reply, how to arrange a packing step, or which routine detail goes in a product description - I hand over completely. Decisions that are hard to reverse, such as choosing a new supplier, changing a material, or making a claim about certification, I keep, because a mistake there affects trust that took time to build. For instance, I would never delegate how we describe our certification, since the raw materials are certified organic where possible but the finished products are not yet certified, and that wording has to stay exact.

The practice that freed up the most of my time without causing confusion was a short weekly review instead of constant check-ins. People make their calls through the week, write one line on what they decided and why, and we go through the list together. If I disagree, we talk about it then, in private. They get freedom, and I keep oversight without hovering.

Since we put this simple weekly review in place, I have reclaimed roughly 8-10 hours a week that used to go into day-to-day decisions. Decision turnaround for routine work has sped up by about 40%, and we have been able to grow order volume more than 2.6x while keeping the core team the same size and without adding layers of management. Clarity went up, and second-guessing went down.

DV

Douglas Van Soest — CEO, Storology Storage

Assign Maintenance Work Through One Platform

When my wife Andrea and I bought our first storage facility, we answered the phone calls and did all the collections. Pretty much everything we could do remotely, we did. Now our team handles those things. The distinction for me is whether somebody's dealing with the business as we run it today or making a decision that changes how we're going to run it. If it's the latter, Andrea and I still want to be involved.

One thing that's helped is having one place to assign work to the maintenance people. We use Monday.com for that. The team can get something taken care of on site without Andrea or me having to make the call and pass the job along. We have a weekly meeting where we catch up on what's going on and talk through issues. If something comes up during the week, we're still in touch by phone, text or email.

Where we still get pulled in more than I'd like is a one-off situation with a tenant. Sometimes a manager comes to us for an answer when I'd be comfortable with them making the decision and just letting us know what they did. That's probably the next thing we need to give up.

SA

Sahil Agrawal — Founder, Head of Marketing, Qubit Capital

Audit Random Outreach Lists Each Week

The lead of our analyst team decides which investors go on each founder's outreach list. I read a few of those lists only after they have gone out. Getting founders in front of investors who actually fit is what they pay us for, which makes that list close to the most important call we make. I used to approve every one. Now I pick 2 at random each week and go through them with her, mostly asking why one fund made it and a similar one did not. You keep oversight that way without becoming the queue everyone waits on. What I hand over are the calls we make every week, where one weak pick is cheap to fix.

Some weeks I find nothing. She has overruled me on a couple of funds I liked. Lists now reach founders about 2 days sooner.

NF

Nicolas Falourd — CEO, Cyber Techwear

Track Decisions in a Shared Log

I keep strategic areas, product direction, brand identity and international e-commerce strategy, under my oversight, and delegate repeatable operational tasks that don't change that direction. That separation lets me focus on collections and positioning while the team runs day-to-day fulfillment, customer service and site maintenance.

One practice that freed time was a single shared decision log: every delegated decision must list the scope, the fallback rule and a short entry in the log. We coupled that with a fixed weekly check-in (30 minutes) so small issues never interrupt the day.

I introduced this after moving from banking to build Cyber Techwear, and it stopped ad-hoc questions without removing responsibility from the team.

KS

Kruno Sulić — Founder & SaaS Product Builder, Cliprise

Set Thresholds for Written Decision Notes

As responsibilities grow, I delegate based on two filters: how reversible the decision is, and how much downstream impact it has. If a decision is easy to reverse and stays within an agreed budget, timeline, or brand standard, it should be owned by the person closest to the work. I keep direct oversight on decisions that are hard to undo, affect pricing, core product direction, legal or financial risk, or change the company's operating priorities.

The practice that freed the most time for me without creating confusion was assigning a clear decision owner and requiring a short written decision note only when something crosses a preset threshold. In practice, that means the team does not ask for approval on every tool, creative variation, or workflow tweak. They decide. But if the choice affects customer experience in a meaningful way, changes a process used by multiple people, or commits us to meaningful recurring cost, they document the recommendation in a few lines: the decision, options considered, expected upside, downside, and what would make us revisit it.

That simple structure removed a lot of meetings because people knew where their authority started and stopped. It also gave me oversight without becoming a bottleneck. Instead of being pulled into every small decision, I review a concise trail of the decisions that matter and can spot patterns early.

One lesson I learned operating SaaS and digital product workflows is that delegation breaks down when authority is vague, not when people lack ability. If you want to free your time, delegate the decision itself, not just the task, then define the guardrails in advance: budget limit, success metric, deadline, and when to escalate. That keeps speed high and confusion low.

KB

Kyle Barnholt — CEO & Co-founder, Trewup

Use a Weekly Decision Register

We created a weekly decision register to separate choices that need input from those that require approval. Before each leadership meeting, team members record the decision, owner, deadline, and risk level. Most entries need no discussion because ownership is clear and the next step is already assigned. This keeps routine decisions moving without unnecessary delays.

The register saves time by preventing every update from becoming a leadership issue. We review it for delayed decisions, recurring patterns, and matters outside agreed boundaries. Written response expectations also prevent people from guessing whether silence means approval. It gives us a simple way to review outcomes and improve judgment without making delegation feel like constant second guessing.

CV

Carolyn Vasquez — Founder, Ready Rental Cleaning

Verify Cleaning Quality With Photo Proof

I sort decisions by how reversible the mistake is. If a wrong call costs a few dollars and gets fixed the same day, it goes to whoever is doing the work. Anything that touches money or access to someone's home stays with me.

The practice that freed the most time is photo proof on every room. My cleaning teams work inside homes I'm never standing in. Each room gets a before and after photo, and the checklist for a standard Airbnb turnover runs 116+ tasks. When I want to know how a job went, I open the photos. That takes a couple of minutes.

It replaced most of the check-in calls and texts I used to field. The cleaner knows what done looks like before they start, so nobody has to guess or ask. Oversight stays light because the evidence arrives on its own, in a form I can scan quickly.

When a photo shows a miss, I fix the line on the checklist, so the next person working that home sees the corrected instruction.

EA

Emmanuel Arad — Founder & CEO, RIVATA

Turn Repeated Answers Into Standing Rules

I sort decisions by how easy they are to undo. If a decision can be reversed in a minute, it gets delegated, with a written rule instead of a conversation. If it can't, it stays with me: anything that gets printed, anything that changes what we promise customers, and anything that moves money.

The practice that freed the most time was turning my repeated answers into standing rules. "Hide, don't delete" is one: when something on the site needs to come down, it gets hidden, never deleted, so any call someone else makes can be undone. "Nothing goes public without my go" is another, and so is "check the source before you state a fact." I wrote each of them down once. Now the same question doesn't come back to me every week, and nobody has to guess what I'd say.

Confusion usually comes from rules that only live in the founder's head. Written down, they let people decide quickly, and they let me check a decision against the rule instead of redoing it.

DM

Dane Maxwell — Founder, Paperless Pipeline

Define Decision Limits for Each Area

I delegate decisions that are reversible and frequent, and I keep the ones that are rare and hard to undo. Refunds, support replies, small product fixes and most hiring of contractors fall into the first group. Pricing, security and anything that changes what a brokerage owner sees on their compliance reports stay with me, because a mistake there affects trust across the whole customer base.

The scale makes that split necessary. Paperless Pipeline has 1,700+ active brokerages (https://www.paperlesspipeline.com/), and we are an independently run company, so if every decision came through me, the support queue would wait on my calendar. The people closest to customers make better calls on most day-to-day questions anyway, because they hear the detail I would only get second hand.

The practice that freed my time without creating confusion was writing down the decision limit next to each delegated area. A support lead knows they can credit an account up to a set amount, extend a trial, or escalate a bug without asking. Above that line, or anywhere a decision would set a precedent for other customers, it comes to me with a recommendation, not just the question. Writing the limit down matters more than the limit itself. Without it, people ask permission for things they could decide, and occasionally decide things they should have asked about. A written line removes both problems, and the monthly review of decisions taken under it tells me whether the line is in the right place.

ND

Neill David Watson — Founder, APMZEE

Require Proof From Specialized Partners

I delegate the decisions that a specialist can make better than me, and I keep oversight by asking for proof rather than reports. As APMZEE grew, manufacturing was the obvious example. I am not the right person to judge a production line, so that work sits with certified manufacturing partners, and what I keep is the right to check the result.

That check is built into how we sell. APMZEE provides a batch-matched Certificate of Analysis on request, normally returned within 48 hours. Because any customer can ask for the certificate for the batch they bought, the oversight is not a quarterly meeting with a supplier. It happens whenever someone wants evidence.

The practice that freed my time without confusion was agreeing in writing what each partner owns and what proof they hand back. The manufacturer owns production and testing, and the proof is the certificate. Customer service owns replies, and the proof is the response time. I stopped needing to be in every conversation because I could see whether the evidence arrived when it should.

JH

Joshua Harrison — Founder, Underground Towing & Salvage

Clarify Authority and Escalation Points

I judge a decision by its consequences and how easily it can be corrected. Routine coordination can sit with the person closest to the job. Decisions affecting safety, recovery methods or a commitment outside the agreed quote need a clear escalation point.

The delegation practice I recommend is agreeing on three things upfront: what the person can decide, what requires a call and what information that call should include. "Use your judgement" leaves too much open to interpretation.

In towing, someone should feel confident pausing a job when the vehicle's condition or access differs from the brief. Clear authority includes knowing when to stop.

ST

Steven Talia, CFP® — Co-Founder & CEO, MY PRO: TRUSTED PROS®

Protect Focus Time for Clearer Requests

I delegate execution once the objective is clear, and I keep oversight by making sure the team has a defined window to bring questions and updates so decisions do not get stuck in constant back and forth. The practice that has freed the most time without creating confusion is protecting the first 2.5 hours of the day from any non-urgent messages or meetings. From 7:00am to 9:30am, the team batches messages and holds non-urgent requests until after that window. It gives everyone uninterrupted time to move work forward, and it also forces clearer questions and better preparation for follow-ups. As a result, communication tends to be more focused later in the day because people engage with a plan instead of interrupting each other all morning.

ER

Emma Rusby — Director, Zenvy Beauty

Publish Policies That Empower Fast Decisions

I delegate decisions where the right answer is already written down, and I keep the ones where a wrong call would change what customers believe about Zenvy. Order problems, delivery questions and most refunds sit in the first group. Which brands we stock, how we describe a product for a particular curl type, and anything to do with the hair analyser stay with me. The practice that freed the most time was turning my own answers into a rule anyone can follow. Our FAQ tells customers that if their order arrives damaged or incorrect, they should contact us within 48 hours of delivery with photos, and we will arrange a replacement or refund (https://zenvy-beauty.com/pages/faqs). Once that was public, whoever handles the inbox could act on it straight away without checking with me, because the policy had already made the decision. Customers got faster answers, and I stopped being the bottleneck on a broken pump or a leaking bottle. Oversight comes from a weekly look at the exceptions rather than the routine cases. Anything outside the written rule, such as a claim after the 48-hour window or a customer who has had several problems, gets flagged to me with what the person handling it would do and why. Most of the time I agree, and over the months that list has shown me which rules needed rewriting. Delegation got easier when the boundary was something customers could read too, because nobody had to guess where my judgement started.

RA

Redha Alayesh — Founder, BMD

Fence Experiment Budgets and Review Winners

Delegate the decisions a number can check. Keep the ones only judgment can check until you have written the judgment down.

When I build marketing departments for clients, I sort decisions by two questions: is it reversible within a week, and is there a metric that shows within days whether it was right? Moving budget between ad sets inside a running campaign passes both tests, so the team owns it. Changing the offer, the positioning or the channel mix fails both, so it stays with the founder.

The delegation practice that frees the most time without confusion is a fenced experiment budget. I recommend setting aside roughly 5 to 10% of the marketing budget for tests, and the team decides everything inside that fence: which message, which audience, which landing page. The founder does not approve each test. The founder reviews results on a fixed day and decides only one thing: which winning test graduates into the core mix. Oversight sits at the graduation point, not at every step.

Everyone knows where their authority ends because the line is written as a number, not as a mood.

RW

Roo Wright — Founder, Signalto Limited

Document Context Before You Delegate

One of my developers now takes on bigger projects without me having to be across everything. He's worked with me for nearly ten years, so the trust was already there. What helped was getting the business context out of my head and into the project.

At SignalTo.ai, we document what the software needs to do, the business requirements and the rules it must follow. We use a planning framework around Claude Code that breaks work into phases, with separate AI agents handling planning, execution and verification. The developer directs those agents and judges their work, with code and security reviews built into the process. The plans and progress are saved, so oversight doesn't depend on me being in every conversation.

For me, that's the test for delegating a decision: does the person understand what we're trying to achieve and what their decision could affect? Knowing how to do the task is only part of it.

My advice is to document the reasons and boundaries before handing over responsibility. A capable person can make much better decisions when they know why you're doing something, rather than having to keep coming back to ask.

AF

Aviad Faruz — Owner, Elvis Loft & Karaoke

Set Standards for Authorized Model Selection

One decision I have delegated is which AI model to use for work I have already authorized. I run Elvis Loft & Karaoke, a private karaoke venue in Jerusalem, and use an AI assistant for project work.

My instruction is to choose the least expensive available model capable of meeting the task's quality requirements. Before dispatching an authorized subtask, the assistant must tell me the model and briefly explain why it fits. Small checks and difficult technical work can therefore receive different resources without asking me to make each selection.

The permission has a limit: choosing a model does not authorize extra work or additional agents. If a more capable model is needed, the explanation must identify a concrete quality or capability problem. I want to be able to understand the choice without managing every detail behind it.

That moves a recurring choice out of my approval queue. I have not measured hours saved. The practice I would carry over to delegating to a person is to name the decision they own, give them a usable standard, and agree on what needs to be reported before they act. A brief explanation of an exception is useful; a long report on every routine step would give me another job.

Aviad Faruz, Owner, Elvis Loft & Karaoke https://www.elvisloft.co.il/

LI

Luba Inz — Founder, Efficiency Sprint

Set Dollar Limits for Each Level

As a COO, at first there were decisions all the time, because I was putting out fires. Then it became about one decision a day. What changed it was decision limits per level, in dollars. The fourth level could make a mistake of up to $100, the third up to $500, and so on. I explained that everything you do can be translated into money.

Below the limit, people decide and log it. Above it, it goes up one level. Not some ghostly concepts. Numbers. Then a weekly one-on-one with your direct reports, with the same questions every time. Only discipline changes our habits.