Delegation: Giving Work Its Rightful Owner

Everyone Says They Delegate

Lesson 7.3 ended at a constraint that reframes the whole job: a mayor appoints commissioners but cannot appoint the workforce, because New York State's Constitution requires civil service appointment by merit and fitness ascertained by competitive examination. You inherit an organization rather than assembling one. The question that leaves you with is the one this lesson answers. If you cannot choose most of the people, and you cannot do most of the work, what exactly is it that you do?

Here is the answer in a sentence, and then we will spend the lesson earning it. You decide who owns what, and then you leave it owned.

Almost every leader believes he delegates. Ask and you will hear about the things he has handed off, and the list will be real. Then watch a week of his calendar and you will usually find something else: he has distributed tasks while keeping the outcome, the authority, and the information. His people are busy. They are not responsible for anything, because responsibility is the thing he did not transfer. And he is exhausted, and he thinks the exhaustion proves his commitment, when it mostly proves his design.

So let me name the framework. Call it the Handoff Standard, and it has three transfers.

The first transfer is the outcome. Not the task — the result. There is an enormous difference between asking someone to write the report on shelter capacity and making someone responsible for shelter capacity. The first assigns motion. The second assigns a problem, and a person who owns a problem thinks about it in the shower. Task delegation produces compliance and terminates when the task is done, whether or not anything improved. Outcome delegation produces ownership and terminates when the outcome changes.

The second transfer is the authority to pursue it. This is the one leaders withhold most often, usually without noticing, and it is the cruelest omission in management. Give a person an outcome without the authority to affect it and you have created responsibility without power — the most demoralizing arrangement in organizational life. They will be measured on something they cannot move. They will come back to you for every decision that actually matters, which you will experience as their lack of initiative. And your best people, who are the ones most sensitive to this, will leave first.

The third transfer is the information the outcome requires. Leaders hoard information the way they hoard authority, often for defensible reasons — it is sensitive, it is unsettled, it is political. But a person cannot own an outcome while reasoning from a partial picture, and when they decide badly on incomplete information you will conclude, wrongly, that their judgment is poor. Their judgment was fine. Their inputs were rationed.

And then the thing you do not transfer, which is the whole moral weight of the framework. You keep the accountability. Not the decision, not the execution, not the credit — the accountability. When something you delegated fails, the failure is a delegation you made: to that person, at that scale, with that support, with that threshold for escalation. Every element of that was yours. A leader who delegates the outcome and then delegates the blame has not built a system. He has built an alibi, and everyone under him can see it from the first week.

Jethro's Architecture and the Sentence Everyone Skips

Exodus 18 is the oldest management text most leaders have read and the one they most consistently misread, because they remember the org chart and forget the rule that makes it work.

The setup: Jethro, Moses' father-in-law, arrives and watches him judge the people from morning to evening while everyone stands around waiting. In verses 17 and 18 he says, NASB 1995: 'The thing that you are doing is not good. You will surely wear out, both yourself and these people who are with you, for the task is too heavy for you; you cannot do it alone.'

Notice who gets worn out. Both yourself and these people who are with you. Jethro does not say Moses will burn out, which is how this passage is usually preached. He says the bottleneck damages the people waiting in line as much as the man in the chair. That is the executive claim, and it is the one that should move you if concern for your own stamina has not. Centralization is not primarily a wellness problem. It is a service failure, distributed across everyone whose matter is sitting in a queue behind a person who cannot get to it.

Verse 21 gives the selection criteria we examined in Lesson 7.2 — able men who fear God, men of truth, those who hate dishonest gain, set over thousands, hundreds, fifties and tens. That is the famous part, the pyramid, and it is where most treatments stop.

Verse 22 is the sentence everyone skips, and it is the operative one: 'Let them judge the people at all times; and let it be that every major dispute they will bring to you, but every minor dispute they themselves will judge. So it will be easier for you, and they will bear the burden with you.'

That is an escalation rule, and without it the structure is decorative. Every delegation that fails in practice fails at this exact point. Either no threshold was stated, so everything flows back up on the theory that the leader would want to know — and he did want to know, which is precisely how he drowns. Or a threshold was stated so loosely that genuinely consequential matters get settled three levels down by someone who does not have the standing to settle them, and the leader learns about it from a reporter. The Hebrew phrase in verse 22 for the matters that come up is kol-haddavar haggadol, every great matter, against haddavar haqqaton, the small matter. The text does not define the boundary for you, and I am not going to pretend it does. What it establishes is that the boundary must exist and must be named in advance.

So name yours. Write the three or four conditions under which something must come to you — an irreversible commitment above a stated threshold, anything that changes a public promise, anything with legal exposure, anything that would surprise you to read about. Then honor the other side of the rule, which is harder: when something below the line reaches you anyway, send it back. Every time you decide a small matter that was properly someone else's, you have retrained the whole system in one gesture, and no memo will undo it.

