Delegation is usually framed as a straightforward time-management win: hand a task to someone else, and the hours it used to take are now free for something else. The framing isn't wrong exactly, but it's incomplete in a way that causes real disappointment when the promised time savings don't fully materialize — because delegation doesn't remove time from a manager's schedule so much as it converts one kind of time into a different, usually smaller, but real kind.
The time delegation actually costs the delegator
Effective delegation still requires explaining the task clearly, being available for questions especially early on, reviewing the output, and giving feedback — none of which is zero-cost, and all of which is easy to underestimate when a task is being delegated for the first time. For a genuinely new task, the upfront explanation and early oversight can, for a while, cost more of the delegator's time than simply doing the task would have — the payoff comes later, once the person receiving the task no longer needs the same level of support, not immediately upon handoff.
This is why delegation of a brand-new, one-off task rarely pays off in the short term, while delegation of a recurring task pays off increasingly over time as the upfront investment amortizes across many repetitions — a distinction that's easy to lose when a delegation decision is evaluated only against the very next instance of the task rather than the pattern over months. A related software-oriented reference is Monitask’s guide to accountability and responsibility at work.
Under-delegation and over-delegation, and how to tell them apart
Under-delegation shows up as a person doing tasks that someone else on the team could reasonably do, usually justified by 'it's faster if I just do it myself' — which is often true for a single instance and false as a repeated pattern, since the explaining cost is only paid once while the doing cost repeats every time. Over-delegation shows up differently: tasks handed off with too little context or too little early support, producing output that requires extensive rework — which can end up costing more total time than not delegating at all, while looking on paper like time was freed up.
- For a recurring task, calculate the break-even point roughly: how many repetitions until the upfront training time is paid back by the ongoing time saved.
- Delegating a one-off task rarely saves time in the short term — delegate one-off tasks for development or capacity reasons, not primarily for immediate time savings.
- Early, frequent check-ins on a newly delegated task cost less total time than a single late review that discovers the work went in the wrong direction.
- 'It's faster if I do it myself' is true for a single instance and often false as a repeated policy — the comparison that matters is cumulative, not per-instance.
The part of delegation that's about more than time
Purely time-based accounting misses a real dimension of delegation: capability-building. A task delegated even at a short-term time cost can be a long-term investment in someone else's skills and in the team's overall resilience against any single person being a bottleneck — a value that doesn't show up in a simple hours-saved calculation but is often the more important reason to delegate a given task in the first place.
Treating delegation as a time-management tactic with its own real costs, rather than as a simple, free way to reclaim hours, produces more realistic expectations about when it pays off — and prevents the common disappointment of delegating a task and feeling, a week later, no less busy than before. For additional background on this subject, consult the delegation overview.