A pen, a cup, a block and a coil of cord on a table, with a rectangle of window light falling only on the pen.

3of 4

Delegating even when you’re the best at it

Weigh the value of delegating against what you could achieve with that time yourself. The decision is not just about who has the skills, but where your time will have the greatest impact.

Lead & Operate
Founder leverage

Adapted by the EWOR Team from Daniel Dippold’s article (opens in a new tab)3 min read

Just because you’re the best, doesn’t mean you should

Even if a founder is the strongest coder, salesperson and writer in the room, doing all three could reduce total team output. Daniel Dippold, CEO and co-founder of EWOR, uses comparative advantage to explain why: the question is not who performs a task best in isolation, but where each hour creates the most value across the business.

This comes down to opportunity cost: when you spend an hour on a task someone else could handle well enough, what are you giving up the chance to do instead? The best use of your time depends on what else you could achieve with it. Daniel illustrates this principle with a fictional founder, so the numerical allocation is illustrative rather than measured company evidence. If you build a similar model, check that the hours and task requirements support your conclusions.

Separate absolute skill from relative advantage

For each recurring task, ask two questions:

  1. Absolute skill: Who can deliver the strongest result on this task today?
  2. Relative advantage: Compared with their other available work, where does this person create the greatest value?

The answers may differ. A founder might be slightly better at implementation than a teammate, for example, but far better placed to make a financing decision, recruit a key leader, resolve a major trade-off or build an important external relationship. In that case, delegating implementation could create more value for the company overall.

That does not mean every task labelled "strategy" belongs to the founder. Keep the work that genuinely depends on the founder's context, authority, relationships or distinctive strengths, and delegate the rest where others can deliver effectively.

Identify what really needs you

Create a task list and mark work:

  • Only the founder can authorise or credibly perform;
  • Where the founder has a material edge but another person can execute with guidance;
  • Where a teammate can own the result;
  • That should stop rather than be delegated.

Estimate the consequence of delay in each category. Though, a small quality difference on a repeatable task may matter less than a founder bottleneck on an irreversible or time-sensitive decision.

Then set a quality floor for delegated work. Comparative advantage is not an argument for accepting outcomes that create unacceptable customer, security, legal or operational risk.

Delegate an outcome, not an abandoned task

A sound handoff contains:

  • The result and why it matters;
  • Boundaries and decision rights;
  • Relevant context and examples;
  • The quality and safety floor;
  • The check-in or evidence needed;
  • The conditions for escalation.

Delegation without context creates rework. Delegation without authority leaves the founder as a hidden approval queue. Delegation without a feedback loop makes both sides guess whether the handoff worked.

You can remain accountable without rewriting every deliverable. Clear interfaces, proportionate review and outcome measures can preserve visibility while allowing another person to own execution.

To identify where your time is being misallocated, review a few substantial tasks and ask:

  • Could someone else have delivered an acceptable outcome?
  • What founder-specific work did I give up to do this myself?
  • Was my involvement needed for direction, execution, quality control or simply out of habit?
  • What context, capability or system would make delegation safe next time?

Pay particular attention to tasks you repeatedly take back because doing them yourself feels faster. That may be the right call once, but as a recurring pattern, it can limit the team's output and keep you from work where your time would have a greater impact.

Know the boundaries

Some work remains with the founder because of governance, fiduciary responsibility, material risk or unique relationships. Some early functional work is valuable because it builds enough understanding to hire and audit well. Comparative advantage does not erase either point.

It changes the default question. Instead of asking, “Who can do this task best?”, ask, “What allocation lets the whole team create the strongest result, given the work only each person can do?”

Once you know what a handover would free you to do, consider which work gives you energy and where your edge matters most. You may need help with execution while retaining ownership—or someone who can take ownership too.

Source: EWOR article by Daniel Dippold (opens in a new tab)

No comments yet.

Be the first to comment on this signal.

Get the next signal before everyone else.

Frameworks and contrarian theses for outlier founders, straight to your inbox. No fluff, no recycled advice, weekly.

The EWOR Signals newsletter

Continue learning

Related modules