What to never delegate

The idea

Some decisions and responsibilities must remain with you — knowing which ones is a meta-skill.

That heuristic unlocks leverage. It frees your attention for higher-value work. It is one of the most powerful operating principles in personal epistemology.

An 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.

Where it goes wrong

Treating the non-delegable list as static. The most common failure is building a fixed inventory of things you never delegate and then applying it rigidly regardless of context. What must remain with you changes as your role changes, as your competence develops, and as the stakes of specific decisions shift. The person who must personally handle every client relationship at five clients cannot do the same at fifty — but the person who delegates all client relationships at fifty may have delegated the one relationship that defines the company's future. The meta-skill is not maintaining a permanent list. It is continuously re-evaluating which decisions carry identity-level, irreversibility-level, or context-dependency-level stakes — and keeping only those.

Make it stick

Take the decision you identified in the exercise — the one that scored two or more on the non-delegable filter — and write a delegation specification for the parts of that decision that can be delegated. Separate the decision into its non-delegable core (the judgment, the value trade-off, the contextual interpretation) and its delegable execution (the research, the options analysis, the implementation).