Verse 23 gives the outcome Jethro is aiming at: 'then you will be able to endure, and all these people also will go to their place in peace.' Endurance for the leader, resolution for the people. Both. And notice what verse 24 records — 'So Moses listened to his father-in-law and did all that he had said.' The most authoritative leader in the narrative took organizational counsel from a Midianite priest with no standing in Israel, and the text presents it as wisdom rather than weakness.

Seven Men With Greek Names

Acts 6 is the other delegation text, and it is more sophisticated than Exodus 18 because the problem it solves is not volume. It is legitimacy.

The situation, in verse 1: as the number of disciples increased, the Hellenistic Jews complained against the native Hebrews because their widows were being overlooked in the daily serving of food. Read that carefully. This is not an efficiency problem. It is an equity complaint from a minority group inside the community, alleging that a distribution system was failing them specifically.

The twelve respond in verse 2: 'It is not desirable for us to neglect the word of God in order to serve tables.' That sentence gets quoted as though it were about status, and it is not — it is a statement about the highest and best use of a specific person's time, which is exactly the judgment every executive has to make and most make badly. Then verse 3: 'But select from among you, brethren, seven men of good reputation, full of the Spirit and of wisdom, whom we may put in charge of this task.' And verse 4: 'But we will devote ourselves to prayer and to the ministry of the word.'

Three things in that structure deserve your attention. First, the delegating body did not select the people; the community did — 'select from among you.' The apostles set the criteria and confirmed the appointment, but the choosing belonged to the group whose need was at issue. Second, the criteria are character and wisdom, not administrative experience, which is consistent with everything Lesson 7.3 said about trustworthiness being the harder half of selection. Third, the twelve named what they were protecting. They did not simply offload an annoyance; they stated the thing that would suffer if they kept doing this, which is the only honest justification for any delegation.

Now the detail that makes this passage remarkable, and it is a detail of the plain text rather than a clever reading. Verse 5 lists the seven: Stephen, Philip, Prochorus, Nicanor, Timon, Parmenas, and Nicolas, a proselyte of Antioch. Every one of those is a Greek name. The complaint came from the Hellenistic Jews, and the men appointed to fix it appear, on the evidence of their names, to have come from the complaining group. Commentators have long noted this and it is an inference from onomastics rather than an explicit statement by Luke, so hold it as a strong reading rather than a certainty. But if it is right, the apostles did not merely delegate the task. They handed the authority over the disputed distribution to the people alleging they had been shortchanged.

That is harder than it sounds. The instinctive response to a fairness complaint is to investigate it yourself, because your own oversight feels like the strongest guarantee of impartiality. The text describes the opposite move: give the aggrieved party the authority, and the accountability with it. It is riskier and far more legitimate, and legitimacy is the actual currency in a fairness dispute.

And note verse 7: 'The word of God kept on spreading; and the number of the disciples continued to increase greatly in Jerusalem.' The narrative treats the delegation as the reason growth continued. One more thing worth noticing about scope creep in the good direction — two of the seven appointed to distribute food, Stephen and Philip, are the ones the following chapters show preaching and evangelizing. People given real ownership frequently grow past the box you put them in. That is not a failure of the delegation. It is the return on it.

Subsidiarity, and What the Research Will and Will Not Support

There is a name for the principle underneath both texts, and you will meet it again in Module 8 as a constitutional idea. Here I want you to have it as a management principle first, because it is far easier to understand in an organization than in a federal system.

Subsidiarity holds that a decision belongs at the lowest level competent to make it, and that moving it upward without necessity is a wrong done to the level that lost it. The classic formulation is in Pius XI's 1931 encyclical Quadragesimo Anno, which argues at paragraph 79 that it is an injustice and a grave evil to assign to a greater and higher association what lesser and subordinate organizations can do. Whatever you make of the source, notice the moral framing: taking a decision from a competent lower level is not merely inefficient, it is an injury, because it strips the capacity and dignity of the people who should have made it.

The word competent is doing all the work and I will not let it slide. Subsidiarity is not localism for its own sake, and it does not say the lowest level should decide. It says the lowest competent level should. Determining competence is a judgment you cannot avoid, and a leader who invokes subsidiarity to justify pushing a decision to people who cannot carry it has not delegated. He has abandoned.

The strongest secular argument for the principle is informational, and Friedrich Hayek made it in the American Economic Review in 1945 in The Use of Knowledge in Society. His claim is that the knowledge relevant to most decisions is not scientific knowledge that can be centralized but knowledge of particular circumstances of time and place, dispersed among the people on the spot and largely impossible to transmit upward without destroying it. He was arguing about economic planning. The organizational implication is exact: when you pull a decision up three levels, you are not adding judgment to it, you are subtracting information from it, and the leader making the decision has more authority and less to go on.

