What is systems delegation?

Systems delegation is a concept in personal epistemology: Tools, checklists, and automated processes are delegation targets.

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.

This concept is part of Phase 27 (Delegation Patterns) in the How to Think curriculum, which builds the epistemic infrastructure for delegation patterns.