You Can't Delegate Understanding

Execution delegates, understanding does not

The small problems a leader cannot see are the ones that grow, until, in Ryan Petersen's phrase, you end up "running around putting out forest fires instead of putting the fire out while it's tiny."¹ The habit that lights them is the one he says most managers get backwards: a whole function is handed to an executive, that org becomes a black box seen only through reports, and the ground truth good decisions require is forfeited.

Petersen credits Toby Lutke of Shopify with the sharpest version of the reframe, and says Brian Chesky arrived at the same discovery. The claim is that "micromanagement" and "attention to detail" are two names for one thing, separated only by whether the boss knows what they are talking about. As Petersen puts it, "micromanagement is only a bad thing if your boss is an idiot and doesn't know what he's talking about and is telling you to do the wrong thing. But if your boss is involved in your work, helping you, and knows what he's talking about, that's awesome."² The move is to relocate the fault: what people dislike about involvement is not the involvement but the incompetence, so the real failure mode is involvement without competence, or its inverse, delegation without understanding.

The black-box confession

Petersen describes his own version of the mistake. For years, by his account, he "managed the company through" executives and consumed each org's reports rather than seeing the work directly, which is precisely what let problems fester. His stated remedy is not to stop delegating but to keep understanding: skip-levels to the frontline and the customer "ten times more than I used to," and a norm that an executive who resents the founder talking to anyone in the company "is not going to be a good fit."¹ He compresses the discipline into a single line: "You can't delegate understanding. You've got to understand what they're doing, but empower people to go execute."

The affirmative practice he attaches to this is going to where the work is done and solving the problems found there, so that information keeps flowing. He describes the reciprocity directly: help the team solve their problem and they will tell you about problems the next time you come around, whereas a closed office door shuts the channel.³ This connects the principle to Chesky's account of founder-led companies, which Petersen reads as an epistemic claim rather than a claim about energy: presence matters because understanding cannot be handed off, not merely because intensity is contagious. It pairs with Super IC (Promote From Within), on the view that understanding can be grown internally but not bought in an outside senior hire.

The competence gate and the scale limit

Both the strength and the risk of the principle sit in what Petersen calls the competence question. "Micromanagement is fine if the boss is right" is only usable if a leader can tell when they are right, and Petersen himself warns elsewhere in the same interview about the damage a confidently wrong founder can do under this doctrine.¹ There is also a scale limit he acknowledges: understanding by skip-level costs the leader's time and does not scale linearly, which is why he stresses ruthless prioritization, looking at the few worst shipments rather than all of them. By his account the walk must be replicated by every leader as culture, since as CEO he reached only 19 of 147 countries in a year.^{3 2 3}