Background and Context
Fogleman became chief of staff in October 1994, in the wake of an air campaign that had made his service look, briefly, invincible. Desert Storm was the most lopsided major air war ever fought, and the images that survived it were machines: the nose-camera footage, the stealth fighter, the missile through the window. What followed was subtraction. The Air Force of the mid-1990s was shedding a large fraction of its people and its aircraft, closing bases, and asking whoever remained to hold a deployment tempo that had gone up rather than down — the no-fly zones over Iraq, then the Balkans. So the service carried two facts at once: a public identity built on equipment, and an internal experience of being smaller, tireder, and less certain of a career than it had been in a decade. A chief of staff talking about people in that particular moment was not offering a pleasantry.
Interpretation
The passage begins somewhere leadership writing usually declines to begin. Its first move is not an appeal to duty, service, or the welfare of subordinates but a flat concession to ambition: good leaders are people who have a passion to succeed. Fogleman is not asking his audience to become better people. He grants them the motive they already have and proposes to tell them how it gets satisfied. Everything after the ellipsis is addressed to that motive — which means the case for human relations here rests on self-interest rather than on virtue, a choice with consequences the passage never acknowledges and also the reason it has any chance of reaching the people it is aimed at.
The second sentence takes on the obvious rival. Note that it does not deny the equipment is good; it concedes that in the same breath — no matter how good the technology. What it denies is sufficiency. And the word doing the real work is shiny, which is not a synonym for capable. Shiny describes how a thing looks on a ramp, in a photograph, at a rollout. It is the word for equipment considered as a display object rather than as a tool, and by reaching for it Fogleman quietly separates two things his own service was in the habit of running together: what the machines can do, and what having the machines says about you.
Then the claim itself, which is narrower and harder than it first appears. People-to-people relations get things done. Not: make people happy, build culture, lift morale. Get things done is a claim about throughput — about whether work actually moves — and it locates the argument in the domain of results rather than the domain of climate. The following sentence presses further: people are the assets that determine our success or failure. Asset is worth pausing on, because in the mouth of an operational commander it is not the vocabulary of appreciation. An asset is something you have available to task, count, position, and spend. Fogleman has just finished deflating the equipment, and he now puts people into the column the equipment was in — the inventory column — and ranks within it. This is not an elevation of people above machines on moral grounds. It is a reclassification, and it is colder and more useful than the sentiment it usually gets read as.
The final sentence carries the payload, in two words. Cultivate is agricultural and durational; it names something grown by repeated attention across time, and you do not cultivate a trait you were issued at birth. Arena is the stranger choice, because in American usage it is not a neutral word — it belongs to Roosevelt, to the man marred by dust and sweat and blood, and it names a place where you are watched, where the stakes are real, and where you can be beaten. Putting personal relations inside it is a deliberate relocation of a word that had been reserved for physical daring. Together the two perform the passage's actual argument, which is not that leaders should be kind. It is that interpersonal capability is a competence rather than a temperament — learnable, therefore trainable, therefore assessable, therefore something a person can be found wanting in.
The two implications arrive together and they cut in opposite directions. If relational ability is a skill, then being poor at it is not a fixed feature of anyone's character, which is genuinely good news for a person who has been told otherwise for twenty years. But for exactly the same reason it stops being an excuse. The officer who explains that he is simply not a people person is, on this reading, reporting that he has not trained — and in a profession an untrained skill is a gap in the file, not a fact about the self. That is the sentence's sting, and it is aimed with some precision at the ambitious reader it opened by flattering.
Current Relevance
The claim that has aged most interestingly is the one about the arena, because an arena implies a scoreboard, and the scoreboard has never reliably been built.
Fogleman asserts stakes: personal relations is a domain in which you can lose. Thirty years on it is worth asking where, exactly, anyone loses. The most durable figure in organizational life remains the technically excellent person who is corrosive to work with, and the durability is structural rather than moral. Individual output is measurable and attributable; the cost of a bad relational climate is entirely real but arrives as attrition, as decisions that take longer than they should, and as information that does not travel — all of it diffuse, lagged, and almost never traced back to the person who produced it. The arena exists. The scoreboard is in a different part of the building.
What has changed since the mid-1990s sharpens the problem rather than solving it. Exit is cheaper now. People leave rather than escalate, and the familiar formulation that people quit managers rather than companies is, read as accounting, a description of a cost that has moved off the manager's ledger entirely: the manager keeps the output, and the organization absorbs the replacement. Distributed work has made the same cost harder to see, since the relational failure that once happened visibly in a corridor now happens as a message nobody sent.
The institution Fogleman ran is among the few to have built a partial answer. Command climate assessments, the practice of relieving a commander over climate rather than over performance, and the working assumption that a unit's atmosphere is its commander's product rather than his inheritance are all mechanisms for making relational failure attributable to a named person. They are imperfect, and they are criticized hardest from inside. But they exist, which is more than most civilian organizations can say, and they suggest something the passage leaves implicit: an arena is constructed, not discovered. An organization that has not built one has not, whatever it announces, accepted the premise.
Impact and Legacy
The sentence's afterlife is unusual for a leadership aphorism. It did not circulate so much as get installed: it sits as a pull-quote in the Air Force's own leadership doctrine, in the passage introducing what a leader owes the people under them, where it is met not by admirers browsing a compilation but by officers being taught what the service holds. Most quotations of this kind live in slide decks. This one became part of the material.
Fogleman's larger legacy on the same axis is more consequential than the quotation. He took the Air Force Academy's core values — integrity first, service before self, excellence in all we do — and made them the whole service's, which is the most durable institutional act of his tenure and remains the thing airmen can still recite. What makes that worth noticing here is what he was doing at the same time with the other hand. Global Engagement, the long-range vision published in 1996 over his signature and the secretary's, was the most technology-forward statement the Air Force had produced, organized around six core competencies whose vocabulary — precision engagement, information superiority, global attack — is machine language nearly throughout.
So the chief who put his name to the service's most equipment-confident document also installed its character statement, and also said that no matter how shiny the equipment, people-to-people relations get things done. Those are not in contradiction. They are a division of labor: the technology is what the service has, and the relations are how it gets spent. The quotation is the second half of a position whose first half is the only one usually remembered.
Contrasting Views or Controversies
The vulnerable claim is trainability. Cultivate your skills assumes relational ability is developable in adults to a degree that matters, and the evidence for that is thinner than the size of the leadership-development industry implies: transfer from classroom training to sustained on-the-job behavior is notoriously poor across the management-education literature, and the dispositional traits underneath relational ease are substantially stable by adulthood. If the ability is mostly selected rather than grown, the honest imperative is screen for this, not cultivate this, and the sentence is an encouraging category error. There is also a plainer possibility that dissolves the argument before it starts. This is an excerpt — the ellipsis belongs to the source, not to this corpus — and the original it was cut from has never been identified, so nothing establishes that these words were weighed rather than reached for. "The arena of personal relations" may simply have been a serviceable phrase of the period. If the words are only the words available, then cultivate was never a claim about trainability at all, and the reading offered here has spent four paragraphs arguing with its own vocabulary.
Grant the deliberate reading, and a rival solution goes unconsidered, one that comes out of Fogleman's own domain. The reason a modern airliner is safe is not that crews were taught to relate to one another better. It is crew resource management: standardized callouts, explicit challenge-and-response protocols, a procedural authority gradient that lets a first officer contradict a captain without the relationship between them having to be good. That is a serious answer to the problem the passage names, and it is the inverse of the passage's answer — rather than cultivating the relations, engineer a system that holds when they fail. It was developed in aviation, after accidents in which the relations were the failure, and it works.
Finally, the warrant. An argument running from ambition has nothing to say at precisely the point where something needs saying: the case in which treating a person badly is efficient. Fogleman never claims otherwise, and a reader who accepts the passage on its own terms has agreed that people are the assets determining success or failure, with nothing prepared for the day the accounting comes out the other way. The passage is well-built for persuading the ambitious and structurally unequipped to restrain them.
Practical Application
- For the individual — name the repetition you are avoiding. If this is a skill, it has reps, and the reps are specific: the correction delivered directly rather than routed through a process, the bad news carried in person, the request made without a favor attached. Almost everyone practices the easy half and calls it relationship-building. A skill exercised only when it is comfortable is not being trained; identify the one move you route around, and stop routing around it.
- For the manager — separate knowing about people from knowing them. The passage's word is relations, not information. A file of personal details gathered to be deployed later is a database, and people can tell the difference immediately. The working test is whether anything you learned last quarter has changed a decision you made since.
- For the organization — build the scoreboard the arena implies. Fogleman asserts stakes that most organizations have never installed. Make relational cost attributable: track retention and internal transfer by manager rather than by department, route departure interviews to the departing person's second-level leader, and treat a pattern as a performance fact about a named individual rather than as an ambient climate problem.
- For the organization, in the other direction — engineer for the relationship's absence. Wherever a relationship is carrying safety, quality, or a decision that must not be delayed, do not rely on cultivating it. Install the procedural version: an explicit escalation path, a standing obligation to raise a concern, a channel that works between two people who dislike each other. Cultivation and engineering are not rivals; the second is what you owe everyone the first has not yet reached.
- For civic and public institutions — audit the purchase against the problem. Public failures in health, disaster response, and schooling are routinely coordination failures answered with procurement, because buying a system is visible, fundable, and finishes on a schedule, while building the relations between agencies is none of those things. When a technological remedy is proposed for a problem whose actual failure was that two organizations did not talk, the passage is the question to ask out loud.
Background on the Author
Ronald Fogleman took a master's degree in history and political science at Duke, and as a major he sat down with Jimmy Doolittle to conduct an oral-history interview — which is to say that he spent part of his early career formally asking the previous generation how the job had been done. That habit is the closest thing in his record to a warrant for a sentence about cultivating a skill. He treated leadership as a subject with a literature and with living practitioners who could be interrogated, rather than as something absorbed by proximity to it.
The commands supply the other half. Before becoming chief of staff he ran Air Mobility Command and, at the same time, US Transportation Command — an organization whose entire product is coordination across services, agencies, and commercial carriers that do not report to it. TRANSCOM cannot order most of what it needs into a plan; it has to obtain it. In a job of that shape, personal relations is not a supplement to the mechanism. It is the mechanism, and a commander who is poor at it does not produce a worse atmosphere, he produces less cargo, later.
He had also flown 315 combat missions across two tours in Vietnam, including time as a Misty forward air controller — low-level work over North Vietnam and Laos, flown by volunteers, and among the most dangerous flying of the war. It is a record built on nerve, and it would have supported a very different sentence about what makes someone successful. What he said instead was that it runs through the arena of personal relations, and he had spent his last command in one of the few places where that arena came with a visible scoreboard.