A founder of a 22-person services firm at her Sunday evening review of the week. The operations director handled five customer escalations during the week. The founder reviews the transcripts of four of them and thinks: “I would have handled this differently in three places, and the customer would have left happier in two cases.“ She decides to take customer escalations back next week.
She does not run the second part of the math. The five escalations cost the operations director a total of about six hours. The founder, who would have handled them slightly better, would also have spent six hours on them, while skipping the strategic planning session she had moved them out of her diary to make room for. She has just chosen the lower-leverage outcome and feels good about it.
Why does the comparison feel like good judgement?
The comparison feels rigorous. The founder has reviewed the actual work. They have identified specific places where they would have done it differently. They have a defensible quality argument. And the conclusion (I should keep doing this) feels protective of the customer, of the firm’s standards, and of the founder’s craftsmanship. It does not feel like avoidance.
The trap is that the comparison is partial. The founder is comparing the role holder’s actual work against their own hypothetical work. They are not comparing the role holder’s actual work against the actual work the founder would not have done if they had taken back this category. The full comparison includes the strategic planning session that did not happen, the customer-development call that got postponed, the senior hire interview that ran late. The partial comparison protects the founder’s craft. The full comparison would protect the firm.
The 70 percent rule, attributed and explained
The practitioner heuristic: if someone can do the job at least 70 percent as well as you can, it should be delegated. The rule reads as a slogan but operates as a math claim. The 30 percent gap in quality is the cost; the 100 percent recovery of founder time on that work is the benefit. Founder time recovered goes on work that has no 70 percent substitute.
The math typically favours delegation strongly even when the quality gap feels uncomfortable. The rule is calibrated to ordinary operational work, not to the small set of categories that genuinely need the founder. The 70 percent threshold is also a starting point, not a ceiling. After three to six months in role, most role holders move from 70 to 85 percent quality as they learn the specific shape of the work. The first-review snapshot captures the starting position, not the long-run quality.
The hidden math founders skip
When the role holder does the work at 70 percent quality, the founder reads it as “30 percent quality lost.“ The founder rarely asks “100 percent of what was freed, what did I do with it?“ If the freed time went into strategy, customer relationships, or market expansion (work only the founder can do), the leverage gained is huge.
If the freed time went into other operational work the founder also should not be doing, the math collapses; the issue is then a separate one about how the founder is using freed time, not about whether the delegation was right. This is why the post-delegation calendar discipline matters. Delegation moves the founder’s plate from one set of work to another, rather than simply emptying it. If the freed time fills with another set of operational distractions, the founder concludes (incorrectly) that the delegation did not work. The delegation worked; the calendar discipline did not. Two separate problems get diagnosed as one.
Work that has no 70 percent substitute
Strategy. Major customer relationships at the founder level. Senior hiring decisions. Industry visibility and thought leadership. Investor or stakeholder relationships at the principal level. These are the areas where 70 percent quality from someone else is genuinely a quality drop because the founder’s specific role, history, and authority are part of the deliverable.
A senior hire who feels they have been interviewed by the operations director rather than the founder gets a different signal about the role’s importance. A key customer who has the founder’s mobile number reads the relationship differently than one who has the account manager’s. These categories are narrow. Most owner-led firms have five to ten categories where the founder’s specific involvement is the work; the other 30 to 40 categories are operational and delegable. The trap is conflating the two. Founders who treat operational work as if it requires their specific authority end up doing work that any competent role holder could do at 70 percent, while the genuinely founder-only work (strategy, principal relationships) does not get done at all.
Where 70 percent quality is acceptable
Operational decisions inside defined boundaries. Customer escalations within defined service standards. Hiring decisions within budget and within a defined team. Vendor relationship management. Financial reporting and review work. Process improvement decisions. In all of these, 70 percent of the founder’s quality is not a meaningful business risk; the work happens, the standard holds, the lights stay on.
The team’s 70 percent will produce some outcomes the founder would have handled differently. The customer escalation that ended at “we agreed on a partial credit“ rather than “we agreed on a partial credit plus a discounted upgrade for next year.“ The hire who was selected for technical fit when the founder might have weighted cultural fit higher. The vendor relationship that ran on quarterly reviews rather than monthly check-ins. None of these is a fatal error. All are recoverable. The founder retains the right to refine the boundaries and feedback into the role holder’s process for next time, not to redo the work.
The honest re-comparison after months
After two or three months of delegation, the founder reviews the role holder’s actual quality. Often what the founder remembers as 70 percent is closer to 85 to 90 percent once they have stopped over-comparing. The first reviews are usually the harshest. The discount the founder applies to others' work is itself part of the bias.
Founders who run the comparison again at month three or six are often surprised to find the work is genuinely closer to founder quality than the day-30 review suggested. The shift here is the founder’s frame loosening, although the team improving over time is also part of it. The day-30 review measures against the founder’s hypothetical perfect output. The day-90 review measures against actual operational performance and the founder’s actual track record on the same work. The first measure is biased; the second is honest. Founders who only run the day-30 review tend to take work back; founders who run both find the day-90 picture changes the call.
The reverse failure
The founder who refuses to delegate because the role holder gets the work to “only 70 percent“ is implicitly claiming that everything the founder does is already at 100 percent. This is rarely true. The founder is also doing the work at perhaps 75 to 90 percent of their best, because they are doing too many things.
Delegating a task that the role holder will do at 70 percent often improves the quality of everything else the founder does, because the founder is no longer cognitively split. A founder doing 12 things at 80 percent quality is producing less total firm value than a founder doing 5 things at 95 percent and a team doing 7 things at 75 percent. The math at firm level is the leverage gained, not the quality gap on any individual task. Founders who hold the leverage frame consistently delegate more, hold quality better on the work they keep, and produce a firm with both higher founder-level quality and higher team-level capability.
What to do this week
Pull the last five operational tasks you took back from a team member because “I would have done it better.“ For each one, write down the founder-only work that did not happen because the task came back to you. Be honest.
The five hours on customer escalations were five hours not on the strategic planning session, the customer-development call, the senior hire interview, or the industry positioning conversation. The full ledger usually shows the leverage went the wrong way. Then pick one task to delegate back this week. Use the explicit handover language. Resist the urge to take it back at the first review. At the day-90 review, run the comparison against your actual track record on the same work, not your hypothetical perfect performance. The honest picture usually surprises the founder.
If you would like a second pair of eyes on which work genuinely needs you and which is a leverage trap, book a conversation.
