What is non-delegable responsibilities?

Non-delegable responsibilities is a concept in personal epistemology: Some decisions and responsibilities must remain with you — knowing which ones is a meta-skill.

Example: You are leading a product team. You delegate the technical architecture to your lead engineer, the design system to your design lead, and the go-to-market timeline to your marketing partner. All reasonable. Then a customer-facing crisis emerges: a data breach that affects trust, requires a public response, and forces a strategic decision about how the company will handle user privacy going forward. You delegate the crisis response to your communications team, the technical fix to engineering, and the privacy policy revision to legal. Each team executes competently in isolation. But nobody made the integrating decision — the one that says what this company stands for, what trade-offs it will accept, and what it will tell customers about its values. Six months later, the technical fix, the public statement, and the revised policy all point in slightly different directions, because the identity-defining decision at the center was never made by a person with the authority and context to make it. You delegated the tasks correctly. You delegated the decision you should have kept.

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