01 / Distinction
Why does delegated work still return to the founder?
A founder asks someone to prepare a supplier shortlist. The person gathers quotes, compares quality and sends back a spreadsheet. Nothing moves until the founder chooses. The research was delegated; the decision was not. That can be correct when a contract crosses a material threshold. It becomes expensive when the founder must choose the paper stock, meeting time and delivery route as well.
List the last ten decisions that returned to you. For each, write the person who did the work, the person who could choose, and what would have happened if no one replied for two days. This short audit exposes whether the bottleneck is missing information, unclear authority or a genuine reserved decision. Those problems need different fixes.
| Assignment | Who may choose? | Founder involvement |
|---|---|---|
| Prepare three supplier options | Founder | Choose after receiving a recommendation |
| Select within an approved specification and budget | Named operator | Review the result at the next check-in |
| Change equity, debt or legal entity | Founders or board as agreed | Approve before commitment |
02 / The mandate
What belongs in a useful delegation mandate?
Write a one-page mandate before assigning a recurring decision. Begin with the outcome: for example, keep approved products in stock without exceeding the cash limit. Name one owner, the information they can use, the spending ceiling, the quality and customer constraints, and the cases that must be escalated. End with the date on which the mandate will be reviewed. A job title alone does not supply any of these boundaries.
Make authority match accountability. If the operator is accountable for delivery time but cannot change the carrier or resolve a customer exception, the mandate is incomplete. Ask the operator to restate the boundary in their own words and decide one realistic example together. That conversation catches ambiguity before a customer or supplier pays for it.
- Outcome and one named decision owner
- Choices the owner can make without asking
- Budget, quality, legal and reputation limits
- Escalation trigger and response time
- Date, evidence and person for review
03 / The boundary
Which decisions should remain with the founder?
Keep decisions that change the company's purpose, ownership, major financial exposure or legal commitments within the governance process agreed by the company. For the rest, separate choices that are easy to reverse from choices that are costly to unwind. A pricing page experiment may be reversible; signing an exclusive, multi-year supply contract may not be. The test is the cost of reversal, not whether the founder has an opinion.
Create a reserved-matters list with specific thresholds. 'Important decisions' is not a threshold. 'Any new debt, any change to share ownership, or spending above the approved monthly cap' can be applied. Revisit the list when cash position, team capability or regulation changes. Do not treat a borrowed framework as a substitute for legal or board requirements.
04 / Review without control
How do you keep visibility without taking the decision back?
Ask the owner to record the choice, options considered, evidence, expected result and review date. During the review, discuss whether the decision followed the mandate and what the result taught the team. Do not quietly re-approve every choice after the fact. If the mandate was wrong, change the boundary explicitly for the next decision.
Start with one narrow domain for two weeks, such as routine vendor selection below a defined limit. Count requests for founder approval, time spent waiting, and decisions reopened after review. If waiting falls but errors rise, tighten the specification or add coaching. If both improve, extend the mandate. This is an operating experiment, not a claim about any company's performance.