How much of my time does delegating really give back?
Count what leaves your week and what returns to it. Hand over four hours of admin, keep one hour to review it and spend two hours teaching in the first week: you get one hour back at first and three hours later. Your collaborator's hours still count, so total work can rise.
Handing over four hours of work does not necessarily free four hours immediately. You may still review it, teach it or handle exceptions. The work also moves into someone else's week.
Time moved is different from time recovered
Count the work that remains with the founder as well as the task that moves. In this example, four hours leave but one review hour returns. The recurring difference is three hours. Two additional teaching hours reduce the first week's difference to one.
The collaborator also needs room for the task and learning. HSE's workload guidance considers task timing, competence and the whole team's allocation. It does not prescribe a founder's ideal week or promise a gain from delegation.
The first week includes teaching; later weeks still include review
A founder's fully logged 40-hour week contains 20 hours delivering, eight selling and serving customers, eight on administration and four on improvement and planning. A collaborator has the access and capacity to take four of the administration hours.
The founder keeps four administration hours and adds one hour to review the transferred work. With the other 32 hours unchanged, recurring commitments become 37 hours. That could release three hours from the original 40.
In the first week, the founder also spends two hours teaching the task. Commitments are therefore 39 hours, leaving one hour. The collaborator spends four hours doing the task plus two learning alongside the founder: six first-week hours and four recurring hours.
Together they spend 45 hours in the first week and 41 recurring hours on the counted work. The founder has recovered time, but total labour has increased. The lesson is to count the whole transfer and decide whether its cost, quality and use of the founder's time justify it. These are assumptions to illustrate the calculation, not promised savings.
- This fictional comparison accounts for the founder's complete original 40-hour week. Other commitments remain unchanged.
- The collaborator confirms capacity for six first-week hours and four recurring hours. The founder's review takes one hour, teaching takes two and no additional correction time is assumed.
- Combined hours count both people's time, including both participants in teaching. No claim about wages, equal skill, improved quality or increased profit follows.
| Time category | Before | First handover week | Recurring arrangement |
|---|---|---|---|
| Founder: delivery, sales/service, improvement | 32 h | 32 h | 32 h |
| Founder: remaining administration | 8 h | 4 h | 4 h |
| Founder: review of transferred task | 0 h | 1 h | 1 h |
| Founder: teaching | 0 h | 2 h | 0 h |
| Founder: total committed | 40 h | 39 h | 37 h |
| Founder: time released from original week | 0 h | 1 h | 3 h |
| Collaborator: task plus learning | 0 h | 6 h | 4 h |
| Combined labour on counted work | 40 h | 45 h | 41 h |
Try it with your own numbers
All the hours in your logged week.
The weekly hours of the task that moves to someone else.
Each week, including after the first.
Time you spend showing the task.
Teaching time counts for both people.
Your result
Fill in every field to see the result.
Your numbers stay in this browser. Nothing you type is sent or saved.
Customer work and spare capacity answer different questions
Before the change, this founder spends 28 of 40 logged hours delivering, selling and serving customers: 70%. That describes the supplied categories and denominator. It does not prove that 70% is desirable, that the remaining time is wasted or that there is room for a particular improvement.
The four improvement hours are already committed work, not an empty slot. The newly released hour in the first week is separate. What the founder chooses to do with it, including leaving it free, determines its practical value.
A solo founder can examine decisions without inventing a team
A log of decisions is not a log of every task. A solo designer might spend time repeatedly deciding how to handle similar enquiries, while delivery work takes much longer. A bounded default, a planned review point or removing an unnecessary choice may change the decision time without transferring delivery to another person.
Check the same activity before and after, including exceptions and any new monitoring. Time-sensitive commitments and safety issues may need action before the next review point. Batching every question regardless of consequence is not the lesson.
Common misconceptions
- Four delegated hours mean four hours immediately free.
- Here review and teaching take three founder hours in the first week, leaving a net difference of one. Different actual effort changes that result.
- Any remaining review means delegation failed.
- The example deliberately retains a review. The relevant question is whether the arrangement produces acceptable work with a useful allocation of time.
- Founder time recovered is total business time saved.
- The collaborator's work and learning still count. Combined labour rises in this example even though the founder's commitments fall.
Follow one task through a small transfer
Record what leaves your week, what review and teaching remain, and what the recipient can actually carry. Compare the first week with the recurring arrangement using observed hours and work quality. Check what the returned time enables before calling the transfer worthwhile. If you work alone, apply the same accounting to one repeated decision and its exceptions.
Sources
- HSE: Workload (opens in a new tab)Examining tasks, timing, competence and redistribution across the whole team. The industrial guidance does not establish an ideal founder schedule or the hypothetical numerical outcomes.