Now the research, described conservatively, because this is a topic where popular management writing makes claims the literature does not support.

On span of control: the classical rules are older than their evidence. Graicunas in 1933 computed the combinatorial explosion of relationships as subordinates increase, and Urwick popularized a rule of five or six. Those are analytical arguments, not empirical findings, and modern evidence does not support a universal optimal span; workable span depends on task interdependence, standardization, and how much judgment the work requires. Rajan and Wulf, using panel data on corporate hierarchies in the Review of Economics and Statistics in 2006, documented firms flattening over the period they studied — CEO spans widened, layers were removed — which is at minimum evidence that the narrow-span rule was not a law of nature.

On autonomy: this is the best-supported piece. Hackman and Oldham's job characteristics model, published in 1976, put autonomy among the core dimensions that shape experienced responsibility and, through it, motivation and satisfaction. Decades of subsequent work-design research support a genuine but moderate relationship between autonomy and outcomes, stronger for satisfaction than for raw performance. That is the honest size of the effect.

On micromanagement: here I am going to disappoint you deliberately. Micromanagement is a folk category, not a well-operationalized research construct, and the confident statistics you see quoted about what it costs organizations generally do not trace back to controlled research. What can be said responsibly is this: the evidence on autonomy points one direction, the evidence on close monitoring suggests that its effects depend heavily on whether people read it as developmental or punitive, and the informational argument from Hayek is strong on its own terms. That is a real case. It is not a quantified one, and a leader who cites a fabricated percentage in a room with an analyst in it has damaged something more valuable than his point.

The Desk, and the Difference Between Delegation and Abdication

So bring it to the mayor's desk, which is where this gets concrete.

What must a mayor decide personally? A short list, and it should stay short. Who holds each agency, and who leaves. The budget's priorities, since the budget is the only document where every stated commitment gets priced against every other. The decisions with irreversible moral weight — the ones where someone is harmed whichever way you choose. The public posture in a crisis, because that cannot be delegated by its nature. And the choice of what the administration will be about, which no one else can make for you.

What must never reach his desk? Anything a commissioner was appointed to decide. Anything where his involvement adds authority but no information, which is the honest description of most escalations. Anything he would decide from a briefing that a competent official would decide from the facts. And every procurement, permit, and personnel matter where a mayor's attention creates the appearance of a thumb on the scale — this last one matters enormously in a city with a Department of Investigation and a Conflicts of Interest Board, because in public life the appearance is part of the substance.

Now the failure at the other pole, and New York supplies both. Rudolph Giuliani ran a highly centralized City Hall, and the most consequential artifact of that instinct was the siting of the city's emergency command center on the twenty-third floor of 7 World Trade Center — a decision that was his, that was criticized at the time by people who preferred a location away from a known terrorist target, and whose consequence is recorded in the 9/11 Commission Report: on the morning of September 11, 2001, the Office of Emergency Management's headquarters had to be evacuated, leaving the city without its designated command post. The centralizing instinct is not a personality quirk. It builds single points of failure, and those are discovered on the day you needed them least.

And the opposite failure, which is abdication wearing delegation's clothes. In November 2015 the Department of Citywide Administrative Services accepted a payment of $16.15 million to lift two deed restrictions limiting a Lower East Side property, Rivington House, to use as a nonprofit health care facility. Months later the property was sold to condominium developers for $116 million. The Department of Investigation's report of July 14, 2016 found that the actions and inactions of officials across DCAS, the Mayor's Office of Contract Services, the Law Department, and the Mayor's Office facilitated the outcome, and that the city's deed-modification procedure lacked safeguards to ensure such removals served the city's interest; the Comptroller issued his own investigative report on the transaction the same year. The mayor said he had not been aware.

Take him at his word, because that is the lesson. This is not a story about a decision made badly at the top. It is a story about an outcome that no one owned. Multiple offices touched the transaction. Not one of them held the result. That is the signature of abdication, and it is why the third transfer in the Handoff Standard is not optional and why the thing you keep is accountability. The test is not applied afterward, when everyone is looking for the person who signed. Ask it before: if this goes wrong, whose name is on it, and does that person know it is on it? If you cannot answer both halves in one sentence, you have not delegated. You have merely stopped paying attention, and the two feel identical right up until the report comes out.

One last word, and it is the founder's rule rather than the framework's. Doing this well will cost you something personally. Real delegation means watching someone do a thing less well than you would have done it, on purpose, because they will only own it if you let them carry it. It means taking the hit publicly for a decision you did not make and would not have made. It means putting yourself on the back burner so that someone else can grow into a capability the organization will still have after you are gone. That is not a management technique. That is the definition from Lesson 7.1 arriving at your calendar, and Lesson 7.5 will take it further, because the point of giving work its rightful owner was never your bandwidth. It was their formation.