Delegate to systems, not just people

The idea

Tools, checklists, and automated processes are delegation targets.

When your workload exceeds your capacity, the default question is: "Who can I hand this to?" That question has a built-in assumption — that delegation means finding another human being to absorb the overflow. Sometimes that is the right answer. But most of the time, it is the wrong question entirely.

The right question is: "What can handle this?"

An example

A startup founder handles customer onboarding personally for the first fifty clients. Every email is hand-written. Every walkthrough is live. The quality is excellent — but the founder is now spending four hours a day on onboarding and zero hours on product development. The typical advice is 'hire someone.' So the founder hires an onboarding specialist. Quality drops to 70% of what it was, because the new hire lacks the founder's product intuition. Now the founder spends two hours a day reviewing the specialist's work and correcting mistakes — trading four hours of doing for two hours of supervising, a net gain but not a transformation. The alternative: the founder builds an onboarding system. A sequenced email series triggered by signup events. An interactive product tour embedded in the application. A knowledge base with searchable answers to every question the founder has answered more than twice. A feedback form that routes issues to the right team automatically. The system handles 90% of onboarding at consistent quality, 24 hours a day, for the 51st client and the 5,000th client identically. The founder's onboarding time drops to thirty minutes a week reviewing edge cases. The delegation target was never a person. It was a process.

Where it goes wrong

Treating systems delegation as an either/or choice against people delegation, rather than recognizing the hierarchy. The subtle error is not that you refuse to delegate to systems — most people intellectually accept the idea. The error is that when a task needs delegating, your first instinct is still to look for a person. You think 'who can handle this?' before you think 'what process can handle this?' This ordering bias means you systematically under-invest in systems and over-depend on individuals, creating fragile delegation chains that break when a person is sick, quits, or simply has a bad day. The fix is to invert the question sequence: first ask 'can a system handle this?', then 'can a system handle 80% of this with a person handling the remaining 20%?', and only then 'does this require full human judgment?'

Make it stick

You now have a framework for choosing between system and human delegation targets. But in practice, most delegation decisions are not this clean. They involve gray areas — tasks that seem to require human judgment but might not, or tasks that seem automatable but have hidden complexity.