Download the Book (PDF): Introduction A guest arrives at a luxury hotel late at night, exhausted, having mentioned nothing to anyone. The doorman notices that she is limping slightly and carrying her shoes. By the time she reaches her room, a pair of slippers and a note offering a foot soak have been placed on the bed. Nobody asked her. Nobody told the housekeeper what to do. The guest will describe the moment to friends for years. Stories like this are the currency of Exceptional Service, Exceptional Profit, by Leonardo Inghilleri and Micah Solomon, published in 2010. Inghilleri built his career in the development of luxury hotel companies, including The Ritz-Carlton and Bulgari Hotels & Resorts; Solomon is a business author and customer service consultant. Their book distils the methods behind five-star service into principles that any organisation can apply, from a hotel to a software company. Its central claim is contained in its title: exceptional service is not a cost to be tolerated but a source of exceptional profit, because it creates loyal customers, and loyal customers are worth far more than satisfied ones. For students, the book presents a particular difficulty. It is persuasive, practical and full of vivid examples, but it is written for managers, not for examiners. Its core concepts — empathy, anticipation, caring, loyalty — describe feelings and relationships, and a university essay on business strategy or service management demands something more: definitions, mechanisms, evidence and measurement. A student who writes that the Ritz-Carlton succeeds because its staff “genuinely care” has said something true but academically empty. What does caring consist of? How is it produced? How would we know if it had increased? And how does it turn into money? The argument of this guide This guide answers those questions. Its controlling idea is that empathy can be engineered and its returns can be measured. Behind every moment of apparently spontaneous warmth in an excellent service organisation lies a system: people selected for particular traits, language designed with care, standards that define the basics, information that tells employees what guests need, authority to act, and recovery processes for when things go wrong. Each part of that system can be described in the language of operations and organisational behaviour. And the outputs of the system — loyalty, retention, price premiums, recommendations — can be connected, through a chain of reasoning and evidence, to the financial performance of the organisation. Inghilleri and Solomon gesture at this chain throughout their book. This guide makes it explicit. It takes each of their major ideas and does three things with it. It defines the idea precisely, so that it can be used as a concept rather than a slogan. It connects the idea to the academic research that supports, refines or challenges it, so that you can cite that research in your own work. And it operationalises the idea — identifies the observable indicators through which it can be measured and the financial outcomes to which it can be linked. From feeling to construct The translation problem students face has a name in research methods: operationalisation. Social scientists routinely study things that cannot be observed directly — trust, satisfaction, commitment, organisational culture. They handle them by treating each as a construct: a precisely defined concept that can be linked to observable indicators. Satisfaction cannot be seen, but a guest’s answers to a carefully designed survey, the likelihood of a return visit, and the content of a review can. Culture cannot be seen, but employees’ responses to an engagement survey, the rate at which they stay or leave, and the behaviours recorded by a mystery shopper can. Two tests determine whether an indicator is any good. It must be reliable — it should give consistent results when the thing it measures has not changed. And it must be valid — it should actually measure the construct it claims to, rather than something else. A single question asking guests whether staff were “friendly” may be reliable but only partially valid as a measure of empathy, since friendliness and empathy are not the same thing. A mystery shopper’s record of whether an employee noticed and responded to an unexpressed need may be a more valid indicator of anticipatory service, though harder to collect consistently. Empathy itself is a good example of a construct that needs careful handling. In psychology, empathy is usually understood to have a cognitive side — understanding what another person is thinking or feeling — and an affective side — responding emotionally to it. In a service context, what matters to the guest is a third thing: the behaviour that results, the action that shows the guest they have been understood. An essay that treats “empathy” as a single vague quality will struggle; one that distinguishes the employee’s understanding, the employee’s response and the organisation’s systems that make the response possible will be able to analyse, measure and evaluate. Every chapter of this guide applies this discipline. When the book offers an idea, the guide asks what construct it names, what indicators would show it, and what outcome it should affect. How the guide is organised The chapters follow the logic of the causal chain from the outcome back to its sources, and then forward again to money. Chapter 1 starts with the outcome the book is ultimately about: loyalty, and the distinction the authors draw between satisfied customers and loyal ones. It explains why the distinction matters financially and how loyalty can be defined and measured. Chapter 2 examines the authors’ foundation — the four elements of customer satisfaction — and turns them into an operating model with measurable indicators. Chapter 3 addresses anticipation, the idea at the heart of five-star service, and shows how an organisation can build the ability to meet needs guests have not expressed. Chapter 4 covers what the authors call language engineering, and the critical moments of greeting and farewell. Chapter 5 turns to people and culture: selection, orientation, reinforcement and leadership. Chapter 6 deals with service recovery and the use of customer information. Chapter 7, the longest, sets out the methods by which the financial return on service investment can be estimated. Chapter 8 considers the limits: which service investments are worth making, how pricing should reflect a customer-centric philosophy, and where empathy’s economics break down. The conclusion draws the argument together. How to use this guide Read each chapter alongside the relevant part of Inghilleri and Solomon’s book. Their chapters provide the practice, the stories and the managerial detail; this guide provides the concepts, the research and the measurement. In an essay, you will need both. A good assignment on this subject uses the book’s examples to illustrate, the academic literature to explain, and the measurement frameworks to evaluate. A word of caution before starting. Some of the most famous claims about the economics of service are frequently repeated in forms their original authors never intended, and some popular statistics have no reliable source at all. Throughout this guide, figures are attributed to their original studies, with an indication of what those studies actually found. In an academic essay, a modest claim correctly sourced is always worth more than a dramatic one of uncertain origin. The book’s own premise is that service excellence is learnable — that it is the product of methods, not magic. The premise of this guide is that the same is true of writing about it. Once you can see the system beneath the story, the feeling becomes something you can analyse. Chapter 1: The Outcome that Matters Every argument in Exceptional Service, Exceptional Profit leads to one outcome: customer loyalty. The authors are emphatic that satisfaction, the measure most organisations track, is not enough. A satisfied customer, in their account, believes the business offers a reasonable solution and delivers it well, and will say so if asked; but that customer remains a free agent, open to a competitor’s offer. A loyal customer is different: attached to the business, inclined to return, less sensitive to price, and willing to recommend it unprompted. The whole apparatus of five-star service — the anticipation, the language, the recovery, the culture — exists to convert the first kind of customer into the second. This chapter examines that outcome. It explains what loyalty is, how it differs from satisfaction, why the difference matters financially, and how it can be measured. Because the rest of the guide traces the causes of loyalty, it is important to be clear about loyalty itself first. An analysis needs a precisely defined outcome before it can explain what produces it. Satisfaction is necessary but not sufficient The distinction between satisfaction and loyalty is well established in academic research, and the evidence supports Inghilleri and Solomon’s emphasis on it. Satisfaction is typically defined as a customer’s evaluation of a specific experience, or of the cumulative experience with a provider, relative to their expectations — the expectancy–disconfirmation logic developed by Richard Oliver in the 1980s. Loyalty is a broader and more durable relationship. The key finding is that satisfaction and loyalty are related, but not in a simple straight line. A famous analysis by Thomas Jones and Earl Sasser, published in the Harvard Business Review in 1995 under the title “Why satisfied customers defect”, showed that in many markets customers who described themselves as merely “satisfied” defected at much higher rates than those who were “completely satisfied”. The relationship between satisfaction and loyalty was not proportional: the big gains in loyalty came at the very top of the satisfaction scale. In competitive markets with many alternatives and low switching costs — which describes most of hospitality — being “good enough” earned very little loyalty. This finding supports the book’s central strategic argument. If loyalty is concentrated among customers who are delighted rather than satisfied, then an organisation that aims merely to meet expectations will find its customers drifting away despite reasonable satisfaction scores. The economic case for exceptional service rests on the non-linearity of the satisfaction–loyalty relationship. That is a point worth making explicitly in any essay on the subject, with the source cited. What loyalty is Loyalty has been defined in many ways, and an essay should adopt a clear definition rather than using the word loosely. Two dimensions are generally recognised. Behavioural loyalty is what customers do: repeat purchase, share of spending, frequency of visits, length of relationship. It is observable in transaction data — a hotel’s property management system, a restaurant’s loyalty app, an airline’s frequent flyer records. Attitudinal loyalty is what customers feel and intend: preference for the brand, emotional attachment, commitment, willingness to recommend. It is measured through surveys and inferred from behaviour such as unsolicited recommendation. Alan Dick and Kunal Basu showed in a 1994 article why both dimensions matter by crossing them. Customers with high repeat purchase and high attitudinal attachment show true loyalty. Customers with high repeat purchase but weak attachment show spurious loyalty: they return out of convenience, habit or lack of alternatives, and will leave as soon as a better option appears. Customers with strong attachment but low repeat purchase show latent loyalty: they like the brand but something — price, location, availability — prevents them from buying more. Customers with neither show no loyalty. The framework matters for the economics of empathy. Many hospitality organisations have large numbers of spuriously loyal customers — travellers who stay at a hotel because their company’s travel policy requires it, or who eat at a restaurant because it is next to their office. Such customers look loyal in the transaction data, but the relationship is fragile. Inghilleri and Solomon’s methods aim at true loyalty: the emotional attachment that keeps a customer returning even when a competitor offers a lower price or a closer location. Distinguishing the two in an essay shows a sophisticated understanding of what service investments are meant to achieve. Richard Oliver, in a widely cited 1999 article, proposed that loyalty develops in stages: from cognitive loyalty (based on information about price and features), to affective loyalty (based on liking), to conative loyalty (a commitment to repurchase), and finally to action loyalty (a readiness to act that overcomes obstacles). His argument was that the earlier stages are vulnerable to competitors, and that only the deeper stages provide real protection. Oliver’s framework is a useful complement to the book, because the practices the authors describe — personal recognition, anticipation of needs, warm language, excellent recovery — work mainly on the affective and conative stages. Loyalty programmes that reward points, by contrast, tend to work at the cognitive level, which is why they are so easily matched by competitors. Why loyalty is valuable The financial case for loyalty rests on several mechanisms, each of which can be analysed separately. Retention reduces acquisition costs. Winning a new customer usually involves marketing, promotion, sales effort, and in hospitality, commissions to intermediaries. A customer who returns directly avoids some or all of these costs. Loyal customers tend to spend more over time. They buy additional services, try new products, and consolidate their spending with a provider they trust. Loyal customers are often less price-sensitive. Because they value the relationship and trust the quality, they are less likely to switch for a small price difference. Inghilleri and Solomon make this argument explicitly in their discussion of pricing. Loyal customers recommend. Word of mouth — today, largely online — brings new customers at little or no acquisition cost, and those customers arrive with favourable expectations. Loyal customers are cheaper to serve. They know the organisation’s processes, need less guidance, and forgive occasional errors more readily. The most frequently cited evidence for the size of these effects comes from Frederick Reichheld and Earl Sasser’s 1990 Harvard Business Review article, “Zero defections: quality comes to services”. Drawing on analysis of a range of service businesses, they reported that reducing customer defections by five percentage points could increase profits by between 25 and 85 per cent, depending on the industry. The figure has been quoted countless times, often without its context, and it is worth using carefully. It came from a particular set of businesses and a particular period, and the size of the effect varied widely across industries. It should be cited as evidence that retention can have large profit effects in some service businesses — which is what it shows — not as a universal law. The service–profit chain The mechanisms linking service, loyalty and profit were brought together in the service–profit chain, developed by James Heskett and colleagues at Harvard Business School and set out in a 1994 Harvard Business Review article and a 1997 book. The chain proposes a sequence: internal service quality (the support, tools and working environment employees receive) drives employee satisfaction; employee satisfaction drives retention and productivity; these drive the value of the service delivered; service value drives customer satisfaction; satisfaction drives customer loyalty; and loyalty drives revenue growth and profitability. The service–profit chain is the natural academic framework for Exceptional Service, Exceptional Profit, because the book’s chapters map onto its links almost exactly. The chapters on people, selection, training and leadership address internal service quality and employee satisfaction. The chapters on the four elements, anticipation, language and recovery address service value and customer satisfaction. The chapters on loyalty, tracking and online relationships address loyalty. And the book’s title claims the final link: profit. Research since 1994 has tested the chain extensively. The broad pattern is supportive — links between employee attitudes, customer satisfaction and financial outcomes have been found in many settings — but the links are weaker and more conditional than the original presentation suggested, and some studies have found the chain breaks down in particular industries or when competition, pricing or market conditions intervene. In an essay, present the chain as a well-supported framework whose individual links need evidence in each context, rather than as an established law. Measuring loyalty Because this guide is concerned with turning concepts into measurable data, it is worth setting out how loyalty is measured in practice. Behavioural measures include the retention rate (the proportion of customers in one period who return in the next), repeat visit frequency, share of wallet (the proportion of a customer’s category spending captured by the organisation), tenure (how long the relationship has lasted), and, in hospitality, the proportion of bookings made directly rather than through intermediaries — since loyal guests are more likely to go straight to the brand. Attitudinal measures include survey questions on intention to return, intention to recommend, preference over competitors and emotional attachment. The Net Promoter Score, proposed by Frederick Reichheld in 2003, asks a single question — how likely the customer is to recommend the organisation on a scale of zero to ten — and subtracts the percentage of low scorers from the percentage of high scorers. Its simplicity has made it the most widely used loyalty measure in business, though its claims to predict growth have been challenged by researchers, a point discussed in Chapter 7. Composite measures combine behaviour and attitude, in the spirit of Dick and Basu, to distinguish true from spurious loyalty. Financial measures translate loyalty into money. The most important is customer lifetime value, the present value of the margins a customer is expected to generate over the whole relationship, which Chapter 7 explains in detail. A strong essay uses more than one type of measure, and explains why. Behavioural data show what customers actually do but not why; attitudinal data show what they feel but may not predict behaviour; financial measures show value but depend on assumptions. Together, they give a reasonably complete picture of whether an organisation’s service strategy is producing the outcome it is designed to produce. Loyalty programmes and relational loyalty Hospitality offers a natural test of the difference between the kinds of loyalty just described, because the industry has invested so heavily in formal loyalty programmes. The large hotel groups, airlines and many restaurant chains run programmes that award points for spending and offer benefits — upgrades, late check-out, free nights — to frequent customers. Their membership runs into the tens and, for the largest hotel groups, the hundreds of millions. Such programmes are valuable. They encourage direct booking, give the organisation data about its customers, and create switching costs: a traveller who is close to a higher membership tier has a reason not to stay elsewhere. But viewed through Oliver’s stages, most programme benefits operate at the cognitive level. They give customers a calculable reason to return, which a competitor with a comparable programme can match. When every major brand has a programme, the programmes themselves tend to cancel each other out, and the remaining difference between brands lies in the experience — which is exactly where Inghilleri and Solomon locate it. The contrast with what might be called relational loyalty is instructive. Some of the most admired luxury hotel companies have long operated without a conventional points programme, relying instead on recognition, personal relationships and the quality of the experience to bring guests back. The loyalty they seek is affective and conative: guests return because they feel known and cared for, not because they are accumulating points. That kind of loyalty is harder to build and harder to measure, but also harder for competitors to take away. In an essay, the distinction lets you evaluate a loyalty strategy critically: does the organisation’s investment build attachment, or only switching costs? A worked example: reading a guest base To see how the concepts in this chapter can be used together, imagine a city hotel that has analysed its database of guests who stayed at least once in the past three years, combining booking records with the results of a post-stay survey. Roughly, the analysis might sort guests into four groups. A group of frequent guests who also give high scores for intention to recommend and preference over competitors would be truly loyal. A second group of frequent guests who give only middling scores, many of them booked through a corporate travel agreement, would be spuriously loyal: they return because their employer sends them. A third group of infrequent guests who give very high scores — often leisure travellers who visit the city once a year — would be latently loyal. The rest would show no loyalty. The strategic implications differ sharply by group. The truly loyal are the hotel’s most valuable asset and deserve recognition and protection. The spuriously loyal are a risk: if the corporate agreement is lost or a competitor opens nearby, they will leave, so the hotel’s priority is to convert habit into attachment through precisely the kind of personal service the book describes. The latently loyal are an opportunity: they already love the hotel, and the question is whether something — a targeted offer, an invitation to book directly for a return visit — can turn attachment into more frequent stays. And the analysis itself shows why a single satisfaction average would have hidden almost everything that matters. Why this chapter comes first It may seem odd to begin a guide to service with the outcome rather than the service. The reason is methodological. Students writing about exceptional service often describe the practices — the anticipation, the recovery, the empowered employees — and simply assert that they produce loyalty and profit. The assertion is the weakest part of the essay. By defining loyalty precisely, distinguishing it from satisfaction, understanding the mechanisms through which it produces value, and knowing how it is measured, you are equipped to test the assertion rather than repeat it. The rest of this guide traces the causes of loyalty back through Inghilleri and Solomon’s system. Chapter 7 then returns to the financial link and shows how to estimate it. Chapter 2: The Four Elements as an Operating Model Before Inghilleri and Solomon discuss anything that sounds like magic — anticipation, wow, emotional connection — they insist on the basics. Their second chapter sets out four elements that every customer expects, and argues that no amount of charm can compensate for their absence. In their formulation, customers are satisfied when they receive a perfect product, delivered by a caring, friendly person, in a timely way, supported by an effective problem resolution process. The four elements are the foundation on which everything else in the book is built. For students, the four elements are the easiest part of the book to understand and the easiest to underuse. They are often summarised in a sentence and left behind. This chapter shows how to treat them as an operating model: a set of four constructs, each of which can be defined, connected to research, broken down into measurable indicators, and managed. Element one: the perfect product By “perfect product”, the authors do not mean something flawless in an absolute sense. They mean a product or service that does what it is supposed to do, reliably, within the range of circumstances the customer can reasonably foresee. A hotel room that is clean, quiet and as described; a meal that matches the menu and is cooked correctly; a flight that departs and arrives as scheduled. The product must work. In academic terms, this element corresponds most closely to reliability, one of the five dimensions of service quality identified by A. Parasuraman, Valarie Zeithaml and Leonard Berry in their SERVQUAL research in the 1980s. Their consistent finding — that reliability is the dimension customers weight most heavily — gives strong support to the book’s insistence on putting the product first. Customers are rarely impressed by extras if the core has failed. The operational discipline behind the perfect product is defect elimination. Inghilleri and Solomon draw on the quality management methods used at the Ritz-Carlton, which adopted a simple tool for identifying defects known by the mnemonic “Mr. BIV”: Mistakes, Rework, Breakdowns, Inefficiencies and Variation. Each is a category of defect that employees are trained to notice and report. The approach descends from the total quality management tradition associated with W. Edwards Deming and Joseph Juran, which held that most quality problems are caused by systems rather than individuals, and that the way to improve quality is to find and remove the causes of variation in processes. Indicators for this element are relatively easy to define: the proportion of rooms that pass inspection first time, order accuracy, the number of maintenance defects reported per hundred occupied rooms, the rate of complaints about the core product, on-time performance. These are the measures that tell an organisation whether its product is, in the authors’ sense, perfect. Element two: caring delivery The second element is the human dimension: the product must be delivered by someone who is caring and friendly. The same room, meal or flight feels different depending on whether the person providing it seems to notice and value the customer. In SERVQUAL terms, caring delivery spans two dimensions: empathy (caring, individualised attention) and assurance (courtesy, competence and the ability to inspire trust). Research on emotional contagion, discussed in Chapter 4 of this guide, suggests one mechanism through which caring delivery affects customers: the displayed emotions of employees tend to be “caught” by customers, influencing their mood and their evaluation of the service. This element is harder to measure than the first, because it concerns perceptions of warmth and attention rather than objective facts. But it is not unmeasurable. Guest surveys can ask about specific behaviours rather than general impressions: whether the employee used the guest’s name, made eye contact, offered help without being asked, or seemed to take a personal interest. Mystery shoppers can record the same behaviours. Online reviews can be analysed for the frequency and tone of comments about staff. The trick, as the introduction to this guide explained, is to move from the abstract construct — caring — to observable behaviours that indicate it. Element three: timeliness The third element is time. The product must be delivered when the customer needs it, on the customer’s schedule rather than the organisation’s. The authors emphasise that timeliness is defined by the customer’s expectations, which vary: a business traveller checking out before an early flight has a different sense of “timely” from a family at a leisurely weekend breakfast. Timeliness corresponds to the SERVQUAL dimension of responsiveness — willingness to help and to provide prompt service. It also connects to the extensive research on waiting, which shows that the perceived length of a wait depends not only on its actual duration but on whether it is explained, whether the customer is occupied, and whether it seems fair. Timeliness is the most straightforward of the four elements to measure objectively: check-in duration, time to answer the telephone, time from order to service, time to respond to a request or an email, on-time delivery rates. It is also one of the easiest to improve through operational design — scheduling, capacity planning, process simplification — which makes it a natural target for early investment. Element four: effective problem resolution The fourth element recognises that failures will happen. What the customer expects is not perfection but a reliable process for putting things right when something goes wrong. The authors treat this as part of the basic promise, not an optional extra, and they devote a separate chapter of their book to service recovery, which Chapter 6 of this guide covers. In the service quality literature, problem resolution is sometimes treated as an aspect of reliability or responsiveness, and sometimes as a separate construct. What matters for measurement is that it can be assessed directly: complaint resolution rates, time to resolution, the proportion of problems resolved at first contact, and the satisfaction of customers who experienced a problem compared with those who did not. Basics before delight: the Kano model The book’s insistence on mastering the four elements before pursuing anything more ambitious has a useful academic parallel in the Kano model, developed by the Japanese quality researcher Noriaki Kano and colleagues in 1984. Kano distinguished three kinds of product and service attributes. Must-be attributes are basic expectations. Their presence does not create satisfaction — customers take them for granted — but their absence creates strong dissatisfaction. A clean bathroom in a hotel room is a must-be attribute. One-dimensional attributes create satisfaction in proportion to how well they are delivered. The speed of check-in or the comfort of the bed may behave this way: better is better, and worse is worse. Attractive attributes delight customers when present but cause no dissatisfaction when absent, because customers did not expect them. An unexpected personal gesture — the slippers left for the guest in the introduction to this guide — is an attractive attribute. The Kano model explains precisely why the four elements come first. The perfect product and effective problem resolution are largely must-be attributes: failure on them generates intense dissatisfaction that no attractive attribute can offset. Timeliness and caring delivery are often one-dimensional. Anticipatory service, the subject of the next chapter, largely creates attractive attributes. An organisation that invests in delight while failing on the basics is spending money on attractive attributes while its must-be attributes cause dissatisfaction — a poor use of resources. The model also explains a dynamic the authors recognise: attributes migrate over time. What is attractive today becomes one-dimensional and then must-be as customers become used to it. Free Wi-Fi in hotels followed exactly this path. Organisations that aspire to delight must therefore keep innovating, while continuously protecting the basics. The operating model Taken together, the four elements form an operating model: a small set of constructs that define what the organisation must deliver, each with its own academic grounding and its own measurable indicators. Table 1 sets them out. Table 1. The four elements of customer satisfaction as measurable constructs. Element Closest research construct Example indicators Typical data source Perfect product Reliability (SERVQUAL); must-be quality (Kano) First-time inspection pass rate; order accuracy; defects per 100 occupied rooms Inspections; operational logs; defect reports Caring delivery Empathy and assurance (SERVQUAL) Use of guest’s name; unprompted offers of help; staff mentions in reviews Mystery shopping; guest surveys; review analysis Timeliness Responsiveness (SERVQUAL) Check-in time; response time to requests; order-to-table time System timestamps; call logs; observation Effective problem resolution Recovery satisfaction; procedural justice First-contact resolution rate; time to resolve; satisfaction after a problem Complaint tracking; follow-up surveys The value of the table for an essay is that it turns a qualitative framework into something you can evaluate. Asked to assess a hotel’s service, you can examine each element in turn, identify indicators and evidence, and judge where the organisation is strong and where it is weak. Asked to recommend improvements, you can prioritise the element where performance is weakest — which, following Kano, should usually be a must-be attribute before an attractive one. From elements to standards An operating model becomes real when it is translated into standards: specific, observable statements of what employees and systems must do. Writing good standards is a skill, and it is one that essays rarely examine. A useful standard has several properties. It is specific enough that two people would agree whether it had been met — “answer the telephone within three rings” rather than “answer the telephone promptly”. It is observable, describing behaviour or outcomes rather than attitudes — “greet every guest within ten seconds of their arrival at the desk” rather than “be welcoming”. It is linked to a guest need, so that employees understand why it matters and can adapt sensibly when the standard does not quite fit the situation. And it is reviewed, because guests’ expectations change and a standard that made sense five years ago may now be irrelevant or insufficient. The four elements provide a natural structure for a standards manual. Perfect-product standards specify the condition of the room, the preparation of the dish, the maintenance of equipment. Timeliness standards specify response times. Caring-delivery standards specify greeting, use of names, eye contact, offers of help and farewell behaviours. Problem-resolution standards specify who can resolve what, within what limits, how quickly, and how the problem is recorded. There is a tension here that the book acknowledges and that a good essay should discuss. Standards produce consistency, which supports reliability. But caring delivery cannot be fully standardised: a greeting delivered because a manual requires it can feel mechanical, and customers notice. The most sophisticated organisations resolve the tension by standardising the what — the guest must be greeted, by name where possible, within a set time — while leaving the how to the employee’s judgement and personality. Standards define the floor; people and culture determine how far above it the experience rises. A worked example: a restaurant against the four elements Consider how the operating model might be applied to a busy mid-priced restaurant whose online rating has slipped over a year. For the perfect product, the manager examines kitchen records and guest comments. Order accuracy is high, but reviews mention dishes arriving lukewarm on busy evenings. The kitchen’s own logs show that plates wait at the pass for several minutes at peak times because there are not enough runners to take them to tables. The defect is real, but its cause lies in the delivery process rather than the cooking. For caring delivery, a mystery shopper’s reports show that servers are polite but rarely use guests’ names from the booking, seldom check back after food is served, and do not offer help to guests who are clearly looking around for something. The staff are not unfriendly; they are stretched, and the behaviours that signal care are the first to disappear under pressure. For timeliness, till timestamps show that the time from ordering to the arrival of main courses has lengthened by several minutes on Friday and Saturday evenings over the year, while bookings have risen. For problem resolution, the complaint log shows that most complaints are handled well when a manager is present, but that servers do not feel able to offer anything — a replacement dish, a dessert, a discount — without finding one, which can take several minutes on a busy night. The diagnosis is coherent: the restaurant’s demand has grown faster than its floor staffing and its recovery authority. Lukewarm food, thinner caring behaviours, longer waits and slower recovery all follow from the same underlying constraint. The recommendations follow too: add runners at peak times to protect the perfect product and timeliness, which will also free servers to deliver the caring behaviours; and give servers limited authority to resolve common problems on the spot. Each recommendation targets a measured indicator, which means its effect can be checked. Managing the four elements The four elements also suggest where different kinds of management intervention belong. The perfect product and timeliness depend heavily on systems, processes and capacity — the domain of operations management. Caring delivery depends on people — selection, training, culture and leadership, which Chapter 5 of this guide covers. Effective problem resolution depends on both: on processes that capture and route problems, and on people with the authority and skill to resolve them. This distinction helps avoid a common error in essays and in management practice: treating every service problem as a people problem. A hotel whose guests complain of waiting at check-in may be tempted to run a customer service training course for front-desk staff. If the cause is too few agents at peak times, or a slow computer system, the course will achieve nothing. The four elements, mapped to their operational and human drivers, direct attention to the real cause. Satisfaction is only the start The four elements, in the authors’ account, produce satisfaction. But as Chapter 1 explained, satisfaction is not loyalty. The four elements are necessary to earn a customer’s trust, but they do not, on their own, create the emotional attachment that keeps customers returning when a competitor offers a lower price. That requires something more — the anticipation of needs, the use of language that makes customers feel valued, the recognition of individuals, and the recovery that turns a failure into a demonstration of commitment. These are the subjects of the chapters that follow. The logic of the book, and of this guide, is therefore cumulative. The four elements are the foundation: measurable, manageable, and essential. Anticipation and emotional connection are built on top of them. An organisation — or an essay — that skips the foundation to reach the more exciting material will find that the structure does not stand. Chapter 3: Anticipation — Engineering the Unexpressed Need If the four elements are the foundation of Inghilleri and Solomon’s approach, anticipation is its signature. The book opens with it: its first chapter, on reaching for the highest level of service, is built around the idea that the best service meets needs before customers express them — and sometimes before customers are aware of them. Later, the authors return to the theme in a chapter on building anticipation into products and services themselves. Anticipatory service is what separates the five-star experience from the merely competent one, and it is the part of the book most often described in the language of instinct and intuition. This chapter argues that anticipation is not instinct. It is a capability that organisations can build, with identifiable components that can be designed, trained, supported and measured. That is the claim a student needs to be able to make and defend. Levels of service A useful way to locate anticipation is to distinguish levels of service according to when and how the organisation responds to customer needs. Reactive service responds to needs once the customer has expressed them, often after a delay and sometimes grudgingly. The guest asks for extra towels; eventually, towels arrive. Responsive service responds to expressed needs quickly, accurately and graciously. The guest asks for towels; they arrive within minutes with a smile and an offer of anything else. Responsive service satisfies the four elements well. Anticipatory service meets needs before the customer expresses them. The housekeeper notices that the family in the room has two small children and leaves extra towels without being asked. The server sees a guest glance at her watch and brings the bill before she has to ask for it. The distinction between responsive and anticipatory service has a parallel in marketing research. John Narver, Stanley Slater and Douglas MacLachlan distinguished in 2004 between a responsive market orientation, which seeks to understand and satisfy customers’ expressed needs, and a proactive market orientation, which seeks to discover and satisfy their latent needs — needs of which customers may not be aware. Their research, conducted in the context of new product development, found that the proactive orientation was particularly associated with innovation success. Anticipatory service is the equivalent orientation applied to the individual encounter. Three kinds of need It helps to be precise about which needs anticipation addresses. Customers’ needs can be sorted into three kinds. Expressed needs are those the customer states: a request, a booking, an order. Meeting them is the job of responsive service. Unexpressed but conscious needs are those the customer is aware of but has not stated, perhaps because they did not think to ask, did not want to bother anyone, or did not expect the organisation to help. The tired guest who would love a quiet room but did not like to ask; the business traveller who needs to print a boarding pass but has not mentioned it. Latent needs are those the customer has not yet recognised. The guest checking out does not yet know that it is about to rain; the doorman who offers an umbrella has anticipated a need the guest will have in two minutes. Anticipatory service works on the second and third kinds. Its value is that it removes effort, anxiety or inconvenience that the customer would otherwise have experienced — and, crucially, it signals that someone was paying attention. It is this signal of attention, as much as the practical help, that produces the emotional response the book describes. Two arenas of anticipation Inghilleri and Solomon discuss anticipation in two distinct arenas, and a strong essay keeps them separate. The first is anticipation in the encounter: an individual employee noticing, in the moment, something about a particular guest and acting on it. This depends on the employee’s attentiveness, judgement and freedom to act. The second is anticipation by design: building the anticipation of common needs into the product, the process and the environment, so that the need is met for every customer without anyone having to notice it individually. The authors encourage organisations to think like customers — to walk through the experience step by step and identify every point where a customer is likely to be confused, delayed or inconvenienced — and then redesign it. A hotel that places phone chargers at the bedside because guests so often forget theirs, offers a late check-out automatically to guests whose flight details show an evening departure, or provides umbrellas at every entrance, is anticipating by design. The two arenas are complementary. Design handles the predictable needs of many guests efficiently and consistently; encounters handle the unpredictable needs of individuals. Organisations that rely only on design risk a service that feels thoughtful but impersonal. Organisations that rely only on individual employees risk inconsistency and depend heavily on who happens to be on duty. Anticipation as a standard One of the most striking features of the Ritz-Carlton approach, which the book draws on, is that anticipation is not left to chance. The company’s long-standing “Three Steps of Service” set out a sequence for every guest interaction: a warm and sincere greeting, using the guest’s name; the anticipation and fulfilment of each guest’s needs; and a fond farewell, again using the guest’s name. By making anticipation the second of three formal steps, the company turned an aspiration into an expectation of every employee. The point is methodological as well as practical. It shows that anticipation can be specified as a standard, trained as a skill and evaluated as a behaviour — which is exactly what the translation into academic terms requires. The components of an anticipation capability What does an organisation need in order to deliver anticipatory service reliably? Breaking the capability into components makes it analysable. Attention and cue recognition. Employees must notice the signals that indicate unexpressed needs: luggage, children, the time of day, the weather, a guest’s body language, a hesitation, a repeated glance. Noticing is partly a matter of disposition — some people are naturally more observant than others, which is why selection matters (Chapter 5) — and partly a matter of training. Organisations can teach employees the common cues and their likely meanings, share examples, and practise through role-play. Information. Many needs can be anticipated only if the organisation knows something about the guest: a preference recorded on a previous visit, an allergy mentioned at booking, a special occasion, a flight time. The book devotes a chapter to keeping track of customer information, discussed in Chapter 6 of this guide, precisely because personal anticipation depends on it. The information must be captured, stored, and — most importantly — put in front of the employee who can act on it at the right moment. Authority and resources. An employee who notices a need but must seek a manager’s permission to meet it cannot anticipate; they can only report. Anticipation requires the authority to act and access to the resources needed — the ability to send extra towels, arrange a late check-out, or bring a complimentary item without approval. Time. Anticipation requires slack. An employee rushed from task to task has no time to notice or respond to anything beyond the immediate request. Staffing levels set purely to handle expressed demand leave no capacity for anticipation. This is one of the most important and least discussed links between the economics of empathy and operational decisions: anticipation has a labour cost, and organisations that cut staffing to the minimum should not expect it. Culture and reinforcement. Employees must believe that anticipation is valued, that it will be recognised, and that they will be supported if they occasionally misjudge. Stories of anticipatory service, shared across the organisation, both teach the behaviour and signal its importance. Framed this way, anticipation becomes a capability with five components, each of which can be assessed and developed. That is a far stronger basis for analysis than the claim that some organisations simply “care more”. Anticipation and competitive advantage Why does anticipation matter strategically, beyond its effect on individual guests? The resource-based view of the firm, associated with Jay Barney, holds that sustained competitive advantage comes from resources and capabilities that are valuable, rare and difficult to imitate. An anticipation capability fits this description unusually well. It is valuable because, as the Kano model in Chapter 2 suggests, anticipatory gestures act as attractive attributes that create delight and, ultimately, the attachment that underpins true loyalty. It is rare because most organisations lack one or more of the five components. And it is difficult to imitate because it is socially complex — it arises from the interaction of selection, training, information systems, authority, staffing and culture — and causally ambiguous — competitors can see the results but cannot easily identify which elements produce them. A rival can copy a hotel’s décor or a restaurant’s menu within months. It cannot copy the combination of practices that makes an organisation’s employees notice and act on what guests need. This argument is one of the strongest available for connecting the book’s practical advice to strategic theory. It explains why anticipatory service can be a source of sustained advantage rather than merely a nice extra. A worked example: designing anticipation into a stay The authors’ advice to think like the customer can be turned into a simple method. Take one segment of guests, walk through their journey stage by stage, and at each stage ask three questions: what is this guest likely to need that they will not ask for, what signal would reveal it, and could the need be met by design rather than by an individual employee noticing it? Consider business travellers arriving at an airport hotel for one night before an early flight. Before arrival, they are likely to wonder whether the hotel runs a shuttle at the hour they land, and whether they can check in late. Both needs are predictable, so both can be met by design: a pre-arrival message giving shuttle times and confirming that the room will be held. On arrival, they are likely to be tired, hungry and anxious about the morning. An employee who notices the late hour and the carry-on luggage might offer to arrange a wake-up call and a packed breakfast; but since almost every guest in this segment will have the same needs, the hotel can design the offer into the check-in conversation and the booking system, prompting the agent to ask about the flight time and propose both. In the room, the guest will need to charge devices and perhaps print a boarding pass, so chargers at the bedside and a simple way to print from a phone meet predictable needs without anyone having to notice. At departure, the guest is likely to be in a hurry and worried about time; an express check-out with the bill sent by email, a shuttle timed to the flight and a coffee ready in the lobby remove the anxiety before it arises. What remains for employees is the unpredictable: the guest who has missed a connection and needs a different flight, the one who looks unwell, the one travelling with an elderly parent. Because the predictable needs have been designed out, employees have more time and attention for these — which is where individual anticipation creates its greatest effect. The exercise produces something an essay can use: a clear division between needs anticipated by design and needs left to encounters, each with its own management requirements. Design needs process owners, systems and audits; encounters need selection, training, time and authority. It also shows that anticipation is segment-specific. The same exercise for a family arriving at a beach resort would produce an entirely different set of predictable needs — cots, pool towels, children’s menus, sunscreen — and a different set of cues for employees to watch for. The limits of anticipation Anticipation can go wrong, and a critical essay should say so. It can be presumptuous. Guessing a need incorrectly can irritate rather than delight, particularly if it seems to rest on a stereotype. The guest who is assumed to want help with luggage may feel patronised; the couple assumed to be celebrating may be anything but. It can be intrusive. Anticipation that depends on information about the guest raises questions about privacy. The book itself warns against tracking that feels invasive, and the concern has grown since its publication as organisations have acquired far more data about their customers. A guest who is greeted with a reference to something they never told the hotel may feel watched rather than welcomed. It can be culturally variable. What counts as attentive in one culture may be overbearing in another. Some guests value being left alone. And it can be costly. Every anticipatory gesture consumes time and resources. Not every possible need is worth anticipating, a question the book addresses in its discussion of what is worth doing and what is not, and which Chapter 8 of this guide takes up. The practical answer to most of these risks is judgement — which is why anticipation is ultimately a human capability supported by systems, rather than a purely systematic one. Measuring anticipation Anticipation is harder to measure than timeliness or accuracy, but several indicators can capture it. Critical incident analysis of guest comments and reviews can count the frequency of incidents in which guests report that a need was met before they asked. Phrases such as “before I even asked” or “they had already thought of it” are observable markers of anticipatory service. Preference fulfilment rates measure the proportion of recorded guest preferences that are honoured on subsequent visits. If a guest asked for a feather-free pillow last time, was one there this time? Mystery shopping with planted cues tests whether employees notice and respond to signals deliberately built into the scenario: the shopper mentions a headache, carries a heavy bag, or appears lost. Survey items can ask directly whether staff anticipated the guest’s needs, though self-reported perceptions should be triangulated with other evidence. Design audits can assess whether predictable needs at each stage of the customer journey have been met by design. Each indicator is partial, but together they allow an organisation — and a student — to assess whether anticipation is actually happening, rather than simply asserting that it is. Summary Anticipatory service is the part of Inghilleri and Solomon’s approach that looks most like an art. Analysed carefully, it turns out to be a capability with identifiable components — attention, information, authority, time and culture — delivered in two arenas, the encounter and the design, and measurable through a set of complementary indicators. Its strategic value lies in its difficulty to imitate. Its limits lie in the risks of presumption, intrusion and cost. An essay that can present anticipation in these terms has done exactly what the book invites but does not itself do: it has turned a feeling into a theory. Hashtags: #TheEconomicsOfEmpathy #ExceptionalServiceExceptionalProfit #LeonardoInghilleri #MicahSolomon #CustomerServiceExcellence #ServiceManagement #CustomerExperience #CustomerEmpathy #EmotionalIntelligence #CustomerLoyalty #CustomerSatisfaction #CustomerRetention #ServiceProfitChain #CustomerLifetimeValue #AnticipatoryService #FiveStarService #LuxuryHospitality #HospitalityManagement #ServiceQuality #SERVQUAL #KanoModel #ServiceRecovery #EmployeeEmpowerment #CustomerCentricity #PersonalizedService #CustomerDelight #RelationshipMarketing #NetPromoterScore #ServiceInnovation #BusinessProfitability

Download the Book (PDF): Introduction In the twelve months to the end of 2026, four American companies — Amazon, Microsoft, Alphabet and Meta — will have committed capital expenditure in the region of seven hundred billion dollars, most of it to buildings full of accelerators and the electrical plant required to run them. That is roughly seventy per cent more than the same four spent the year before, and it is being deployed at a speed that has no close peacetime precedent. It exceeds the annual gross fixed capital formation of most European economies. It is being decided by perhaps two dozen people. In the same period, a study of roughly twenty-five thousand Danish workers across seven thousand workplaces, in eleven occupations chosen precisely because they were thought highly exposed to large language models, found that adoption had been fast and near-universal, that the average time saving amounted to something like three per cent of working hours, and that there was no detectable effect on earnings or hours worked. Both of those things are true. Reconciling them is the problem this book sets out to solve. The easy resolutions are both wrong. The first says that the capital is delusional — a bubble, a mania, money thrown at a chatbot by people who have confused fluency with intelligence. The second says that the Danish result is simply early — that the technology is real, the gains are coming, and measurement will catch up. Each of these is a way of not doing the work. The interesting position, and the one the evidence actually supports, is that generative AI is a genuinely powerful technology whose economic effects are being routed through channels that neither the enthusiasts nor the sceptics predicted, and that most of the public argument is aimed at the wrong questions. The argument of this book is a specific one. For fifty years, the dominant account of how technology reshaped work held that machines took over tasks that could be reduced to explicit rules, and that those tasks were concentrated in the middle of the wage distribution — clerical work, bookkeeping, routine production. The prediction that followed was hollowing out: growth at the top, growth at the bottom, decline in the middle. That prediction was broadly correct for four decades and it is close to useless now. Generative AI does not learn rules; it learns from examples, and what it learns from best is knowledge that has already been written down. Legal reasoning is written down. Diagnostic protocols are written down. Marketing copy, code conventions, financial commentary, undergraduate essays and internal memoranda are all written down, at enormous volume, and they are exactly what these systems ingest. What is not written down is the thing experienced people know and cannot fully articulate: which client will object, which exception is the one that matters, when an answer that looks right is wrong. That knowledge is acquired by doing the work, and it is the reason experienced professionals are paid more than inexperienced ones. Generative AI is extraordinarily good at the first kind of knowledge and structurally weak at the second. That single asymmetry — codified knowledge substituted, tacit judgement complemented — generates almost everything else in this book. It explains why exposure to this technology rises with education and wages rather than falling, inverting the pattern of the last half-century. It explains why the sharpest measured effects in the labour market so far are on twenty-two- to twenty-five-year-olds rather than on the middle-aged, and why the adjustment is running through hiring rather than through dismissals. It explains why the same tool raises output thirty-four per cent for a novice call-centre agent and close to zero per cent for an expert one. It explains why a randomized trial can show consultants working twenty-five per cent faster on one task and nineteen percentage points less accurately on another. And it points toward a labour-market problem that is not mass unemployment but something subtler and possibly worse: the erosion of the rungs by which people used to acquire the tacit knowledge that the technology cannot supply. The second half of the argument concerns money rather than work, and it is a claim about where profit lands. The weights of a trained model are a file. Files can be copied, distilled, approximated and — increasingly — released for nothing by firms with a strategic interest in giving them away. The cost of reaching a given level of capability has been falling by close to an order of magnitude a year. Nothing that behaves like that can sustain a margin. What cannot be copied is a grid interconnection, a packaging line for high-bandwidth memory, a relationship with a customer's finance department, a licence to practise, a proprietary record of how a particular business actually works. The durable returns from this technology will accrue to those complements, not to the models — which is awkward, because the models are where most of the capital has gone. This book will try to do three things properly and will decline to do several others. It will explain how the numbers everyone quotes are actually manufactured. When a report says that three hundred million jobs are exposed to automation, or that forty per cent of global employment is affected, or that AI will add seven per cent to world output, those figures are the product of a chain of multiplications, each link of which is a judgement call. The reader who understands the chain can evaluate the number; the reader who does not can only choose a side. Explaining the chain is more useful than picking a winner, and it is why this book spends a chapter each on the macro arithmetic and on the occupational exposure indices that feed it. It will present the disputes as disputes. The serious economics of this subject is genuinely unsettled. Daron Acemoglu's calculation yields total factor productivity gains of well under one per cent cumulatively over ten years. Goldman Sachs's yields one and a half percentage points a year for a decade. These are not different opinions about the same estimate; they are different estimates by a factor of more than ten, produced by economists using the same analytical framework and disagreeing about calibration. Where the evidence does not settle a question, this book says so, names the parties, and explains what would settle it. And it will keep the capital and the labour sides of the story in the same frame. They are usually treated as separate literatures — one for the financial press, one for the labour economists — and the separation obscures the most important feature of the situation, which is that the returns to the buildout depend entirely on whether the substitution actually happens. Seven hundred billion dollars a year is justified by a future in which models do a great deal of work that people currently do. The labour-market evidence to date is that models are doing rather less of it than that, rather more slowly, and mostly at the bottom of career ladders where the wages are lowest. Those two facts sit in the same accounting identity, and most commentary manages to discuss only one of them at a time. What this book will not do is forecast. It contains no proprietary model of job displacement and no number for when the sector's capital will earn its cost. It reports the published forecasts, explains their construction and their disagreements, and is explicit that the point estimates they produce vary by an order of magnitude for reasons that are structural rather than accidental. Anyone who tells you confidently what the unemployment rate will be in 2032 is either selling something or has not understood the problem. The honest deliverable is not a number but a map of which parameters the answer depends on, so that a reader can update as the evidence arrives — and the evidence is arriving quickly now, in payroll microdata and firm surveys and depreciation schedules, which is why so much of what follows is dated 2025 and 2026. It is also not a book about whether artificial general intelligence is imminent, whether these systems reason, or what happens if capability keeps compounding. Those are important questions and they are somebody else's. The premises here are deliberately conservative: assume the technology continues to improve at something like its current rate, assume no discontinuity, and ask what follows for output, wages, employment and returns on capital. If a discontinuity arrives, the economics in this book will be beside the point, and so will everyone else's. The reader it is written for is someone who has to make decisions with money or policy or a career riding on them, and who has noticed that the available commentary oscillates between two unusable poles. It assumes no prior acquaintance with task-based models, Hulten's theorem, the elasticity of substitution or the productivity J-curve; each is explained where it first matters. It assumes, instead, the willingness to sit with an argument that does not resolve into a slogan. The most interesting economic question of this decade is not whether the machines can do the work. Increasingly, on a widening set of tasks, they plainly can. It is whether anyone will be able to charge for it. Chapter 1 The Ledger and the Statistic Amazon's guidance for 2026 capital expenditure sits somewhere in the range of a hundred and ninety to two hundred and ten billion dollars. Microsoft's is around a hundred and eighty to two hundred billion. Alphabet raised its ceiling twice during the year, finishing somewhere near two hundred billion, and Meta, which does not sell cloud computing to anyone and has no external customer for any of it, guided to something in the region of a hundred and twenty-five to a hundred and forty-five billion. Together the four have signalled roughly seven hundred billion dollars of capital spending in a single calendar year, against something closer to four hundred billion in 2025 and under two hundred billion as recently as 2022. These are guidance ranges, not audited totals, and they have been revised upward more often than down. But the magnitude is not in dispute, and the magnitude is the point. Annual private fixed investment in the entire United States runs to a few trillion dollars. Four firms are now accounting for a visible fraction of it, and they are directing that fraction at a single technology whose commercial revenues remain, by any conventional accounting, a small multiple of a single year's spending on it. Capital expenditure — capex — is money spent acquiring assets expected to produce income over several years: buildings, machines, in this case accelerators, networking gear, transformers, chillers and substations. It is not an expense in the year it is spent. It sits on the balance sheet and is written off gradually through depreciation, a charge that spreads the cost across the asset's assumed useful life. That accounting convention will turn out to matter enormously, because the assumed useful life of an AI accelerator is a genuinely contested number and the answer moves reported profits by tens of billions of dollars. Against that ledger, set the statistic. What productivity actually measures Productivity is not output. It is output per unit of input, and which input you choose determines what you are measuring. Labour productivity is output per hour worked. It is the number most often quoted because it is the easiest to compute and because it bears most directly on living standards: over long horizons, real wages track labour productivity closely. But labour productivity can rise simply because workers have more equipment to work with. If a firm buys every clerk a faster computer, output per hour rises, and nothing has happened except that capital was substituted for labour at the margin. That is a real gain, but it is not a gain in the efficiency with which the economy converts inputs into outputs. Total factor productivity — TFP — attempts to isolate that residual. It measures the output produced from a given combination of labour and capital together. If TFP rises, the same inputs are producing more, which means something has genuinely improved: better technology, better organisation, better allocation of resources across firms. TFP is the number economists care about when they ask whether a technology is transformative, and it is the number at the centre of the dispute this book keeps returning to. TFP is also, notoriously, a residual: it is what is left over after measured inputs are accounted for. Robert Solow, who invented the framework, called it a measure of our ignorance. Anything that raises output without showing up in the measured input series lands in TFP, including mismeasurement of the inputs themselves. On the numbers, the picture as of 2026 is ambiguous in a specific and frustrating way. Chad Syverson, who has spent a career on productivity measurement, summarises it thus: United States labour productivity grew at roughly one and a half per cent a year through the 2010s, about half the rate achieved during the information-technology boom of 1995 to 2004. From the middle of 2022 onwards it has run at something closer to two point two per cent a year. That is a real acceleration, sustained over several years, and it is the first sign of life the productivity statistics have shown in a long time. It is also almost uninterpretable. The acceleration began when generative AI investment was still modest and adoption was negligible — ChatGPT was released in November 2022, and the first enterprise deployments of any scale came a year or more later. Meanwhile the same period saw an extraordinary burst of business formation, a large reallocation of workers between firms and industries following the pandemic, the unwinding of supply-chain disruption, and a labour market tight enough to push workers toward more productive employers. Any of these could produce a multi-year acceleration of this size. Attribution, here, is not a technicality; it is the whole question. The gap that has to close Put the two numbers in the same sentence and the tension becomes an arithmetic problem rather than a rhetorical one. Capital invested in productive assets has to earn a return. If seven hundred billion dollars of accelerators and datacentre shells are depreciated over, say, five years, that is a hundred and forty billion dollars of annual depreciation charge from one year's spending alone — before power, before staff, before the cost of the capital itself. For that spending to be rational, it must eventually generate revenue streams substantially larger than the cost, which means either that customers pay a great deal more for AI services than they currently do, or that the firms deploying these systems internally capture large enough cost savings to justify the outlay, or both. Neither has visibly happened yet at the required scale. The aggregate revenue of the generative AI industry — model providers, AI-specific cloud capacity, AI features sold as software upgrades — is a fraction of the annual capital spend. That is not, by itself, damning. Infrastructure is built ahead of demand; that is what makes it infrastructure. Railways, electrical grids and fibre-optic networks were all constructed at a loss by their original owners and generated enormous value for everyone afterwards. But the comparison carries a trap, and the trap is depreciation. Rail embankments last a century. Fibre in the ground lasts decades. Accelerators may or may not last five years. Durable overbuild transfers value to the future; rapidly depreciating overbuild destroys it. Which of those two stories applies here is an empirical question about hardware obsolescence, and it is a question on which serious people disagree. The other half of the gap concerns what the technology would have to do to the economy for the optimistic case to hold. Suppose generative AI raised United States labour productivity growth by a percentage point a year for a decade, an assumption well within the range of published forecasts. That is roughly the contribution attributed to the entire information-technology revolution of the late 1990s, a period in which the personal computer, enterprise software, the internet and mobile telephony all arrived together and reorganised nearly every white-collar workplace. It would be an extraordinary outcome from a technology that, five years in, most firms use in three business functions or fewer. Why both numbers are unreliable The honest complication is that neither the ledger nor the statistic means quite what it appears to mean. The capex figures are not a clean measure of resources committed to artificial intelligence. They mix genuinely AI-specific hardware with ordinary cloud capacity that would have been built anyway; they include land, shells and power infrastructure with long lives alongside chips with short ones; and a meaningful share of the headline totals reflects contracts between firms that are also each other's investors and customers. When a chip vendor takes an equity stake in a model developer which then uses the proceeds to buy the vendor's chips, the same dollar appears as investment on one balance sheet and revenue on another. This circularity is not fraud — it is a normal feature of capital-intensive industries in their expansion phase, and vendor financing built the early telecommunications and automobile industries — but it inflates any naive reading of demand. Nor are the numbers all carried where you would expect. A growing share of datacentre construction is being financed through special-purpose vehicles, joint ventures with infrastructure funds and private credit rather than from the hyperscalers' own balance sheets. Morgan Stanley has estimated global datacentre spending on the order of three trillion dollars between 2025 and 2028, with roughly half of it requiring financing from outside corporate cash flow. Structures of that kind move the depreciation and the leverage out of the reported accounts while leaving the operator carrying the demand risk through long-term commitments to pay for capacity. The headline capex number therefore understates the total capital at risk, and the reported earnings of the firms doing the spending overstate what is left after the cost of it. The productivity statistic is unreliable for different reasons. National accounts measure output that is transacted at observable prices. They do a poor job of capturing quality improvement, they largely miss free goods, and — most important here — they treat much of the investment required to make a new technology useful as a current expense rather than as capital formation. When a firm spends six months retraining staff, rebuilding a workflow, rewriting its quality-control procedures and constructing the data pipelines a model needs, it has built an asset. The accounts record a cost. The result is that during the build-out phase of a general-purpose technology, measured output is understated and measured productivity looks worse than reality; during the harvesting phase, the unmeasured capital delivers returns that are attributed to nothing in particular and measured productivity looks better than reality. This is not a convenient excuse invented for the present moment. It is a documented pattern, formalised by Erik Brynjolfsson, Daniel Rock and Chad Syverson as the productivity J-curve, and Syverson's own estimate is that cumulative mismeasurement during such a phase can run into double-digit percentages and persist well beyond a decade. Whether it applies here is exactly what is at issue. The revenue that has to exist There is a third way to state the puzzle, and it is the one an investor would use. Capital markets do not ultimately price technologies; they price cash flows. Work backwards from the spending. Suppose, conservatively, that a dollar of datacentre capital must eventually generate something like thirty to forty cents a year of revenue to cover depreciation, power, maintenance, staffing and a return on capital — a ratio broadly consistent with how existing cloud infrastructure has been financed. A single year's capital spending of seven hundred billion dollars therefore implies an eventual annual revenue requirement in the region of two hundred billion dollars from that year's assets alone, recurring, for as long as those assets are expected to last. Layer several such years on top of each other and the required revenue run-rate climbs toward a number comparable to the entire global market for enterprise software. That revenue does not currently exist. Estimates of total generative AI revenue across model providers, AI-specific cloud capacity and AI features sold within existing software products vary considerably by definition, but on any reasonable accounting the figure is a small fraction of annual capital spending rather than a multiple of it. Bridging that gap requires one of three things to happen, and they have very different implications. Either enterprises pay substantially more for AI services than they do now, which requires the services to displace enough labour cost that the payment is obviously worthwhile — the substitution story, whose evidence is examined at length in this book. Or consumers pay, at a scale that would make AI subscriptions a mass-market utility comparable to mobile telephony. This is possible and is being attempted, but consumer willingness to pay for software has historically been an order of magnitude below enterprise willingness to pay, and the free alternatives are very good. Or the firms deploying these systems internally capture the value as cost reduction rather than paying for it as a service — in which case the revenue accrues to the deploying firm rather than to the infrastructure, and the return on the datacentres has to come from somewhere else. The third possibility is the one that receives least attention and is the most consistent with everything else in this book. It would mean the technology works, the economy benefits, and the capital does not earn its cost. That is not a contradiction. It is what happens when a valuable technology turns out to be cheap to supply. Four questions Stated plainly, the puzzle is this: an enormous and accelerating commitment of capital, premised on a substitution of machines for human labour, is being made in an economy whose aggregate statistics show, at most, an ambiguous acceleration, and whose best micro-level evidence shows genuine but uneven gains that mostly fail to aggregate. Either the capital is wrong, or the measurement is wrong, or the timing is wrong, or the gains are real but landing somewhere other than where the spending assumes. Resolving that requires answering four separate questions, and most commentary fails because it conflates them. The first is a question about tasks. What can these systems actually do, how much better than a human, and for whom? This is the domain of controlled experiments, and the answers are surprisingly well established and surprisingly awkward: large gains, concentrated among the less experienced, in settings that look nothing like most jobs. The second is a question about firms. Why does a fourteen per cent gain on a task become an undetectable gain in a company's accounts? The answer is not that the experiments are fake. It is that a task is not a job, a job is not a process, and a process is not a firm, and value leaks at every one of those boundaries. The third is a question about people. Where is the adjustment actually landing? Here the evidence has changed sharply in the last two years, and it points somewhere almost nobody predicted in 2023: not at the middle-aged clerical worker but at the twenty-three-year-old graduate, and not through dismissal but through a vacancy that never opens. The fourth is a question about capital. If the technology does what its backers expect, who earns the return? This is the question the buildout implicitly answers — the capital is being spent as though the answer is "whoever owns the largest model" — and it is the question where the answer is most likely to be wrong. These questions interlock. The task evidence determines the firm evidence, which determines the labour evidence, which determines whether the revenue exists to justify the capital. The chain runs in one direction, from the microeconomic to the financial, and it is worth noticing that almost all the money is being bet on the far end of a chain whose near end is still contested. What the buildout is really betting on It is worth being explicit about the implicit forecast embedded in seven hundred billion dollars a year. It is not a bet that these systems are impressive. Impressiveness is free. It is a bet that a substantial fraction of the work currently performed by expensive humans in rich economies can be performed instead by a metered service, that the firms currently employing those humans will pay something close to the value of the labour saved, and that the providers of the service will be able to hold a price against competitors doing the same thing with a similar model. Every one of those three clauses is doing load-bearing work, and the third is the weakest. The reason the third is weakest is worth stating now, because the rest of the book keeps returning to it. The cost of achieving any given level of model capability has been falling extraordinarily fast — the Stanford AI Index has documented a reduction of something like two hundred and eighty-fold over roughly two years in the cost of reaching the performance level of an early-generation frontier model. Capability that cost a fortune in 2023 is nearly free in 2026, and capability that costs a fortune now will be nearly free in 2029. A business whose product is access to a level of capability is therefore selling something whose price declines by an order of magnitude a year. Under those conditions, producers capture very little and users capture almost everything — which would be wonderful for the economy and disastrous for the people who paid for the buildings. That possibility — enormous social value, negligible producer surplus — is the outcome the capital markets are least prepared for and the one most consistent with the structure of the technology. It would mean the sceptics are wrong about the technology and right about the investment, and the enthusiasts are right about the technology and wrong about who profits from it. It is not the outcome anyone is positioned for, which is generally a reason to take it seriously. Before any of that can be argued properly, though, the analytical equipment has to be assembled, and the equipment most people are still using was built for a different machine. Chapter 2 What the Routine-Task Model Got Right, and Why It Fails Now In 2003, David Autor, Frank Levy and Richard Murnane published a paper in the Quarterly Journal of Economics that would organise the next twenty years of thinking about technology and work. Its central move was to stop treating jobs as indivisible things that are either automated or not, and to treat them instead as bundles of tasks. A task is a unit of work that produces an output: verifying an invoice, diagnosing a rash, persuading a customer, welding a seam, drafting a clause. A job is a bundle of tasks that a firm has found it convenient to assign to one person. The distinction sounds pedantic and is in fact the whole analytical apparatus, because technologies almost never automate jobs. They automate tasks, and the job survives, reconstituted around whatever is left. Autor, Levy and Murnane then asked which tasks computers could take. Their answer was that computers execute instructions, so a computer can perform a task to the extent that the task can be fully specified as a set of explicit rules. They called such tasks routine — a term that has caused endless confusion, because routine here does not mean repetitive or boring. Sorting mail is repetitive and, in 2003, hard to automate, because it required visual recognition of handwriting. Calculating an actuarial reserve is intellectually demanding and, in 2003, trivial to automate, because the procedure is written down. Routine meant codifiable, nothing more. Everything else fell into two non-routine categories. Non-routine analytical tasks required problem-solving, judgement and the generation of novel solutions — the work of scientists, lawyers, designers, senior managers. Non-routine manual tasks required physical dexterity, environmental adaptation and in-person interaction — the work of cleaners, carers, cooks, drivers. Neither could be written as a rule, so neither could be computerised, and computers therefore complemented the people who did them, raising their productivity and their wages. The hollowing out The prediction that followed was precise. Routine tasks, being codifiable, would be substituted by machines. Non-routine tasks, being resistant, would be complemented. And crucially, routine tasks were not spread evenly across the wage distribution. They were concentrated in the middle: bookkeepers, bank tellers, typists, telephone operators, machine setters, assembly-line workers. These were the well-paid jobs that a person without a degree could get and keep — the industrial and clerical spine of the postwar middle class. The prediction was that the middle would hollow out. Employment and wages would grow at the top, where analytical work was being complemented; they would grow at the bottom, where manual service work was untouchable by software and where displaced middle-earners would compete for jobs; and they would fall in the middle. They did. David Autor, Lawrence Katz and Melissa Kearney documented the U-shaped pattern in United States employment growth by occupational wage rank. Maarten Goos and Alan Manning found the same shape in Britain and gave it the name that stuck: lousy and lovely jobs. Versions of the pattern turned up across the OECD. For roughly three decades from the early 1980s, the routine-task model was about as good as empirical macroeconomics gets — a simple mechanism, a sharp prediction, and international data that obligingly complied. Michael Polanyi had supplied the philosophical reason for the model's central asymmetry four decades earlier, in the observation that "we can know more than we can tell". A skilled radiologist cannot fully explain how she recognises a malignancy; a skilled driver cannot fully explain how he judges a gap. Autor named this Polanyi's paradox and made it the boundary of automation: you cannot program what you cannot articulate. Everything a person could describe, a computer could eventually do. Everything a person merely knew was safe. Displacement, productivity, reinstatement The task framework was subsequently given a fuller economic treatment by Daron Acemoglu and Pascual Restrepo, in a sequence of papers that supplies most of the vocabulary used in the rest of this book. Their formulation identifies three distinct effects of automating a task, and the whole argument about artificial intelligence turns on their relative sizes. The displacement effect is the direct one. A task formerly performed by labour is now performed by capital. Labour demand falls, and with it the share of national income going to workers. This effect is always negative for labour and is the one everyone intuits. The productivity effect runs the other way. Automating a task makes the final good cheaper to produce. Cheaper production means lower prices, higher output, and more demand for all the inputs still required — including labour in the tasks that were not automated. James Bessen's much-cited case is the bank teller: the automated teller machine reduced the number of tellers required per branch, which reduced the cost of operating a branch, which caused banks to open a great many more branches, which meant total teller employment rose for roughly two decades after the ATM's introduction. The mechanism is not that ATMs were harmless; it is that the productivity effect operated through firm entry and swamped the displacement effect for a long time. The reinstatement effect is the slowest and, historically, the most important. New tasks appear in which labour has a comparative advantage, and they appear disproportionately in the industries doing the automating. The mechanised textile industry created overseers, mechanics and quality inspectors. Computerisation created an entire occupational structure — systems administration, database design, user-experience research, information security — that did not exist and could not have been described in 1975. Reinstatement is why two centuries of relentless automation have not produced mass technological unemployment. Acemoglu and Restrepo's most useful contribution to the present argument, though, is the concept they named so-so automation: a technology just good enough to replace a worker and not good enough to produce a meaningful cost saving. The supermarket self-checkout is the canonical instance. It shifts the scanning task from a paid employee to an unpaid customer who performs it worse, generating a modest saving on wages and a modest loss of throughput and accuracy. The displacement effect is real; the productivity effect is close to nil. So-so automation is the worst configuration available: labour loses tasks, and the economy gains almost nothing to redistribute. The possibility that much of generative AI's deployment will be so-so automation — good enough for a firm to cut a role, not good enough to make the firm meaningfully more productive — is the sharpest version of the pessimistic case, and it is not a claim that the technology is unimpressive. It is a claim about where on the quality distribution the deployments will land. The inversion Now the problem. The routine-task model rests on a single premise: that machines can do what can be specified in rules, and only that. Large language models are not built from rules. They are built by fitting an enormous function to an enormous quantity of text, and what they acquire is not a procedure but a statistical representation of how the material they were trained on behaves. This dissolves Polanyi's paradox in one direction without dissolving it in the other, and the asymmetry is the most consequential fact in the economics of this technology. Consider what these systems are trained on. They are trained on text, and text is where humanity writes down what it knows. Case law is written down, in volume, with reasoning attached. Clinical guidelines are written down. Accounting standards, engineering codes, marketing copy, software documentation, financial commentary, undergraduate essays, internal memoranda, diagnostic decision trees and the entire apparatus of professional training are written down, because writing them down is how professions reproduce themselves. A model trained on this corpus does not need the rule to be articulable in advance. It needs only that enough examples exist. So the boundary moved. It is no longer between what can and cannot be reduced to rules. It is between what has and has not been written down. That new boundary cuts across the wage distribution in almost exactly the opposite direction. Highly-paid professional work is more thoroughly documented than mid-wage clerical work, not less, precisely because professions are credentialed, regulated and taught through written material. And physical work — the non-routine manual tasks that the old model considered safe only because computers had no hands — remains safe for the same reason, which is that progress in robotics has been far slower than progress in language. The empirical confirmation came quickly. When Tyna Eloundou, Sam Manning, Pamela Mishkin and Daniel Rock mapped large language model capabilities onto the detailed task descriptions of the United States occupational database, they found that exposure to these systems rises with wages and education. Around eighty per cent of American workers had at least a tenth of their tasks exposed; around nineteen per cent had at least half. The occupations at the top of the exposure ranking were not cashiers and assembly workers. They were mathematicians, tax preparers, writers, web designers, accountants, legal secretaries, financial analysts and public relations specialists. The occupations at the bottom included dishwashers, roofers, stonemasons, short-order cooks and motorcycle mechanics. Half a century of automation anxiety had been pointed at the wrong end of the labour market. The radiologist who was not replaced The clearest single illustration of how badly the old boundary now performs is a prediction made in 2016 by Geoffrey Hinton, one of the people most responsible for the deep-learning revolution. Speaking about the rapid progress of convolutional neural networks on medical image classification, he suggested that we should stop training radiologists, because within five or ten years deep learning would do the job better. The technical prediction was substantially correct. Image classification models now match or exceed human performance on many narrowly specified detection tasks, and they are deployed clinically. The economic prediction was wrong in the other direction. Radiology employment has grown. Radiology residency positions have expanded. Radiologist compensation has risen, and in several health systems the specialty is among the hardest to recruit into. The reasons expose every filter between technical capability and labour-market outcome. Reading images is only part of what a radiologist does; the rest is protocolling studies, integrating findings with clinical history, communicating with referring physicians, performing image-guided procedures, and taking legal responsibility for a diagnosis. Demand for imaging has risen faster than the productivity of reading it, partly because cheaper interpretation encourages more scanning. Regulatory approval of clinical algorithms is slow and narrow, so each approved model addresses one finding on one modality rather than a whole study. And liability requires a named human signature, which reintroduces most of the cost that automation was supposed to remove. The instructive part is not that Hinton was wrong about the technology. He was right about the technology. He was applying the old boundary — perception is hard for machines, so once machines can perceive, the perceiving professions go — to a case where perception was the visible part of the job rather than the valuable part. Exactly the same error is available now, in the other direction, to anyone who assumes that because a model can draft a contract, contract lawyers are finished. Codified and tacit The distinction that does the real work here is between codified and tacit knowledge, and it is worth stating carefully because the rest of the book leans on it. Codified knowledge is knowledge that has been made explicit and recorded: what the statute says, how the procedure runs, what the standard requires, how this kind of document is normally structured. It is acquirable by study. It is what examinations test. It is, overwhelmingly, what constitutes the formal content of professional training. Tacit knowledge is knowledge acquired through doing and not fully articulable: knowing which of the twelve applicable precedents the judge in this jurisdiction actually cares about; knowing that this client says "interesting" when they mean "no"; knowing that a plausible-looking output is wrong because the underlying data collection changed definitions in 2019; knowing which exception matters and which is noise. It is what distinguishes the fifth-year associate from the first-year associate, and it is the substance of the experience premium that every professional labour market pays. Generative AI is superb at the first and structurally weak at the second, and the weakness is not a temporary limitation of scale. Tacit knowledge is, by construction, the residue of what was never written down. A system trained on written material cannot acquire it from the training data, because it is not there. It can be acquired only from feedback in the specific environment — which is possible in principle and enormously harder in practice, because in most professional settings the feedback is slow, noisy, confounded and arrives long after the decision. The consequence, stated as a proposition: generative AI substitutes for codified knowledge and complements tacit judgement. Expertise, diluted and extended David Autor has pushed this into its most useful form. The scarce and valuable thing in an economy, he argues, is not labour but expertise — the capacity to make judgements that most people cannot make, protected by the cost of acquiring it. Wages are, in large part, the rent on expertise. Technologies matter according to what they do to that rent. In work with Neil Thompson, Autor has formalised the point in a way that explains an otherwise baffling pattern in the data. Take a job and rank its tasks by the expertise they require. If a technology automates the least expert tasks in the bundle, the worker is left doing the more demanding remainder; the expertise required by the job rises, and so do wages. If it automates the most expert tasks — if it performs the judgement that was the reason the job existed — then the remaining work is routine coordination, the expertise required falls, and so do wages, even as employment in the occupation may rise. This is why the same technology can raise one occupation's wages and cut another's, and why the aggregate effect on inequality is genuinely indeterminate rather than merely uncertain. The historical example Autor uses is the transformation of typesetting: the skilled compositor's craft was destroyed by desktop publishing, while the demand for people who could lay out a page rose enormously, at much lower wages. The same technology, expertise diluted. Apply this to generative AI and the optimistic and pessimistic readings become precise rather than temperamental. The optimistic reading — Autor's own — is that these systems lower the cost of expertise, letting people without the expensive credential exercise judgement that previously required it, which would widen access to well-paid work and compress inequality. The pessimistic reading is that in professional occupations, the codified component is the expertise that the credential certifies, so automating it dilutes the occupation and drags wages down toward the value of the tacit residue. Which of these obtains is not a matter of opinion about technology. It depends on where in a given occupation's task hierarchy the automatable material sits, and that varies enormously by occupation. It is high in the hierarchy for a paralegal, a junior analyst, a translator, a first-pass coder. It is low in the hierarchy for a surgeon, a trial lawyer, a plant manager, a skilled negotiator, whose codified knowledge is a precondition for the job rather than its point. What the old model still gets right None of this means the task framework is wrong. It means the framework was right and the empirical premise plugged into it has changed. Tasks are still the unit of analysis; displacement, productivity and reinstatement are still the three effects; so-so automation is still the worst case. What has changed is the mapping from tasks to automatability, and therefore the incidence. Two implications follow immediately and neither is obvious. The first is that the standard policy response is aimed at the wrong target. Forty years of technology-and-work policy has consisted of recommending more education, on the reasonable grounds that education moved workers out of the routine middle and into the complemented top. If exposure now rises with education, the recommendation is at best neutral and at worst counterproductive — not because education is worthless, but because the specific thing formal education transmits most efficiently is codified knowledge, which is the substitutable part. The second is that the adjustment should be expected to appear first among the least experienced workers in exposed occupations, and to appear as a hiring effect rather than a firing effect. An experienced professional's value rests substantially on the tacit component, which is complemented; a new entrant's value rests almost entirely on the codified component, which is substituted, and whose function within the firm was partly to be the apprenticeship through which tacit knowledge was acquired. The firm does not need to dismiss anyone to adjust. It simply hires fewer of them. That is a testable prediction, it was made before the evidence arrived, and it is where the labour-market data have in fact landed. Chapter 3 The Experiments Five thousand one hundred and seventy-nine customer support agents at a Fortune 500 software company were given access to a conversational assistant built on a large language model. The rollout was staggered across teams over several months, which meant that at any moment some agents had the tool and some did not, and the difference between them could be attributed to the tool rather than to the season, the product or the state of the market. Erik Brynjolfsson, Danielle Li and Lindsey Raymond measured what happened to issues resolved per hour. The average agent resolved about fourteen per cent more. That figure is now the most-cited number in the economics of generative AI, and it is the least interesting thing in the paper. The interesting thing is the distribution. Agents in the bottom skill quintile — the newest, the worst-performing, those in their first months on the job — improved by around thirty-four per cent. Agents in the top quintile improved by essentially nothing, and by some specifications slightly less than nothing. The tool did not make good agents better. It made bad agents good. The authors' explanation is the cleanest statement available of what these systems do to organisations. The model had been fine-tuned on the firm's own conversation transcripts, which meant it had absorbed the accumulated practice of the best agents — the phrasings that de-escalated, the diagnostic sequences that worked, the knowledge of which fix to try third. That practice was tacit in the sense that nobody had written it in a manual, but it was not tacit in the sense that mattered: it had been recorded, incidentally, in the exhaust of the firm's own operations. The model read the exhaust and handed the expertise back to the novices. Two further findings deserve more attention than they get. Customer sentiment improved, which suggests the gain was not achieved by rushing. And attrition fell, particularly among newer agents, which has an obvious mechanism — the job became less miserable — and a less obvious consequence: a firm that retains its novices longer accumulates the tacit knowledge it would otherwise lose, and an experienced agent is more valuable than a model-assisted novice at the hard end of the distribution. Writing, coding, consulting The pattern replicates across the controlled evidence. Shakked Noy and Whitney Zhang ran four hundred and fifty-three college-educated professionals — marketers, grant writers, consultants, data analysts, human-resources staff — through mid-level professional writing tasks of the kind they actually did at work: a press release, a short analysis, a departmental memorandum. Half were given access to ChatGPT. Time to complete fell by roughly forty per cent. Independent graders rated the output about eighteen per cent higher. And, once again, the variance compressed: the workers who had scored worst without the tool improved most with it, so inequality in measured output between workers fell. Sida Peng, Eirini Kalliamvakou, Peter Cihon and Mert Demirer randomised access to GitHub Copilot among developers asked to implement an HTTP server in JavaScript. Those with the tool finished around fifty-six per cent faster. It is the largest productivity effect in the literature and it should be read with its conditions attached: a self-contained, precisely specified, greenfield task, of a kind extremely well represented in the training data, with an unambiguous test of correctness. This is as close to the ideal case as software engineering gets. The most informative experiment is the one that was designed to find the edge. Fabrizio Dell'Acqua, Edward McFowland, Ethan Mollick, Hila Lifshitz-Assaf, Katherine Kellogg and colleagues, working with Boston Consulting Group, randomised seven hundred and fifty-eight consultants across a set of realistic tasks. On tasks that fell inside the model's capabilities — generating product concepts, drafting go-to-market copy, writing a persuasive memorandum — consultants with GPT-4 completed about twelve per cent more tasks, around twenty-five per cent faster, at a quality rated more than forty per cent higher by human graders. These are extraordinary numbers for knowledge work performed by people who are already selected for ability. Then the researchers included a task deliberately placed outside the frontier. It required reconciling quantitative data from a spreadsheet with qualitative material from interview transcripts, and it was constructed so that the obvious quantitative answer was wrong and the correct answer depended on information available only in the interviews. On that task, consultants using the model were about nineteen percentage points less likely to reach the right answer than those working unaided. The model produced a confident, well-structured, plausible and incorrect analysis, and the consultants adopted it. The authors called the capability boundary a jagged technological frontier: irregular, unpredictable, and — critically — invisible from the outside. Two tasks that appear equally difficult to a human can sit on opposite sides of it. A worker cannot tell which side a task is on without already knowing the answer, which is precisely the situation in which trusting the tool is most dangerous. Dell'Acqua and colleagues also identified two viable working patterns among the successful consultants. Centaurs divided the work, assigning whole subtasks to the model or to themselves according to a judgement about where the frontier lay. Cyborgs interleaved continuously, checking and redirecting at every step. Both outperformed the naive user who delegated and accepted. Both require the user to hold a model of the model, which is itself a form of tacit knowledge acquired through use. The results that go the other way A literature consisting entirely of large positive effects would be suspicious, and this one does not. In July 2025, METR published a randomised controlled trial of sixteen experienced open-source developers working on two hundred and forty-six real tasks in repositories they themselves maintained — mature codebases of hundreds of thousands of lines, with established conventions, long histories and implicit constraints known only to the maintainers. Tasks were randomly assigned to permit or forbid AI assistance. The developers took roughly nineteen per cent longer on the tasks where they were allowed to use AI tools. The finding that matters most is not the slowdown; it is the perception gap. Before the study, the developers forecast that AI would speed them up by around twenty-four per cent. Afterwards, having been slowed down, they estimated that they had been sped up by about twenty per cent. They were wrong about their own experience by roughly forty percentage points, in a domain where they were experts, on tasks they performed daily. The study has real limitations and its authors state them: sixteen developers is a small sample; they were unusually expert; the codebases were unusually mature; and the tooling was that of early 2025, which is several generations behind current practice. METR themselves published a note in February 2026 revising their experimental design. The result should not be used to claim that AI does not help programmers — the Copilot trial says otherwise, in the same broad domain. It should be used for the thing it demonstrates cleanly, which is that the sign of the effect depends on the setting, and that self-reported productivity gains are worthless as evidence. The reason the two coding studies point in opposite directions is visible in their designs. Writing an HTTP server from scratch is a task where the model's training data contains thousands of near-identical solutions and where the constraints are fully specified in the prompt. Fixing a subtle bug in a codebase you have maintained for six years is a task where the relevant constraints live in your head, the model cannot see them, and the cost of explaining them exceeds the cost of doing the work. The first is codified. The second is tacit. This is the chapter's thesis arriving twice from opposite directions. The broadest sceptical result comes from Denmark. Anders Humlum and Emilie Vestergaard linked survey responses to administrative records covering roughly twenty-five thousand workers across seven thousand workplaces, in eleven occupations selected because they were thought highly exposed — including software developers, journalists, marketing professionals, accountants, lawyers and teachers. Adoption had been fast and widespread. Time savings averaged something like three per cent of working hours. There was no significant effect on earnings, and none on hours worked. Three per cent of hours is not nothing, but it is an order of magnitude below what the experiments would predict. This is the single most important datapoint in the sceptical case, and it is important precisely because it does not contradict the experiments. It measures a different thing: not what the tool can do to a task under observation, but what happens to a worker's week when the tool is available and the job, the process, the client expectations, the regulatory constraints and the organisational chart all remain exactly as they were. Table 1: The controlled evidence on task-level productivity Study Setting and sample Design Headline effect Where the effect concentrated Brynjolfsson, Li & Raymond 5,179 customer support agents, software firm Staggered rollout across teams +14% issues resolved per hour +34% for least-experienced agents; ~zero for most experienced Noy & Zhang 453 college-educated professionals, mid-level writing tasks Randomised access to ChatGPT Time −40%; graded quality +18% Largest gains for the weakest writers; between-worker inequality fell Peng, Kalliamvakou, Cihon & Demirer Developers implementing an HTTP server in JavaScript Randomised access to GitHub Copilot +56% faster completion Greenfield, fully specified task with an objective correctness test Dell'Acqua et al. 758 Boston Consulting Group consultants Randomised access to GPT-4 across realistic tasks Inside the frontier: +12% tasks, −25% time, +40% quality Outside the frontier: 19 percentage points less likely to be correct METR 16 experienced maintainers, 246 tasks in mature open-source repositories Randomised permission to use AI tools per task −19% (slower with AI) Participants believed they had been 20% faster Humlum & Vestergaard ~25,000 workers, ~7,000 Danish workplaces, 11 exposed occupations Survey linked to administrative records ~3% of hours saved; no effect on earnings or hours Whole-job measurement rather than isolated tasks What the experiments actually establish Read together rather than cherry-picked, this literature supports four propositions with reasonable confidence. The first is that the gains are real and sometimes very large. Anyone arguing that generative AI is a parlour trick has to explain away a set of well-designed randomised trials with large samples and clean identification, and they cannot. The second is the compression result, which is the most robust finding in the field. In customer support, in professional writing, in consulting and in several smaller studies, the least capable workers gain most and the most capable gain least or not at all. This is what you would expect if the model's function is to supply codified best practice to people who have not yet internalised it. It has an uncomfortable corollary: the tool's value to a firm is greatest where its workforce is weakest, which is not where the highest wages are, and therefore not where the largest cost savings sit. The third is that the effect is conditional on task structure in a way that can flip its sign. Gains are largest where the task is self-contained, where the specification is complete, where the model's training data contains close analogues, where output quality is cheaply verifiable, and where errors are recoverable. Gains shrink or become losses where the binding constraints are unstated, where the relevant context lives in the worker's head or in systems the model cannot see, where verification is expensive, and where a confident wrong answer is costly. There is a corollary to the third proposition that firms consistently miss. The conditions favouring large gains and the conditions favouring large losses are not symmetric. A task inside the frontier yields a bounded gain — you cannot save more than the time the task took. A task outside it yields an unbounded loss, because a confident wrong answer propagates: it is incorporated into a decision, cited in a document, relied on by someone downstream, and discovered late. Expected value calculations that average the two therefore understate the risk, and the organisations that have been burned are almost all organisations that measured the average rather than the tail. The fourth is that people cannot tell the difference. The METR perception gap is not an isolated curiosity; it is consistent with a long literature on the unreliability of self-assessed productivity, and it has a direct practical implication. Enterprise adoption decisions are overwhelmingly made on the basis of user satisfaction surveys and pilot enthusiasm. Those instruments are measuring how pleasant the tool is to use, which correlates with time saved only loosely and can correlate negatively with quality. Four objections worth taking seriously Before drawing conclusions from this literature, four criticisms deserve answers, because each would alter what the evidence supports. The first is novelty. Participants in these studies knew they were using a new and much-discussed tool, often for the first time. Enthusiasm raises effort, and effort raises measured output. This is a genuine concern for the short randomised trials, and it is the main reason the Brynjolfsson, Li and Raymond study carries disproportionate weight: it ran for months across a staggered rollout, and the gains persisted and in fact grew as agents learned to use the system. Novelty effects decay; that one did not. The second is task selection. Researchers choose tasks that can be completed inside an experimental session, graded reliably, and randomised cleanly. That selection filter systematically favours self-contained work with verifiable output — which is precisely the category where these systems do best. The sample of tasks in the literature is not a random draw from the economy's tasks. It is a draw from the tractable tail, and any extrapolation from it to the aggregate overstates the mean. This is the sharpest methodological criticism available and it is why the whole-job studies matter so much. The third is publication and reporting incentives. A large positive effect from a prominent technology is publishable, presentable and useful to the firms that grant researchers access to their operations. A null result is none of these. It is notable that the most striking negative result in the field came from an organisation whose purpose is evaluation rather than academic publication, and that it was published as a blog post and a preprint rather than routed through a journal. The fourth cuts the other way. All of these studies used models that are now several generations old. The BCG experiment used GPT-4 in its original form; the METR trial used tooling from early 2025. Capability has improved substantially since, particularly on exactly the dimensions that determined the negative results — handling long context, working within an existing codebase, recognising the limits of one's own knowledge. It is entirely possible that the jagged frontier has moved far enough that the outside-the-frontier task in the consulting experiment now falls inside it. This is the strongest argument for treating the experimental literature as a lower bound rather than an estimate, and it is why the field needs replication on a rolling basis rather than a settled answer. Taken together, the objections do not cancel. Selection and novelty push the measured effects up; model vintage pushes them down. What survives is the structure of the findings — who gains, under what conditions, and where the sign flips — rather than any particular effect size. The gap the rest of the book has to explain Here is the difficulty. Every study above measures a task. The Danish study measures a week. The first set finds effects between twelve and fifty-six per cent; the second finds three per cent. Both are well executed. Both are probably right about what they measured. A worker whose writing takes forty per cent less time has not had their workload cut by forty per cent, because writing is one of several things they do and rarely the binding one. A support agent resolving fourteen per cent more tickets increases the firm's output only if there are fourteen per cent more tickets to resolve, or if the firm reduces headcount, or if agents are redeployed to work that generates revenue. A consultant producing higher-quality decks does not obviously produce more billable value, because the client pays for engagements, not slides. The arithmetic of aggregation is brutal and it runs in one direction. Take a very generous assumption: a thirty per cent productivity gain on the tasks affected. Suppose those tasks account for a quarter of a worker's time — itself optimistic for most jobs. The worker's time falls by seven and a half per cent. Now suppose the affected occupations account for a fifth of the wage bill. The economy-wide labour-cost saving is one and a half per cent, spread over however many years adoption takes, and that is before asking whether the saved time is converted into anything of value or simply absorbed. That is the calculation at the heart of the most important dispute in this field, and it is the reason a technology can be genuinely revolutionary at the level of the task and barely visible at the level of the nation. The gap is not evidence that the experiments are wrong. It is evidence that something systematic happens between the task and the firm, and understanding what that something is matters more than any individual effect size in this chapter. Hashtags: #TheEconomicsOfGenerativeAI #GenerativeAI #ArtificialIntelligence #AIEconomics #MarketDisruption #LaborSubstitution #FutureOfWork #LaborMarketTransformation #AIAndEmployment #TechnologicalUnemployment #AutomationEconomics #TaskBasedAutomation #AIProductivity #ProductivityGrowth #TotalFactorProductivity #AIInvestment #AIInfrastructure #CapitalExpenditure #DigitalEconomy #KnowledgeWorkAutomation #CodifiedKnowledge #TacitKnowledge #LaborMarketDisplacement #SkillBiasedTechnologicalChange #AIAndWageInequality #EconomicTransformation #HumanAICollaboration #AIAdoption #AIIndustryCompetition #EconomicsOfInnovation

Download the Book (PDF): Introduction In May 2019 the United States Food and Drug Administration approved Zolgensma, a single intravenous infusion that delivers a working copy of the SMN1 gene to infants with spinal muscular atrophy. Before disease-modifying treatment existed, most children with the severest form of the condition died or needed permanent breathing support before their second birthday. Novartis set the list price at $2.125 million, and for a time it was the most expensive medicine ever sold. The company defended the figure by pointing to what it would replace: years of chronic therapy, hospital care and ventilation, and, above all, the death of a child. Critics replied that the price bore no visible relation to what the therapy had cost to develop or to make, and that a price justified by the value of a child's life could justify almost any number at all. Both sides were describing something real. That is the problem this book sets out to untangle. Rare diseases are individually uncommon and collectively ordinary. A large epidemiological analysis of the Orphanet database, published in 2020, estimated that between 3.5 and 5.9 percent of the world's population, somewhere between 263 and 446 million people, lives with one of the roughly six thousand rare diseases then catalogued. Around seven in ten of those conditions are genetic, and a similar share begin in childhood. Most still have no approved treatment. For a family receiving one of these diagnoses, the question is rarely how much a drug costs. It is whether anyone has ever bothered to make one. For most of the twentieth century the honest answer was no. Pharmaceutical development is a business of large fixed costs and small marginal costs, and it rewards products that can be sold to millions. A disease affecting a few thousand people offered no prospect of recovering the cost of a clinical programme, so companies left promising compounds on the shelf and patient groups were left to beg. In 1983 the United States changed the terms of the deal. The Orphan Drug Act offered companies seven years of market exclusivity, tax credits on clinical trial costs and regulatory assistance in exchange for developing medicines for conditions affecting fewer than 200,000 Americans. Japan, Australia and the European Union followed with their own versions. The bargain was explicit: society would tolerate a monopoly, and the high prices that come with it, if that was what it took to get the drugs made. The success that became a problem The bargain worked, arguably beyond anyone's expectations. In the decades before the Act only a handful of medicines for rare conditions reached the American market each decade. Today rare disease drugs are not a niche but the centre of the industry's innovative output. Of the 46 novel medicines approved by the FDA's drug centre in 2025, 25 carried orphan designation. Gene therapies, antisense oligonucleotides, enzyme replacements and precision small molecules have transformed the outlook for conditions such as cystic fibrosis, spinal muscular atrophy, haemophilia and transthyretin amyloidosis. Children now walk who would once have died in infancy. The same incentives, however, produced effects nobody designed. Prices rose to levels that would have been unimaginable in 1983, with annual treatment costs of several hundred thousand dollars becoming routine and one-time gene therapies now listed at between two and four million dollars. Companies learned to divide common diseases into rare subsets, to seek orphan status for old drugs that had been used off-label for years, and to accumulate multiple orphan indications for single products that went on to earn billions. Some of the best-selling medicines in the world carry orphan approvals. What began as a narrowly targeted fix for market failure has become one of the main commercial strategies of the pharmaceutical industry. This creates a genuine dilemma for health systems. A public insurer or a national health service cannot simply refuse to pay for a medicine that saves a child's life, and yet it cannot write a blank cheque either, because every pound or euro spent on one patient is unavailable for others. Health economists have spent three decades building tools, most notably cost-effectiveness analysis based on quality-adjusted life years, to make those trade-offs consistent and transparent. Orphan drugs break those tools. When a drug costs several hundred thousand dollars a year, it rarely falls within conventional thresholds of value, and yet most societies are unwilling to say that people with rare conditions should go untreated because there are too few of them. The argument of this book The argument running through these chapters is that the price of an orphan drug is not discovered in a market but settled through a negotiation among institutions, and that the question which matters is how those institutions are designed. The Orphan Drug Act and its imitators did not remove market failure; they replaced it with an administered monopoly, and monopolies do not price themselves. Every orphan price that reaches a patient reflects a series of choices: how long exclusivity lasts and what it covers, how regulators judge evidence from small trials, how assessment bodies weigh rarity and severity, how payers structure payment for one-time cures, and whether anyone at the table has the authority to say no. Where those institutions are well designed, patients get access to genuinely new medicines at prices that reward real innovation. Where they are poorly designed, society pays monopoly rents for repackaged molecules while patients with truly neglected conditions still wait. Seeing prices this way has practical consequences. It means the debate is not a binary choice between rewarding innovation and controlling cost. It is a question of paying for the right things. A regime that pays generously for the first effective therapy for an untreated fatal disease, and far less for a new orphan indication of a drug already earning billions, is not anti-innovation. It is a more precise instrument than the one we have. The chapters proceed in a logical order. The first explains why markets neglect rare diseases in the first place, drawing on the economics of fixed costs, small populations and uncertain evidence. The second describes the legislative bargain, beginning with the American law of 1983 and moving through the European, Japanese and newer Chinese and British frameworks. The third assesses what those incentives have bought, including their unintended consequences and the recent American decisions to protect orphan drugs from Medicare price negotiation. The fourth examines how orphan drugs are actually priced and why price rises as patient numbers fall. The fifth confronts the ethics of multimillion-dollar gene therapies, including the uncomfortable fact that several of them have been withdrawn from markets because health systems would not pay. The sixth turns to the financing tools that have emerged to pay for one-time treatments, from outcomes-based contracts to the American government's model for sickle cell gene therapy. The seventh examines how nationalised and social insurance systems, particularly in the United Kingdom, Germany, France and Italy, decide which orphan drugs to fund. The eighth looks at reforms now under way and at models, including academic manufacturing and individualised genetic medicines, that could loosen the grip of the monopoly bargain. Who this book is for The book is written for readers who need to understand this field without being specialists in it: clinicians and hospital managers who meet these prices in their budgets, civil servants and politicians who must defend funding decisions, investors and industry professionals who want to see how the policy environment is shifting, patient advocates who carry the burden of these negotiations, and students of health policy. It assumes no training in economics or pharmacology. Technical terms are explained where they first appear, and a short glossary at the end collects the essentials. It takes the position that everyone in this debate is responding rationally to the rules they face. Companies price to the limit of what payers will bear because the law and their shareholders encourage them to. Payers resist because their budgets are finite and their duty runs to the whole population. Patients and families fight because their lives depend on it. Nobody needs to be a villain for the outcome to be unsatisfactory. If the outcome is to change, the rules must change, and changing them well requires understanding how they work. The facts in this field move quickly. The European Union has spent three years negotiating the first overhaul of its orphan legislation in a quarter-century, and the United States reauthorised its paediatric priority review voucher programme and narrowed orphan exclusivity in early 2026 while simultaneously widening the orphan exemption from Medicare price negotiation. The analysis here reflects the position as of 2026. The underlying economics change more slowly than the statutes, and those economics are the reason for writing. Chapter 1: Why Markets Orphan Diseases The phrase "orphan drug" was coined to describe medicines that existed in principle, sometimes even in laboratories, but that no company would adopt. It is worth being precise about why. The neglect of rare diseases was not caused by indifference among scientists or cruelty among executives. It followed directly from the cost structure of pharmaceutical development and from the way that structure interacts with the size of a market. Understanding that interaction is the necessary starting point for any discussion of incentives and pricing, because every policy instrument in this field is an attempt to alter one of its terms. The arithmetic of fixed costs A new medicine is expensive to discover and cheap to copy. Almost all of the cost of bringing a drug to market is incurred before the first patient receives a commercial dose: laboratory research, toxicology studies, manufacturing development, three phases of human trials, regulatory submissions and the building of a supply chain. Estimates of the average cost vary widely depending on method and on whether the cost of failures and of capital is included. The most widely cited study, from the Tufts Center for the Study of Drug Development, put the capitalised cost per approved drug at roughly $2.6 billion in 2013 dollars. Independent analyses using public filings have produced lower figures, often in the range of one billion dollars or less, and costs for individual products can be far smaller. Whatever the true average, the central fact is that these are fixed costs. They do not rise much if the drug is later sold to ten times as many people. Once a drug is approved, the marginal cost of producing each additional dose is usually small relative to the price. For a conventional small-molecule tablet it may be pennies. For a biological product it is higher, and for a personalised cell therapy it can be substantial, but even there the bulk of the investment lies upstream. This cost structure means that a company's decision to develop a drug depends on whether the expected revenue, across the whole period in which it can sell the product before competition arrives, will exceed the expected fixed cost, adjusted for the risk of failure and the time value of money. Revenue is price multiplied by volume. For a common disease, volume is large, so a moderate price can recover even a very large fixed cost. For a rare disease, volume is small by definition. If a condition affects three thousand people in the United States, and perhaps ten thousand across the wealthy markets that together make up most global pharmaceutical revenue, then recovering a development cost of several hundred million dollars requires either a very high price per patient, a very long period of sales, or both. Before 1983, companies generally assumed that such prices would be neither tolerated by payers nor defensible in public. They therefore did not start the programmes. The market was not failing to reward rare disease drugs that existed; it was failing to create them. There is a subtlety here that matters later. The fixed cost of development is not independent of disease size. Trials for rare diseases are often smaller, because there are fewer patients to enrol and because effects in severe monogenic conditions can be large enough to detect in small samples. Some studies suggest that the clinical costs of orphan development are lower than for common diseases, though estimates vary and the evidence is contested. What is not contested is that fixed costs fall far less steeply than market size. A trial with one hundred patients is not one hundredth the cost of a trial with ten thousand, because much of the expense lies in site setup, regulatory work, manufacturing and toxicology, which do not scale with enrolment. The result is that the ratio of fixed cost to potential patients rises sharply as diseases become rarer. Beyond cost: the special frictions of rarity If fixed costs were the only obstacle, a sufficiently high price would always solve the problem. In practice rare disease development faces additional frictions that raise risk and deter investment even when prices are high. The first is ignorance about the disease itself. For a common condition, decades of clinical experience have produced detailed knowledge of how the disease progresses, which measurements track its severity, and what counts as a meaningful improvement. For many rare conditions none of this exists. Physicians may see only a handful of cases in a career. There may be no agreed diagnostic criteria, no validated outcome measure and no published natural history, which is the record of how the disease behaves without treatment. A sponsor designing a trial must often build this knowledge from scratch, which adds years and cost, and faces the risk that regulators will not accept the endpoints it chooses. The second is the difficulty of finding patients. Many rare diseases take years to diagnose. Surveys by patient organisations in Europe and the United States have repeatedly found that families move through multiple specialists and misdiagnoses before receiving a correct diagnosis, a process often called the diagnostic odyssey. Patients are scattered across countries and treated at different centres, so trials must be run internationally with few participants at each site. Recruitment becomes the rate-limiting step. Every month of delay consumes patent life and adds cost. The third is the statistical problem of small samples. The conventional architecture of drug approval rests on randomised controlled trials large enough to distinguish a real effect from chance. When the entire population with a condition may number a few hundred, and when randomising a child with a fatal disease to placebo raises obvious ethical objections, sponsors and regulators must rely on single-arm trials, comparisons with historical controls and surrogate markers. These designs carry more uncertainty, both about whether a drug works and about whether it will be approved. Investors price uncertainty as risk, and risk raises the return they demand. The fourth is heterogeneity. Rare diseases are frequently not single entities. The same clinical syndrome can arise from hundreds of different mutations in a gene, each producing different severity and responding differently to treatment. A therapy designed around one mechanism may work in some patients and not others. This fragments already small populations still further. The epidemiology makes this fragmentation vivid. The 2020 analysis of the Orphanet database found that the distribution of patients across rare diseases is extremely skewed. About 150 conditions, roughly four percent of those for which prevalence data existed, accounted for around four fifths of all people living with a rare disease. The great majority of the remaining conditions each affect fewer than one person in a million. For commercial purposes, then, the world of rare disease consists of a few hundred conditions that are rare but not tiny, whose populations are large enough to sustain a business if prices are high, and thousands of conditions so small that no conventional business model could ever serve them. A great deal of confusion in public debate comes from treating these two groups as one. Orphan policy has been far more successful at drawing investment into the first group than into the second, and the arguments that justify high prices for the second group are often borrowed by products in the first. Delay in diagnosis compounds the problem. Surveys conducted by EURORDIS, the European alliance of rare disease patient organisations, have repeatedly found average times from first symptoms to confirmed diagnosis measured in years rather than months, with many patients receiving at least one wrong diagnosis along the way. For a developer, undiagnosed patients are invisible patients. They cannot be recruited into trials, they do not appear in market forecasts, and they will not be treated even when a therapy exists. The spread of genome sequencing and of newborn screening is beginning to change this. When spinal muscular atrophy was added to newborn screening programmes in the United States and several European countries, the number of infants identified early rose, and so did the population that could benefit from treatment before irreversible nerve damage. Diagnostic infrastructure, in other words, is part of the market for rare disease drugs, and it is usually built with public money. The same is true of natural history knowledge. Much of what is known about the untreated course of rare diseases comes from registries built by patient organisations and academic networks, often over decades. The Cystic Fibrosis Foundation's patient registry in the United States, which has tracked the health of people with the disease since the 1960s, is the best-known example, and it proved essential when companies came to design trials. Such assets reduce the cost and risk of development for every sponsor that uses them. They are a form of public or charitable investment that rarely appears in discussions of who paid for a drug. Taken together, these frictions explain why the private market left rare diseases alone even in cases where the science was ready. The problem was not solely that the reward was small. It was that the reward was small, uncertain and distant, while the cost was large, certain and immediate. Market failure and its remedies Economists describe this situation as a form of market failure, although it is worth being careful about the term. In a narrow sense the market is doing exactly what markets do: allocating investment toward the highest expected returns. The failure is relative to a social objective. Most societies believe that people with rare diseases have the same moral claim to treatment as people with common ones, and that a child's life does not count for less because her condition affects few others. If that belief is held, then a market that systematically neglects rare diseases is producing an outcome society does not want, and some intervention is justified. There are two broad families of intervention. The first, often called push incentives, lower the cost of development directly: public research funding, tax credits for clinical trials, grants, regulatory advice and fee waivers. Push incentives are paid whether or not a drug succeeds, which reduces the investor's risk but also means that the public pays for failures. The second family, pull incentives, increase the reward for success: market exclusivity, patent extensions, guaranteed purchase commitments, prizes and transferable vouchers. Pull incentives are paid only if a drug reaches the market, which aligns reward with results but leaves the developer bearing the risk. Market exclusivity is by far the most important pull incentive in rare disease policy, and it has a particular character that shapes everything else in this book. Unlike a prize, which the public pays directly and can size deliberately, exclusivity rewards the developer through the prices that patients and payers pay during the protected period. The size of the reward is therefore not set by legislators. It is set by the company's pricing decision, constrained only by what payers will bear. Exclusivity delegates the decision about how much society should pay for a rare disease drug to the holder of the monopoly. Other designs were available in principle. A government could offer a cash prize for the first approved treatment for a qualifying condition, set in advance and paid from public funds, leaving the product to be sold at a modest price. It could commit in advance to purchase a certain quantity at an agreed price, as donors later did for pneumococcal vaccines for low-income countries through an advance market commitment launched in 2009. It could fund development directly and license the results. Each of these approaches separates the reward to the developer from the price paid by patients, which economists call delinkage. Each also requires the public to specify in advance what it is buying and how much it is willing to pay, and to find the money in a budget. Exclusivity required none of this. It allowed legislators to create a reward without appropriating a dollar, which is a large part of why every major jurisdiction chose it. Push incentives have not disappeared. Public research funding, through bodies such as the National Institutes of Health in the United States and the European Union's successive research framework programmes, underpins much of the basic science on which rare disease drugs depend. International coordination has also grown: the International Rare Diseases Research Consortium, launched in 2011 by the European Commission and the National Institutes of Health, set a goal of accelerating diagnosis and therapy development across participating countries. But push funding typically stops at the point where a candidate therapy needs expensive late-stage trials, which is exactly the point at which private capital, attracted by the prospect of exclusivity, takes over. In 1983 this seemed a reasonable choice. Legislators wanted to encourage development without committing large sums of public money, and exclusivity cost the Treasury nothing at the point of enactment. Its costs appeared later, dispersed across insurance premiums, hospital budgets and patient co-payments. That feature, which made exclusivity politically easy to create, is also what has made its consequences difficult to control. The economic logic of fixed costs has a direct consequence for pricing that is sometimes described as an inverse relationship between prevalence and price. If a developer is to recover a given fixed cost from a smaller number of patients, the price per patient must be higher. Analyses of orphan drug prices in Europe and the United States have consistently found this pattern: the rarer the condition, the higher the annual cost of treatment tends to be. Some of the most expensive chronic therapies in the world treat conditions affecting only a few hundred or a few thousand patients per country. This relationship is often offered as the justification for high orphan prices, and within limits it is valid. A developer serving a population of five hundred cannot charge what one serving five million would charge. But the relationship also explains something less comfortable. Once society accepts that rarity justifies high prices, rarity itself becomes valuable to a company. There is a commercial incentive to define markets as narrowly as possible, to seek approval first in the smallest plausible population, and to present a drug as a treatment for a rare condition even when its eventual use may be broad. The logic that justifies orphan pricing also creates the incentive to game it. Later chapters trace how this has played out. A second consequence is that the price of an orphan drug is rarely anchored to the cost of producing it. Once fixed costs are sunk, a monopolist chooses the price that maximises revenue given the demand it faces. For a life-saving medicine with no alternative, purchased by insurers and health systems that face political pressure to cover it, demand is extremely insensitive to price. Economists call this inelastic demand. In such a market the profit-maximising price may be far above what would be needed to recover the development cost. It is limited not by cost but by the buyer's willingness and ability to pay, and by the reputational and political risk of charging too much. Why the problem was political before it was economic The neglect of rare diseases was an economic phenomenon, but its correction was a political one, and the path by which it became political shaped the institutions that followed. In the United States in the late 1970s and early 1980s, the families of patients with conditions such as Tourette syndrome, Huntington's disease and myoclonus began to organise. They discovered that treatments existed in academic laboratories or had been developed and abandoned by companies because the markets were too small. Abbey Meyers, whose son had Tourette syndrome and who could not obtain an experimental medicine that had helped him, became one of the most effective advocates. The coalition that formed around these families later became the National Organization for Rare Disorders. The campaign found an unlikely ally in popular television. In 1981 and 1982 the crime drama Quincy, M.E. broadcast episodes about patients unable to get drugs for rare conditions, and its star, Jack Klugman, testified before Congress. Representative Henry Waxman, who chaired the relevant House health subcommittee, sponsored the legislation. President Ronald Reagan signed the Orphan Drug Act into law on 4 January 1983. The character of this origin matters. The law was built by patient advocates and legislators to solve a problem of neglect, not a problem of price. Its authors worried that drugs would not be made at all. They did not anticipate a world in which half of all new medicines would carry orphan status and some would cost millions of dollars. Waxman himself later became a critic of the profits some orphan drugs generated. The institutional design reflects its origin: generous, easy to obtain, and largely silent on what happens after approval. The next chapter describes that design and its international descendants in detail. It is also worth noticing what the story reveals about the moral economy of rare disease. Patients with rare conditions have unusually strong claims on public sympathy, because their suffering is often severe, frequently affects children, and is plainly not their fault. They also have unusually weak market power as individual consumers, because each disease is small. Political organisation converts the first into leverage over the second. This is the same dynamic that operates today when patient groups campaign for reimbursement of a particular drug. It is a legitimate and often admirable form of advocacy, but it means that decisions about orphan drug funding are made in an environment where identifiable, sympathetic patients stand on one side and the diffuse, statistical patients who would benefit from the money spent elsewhere stand on the other. Economists call this the identifiable victim effect. It will recur throughout this book. By the early 1980s, then, the economics of rare disease were clear. High fixed costs, small markets, heavy uncertainty and fragmented patient populations combined to make rare disease development commercially unattractive. The market's answer was neglect. Society's answer was to alter the returns, principally by granting monopolies that would allow developers to charge whatever the market would bear for a limited time. That answer embedded a tension that has only grown sharper. Exclusivity solves the problem of neglect by permitting high prices, but it gives the monopolist, not the public, control over how high. The rarer the disease, the stronger the justification for a high price, and so the stronger the incentive to present diseases as rare. And because rare disease patients command deep public sympathy, payers find it hard to refuse even very high prices once a drug exists. Each of these features was present from the start. What changed over the following four decades was the science, which made it possible to develop effective treatments for far more rare conditions, and the scale of the money involved, which transformed a humanitarian fix into a central business model. The rest of this book examines how the institutions built in 1983 have coped with those changes, and how they might be rebuilt. Chapter 2: The Monopoly Bargain Every orphan drug regime in the world rests on the same idea: that governments can induce companies to develop medicines for small populations by improving the commercial terms on which those medicines are sold. The details, however, differ in ways that shape prices, strategies and access. This chapter sets out the American law of 1983 and the frameworks that followed it, with attention to the features that matter economically: how a condition qualifies as rare, what the developer receives, and what the law does and does not say about what happens after approval. The American model The Orphan Drug Act as signed in January 1983 defined its target loosely, as a disease or condition for which there was no reasonable expectation that the cost of developing a drug would be recovered from sales in the United States. That definition proved hard to administer, because it required companies to open their books and regulators to judge commercial projections. In 1984 Congress added a simpler alternative: a condition affecting fewer than 200,000 people in the United States would qualify automatically. The cost-recovery route remains on the statute but is rarely used. In practice the prevalence threshold is the definition. A drug can receive orphan designation at any stage of development, often long before its efficacy is known. Designation is granted by the FDA's Office of Orphan Products Development on the basis of a scientific rationale that the drug may work in the condition and evidence that the population falls below the threshold. Designation is cheap to obtain and does not require proof that the drug works. Thousands of designations have been granted since 1983, and only a minority lead to approval. Designation unlocks several benefits. The first is a tax credit for qualified clinical testing expenses. As originally enacted it was worth half of those expenses, a substantial subsidy for a company with taxable profits. The Tax Cuts and Jobs Act of 2017 reduced it to 25 percent. The second is an exemption from the application fee that sponsors normally pay when submitting a marketing application to the FDA, a sum that now runs to several million dollars per application. The third is access to the FDA's orphan products grants programme, which funds clinical studies, often at academic centres, though its budget is modest relative to industry spending. The fourth, and by far the most valuable, is seven years of market exclusivity on approval. Orphan drug exclusivity is distinct from patent protection and operates alongside it. A patent protects an invention and can be challenged in court; orphan exclusivity is a regulatory bar, administered by the FDA, that prevents the agency from approving the same drug for the same rare disease use for seven years after the first approval, unless the later product is shown to be clinically superior or the holder cannot supply enough of the drug. Because it does not depend on the drug being novel or patentable, orphan exclusivity is especially valuable for old molecules with expired patents. A company that runs the trials necessary to gain approval of an off-patent compound for a rare disease can obtain seven years in which no competitor can win approval for that use. The relative value of orphan exclusivity depends on what other protection a product enjoys. For a new small molecule with strong patents running well beyond approval, the seven years may add little, since patents already block competitors. For a biological product, American law since 2010 has granted twelve years of protection from biosimilar competition regardless of orphan status, so orphan exclusivity matters mainly for the particular indication and for the tax and fee benefits that come with designation. For old molecules, reformulations and products with weak or expired patents, orphan exclusivity may be the only barrier to competition, and it is therefore most valuable exactly where the underlying innovation is least novel. This asymmetry reappears in the next chapter. The clinical superiority exception deserves a word. A later sponsor can break an existing orphan exclusivity if it shows that its version of the same drug is safer, more effective, or makes a major contribution to patient care. The exception exists so that exclusivity cannot freeze a disease at its first treatment. In practice it is invoked rarely and determined case by case, and the uncertainty about whether an improvement will qualify discourages investment in follow-on versions of a protected drug. The exclusivity is, in effect, close to absolute for its term. The scope of that bar was the subject of an important legal dispute. For decades the FDA read exclusivity narrowly, as protecting only the specific use or indication approved, so that a second company could gain approval of the same drug for a different population within the same disease. In 2021, in Catalyst Pharmaceuticals v. Becerra, the United States Court of Appeals for the Eleventh Circuit rejected that reading, holding that exclusivity blocked approval of the same drug for the same disease as designated, whatever the approved subpopulation. The ruling threatened to widen every orphan monopoly considerably. The FDA announced it would confine the ruling to the case at hand, and Congress eventually settled the question. The Consolidated Appropriations Act signed on 3 February 2026 amended the statute so that exclusivity covers the same drug for the same approved use or indication within the rare disease, codifying the agency's longstanding interpretation and applying it retroactively. The same 2026 law restored a second, separate incentive: the rare paediatric disease priority review voucher. Created in 2012, the programme awarded a company that won approval for a drug for a rare paediatric disease a voucher entitling it to a faster FDA review, roughly six months rather than ten, for any later product. Vouchers could be sold, and they have changed hands for sums typically in the range of $100 million, making them a direct cash reward for paediatric rare disease development. The programme lapsed in December 2024 and was reauthorised through September 2029 by the 2026 appropriations law. Whether vouchers actually encourage paediatric rare disease development is disputed. Supporters point to the substantial sums vouchers have fetched and to the growth in paediatric rare disease approvals since the programme began. Sceptics note that many voucher-winning drugs were already well advanced when the programme was created, that the value of a faster review for an unrelated product has little connection to the paediatric contribution, and that each voucher used speeds one drug at the cost of drawing FDA reviewers away from others. A 2020 report by the Government Accountability Office concluded that the available evidence did not establish whether the voucher programmes were spurring development that would not otherwise have occurred. Congress reauthorised the programme nonetheless, reflecting strong support from patient organisations and the fact that, like exclusivity, vouchers cost the Treasury nothing directly. The European model The European Union adopted its orphan medicinal products regulation, Regulation (EC) No 141/2000, in December 1999, and it took effect in 2000. The European definition is built on prevalence per head rather than absolute numbers: a condition qualifies if it affects no more than five in ten thousand people in the Union and is life-threatening or chronically debilitating. As with the American law, there is an alternative route based on insufficient expected return, which is little used. In addition, the European regulation requires that there be no satisfactory existing method of treatment or, if there is one, that the new product offer significant benefit over it. This significant-benefit test, assessed by the European Medicines Agency's Committee for Orphan Medicinal Products, is a meaningful difference from the American law, which imposes no comparable requirement at designation. The reward is also larger. An approved orphan medicine in the European Union has received ten years of market exclusivity, extendable to twelve for completion of an agreed paediatric investigation plan. Under the existing regulation, exclusivity can be cut to six years if, at the end of the fifth year, the product no longer meets the designation criteria, for example because it has become so profitable that the insufficient-return justification no longer holds. This provision has been used very rarely. Sponsors also receive protocol assistance, the European term for scientific advice on development, and reductions in regulatory fees. The European regime is now being rewritten. After the European Commission proposed a comprehensive reform of pharmaceutical legislation in April 2023, the Parliament and Council negotiated through 2025, and compromise texts were published in March 2026. Formal adoption was expected in the course of 2026, with the new rules applying after a transition of about two years. The reform abandons the single ten-year term in favour of modulated exclusivity. According to published legal analyses of the compromise, the baseline falls to nine years, the final two of which operate as a weaker form of protection allowing competitors to prepare applications; products that address conditions with no authorised treatment and deliver clinically relevant reductions in morbidity or mortality can receive a longer period of up to eleven years; and one-year extensions are available for new orphan indications, up to twice, and for making the product available across member states. The reform also introduces a single global orphan marketing authorisation, intended to prevent companies from obtaining fresh exclusivity for each new indication of the same active substance. Chapter 8 returns to what these changes might achieve. Other jurisdictions Japan introduced its orphan system in 1993. It defines a rare disease as one affecting fewer than 50,000 patients in Japan, a threshold that, relative to Japan's population of roughly 125 million, is similar to the European ratio. Designated products receive subsidies for development costs, tax advantages, priority review and a re-examination period of up to ten years during which generic competitors cannot rely on the originator's data. Australia adopted an orphan programme in 1998 and has since revised its criteria. China has moved rapidly in the past decade from a system in which many rare disease drugs available elsewhere were simply unavailable, to one that actively encourages domestic development. Its first national rare disease list was published in 2018, and regulators have introduced priority review and acceptance of foreign clinical data. Under rules taking effect in 2026, China for the first time offers market exclusivity for new rare disease drugs, of up to seven years, conditioned on the holder maintaining supply. The United Kingdom, after leaving the European Union, established its own orphan regime administered by the Medicines and Healthcare products Regulatory Agency. It kept the European prevalence threshold and the ten-year exclusivity term, extendable by two years for paediatric studies. In 2026 the government consulted on a new rare disease framework that would add a separate designation for very rare conditions, those affecting fewer than one in fifty thousand people. Table 1 sets the main features of these regimes side by side. Table 1. Principal orphan drug incentives in selected jurisdictions (as of 2026). Jurisdiction Rarity threshold Market exclusivity Other main incentives United States Under 200,000 patients 7 years, same approved use 25% trial tax credit; fee waiver; grants; paediatric vouchers European Union (current law) Up to 5 in 10,000 10 years, plus 2 paediatric Fee reductions; protocol assistance; significant-benefit test European Union (reform) Up to 5 in 10,000 About 9 years baseline, up to 11, plus extensions Single orphan authorisation per substance United Kingdom Up to 5 in 10,000 10 years, plus 2 paediatric Fee reductions; new framework under consultation Japan Under 50,000 patients Up to 10 years data re-examination Subsidies; tax relief; priority review China National rare disease list Up to 7 years (from 2026) Priority review; foreign data accepted Sources: statutes and regulator guidance summarised in published legal analyses, including Sidley Austin (2026) and Osborne Clarke (2026). What the bargain leaves out For all their differences, these regimes share a structure. They define eligibility by the size of the patient population, reward developers mainly with monopoly, and say almost nothing about price. None of them conditions exclusivity on reasonable pricing or access. The American law does not mention price at all. The European regulation's provision for cutting exclusivity when a product becomes highly profitable is the closest any of them comes, and it has been used so seldom that it functions more as a symbol than a control. This silence was deliberate, or at least unexamined. In 1983 the priority was to get drugs made. Price was left to the ordinary mechanisms of each country's health system: private insurance negotiation and public programme rules in the United States, and national pricing and reimbursement authorities in Europe. The orphan law created the monopoly, and something else was expected to discipline it. The consequence is a division of labour that runs through the rest of this book. Regulators decide whether a drug is safe and effective and whether it qualifies for orphan status. They do not decide whether it is worth its price. That judgment falls to payers and health technology assessment bodies, which are institutionally separate, often operate under different legal mandates and, in the United States, were until recently largely absent from pricing decisions for government programmes. The monopoly is granted at one level of government; its cost is borne at another. A second omission concerns the definition of rarity. Every regime defines a rare disease by counting patients, but none of them defines what a disease is. That question, it turns out, has an economically important answer. If a common disease can be divided into subtypes by genetic mutation, biomarker, stage or line of therapy, then each subtype may fall below the threshold. Regulators have tried to prevent artificial subdivision: the FDA's rules require that a proposed subset be medically plausible, meaning that the drug's properties would limit its use to that subset. But advances in molecular medicine have made genuinely distinct subsets far more common, particularly in cancer. A treatment for a lung cancer driven by a specific mutation is, in a real sense, a treatment for a rare disease. It is also a treatment for a subset of one of the most common cancers in the world. A third omission is the absence of any mechanism to adjust the reward to the need. The seven or ten years of exclusivity are the same whether a drug is the first treatment for a fatal paediatric disease with no alternatives, or a reformulation of an existing product for a condition that already has several treatments. The same reward for very different contributions is a crude instrument. The European reform's modulation of exclusivity is the first serious attempt by a major jurisdiction to address this, and it remains modest. A fourth omission concerns time. The regimes were designed as permanent features of law, with no requirement for periodic review of whether their terms remained appropriate. In the United States, the Orphan Drug Act's basic incentives have been amended only occasionally, and usually in the direction of expansion, as when the definition was simplified in 1984. The most significant contraction, the halving of the tax credit in 2017, was a by-product of a general tax reform rather than a judgment about orphan policy. The European regulation was evaluated by the European Commission in 2020, and the evaluation found that it had increased the number of orphan medicines, but that new products were concentrated in a limited number of therapeutic areas, particularly oncology, and that most rare diseases, especially the rarest, still had no authorised treatment. It also found that the regulation's incentives had not been well matched to areas of greatest unmet need. That evaluation fed directly into the reform now under way. Taken together, these omissions define the space in which the rest of the story unfolds. The orphan regimes create a valuable monopoly, grant it on the basis of a population count, apply the same terms regardless of novelty or need, and leave the price to be settled elsewhere. Each of those design choices has been exploited, and each is now the target of reform. It is helpful to think of the orphan regime as a contract between society and industry whose terms were written at a time when neither side could foresee how it would be used. Society offered monopoly in exchange for development. It left open how high prices could go, how broadly rarity would be interpreted, and whether the reward should vary with the importance of the contribution. For two decades these open terms mattered relatively little, because orphan drugs were a modest share of the market and prices, while high, were not yet extraordinary. That changed as genomics, biologics and later gene and RNA therapies made rare diseases scientifically tractable, and as the industry recognised that orphan status offered a combination of regulatory advantages, pricing power and protection from competition that no other segment could match. The next chapter examines what the bargain produced once it was put to full commercial use: a great deal of genuine innovation, and a set of strategies that stretch the terms of the original contract close to breaking. Chapter 3: What the Incentives Bought Four decades after the Orphan Drug Act, it is possible to judge the bargain by its results. The verdict is mixed in an instructive way. The incentives worked: they drew enormous investment into rare diseases and produced medicines that have changed the course of conditions once regarded as hopeless. They also worked on things they were never meant to reach, rewarding strategies that exploit the definition of rarity rather than address neglect. Separating these two effects is the central analytical task in orphan drug policy, because a reform that suppresses the second without damaging the first is the prize. The genuine achievement The first question is whether orphan incentives caused more rare disease drugs to be developed, or merely rewarded development that would have happened anyway. That is harder to answer than it looks, because the science of rare diseases advanced dramatically over the same period. Molecular genetics identified the causes of thousands of inherited conditions, biotechnology made it possible to manufacture enzymes and antibodies, and gene and RNA technologies opened entirely new ways of intervening. Some of the growth in orphan approvals would have occurred under any policy. The best economic evidence nonetheless suggests that the incentives mattered. The most frequently cited study, by the economist Wesley Yin and published in the Journal of Health Economics in 2008, compared the flow of clinical trials for rare diseases with trials for otherwise similar common conditions before and after the Act. It found a substantial and sustained increase in rare disease trials attributable to the law. Other research has linked the increase in orphan drug approvals to declines in mortality from rare diseases relative to common ones. And the European experience after 2000 displayed a similar rise in designations and approvals following the introduction of its regime. The scale of the change is visible in approval statistics. In 2025 the FDA's Center for Drug Evaluation and Research approved 46 novel medicines, of which 25, or 54 percent, carried orphan designation. Orphan products have made up roughly half of novel approvals for most of the past decade. Behind these numbers lie some of the most important therapeutic advances of the era. Cystic fibrosis offers the clearest illustration. The disease, caused by mutations in the CFTR gene, affects roughly forty thousand people in the United States and a comparable number in Europe. For most of the twentieth century patients died young, of progressive lung damage. Beginning with ivacaftor, approved in 2012 for patients carrying a specific mutation, and culminating in the triple combination elexacaftor, tezacaftor and ivacaftor approved in 2019, Vertex Pharmaceuticals developed a class of drugs that correct the underlying protein defect. For the large majority of patients with eligible mutations, lung function improves and projected survival has lengthened dramatically. This was accomplished with an unusual partnership: the Cystic Fibrosis Foundation, a patient charity, invested more than $150 million in the early research and later sold its royalty rights for $3.3 billion, money it reinvested in further research. Spinal muscular atrophy tells a similar story in fewer years. Nusinersen, an antisense oligonucleotide approved in 2016, was the first treatment. The gene therapy onasemnogene abeparvovec followed in 2019 and the oral drug risdiplam in 2020. Children who receive treatment early, particularly after newborn screening, can now reach motor milestones that were never seen in the untreated disease. In haemophilia, transthyretin amyloidosis, several lysosomal storage disorders and a number of rare cancers, the story is comparable. It is not an exaggeration to say that the orphan drug era has produced a larger number of transformative therapies than any comparable period in pharmaceutical history. It is equally important to be clear about what the incentives have not achieved. It is widely estimated that only around one in twenty rare diseases has an approved treatment. The flow of new orphan medicines is concentrated in a relatively small number of areas: cancers, a set of well-characterised monogenic diseases with active patient organisations, and conditions where a single biological mechanism can be targeted. The thousands of conditions that affect a few dozen or a few hundred people worldwide, often with poorly understood biology, remain almost entirely without treatment. The incentives have drawn investment toward the rare diseases that are most commercially tractable, which is what a market-based incentive would be expected to do. They have done much less for the rarest. Stretching the definition The same incentives that produced these successes also encouraged strategies that the law's authors did not intend. Four stand out. The first is repurposing old drugs. Because orphan exclusivity does not depend on novelty, a company can take a medicine that has been available for years, run the trials needed for formal approval in a rare disease, and obtain seven years of protection. In principle this is valuable: formal approval brings reliable manufacturing standards, labelled dosing and insurance coverage. In practice it has sometimes allowed companies to convert cheap, established treatments into expensive monopolies. The case of amifampridine is the textbook example. The drug, known as 3,4-diaminopyridine, had been used for decades to treat Lambert-Eaton myasthenic syndrome, a rare autoimmune disorder of the nerve-muscle junction. In the United States it was supplied free of charge to patients by a small family company, Jacobus Pharmaceutical, through an expanded access programme. When Catalyst Pharmaceuticals won FDA approval for its version, Firdapse, in 2018, it set a list price of about $375,000 a year. Jacobus's programme could no longer continue in the same way, and patients who had received the drug for nothing faced one of the highest prices in the market. Senator Bernie Sanders wrote to the company in protest, and the case became a symbol of the orphan regime's vulnerability. Deflazacort, a corticosteroid used in Duchenne muscular dystrophy, followed a similar path. Families in the United States had for years imported it from abroad for roughly one to two thousand dollars a year. In 2017 Marathon Pharmaceuticals obtained FDA approval and orphan exclusivity and announced a list price of $89,000 a year. After public outcry the company sold the rights to PTC Therapeutics, which continued to sell it at a high price. In a third case, hydroxyprogesterone caproate, used to reduce the risk of preterm birth, was approved as Makena in 2011 with orphan exclusivity. The compounded version had cost patients about fifteen dollars an injection; Makena launched at about $1,500. The drug was eventually withdrawn in 2023 after a confirmatory trial failed to show benefit. The second strategy is subdividing common diseases, sometimes called salami slicing. Precision medicine has made it biologically legitimate to define many cancers and other conditions by molecular markers. A drug that targets a specific mutation in lung cancer, or a specific stage of a haematological malignancy, may treat fewer than 200,000 Americans. Each such indication can qualify for orphan designation. Over time, a single drug can accumulate a series of orphan approvals in different cancers and subsets, each carrying its own exclusivity and, in the United States, contributing to the tax credit. Studies by researchers at Harvard's Program on Regulation, Therapeutics and Law and elsewhere have documented how large a share of orphan approvals now fall in oncology, and how many involve drugs approved or later approved for multiple indications. The third is orphan-first launch. A company developing a drug with potential in both rare and common conditions may seek approval first in a rare indication, securing orphan benefits, faster review and a high launch price, and then expand into larger populations. The launch price, set for a rare disease, tends to persist when the drug moves into more common uses. An investigation by Kaiser Health News in 2017 found that roughly a third of orphan approvals since 1983 had gone either to repurposed mass-market drugs or to drugs that received multiple orphan approvals, and identified more than seventy drugs first approved for mass markets that later won orphan status. The fourth is the blockbuster orphan: a drug that retains orphan status while generating sales comparable to the largest medicines for common diseases. Some of the most commercially successful products of the past two decades belong in this category. Lenalidomide, sold as Revlimid for multiple myeloma and other haematological cancers, carried orphan designations and at its peak earned more than ten billion dollars a year. Eculizumab, sold as Soliris for a series of rare conditions including paroxysmal nocturnal haemoglobinuria and atypical haemolytic uraemic syndrome, earned billions annually at a price that for years exceeded $400,000 per patient per year. Tafamidis, sold by Pfizer for transthyretin amyloid cardiomyopathy, a condition once thought to be rare but now recognised as considerably underdiagnosed, has become one of the company's largest products. Nothing in the orphan laws limits how much revenue a drug can earn while retaining its orphan protections. Why gaming is hard to police It is tempting to describe these strategies as abuses, and in some cases, particularly the conversion of free or cheap treatments into expensive ones, the label fits. But the underlying problem is structural, and simply condemning companies misses why it persists. Consider the repurposing case. There are real benefits to formal approval of an old drug. Unapproved products may be of variable quality; insurers often refuse to cover them; and without a formal trial, the dose and evidence of benefit are uncertain. A company that invests in producing that evidence provides something of value. The difficulty is that the orphan regime pays the same reward, seven years of exclusivity at whatever price the market will bear, whether the company has discovered a new medicine or documented the effects of an old one. The reward is disproportionate to the contribution, but the regime has no way to scale it. Or consider subdivision. A molecularly defined subset of lung cancer may be genuinely distinct, with its own biology, prognosis and treatment. Denying orphan status to such subsets would penalise precisely the kind of targeted research that precision medicine requires. The problem is not that the subsets are fake, but that the cumulative reward, when a drug collects many orphan indications, can exceed anything the original bargain contemplated. The FDA's designation decisions are made one at a time, without reference to the drug's total market. A report by the United States Government Accountability Office in 2018 found inconsistencies in how the FDA's orphan office reviewed designation requests, including incomplete records and a failure to check consistently whether the drug had previously been approved or whether the proposed subset was appropriate. The agency made procedural changes in response. But procedural rigour cannot solve a design problem. As long as the law confers the same reward on every qualifying approval, and as long as the value of that reward depends on the company's own pricing, the incentive to maximise the number of qualifying approvals will remain. Regulators have closed some specific loopholes. American law requires sponsors of many new drugs to study them in children under the Pediatric Research Equity Act, but orphan-designated products were exempt. Some companies obtained orphan designation for a paediatric subset of a common disease partly in order to avoid paediatric study requirements for the whole drug. In 2017 the FDA announced that it would no longer grant orphan designation to paediatric subpopulations of common diseases on that basis. In the same year Congress, through the FDA Reauthorization Act, required paediatric investigation of certain cancer drugs directed at molecular targets relevant to childhood cancers, even when the drug held orphan designation for an adult indication. These are narrow fixes, but they show that the boundaries of the orphan regime can be policed when a particular abuse becomes visible. Protection from price negotiation The most consequential recent development in the American treatment of orphan drugs has come not from the FDA but from Medicare. The Inflation Reduction Act of 2022 authorised the federal government, for the first time, to negotiate the prices of certain high-spending drugs covered by Medicare. The first negotiated prices took effect in January 2026. Drugs become eligible for negotiation seven years after approval for small molecules and eleven years for biologics. The Act excluded from negotiation drugs approved only for a single rare disease or condition. Legislators reasoned that the negotiation threat would otherwise deter development in small markets. The exclusion was narrow, and it immediately raised a concern among developers: a drug with one orphan indication was protected, but if the company sought approval for a second rare disease, it would lose the exemption. Industry argued that this would discourage research into additional rare indications. Congress responded in the reconciliation law signed in July 2025, often referred to as the One Big Beautiful Bill Act. The revised exclusion applies to drugs designated for one or more rare diseases and approved only for those indications, and the clock that determines negotiation eligibility does not begin until a drug receives approval for a non-orphan indication. The change means that a drug can accumulate several orphan approvals and years of sales without ever becoming eligible for negotiation, and that when it finally expands to a common use, it starts the negotiation clock from scratch. Health policy researchers have criticised this expansion sharply. Analysts writing in Health Affairs have described a blockbuster orphan paradox: the drugs most likely to benefit from the broadened exemption are not small products struggling to recover costs but high-revenue products with multiple orphan indications. Analyses published in 2025 and 2026 estimated that the change would remove a number of high-spending drugs from future negotiation and reduce the savings Medicare might otherwise achieve. The companies' counterargument is that protecting orphan indications from negotiation preserves the incentive to study drugs in successive rare diseases, many of which would otherwise go unstudied. The practical stakes are visible in the first round of negotiation. Among the ten drugs selected in 2023 for the first negotiated Medicare prices was ibrutinib, sold as Imbruvica, a blood cancer drug whose approved uses had accumulated across several conditions that each carried orphan designation. Under the original single-orphan exclusion it was eligible because it had more than one orphan indication. Analysts have pointed out that a drug of this profile would likely have escaped selection under the broadened rule. Whatever one thinks of negotiation, it is hard to argue that a product with many billions of dollars in cumulative sales is the kind of commercially fragile medicine the orphan exemption was meant to shelter. The episode is revealing because it shows how the orphan bargain has expanded over time. In 1983, the benefit of orphan status was a limited exclusivity period. By 2025, it had become a shield against the main instrument the American government had created to control drug prices. Each expansion has been justified by the same reasoning, that rare disease development is fragile and must be protected, and each has disproportionately benefited products for which that reasoning is weakest. Viewed as a whole, the record of the orphan era supports two conclusions that are often presented as incompatible. The first is that the incentives have been a success, producing large numbers of genuinely new treatments for serious conditions that the market had neglected. The second is that a substantial share of the money flowing through the orphan system rewards activities, such as repurposing, subdivision and indication accumulation, that do not correspond to the neglect the system was built to address. Both conclusions point to the same weakness: the orphan regime cannot distinguish between the contributions it rewards. It asks only whether a condition is below a numerical threshold, not whether the drug addresses a real gap, whether it is novel, or how much revenue the company is already earning. Because the reward is monopoly pricing power rather than a fixed sum, a company that finds a way to qualify can collect a return scaled to its own pricing decision rather than to its contribution. The policy challenge is therefore not whether to preserve orphan incentives but how to target them. The next chapter looks more closely at the pricing decision itself: how companies set the prices of orphan drugs, what justifications they offer, and what the evidence says about the relationship between orphan prices and the costs of development. Hashtags: #TheEconomicsOfOrphanDrugs #OrphanDrugs #RareDiseases #RareDiseaseEconomics #OrphanDrugPricing #DrugPricing #PharmaceuticalEconomics #HealthEconomics #PharmaceuticalInnovation #OrphanDrugAct #RareDiseaseResearch #DrugDevelopmentIncentives #MarketExclusivity #PharmaceuticalPolicy #HealthcarePolicy #HealthTechnologyAssessment #CostEffectivenessAnalysis #QualityAdjustedLifeYears #GeneTherapy #PrecisionMedicine #RareDiseaseTreatment #DrugMarketAccess #PharmaceuticalRegulation #MarketFailure #MonopolyPricing #ValueBasedPricing #OutcomesBasedContracts #PatientAdvocacy #HealthcareFinancing #Pharmacoeconomics

Download the Book (PDF): Introduction: A Working Translation Jeffrey Liker's The Toyota Way has been in print since 2004, appeared in a substantially revised second edition in 2021, and has been read by an enormous number of managers who came away with the impression that they now understood something about Toyota. Most of them did not, and the reason is instructive. The book's fourteen principles are stated in English. The system they describe operates in Japanese, and a significant part of it is carried in vocabulary that does not survive translation intact. Muda is rendered as "waste," which is approximately right and loses the distinction from muri and mura that makes the concept usable. Kaizen becomes "continuous improvement," a phrase so bland that it has been applied to almost any change programme. Genchi genbutsu becomes "go and see," which sounds like advice about site visits rather than an epistemological commitment. Jidoka is rendered as "automation with a human touch," a phrase that conveys nothing at all to a reader who does not already know what it means. The result is a literature in which organisations adopt the vocabulary without the referents, run improvement events that produce local savings and no systemic change, and conclude after several years that the approach does not transfer. Something like this has happened repeatedly, in a great many industries, for four decades. This guide is a working translation. It takes the fourteen principles, organises them by the four-part structure Liker uses — Philosophy, Process, People and Partners, Problem Solving — and for each one specifies what the Japanese term means, what the practice actually consists of, what it requires that is usually omitted, what its failure mode looks like, and how you can tell whether an organisation is doing it or performing it. The controlling argument The position this guide takes is that the fourteen principles describe an integrated system, and that almost every failed implementation is a failure to recognise which principles are prerequisites for which others. This is not a general claim that everything is connected. It is specific. Continuous flow surfaces problems, which is its purpose; an organisation that creates flow without first building the capability to respond to surfaced problems has simply made itself fragile. Stopping the line to fix defects requires the authority to stop it and a support structure that arrives when it stops; without both, the andon cord becomes decoration. Standardised work is the precondition for improvement, because you cannot improve a process that varies unpredictably; organisations that treat standardisation and improvement as opposing values have misunderstood both. Levelling the schedule is what makes standardised work possible; without it, standard work is a fiction that everyone ignores during peaks. Read this way, the fourteen principles are not a menu. They are a dependency graph, and Chapter One sets it out explicitly, because the graph is the single most useful thing that can be extracted from the material and it is nowhere stated in the original. What this guide adds and what it assumes It adds four things. A glossary that is used, not appended. Chapter Two is devoted to the vocabulary, and the terms are then used in Japanese throughout, because the English equivalents lose the distinctions. A reader who works through that chapter will be able to read the wider lean literature without the persistent low-level confusion that translated terminology produces. A dependency structure. Which principles must be in place before which others can work, and what happens when the order is violated. Failure modes for every principle. Each principle has a characteristic way of being implemented incorrectly, and the incorrect implementation is usually more common than the correct one. Naming them is more useful than restating the principle. An honest treatment of the limits. Toyota is not a perfect organisation, its production system has documented costs as well as benefits, and the company has been through a sequence of quality and regulatory failures — including certification irregularities across the group disclosed between late 2023 and 2024 — that any serious guide has to address rather than bracket. Chapter Eight does so, not to debunk the system but because a management model whose failures cannot be discussed is not a model, it is an advertisement. It assumes very little. No manufacturing background is required. The examples are drawn from production because that is where the system originated, and Chapter Eight addresses what changes when the principles are applied to service, software, healthcare and administrative work — where most readers will actually be applying them. A note on Toyota, the source, and the literature Three sources should be distinguished, because they are frequently merged. The Toyota Production System is the operational system developed at Toyota principally from the late 1940s onward, associated above all with Taiichi Ohno and with Eiji Toyoda, and documented in Ohno's own writing and in Shigeo Shingo's studies. It is about production: flow, pull, changeover, quality at source. The Toyota Way is a document Toyota produced internally in 2001, articulating the values underlying the company's approach under two pillars — continuous improvement and respect for people. It is about management philosophy rather than production technique, and it was written partly because Toyota's international expansion made explicit what had previously been transmitted by apprenticeship. Liker's The Toyota Way** is an outsider's synthesis, published in 2004 and revised in 2021, organising observations of the company into fourteen principles under four headings. The fourteen principles are Liker's formulation, not Toyota's, and this matters: the company does not organise its own thinking this way, and a reader who cites "Toyota's fourteen principles" is citing a scholar's analytical scheme. This guide follows Liker's structure because it is the one the reader is likely to encounter, while attributing practices to their actual sources and flagging where the synthesis imposes an order the original does not have. How to use this guide Three reading paths, depending on what you need. If you are studying the material for examination or citation, read straight through. Chapter One gives the historical and structural context, Chapter Two the vocabulary, Chapters Three to Seven the fourteen principles in Liker's four sections, and Chapter Eight the critical assessment. The glossary and notes at the end supply the reference apparatus. If you are assessing an organisation — your own or someone else's — the operative material is the diagnostic questions. Each principle has a section on failure modes and a behavioural test, and Chapter Two's reference table collects sixteen questions that distinguish practice from vocabulary. A visitor who asks these learns more in an afternoon than most formal assessments produce. If you are attempting an implementation, start with Chapter One's dependency table and Chapter Eight's implementation sequence, and read the individual principles as needed. The single most important thing in the guide for this purpose is that the order in which things are attempted matters more than which things are chosen, and that the natural order — visible tools first — is close to backwards. A note on the examples. The system originated in automobile production and its canonical illustrations are from the factory floor. Most readers of this material work in services, administration, software, healthcare or professional work, and this guide draws examples from those settings wherever the principle permits, flagging explicitly where a principle does not generalise. Chapter Eight sets out what transfers and what does not, and the honest summary is that the analytical and problem-solving material transfers almost entirely while the operational material transfers partially and the structural commitments transfer poorly. Chapter One: The System Behind the Principles Where the system came from The Toyota Production System was not designed. It was assembled over roughly three decades in response to specific constraints, and knowing the constraints explains features of the system that otherwise look arbitrary. Toyota entered automobile production in the 1930s as a small manufacturer in a small market. In the immediate postwar period its position was severe: capital was scarce, the domestic market was small and fragmented across many models, and the productivity gap against American manufacturers was very large — Toyota's own leadership estimated it at roughly a factor of eight to nine at the end of the 1940s. This combination ruled out the American solution. Mass production achieved its efficiency through enormous batch sizes, dedicated equipment, and long runs of identical product, all of which required capital Toyota did not have and volume the Japanese market did not supply. Toyota needed to produce many models in small quantities, with little capital, at costs competitive with high-volume producers. Nearly every distinctive feature of the system follows from that requirement. Small batches were necessary because there was no volume to justify large ones, which required rapid changeover of tooling, which became the single-minute exchange of die techniques associated with Shigeo Shingo. Low inventory was necessary because inventory ties up capital, which required reliable supply and reliable quality, because with no buffer any defect or delay stops production. Building quality in at the source was necessary because there was no inventory to draw on while defects were reworked, which required operators empowered to stop and fix, which required a workforce trained to identify and solve problems, which required long-term employment relationships that made investment in training rational. Read in this order, the system is a chain of necessities rather than a set of choices. A firm with abundant capital and a large homogeneous market would not have invented it, which is precisely why the American manufacturers did not. The two-pillar structure and the house Toyota's own internal presentation of the production system is usually drawn as a house, and the drawing is worth understanding because it encodes the dependency structure this guide argues for. The roof is the goal: best quality, lowest cost, shortest lead time, best safety, high morale. The two pillars are just-in-time and jidoka. Just-in-time means producing what is needed, when it is needed, in the quantity needed — the flow-and-pull side of the system. Jidoka, discussed at length in Chapter Five, means building in quality by making abnormalities visible and stopping when they occur — the quality side. The foundation is levelled production (heijunka), standardised work, visual management, and stable, capable processes. The centre is people and teamwork, continuous improvement, and waste reduction. The structural claim in the drawing is that the pillars rest on the foundation. A firm that implements just-in-time without levelling, standardisation and process stability has built pillars on sand — which is an accurate description of a large proportion of failed implementations, and it is why this guide places so much weight on the foundation principles that practitioners typically find least interesting. The 2001 document and the two values In 2001, before its major international expansion, Toyota produced an internal document articulating what it called the Toyota Way, under two pillars. Continuous improvement comprised challenge (forming a long-term vision and meeting challenges with courage), kaizen (improving operations continuously, always driving for innovation), and genchi genbutsu (going to the source to find the facts and make correct decisions). Respect for people comprised respect (respecting others, making every effort to understand each other, taking responsibility, and building mutual trust) and teamwork (stimulating personal and professional growth, sharing development opportunities, and maximising individual and team performance). Two observations about this document. The first is that it is a values statement, not a method. It says nothing about kanban, changeover, or line stops. This is why the Toyota Way and the Toyota Production System are not the same thing, and why an organisation can adopt the tools without the values or, more rarely, the reverse. The second is that respect for people is not a courtesy principle. In Toyota's usage it means challenging people, expecting them to think, giving them problems to solve, and not insulating them from difficulty. The most common Western misreading treats it as an injunction to be considerate, which drains it of content. The Toyota version is closer to: we respect you enough to expect you to improve your own work, and we will not do it for you. The fourteen principles as a dependency graph Liker's fourteen principles are ordered by category rather than by dependency, which obscures the structure. Reordered by what enables what, they look like this. Foundational, and required by nearly everything else. Principle 1 (long-term philosophy) determines whether the investments the rest requires can be made at all. Principle 6 (standardised work) is the precondition for improvement, since a process that varies unpredictably cannot be improved measurably. Principle 4 (levelling) is the precondition for standardised work, since standard work cannot hold under a fluctuating schedule. Diagnostic, and dependent on the foundation. Principle 2 (continuous flow) and Principle 7 (visual control) both function by making problems visible. They deliver value only where a response capability exists. Implementing them first is the commonest sequencing error and produces an organisation that can see problems it cannot address. Responsive, and dependent on the diagnostic layer plus capability. Principle 5 (stop to fix quality) is the response mechanism. It requires that people can stop, that support arrives, and that stopping is not punished — which is a management commitment rather than a technique. Enabling, and slow to build. Principles 9, 10 and 11 (leaders who know the work, capable people and teams, developed partners) supply the human capability everything else consumes. These take years and cannot be bought. Method, and dependent on everything above. Principles 12, 13 and 14 (go and see, decide by consensus and implement rapidly, reflect and improve) are how the organisation learns. They presuppose people capable of seeing, deciding and reflecting. Constraining. Principles 3 (pull) and 8 (reliable technology serving people and process) are constraints on how the rest is implemented rather than capabilities in themselves. The practical implication of this reordering is the single most useful thing in this guide: the sequence in which a transformation is attempted matters more than the selection of tools, and the sequence most organisations attempt — visible tools first, because they demonstrate progress — is close to the reverse of the one the dependency structure requires. The dependency table Presenting the reordering as a table makes it usable as a planning instrument. Layer Principles What it provides What it requires first Failure if attempted early Foundation 1 (long-term philosophy), 4 (heijunka), 6 (standardised work) Stability and the mandate to invest Senior commitment to accept short-term cost None — this is where to start Diagnostic 2 (flow), 7 (visual control) Problems made visible Stable, standardised processes Visible problems with no response capability; disruption blamed on the method Responsive 5 (jidoka, stop to fix) Problems resolved at source Diagnostic layer plus support structure and authority to stop Andon cords nobody pulls; quality still inspected in at the end Human capability 9, 10, 11 (leaders, teams, partners) The capacity everything else consumes Years; stable employment; internal promotion Tools deployed by people who cannot sustain them; regression on consultant departure Method 12, 13, 14 (genchi genbutsu, nemawashi, hansei and kaizen) Organisational learning Capable people and honest problem reporting Ritual A3s and meetings; reflection that identifies no real problems Constraints 3 (pull), 8 (technology serving process) Discipline on how the rest is built Applies throughout Push systems with kanban cards; technology imposed on unstable processes Two things this table makes visible. The first is that the layer most organisations start with is the diagnostic one, because flow and visual control are the most visible and most demonstrable. They produce charts, boards, and rearranged floor space. They also produce a large increase in surfaced problems in an organisation with no capacity to resolve them, which is experienced as chaos and attributed to the method. The second is that the human capability layer cannot be sequenced away. It takes years, it consists largely of people who have done the work and been developed on the job, and there is no purchasing route. This is the constraint that determines the realistic timescale of any transformation, and it is the one most transformation plans ignore. What the system is optimising A final orientation, because it is frequently misstated. The Toyota Production System is not primarily an efficiency system. Its distinctive commitment is to surfacing problems, and several of its central practices are, considered in isolation, inefficient. Low inventory is the clearest case. Inventory buffers absorb variation and prevent disruption; removing it makes the system fragile to any disturbance. Ohno's own explanation of why this is desirable is the system's central idea: inventory hides problems, and a process that runs smoothly because it is protected by buffers is a process whose defects are never found. Lowering the water level reveals the rocks, which is unpleasant and is the point. Stopping the line is the second case. A line stopped is a line not producing, and the immediate cost is obvious. The claim is that the cost of not stopping — defects propagating, root causes unexamined, rework accumulating — is larger and less visible. This is why the system cannot be adopted as a cost-reduction programme. A cost-reduction programme will remove inventory to release working capital and will not accept line stops, which is the combination that produces fragility without learning. The system's logic is that reducing buffers is worthwhile because it forces problems into the open, and that the value comes from solving them. An organisation that wants the inventory reduction without the problem-solving is buying the cost and declining the benefit. Holding this in mind converts many of the fourteen principles from arbitrary practices into instances of a single strategy: make problems visible, make them impossible to ignore, and build the capability to solve them permanently. Summary of the chapter The Toyota Production System was assembled in response to constraints — scarce capital, a small and fragmented market, a large productivity gap — that ruled out the American mass-production solution. Nearly every distinctive feature follows as a necessity from the requirement to produce many models in small quantities with little capital: small batches require rapid changeover, low inventory requires reliable quality, reliable quality requires empowered operators, and empowered operators require long-term employment and sustained training. Toyota's own house diagram encodes a dependency structure: the just-in-time and jidoka pillars rest on a foundation of levelling, standardised work, visual management and process stability. The 2001 Toyota Way document is a statement of values — continuous improvement and respect for people — rather than a method, and its version of respect means expecting people to solve their own problems rather than protecting them from difficulty. Reordering Liker's fourteen principles by dependency rather than category produces the guide's central practical claim: sequence matters more than tool selection, human capability is the binding constraint and cannot be sequenced away, and the diagnostic principles that most organisations implement first are the ones that do damage when implemented without a response capability. And the system is optimising for problem visibility rather than for efficiency, which is why several of its practices are locally inefficient by design and why it cannot be adopted as a cost-reduction programme. The people who built it A short account of the principal figures, because the system is frequently presented as anonymous and its components have identifiable authors with identifiable concerns. Sakichi Toyoda (1867–1930), founder of the Toyoda loom works, developed the automatic loom that stopped when a thread broke. This is the origin of jidoka, and its logic — a machine that detects its own abnormality frees the human to do something other than watch it — predates the automobile business entirely. Kiichiro Toyoda (1894–1952), his son, founded the automobile operation and is credited with the just-in-time concept, reportedly influenced by observation of American supermarket replenishment, in which shelves are restocked according to what customers have taken rather than according to a plan. Whether the supermarket story is literal or apocryphal, it captures the pull idea exactly. Taiichi Ohno (1912–1990) is the system's principal architect. A production engineer rather than a theorist, he built the pull system, developed the kanban mechanism, formulated the seven wastes, and drove the reduction of batch sizes and inventory over several decades of practical experimentation on the shop floor. His own account, Toyota Production System, is short, blunt and worth reading in the original; it is considerably less systematic than the later synthesis literature and considerably closer to how the system actually developed. Shigeo Shingo (1909–1990), a consultant and engineer who worked extensively with Toyota, developed the changeover reduction techniques that made small batches economic and wrote the most detailed analytical studies of the system. His work on poka-yoke and on source inspection is the technical foundation of the quality principles. Eiji Toyoda (1913–2013) provided the managerial authority under which the system was developed and later led Toyota's international expansion. Two figures from outside the company also matter. W. Edwards Deming brought statistical quality methods to Japanese industry in the postwar period and, more importantly for present purposes, the emphasis on process variation and on management responsibility for systemic causes. And the Training Within Industry programmes, developed in American war production and disseminated in occupied Japan, supplied the job-instruction and job-methods disciplines that underlie Toyota's approach to teaching work. The last point is the one worth carrying. A system routinely described as an expression of Japanese culture incorporates, at its foundations, American statistical methods and American industrial training programmes, retained in Japan after being abandoned in the country that produced them. Whatever explains the system's persistence in one place and its neglect in another, it is not that its components are culturally inaccessible. Chapter Two: The Language Why the vocabulary matters The terms in this chapter are used untranslated throughout the rest of the guide, for a reason worth stating: the English renderings collapse distinctions the Japanese terms keep separate, and the distinctions are what make the concepts operational. The clearest instance is waste. English has one word. The system has three, and they call for different responses. An organisation working with a single concept of "waste" will apply the wrong remedy about two-thirds of the time. The three enemies Muda — non-value-adding work. Activity that consumes resources and creates no value for the customer. The response is elimination. Muri — overburden. Strain on people or equipment beyond reasonable capacity: excessive workload, unsafe conditions, machines run past their design limits. The response is to reduce the load or increase the capability. Muri causes breakdowns, injuries, quality defects and turnover, and an organisation that attacks muda by making everyone work harder has converted one problem into another. Mura — unevenness. Variation in workload, demand or process output over time. Mura is the deepest of the three because it causes the other two: an uneven schedule means periods of overburden and periods of idleness, and the response to peaks is either muri (push people harder) or muda (hold inventory and capacity to absorb them). The practical implication is a priority order that most improvement programmes invert. Attack mura first, because levelling removes the cause. Then attack muri, because overburden is destructive and is often what levelling reveals. Then attack muda, which is what remains. Most improvement programmes go straight to muda, because waste is visible and its removal is measurable. Removing muda from a system with unlevelled demand and overburdened people produces savings that do not persist, because the underlying variation regenerates the waste. The seven wastes, and the eighth Ohno's classification of muda into seven categories remains the standard checklist. The examples given here are deliberately drawn from outside manufacturing, because most readers will apply this outside a factory. Overproduction. Making more than is needed, or earlier than needed. Ohno regarded this as the worst waste because it generates the others: excess output must be stored, moved, tracked, and frequently reworked or discarded. In office work: reports nobody reads, features nobody uses, analysis produced in advance of any decision that needs it. Waiting. People or work idle, waiting for information, approval, materials, or a prior step. In service work this is usually the largest single component of lead time and the least measured, because it consumes no one's effort. Transport. Unnecessary movement of materials or information. In administrative work: handoffs between departments, forwarding chains, documents circulating for signature. Over-processing. Doing more than the customer requires: precision beyond specification, approval layers that add no scrutiny, formatting that no one values, reviews that never change anything. Inventory. Work held between steps. In knowledge work: queues of requests, tickets, unreviewed drafts, and half-finished projects. Inventory in office work is invisible because it occupies no floor space, which is why it accumulates without limit. Motion. Unnecessary movement by people. In office work: navigating between systems, searching for information, re-entering data. Defects. Work that must be redone. The cost includes not only the rework but the detection, the correction, the disruption to downstream steps, and the erosion of trust in the process. Liker adds an eighth: unused employee creativity — the waste of failing to engage people in improving their own work. Whether this belongs on a list with the others is arguable, since it is a different kind of thing, and it is worth including because it names the failure mode that separates a genuine implementation from a cost-cutting programme wearing its vocabulary. The core operational terms The following are used throughout the remainder of the guide. Each entry gives the term, the usual English rendering, and — more importantly — what the rendering loses. Kaizen. Rendered "continuous improvement." What the rendering loses: kaizen in Toyota's usage means small, incremental changes made continuously by the people who do the work, as part of the work rather than as a separate project. A programme in which specialists conduct improvement events is not kaizen; it is improvement by experts, which is a different thing with different properties. The distinguishing question is who makes the change. Kaikaku. Radical change or transformation, as opposed to incremental kaizen. Occasionally necessary and rarely a substitute; a system that only does kaikaku never accumulates the thousands of small changes that produce the compounding advantage. Heijunka. Rendered "levelling" or "production smoothing." Distributing production of volume and mix evenly over time, so that the schedule does not track demand fluctuation directly. What the rendering loses: heijunka has two dimensions — volume and mix — and levelling volume while allowing mix to fluctuate wildly achieves very little. Jidoka. Rendered "autonomation" or "automation with a human touch." Building in the capability to detect abnormalities and stop automatically, so that defects are not passed on and one operator can attend multiple machines. What the rendering loses: nearly everything. The concept is about separating human work from machine work by giving the machine the ability to detect its own faults, and its historical origin is the automatic loom that stopped when a thread broke. Andon. The signal system by which a problem is made visible — a light, a board, a cord that summons help. Not merely an alarm: the andon is the interface between a person who has found a problem and the support structure that responds. Poka-yoke. Rendered "mistake-proofing." A device or design that makes an error impossible or immediately obvious. What the rendering loses: the emphasis on design rather than on care. Poka-yoke replaces the instruction to be careful with an arrangement in which the mistake cannot be made. Kanban. A signal — traditionally a card — authorising production or movement of a specified quantity. Kanban is the mechanism of pull, not a synonym for it. A kanban card used to authorise production according to a schedule rather than according to consumption is a push system with cards. Takt time. The rate at which product must be completed to meet demand, calculated as available working time divided by customer demand. Not a measure of how fast anyone can work; a statement of the required rhythm. Genchi genbutsu. Rendered "go and see." Literally, actual place and actual thing. What the rendering loses: this is an epistemological commitment, not a management practice. It holds that reports, summaries and data are inadequate substitutes for direct observation, and that a manager who has not seen the work does not understand the problem. Gemba. The actual place where work is done and value is created. The phrase "go to the gemba" is the operational form of genchi genbutsu. Hansei. Rendered "reflection." Structured, honest examination of what went wrong and why, including one's own contribution, conducted even when the outcome was successful. What the rendering loses: hansei carries a strong connotation of acknowledging shortcoming, and its cultural weight is considerable. An organisation in which reflection produces only positive findings is not doing hansei. Nemawashi. Literally, going around the roots — the gardening practice of preparing a tree for transplanting. Building consensus in advance through individual consultation, so that a formal decision meeting ratifies an agreement already reached. What the rendering "consensus building" loses: nemawashi is a specific process conducted before the meeting, not a style of meeting. Hoshin kanri. Rendered "policy deployment" or "strategy deployment." The process by which organisational objectives are cascaded and negotiated through levels, with each level agreeing its contribution and the means. Distinguished from target-setting by the negotiation and by the explicit attention to means rather than only to targets. Yokoten. The lateral transfer of learning — spreading a solution found in one place to all the places it applies. Frequently omitted from implementations, with the result that the same problem is solved repeatedly in different parts of the organisation. Standardised work. The current best-known method for performing a task, documented in terms of sequence, timing and standard inventory. Its purpose is to serve as the baseline against which improvement is measured, not to constrain the worker. The distinguishing question is who writes it: standardised work written by engineers for workers is a specification; written by workers themselves, revised as they improve it, it is the foundation of kaizen. Two terms that carry the philosophy Two further terms are worth knowing because they encapsulate the system's view of itself. Monozukuri — the making of things — carries a connotation of craft, of pride in production, and of manufacturing as a skilled activity rather than a cost centre. Hitozukuri — the making of people — is its counterpart, and Toyota's formulation that it makes people before it makes cars is not a slogan about human resources. It is a claim about what the organisation is for and where its capability resides. The pairing explains something about the system that is otherwise puzzling: the enormous investment in training, the long apprenticeships, the promotion of managers from within, and the reluctance to bring in senior outsiders. If capability lives in people who have spent years in the work, then developing them is the primary activity and production is what they do while being developed. That is close to how Toyota describes itself, and it is the opposite of how most organisations allocate their attention. Using the vocabulary honestly A caution to close the chapter. Adopting Japanese terminology is not evidence of understanding, and in a great many organisations it functions as the reverse — a vocabulary that signals commitment while the practices remain unchanged. Boards labelled kanban that authorise nothing, events labelled kaizen conducted by specialists, meetings labelled hansei at which nothing uncomfortable is said. The test in every case is behavioural rather than terminological, and this guide supplies one for each principle. The question is never whether an organisation uses the word. It is whether the thing the word names is happening: whether production is authorised by consumption, whether the people doing the work make the changes, whether anyone has said something difficult in the reflection meeting. A reference table of the terms Term Usual rendering What it actually specifies Test of genuine practice Muda Waste Non-value-adding activity Is it defined from the customer's view, or the department's? Muri Overburden Strain beyond capacity, on people or machines Is workload measured, or only output? Mura Unevenness Variation in demand, workload or output over time Is the schedule levelled, or does it track orders? Kaizen Continuous improvement Small changes made continuously by the people doing the work Who made the last change to this process? Heijunka Levelling Even distribution of volume and mix over time Is mix levelled, or only volume? Jidoka Automation with a human touch Detecting abnormality and stopping automatically Does the process stop on a defect, or flag it? Andon Signal The interface between finding a problem and getting help How long until help arrives after a pull? Poka-yoke Mistake-proofing Design that makes the error impossible Is the control a device, or an instruction to be careful? Kanban Card, signal Authorisation to produce, triggered by consumption Does downstream consumption trigger it, or a schedule? Takt time Cycle rate Required completion rate, from demand Is it recalculated as demand changes? Genchi genbutsu Go and see Direct observation as the basis of understanding When did the decision-maker last watch the work? Gemba The real place Where value is created Where are problems discussed — at the gemba or in a room? Hansei Reflection Honest examination including one's own contribution Was anything uncomfortable said? Nemawashi Consensus building Consultation before the meeting, not during it Was the decision meeting a ratification or a debate? Yokoten Horizontal deployment Spreading a solution to everywhere it applies Has this problem been solved elsewhere already? Standardised work Standard operating procedure Current best method, as a baseline for improvement Who wrote it, and when was it last changed? The right-hand column is the chapter's practical contribution. Each question can be asked in a single conversation and each distinguishes the practice from its imitation. A visitor who asks all sixteen will learn more about an organisation's system in an hour than most audits establish in a week. Three terms that are frequently confused Three pairs cause persistent trouble and are worth separating explicitly. Kaizen and kaikaku. Kaizen is incremental, continuous and made by the people doing the work; kaikaku is discontinuous, large and typically directed. Both have a place, and the error is to substitute one for the other. An organisation that runs occasional large redesigns and no continuous improvement never accumulates the thousands of small changes that produce compounding advantage; one that runs only kaizen may improve a process that should have been abolished. Standardised work and a standard operating procedure. Both are documents describing how a task is done. The difference is authorship, revision frequency and purpose: standardised work is written by the people doing the work, revised whenever they find a better method, and exists to serve as a baseline for improvement; a procedure is written centrally, revised through a change-control process, and exists to ensure compliance. Organisations frequently believe they have the first and have the second. Just-in-time and low inventory. Just-in-time is a system in which production is authorised by consumption; low inventory is a consequence of it. An organisation that reduces inventory without changing what authorises production has not implemented just-in-time; it has removed its buffers from a push system, which is the combination that produces stockouts and expediting. The distinguishing question, again, is what event authorises the next unit of work. Why insisting on the terms is not pedantry A reader may reasonably ask whether this attention to vocabulary matters, given that any of these ideas could be expressed in English at some length. It matters for a practical reason. In organisations that have adopted the language without the practices, the vocabulary functions as a substitute for assessment: an activity is called kaizen and is therefore taken to be improvement, a board is called kanban and is therefore taken to be pull, a meeting is called hansei and is therefore taken to be reflection. The word carries the claim. Restoring the distinctions restores the ability to check. Once kaizen is understood to mean improvement made by the people doing the work, the question "who made the last change to this process?" becomes decisive, and an activity that fails it cannot claim the name. Once pull is understood to mean authorisation by consumption, "what event released this work?" settles the matter. The vocabulary becomes a set of tests rather than a set of labels. That is the whole justification for this chapter, and it is why the terms are used untranslated throughout. Each one, correctly understood, carries a question that an organisation must be able to answer. Chapter Three: Section I — Philosophy Principle 1: Base management decisions on a long-term philosophy, even at the expense of short-term financial goals This is the only principle in its section, and its isolation is deliberate. It is the precondition for the other thirteen. What the principle claims The claim is not that long-term thinking is generally desirable, which is a platitude, but something specific: the practices in the remaining thirteen principles impose short-term costs and deliver returns over years, so an organisation that optimises for the current period cannot adopt them. The costs are concrete and each is identifiable in a management accounting system. Developing people takes years, during which they are less productive than experienced staff and consume the time of those training them. Building supplier capability means investing in organisations one does not own, with returns that are shared. Stopping the line to fix problems sacrifices output now for quality later. Levelling production means holding some finished goods inventory and declining to chase every demand peak, which reduces short-run revenue. Refusing to lay off during downturns preserves capability at direct cost. Rejecting technology that has not been proven means forgoing announced benefits. Each of these is a decision that reduces this year's reported performance and improves capability in three to ten years. An organisation whose decision rules are annual will decline all of them, and will do so rationally given its rules. What it requires structurally The principle is usually presented as a matter of executive conviction, which understates it. Long-term orientation is a structural property, and it depends on conditions most organisations lack. Ownership that does not require quarterly performance. Toyota's shareholding structure, its cross-holdings, and the continuing role of the founding family have historically insulated it from the pressure to which a widely held public company with dispersed shareholders is subject. Management tenure long enough to see consequences. A manager whose expected tenure in a role is three years has no reason to make an investment that pays in seven, and will not be present to be credited if it does. Toyota's practice of long assignments and internal promotion aligns tenure with the decisions being made. Measurement systems that capture capability. If the accounting system records the cost of training and not the capability it produces, every training decision appears as a loss. Organisations serious about this principle build measures of capability — skill matrices, problem-solving throughput, supplier performance trajectories — and hold managers to them alongside financial measures. A definition of purpose beyond financial return. Toyota's stated purpose, in its own materials, concerns contribution to society and to the customer, with financial performance as a condition of continuing rather than as the objective. Whether this is believed inside the company is not something an outsider can determine; that it is stated, consistently, over decades, does affect what can be argued for internally. The failure mode The characteristic failure is not disagreement with the principle. Almost no one disagrees with it. The failure is stated commitment with unchanged decision rules. The signature is easily detected. The organisation announces a long-term transformation; the budget cycle remains annual; managers are still assessed on current-period results; the improvement programme is funded from a discretionary budget that is cut when results are poor; and the first serious downturn produces layoffs including the people the programme depended on. The diagnostic question is not what the organisation says but what happened the last time short-term results and a long-term commitment conflicted. Every organisation has such an instance in its recent history, and it is dispositive. The employment commitment The most consequential expression of this principle, and the one most often quietly dropped in implementations, concerns employment security. The logic is straightforward and follows from everything in Chapter One. The system depends on workers identifying problems, proposing changes, and improving their own processes. An improvement that eliminates work is a threat to the person who proposed it, unless they are confident that eliminating their own task does not eliminate their job. Under employment insecurity, the rational worker conceals improvement opportunities, and the system's principal engine stops. This is not a moral argument. It is an incentive argument, and it means that employment security is a technical requirement of the system rather than a benefit attached to it. An organisation that runs improvement programmes while conducting periodic redundancies is asking people to participate in reducing their own headcount, and their reluctance is a correct assessment of their situation. The practical form of the commitment is narrower than "no one is ever dismissed." It is that productivity improvements do not result in redundancies: the people released are redeployed, and workforce reduction, where genuinely necessary, occurs through attrition, transfer, and reductions in temporary and contract staffing rather than through cutting the permanent workforce that carries the capability. This is expensive and it is difficult to sustain through a severe downturn. It is also the load-bearing element, and its absence explains a large proportion of implementations that produce initial gains and then stall — the first round of improvements is delivered enthusiastically, redundancies follow, and no second round is ever proposed. Applying the principle For an organisation assessing itself against Principle 1, four questions discriminate. What is the effective planning horizon? Not the horizon of the strategy document, but the horizon over which decisions are actually evaluated. If capital requests are assessed on payback within two years, the horizon is two years whatever the strategy says. How long do managers stay? Compare average tenure in a role against the payback period of the investments the role is expected to make. Where tenure is shorter, the misalignment is structural and cannot be fixed by exhortation. What is measured besides financial performance? If nothing, the organisation's stated commitments are unenforceable. What happened the last time? The single best question. Identify the most recent occasion when a long-term commitment conflicted with a current-period target, and establish which prevailed. Organisations reliably resolve this the same way each time. Why this principle is placed first A note on the architecture of the fourteen principles. Liker places philosophy first and it occupies a whole section on its own, which some readers treat as throat-clearing before the operational content begins. The dependency analysis of Chapter One says otherwise. The remaining thirteen principles all cost something now and pay later — that is what they have in common. Principle 1 is the condition under which the others can be adopted at all, which makes it not an introduction but the constraint. The practical consequence for anyone attempting an implementation is uncomfortable. If the organisation's decision rules are short-horizon and cannot be changed, the correct conclusion is not to proceed carefully with the tools; it is that the system cannot be adopted, and that whatever is adopted will be a set of techniques that produce local savings and decay. That conclusion is rarely welcome and is frequently correct, and stating it early saves several years. The philosophy in practice: three cases Because Principle 1 is abstract, three concrete instances show what adherence and abandonment look like. The downturn test. In severe demand collapses, Toyota has historically retained production workers, using the idle time for training, maintenance, and improvement activity, and absorbing the cost. The reasoning follows the incentive argument above: the capability resides in people who have been developed over years, it cannot be repurchased quickly, and dismissing them destroys both the capability and the trust on which the improvement system depends. The cost is real and appears immediately in reported results; the benefit is a workforce that is still there, still capable, and still willing to identify improvements when demand recovers. The test for any organisation is not whether it admires this but what it did in its own last downturn. The supplier test. Principle 11 requires investing in suppliers one does not own — sending engineers, sharing techniques, and helping them improve processes whose gains they partly retain. On a short-horizon view this is irrational: the investment can be appropriated, the supplier may be switched, and the returns are shared. On a long-horizon view it produces a supply base whose capability is a durable asset and whose quality is a precondition for low inventory. The test is whether an organisation's supplier relationships are managed by procurement on price with annual re-tendering, or by engineers on capability over years. The first is not a variation of the second; it is a different strategy with different requirements. The technology test. Principle 8 requires refusing technology that has not been proven to serve the process and the people, even where it has been announced as transformative and competitors are adopting it. On a short-horizon view this looks like conservatism and it costs announcements. On a long-horizon view it avoids the substantial category of technology implementations that impose themselves on unstable processes and make them worse. The test is whether an organisation has, in the recent past, declined a technology that its competitors adopted, and can articulate why in terms of process fit rather than cost. Why the philosophy is hard to import A final observation about transferability, since this is the principle most often dismissed as culturally specific. The claim that long-horizon decision-making is a Japanese cultural trait does not survive examination. Japanese companies have made short-horizon decisions in abundance, and long-horizon decision-making occurs in family firms, in partnerships, in mutuals and in privately held companies across every economy. What varies is not culture but structure: who owns the organisation, over what horizon they are assessed, how long managers stay, and what the measurement system records. This is a more useful diagnosis than the cultural one, because structure can be changed and culture cannot be adopted. An organisation that wants this principle should look at its ownership, its management tenure, its incentive structures and its measurement system, and should expect that changing any of them is a larger undertaking than any operational improvement programme. That is the honest scale of what Principle 1 asks for, and it explains why so few organisations that admire the Toyota system have replicated it. Summary of the section Philosophy occupies a section of its own because Principle 1 is a constraint rather than an aspiration. The remaining thirteen principles share the property of costing something now and paying later, so an organisation whose decision rules are annual cannot adopt them regardless of its stated intentions. Long-horizon orientation is a structural property rather than a matter of conviction: it depends on ownership that does not require quarterly performance, management tenure long enough to encounter the consequences of decisions, measurement systems that record capability as well as cost, and a stated purpose that makes long-horizon arguments sayable internally. The employment commitment is the load-bearing expression of the principle, and it is a technical requirement rather than a benefit: a workforce asked to eliminate its own work will conceal opportunities unless improvement and redundancy have been decoupled. And the principle's difficulty is structural rather than cultural, which is both more tractable and more demanding than the cultural diagnosis suggests. The single best diagnostic is historical: identify the most recent conflict between a long-term commitment and a current-period target, and see which won. Objections to Principle 1 Two objections deserve a hearing, because the principle is stated in the literature with a confidence the evidence does not entirely support. The first is survivorship. Toyota is cited as evidence that long-horizon decision-making produces superior results, and Toyota is a firm selected for study because it succeeded. Firms that made long-horizon investments and were overtaken before the returns arrived are not written about. The general claim — that patient investment outperforms — requires a sample rather than an exemplar, and the sample evidence on managerial horizons and firm performance is real but considerably more mixed than the management literature suggests. The defensible narrower claim is conditional rather than general: if an organisation wishes to operate a system whose components pay back over years, then it requires decision rules with a matching horizon. That conditional is what this guide asserts, and it is not vulnerable to the survivorship objection because it makes no claim about whether the system is worth adopting. The second is that short horizons are sometimes correct. A firm facing technological displacement, a liquidity crisis, or a market that may not exist in three years is not being short-sighted by declining a seven-year investment; it is responding to its actual situation. Long-horizon decision-making presupposes that the organisation will be there, and in some industries and some conditions that presupposition does not hold. This objection has real force and it identifies a boundary condition rather than a refutation. The system suits organisations in businesses with long product cycles, durable demand, and continuity of technology. It suits them less in businesses characterised by discontinuous change, and the criticism of Toyota's own position in rapidly shifting parts of its market, noted in Chapter Eight, is an instance of exactly this. A reader assessing whether the principle applies to their organisation should therefore ask not whether long horizons are good but whether the specific investments the system requires — in people, in supplier capability, in process stability — will still be valuable when they mature. Where the answer is yes, the principle follows. Where it is genuinely no, the honest conclusion is that this system is not the right one, which is a conclusion the literature almost never permits. Hashtags: #TheEngineOfExcellence #TheToyotaWay #JeffreyLiker #ToyotaProductionSystem #TPS #LeanManufacturing #LeanManagement #LeanThinking #OperationalExcellence #ContinuousImprovement #Kaizen #JustInTime #Jidoka #Kanban #Heijunka #GenchiGenbutsu #Hansei #Nemawashi #PokaYoke #StandardizedWork #WasteReduction #MudaMuriMura #RespectForPeople #ToyotaWay14Principles #QualityManagement #ProcessImprovement #ProblemSolving #OrganizationalLearning #LeadershipDevelopment #ManufacturingExcellence

Download the Book (PDF): Introduction In January 2023 a memoir called Spare went on sale and sold more than a million copies in the English-speaking world on its first day. The name on the cover was Prince Harry, Duke of Sussex. The book was intimate in the way that only first-person writing can be: it described grief for a mother, the fog of a teenage funeral, arguments with a brother, the physical sensations of combat and frostbite. Readers who had never met the author came away feeling they knew him. Almost none of the sentences that produced that feeling were composed by him. They were written by J. R. Moehringer, a Pulitzer Prize-winning journalist who had earlier written Andre Agassi's memoir Open, and who spent the better part of two years interviewing the prince, arguing with him, and turning his recollections into a voice that sounded like a man talking to you across a kitchen table. Nobody who follows publishing was surprised. The involvement of a professional writer in a celebrity memoir is an open secret, and in this case the secret was barely kept: Moehringer's role was reported before publication and he later wrote about the experience in The New Yorker. Yet the book still produced a small, familiar wave of unease. Some readers felt tricked. Some critics asked whether a memoir could be "his" if he had not written it. Others shrugged: of course he did not write it; he is a prince, not a novelist; the story is his, and that is what the book is selling. Both reactions contain something true, and the purpose of this book is to explain why. Ghostwriting, the practice of composing a text that will be published or delivered under another person's name, is everywhere. It produces most presidential speeches, most corporate annual letters, a large share of the bestseller list's memoirs, a surprising proportion of the opinion columns signed by chief executives and politicians, many judicial opinions, some scientific papers, and an unknown but substantial number of university essays. In some of these places it is treated as normal professional service; in others it is a firing offence, a career-ending scandal, or, in a growing number of countries, a crime. The same act, one person writing words that another will sign, is praised in one room and prosecuted in the next. The argument in brief The central claim of this book is that a name on a text is a promise, and that what the name promises differs from one kind of text to another. A signature on a presidential address promises that the president adopts these words as policy and will answer for them. A name on an undergraduate essay promises that this student, alone, produced the work that will be graded as evidence of her learning. A name on a memoir promises something in between and harder to pin down: that the story is the named person's, that the person stands behind its truth, and, more slippery, that the voice on the page is in some meaningful sense theirs. Ghostwriting is ethically acceptable when it keeps the promise the name makes to the audience that is relying on it, and wrong when it breaks that promise. Hidden labor is not in itself a deception. False assurance is. That principle does a surprising amount of work. It explains why nobody feels cheated that Ted Sorensen drafted John F. Kennedy's inaugural address, but many felt cheated when it emerged that Sorensen had also drafted much of Kennedy's Pulitzer Prize-winning book Profiles in Courage. It explains why a pharmaceutical company's writer drafting a journal article that a prominent physician then signs is a scandal, while a ghostwriter drafting a footballer's autobiography is a routine commission. It explains why the law, which cares mostly about who owns a text, so often gives the wrong answer to the question of who wrote it. The principle has a second half, which concerns the ghost. The promise a name makes is a promise to readers. But there is also a person behind the curtain whose skill made the text worth reading, and whose invisibility is part of what is being bought and sold. The ethics of ghostwriting is not only about whether audiences are deceived; it is also about whether the people who do this work are treated fairly, whether their self-effacement is chosen and paid for or extracted from them, and what happens to a writer who spends a career speaking in other people's voices. Any honest account has to hold both halves together. Why the question is harder than it looks It is tempting to settle the matter with a slogan. One camp says authorship simply means writing the words, so every ghostwritten text is a small lie. The other says that everyone knows how these things work, so no one is deceived and there is nothing to discuss. Both slogans collapse on contact with cases. The first fails because authorship has never meant simply writing the words. Editors reshape books; translators recompose them; the drafts of great speeches pass through a dozen hands. A novelist whose editor restructured the second half of her book is still the novel's author. A scientist who designed an experiment and interpreted its results is an author of the paper even if a junior colleague drafted the methods section. If authorship meant composition alone, very little that we read would have an author at all. The second fails because "everyone knows" is rarely true of everyone, and because knowing that a practice exists is different from knowing that it applies in a given case. Many readers of political memoirs assume a professional hand was involved; fewer assume it when a politician publishes a book of personal reflection that won a literary prize. Most university teachers know that essay-writing services exist; that knowledge does not make it acceptable for a particular student to hand one in. The "open secret" defence works only when the secret is genuinely open to the people relying on the name, and part of the task of this book is to identify when that is so. How the book proceeds The first chapter shows that the solitary author, composing alone and owning the result, is a historical latecomer. For most of the history of writing, texts were produced by many hands and signed by one, from the speechwriters of ancient Athenian courts to the workshops of nineteenth-century French novelists. The second chapter takes authorship apart into its components, drawing on the sociologist Erving Goffman's distinction between the person who speaks, the person who composes, and the person whose position is being put forward. The third develops the idea of an attribution contract: the tacit understanding, specific to each genre, of what a name on a text guarantees. The next four chapters test that framework against the major arenas in which ghostwriting happens. Political speechwriting, taken up in the fourth chapter, turns out to be the most openly ghostwritten form and in some ways the most honest. Celebrity and political memoir, the subject of the fifth, is where the attribution contract is most confused, because memoir sells intimacy, and intimacy is exactly what a hired writer manufactures. The sixth chapter turns to the ghost: the craft of writing in another person's voice, the economics and contracts of the trade, and the long history of writers whose labor was taken without consent. The seventh examines academic and scientific writing, where the attribution contract is at its strictest and where ghostwriting shades into fraud, both in student essays and in industry-drafted medical research. The eighth chapter asks what the law says. The answer is that copyright and moral-rights regimes were built to decide who owns a text and who may be named on it, not whether a name tells the truth, and that the gap between ownership and authorship produces some odd results. The ninth chapter considers what happens when the ghost is not a person at all. Large language models now draft emails, speeches, essays and books on request, and they force every one of the book's earlier questions into the open at once: what a name certifies, whether undisclosed help is deception, and whether writing that no human composed can have an author. The conclusion does not summarise. It argues for a small set of commitments that follow from the preceding chapters: what readers are entitled to, what principals owe, what ghosts can fairly ask, and where institutions should draw lines that at present they draw badly or not at all. A note on terms Some vocabulary will recur. The principal is the person under whose name a text appears. The ghost is the person who composes it without, or with only partial, public credit. Attribution means the public statement, usually by a byline or cover credit, of who is responsible for a text. Voice means the recognisable texture of a writer's prose: its rhythms, vocabulary, habits of emphasis and characteristic moves of thought. The word ghostwriter itself is an American coinage of the early twentieth century; the older English term was simply "hack" or "amanuensis," and French long used a term, nègre littéraire, whose racial origin has led many writers and publishers to prefer prête-plume, "lender of the pen." The change of word is a small sign of a larger change of attitude: a practice once treated as faintly disreputable servitude is increasingly understood as a profession with its own skills and its own ethics. This book is an attempt to say what those ethics are. Chapter 1. Many Hands, One Name The image most modern readers carry of an author is of a single person alone at a desk, turning private experience into public words and owning the result. It is a powerful image, and it shapes nearly every intuition people have about ghostwriting. If authorship is solitary composition, then ghostwriting is an impersonation: somebody else sat at the desk. But the image is young. For most of the history of written language, texts were routinely produced by more than one person and presented under one name, and nobody thought this remarkable. Seeing how ordinary the practice once was does not settle whether it is acceptable now. It does show that the question has never been whether a single person composed a text, but what a name attached to it was understood to mean. Speaking in another's character The first professional ghostwriters whose work survives in quantity were the logographoi of classical Athens, the "speech-writers" of the fifth and fourth centuries BCE. Athenian courts had no professional advocates in the modern sense. A citizen who sued or was sued was expected to plead his own case before a large jury of fellow citizens, and to do so in person. Many litigants were not practised speakers, and so a trade grew up of men who would study the facts of a case and write a speech for the litigant to learn and deliver as his own. The most celebrated of these was Lysias, a resident foreigner who could not himself address the Assembly and who made his living composing speeches for others. One of his best-known works, On the Murder of Eratosthenes, is the defence of a husband named Euphiletus who had killed his wife's lover. It is written in the first person, in the voice of a plain, somewhat naive man who describes his domestic life with disarming frankness. Ancient critics admired Lysias above all for what they called ethopoeia, the art of constructing a speaker's character through his words, so that the jury heard not a clever professional but an honest householder. The speech was designed to sound as though no speechwriter had been involved. Several features of the Athenian arrangement are worth noticing because they recur throughout this book. The practice was widely known; Plato's Phaedrus opens with a young man carrying around a text by Lysias, and later orators such as Demosthenes worked as logographers early in their careers. It was also mildly disreputable; being known to have hired a speechwriter could be used against a litigant, and opponents sometimes accused each other of reciting a professional's words. And the whole enterprise depended on a particular kind of craft, the capacity to write convincingly in someone else's character. The ghost's defining skill was the manufacture of an authenticity that was not, strictly, his own. The Athenian jury knew such men existed. What each juror did not know was whether the man in front of him had used one, and the logographer's art was to make sure the question never arose. Secretaries, scribes and the voice of office Rome added the secretary. Cicero's freedman Tiro took down his master's words, managed his correspondence, and after Cicero's death edited and published his letters and speeches. How much of the published text is Tiro's is impossible to recover, and the uncertainty is itself revealing. Nobody at the time thought it mattered, because what gave a letter its value was that it came from Cicero: it carried his authority, his relationships, his political weight. Composition was a service that great men commanded, as they commanded the copying and delivery of their letters. The medieval world institutionalised this. Across Europe, the ars dictaminis, the art of letter writing, was taught as a professional discipline, and trained dictatores composed letters for bishops, merchants, city councils and kings. A letter from a monarch was a letter from the crown, drafted by a chancery. In the chanceries of Renaissance Italy, humanist secretaries became celebrated figures in their own right. Coluccio Salutati, chancellor of Florence at the end of the fourteenth century, composed the republic's official letters in a Latin so forceful that an often-repeated story has Florence's great enemy, the Duke of Milan, complaining that Salutati's pen did him more damage than a troop of cavalry. The letters went out in the name of the Florentine government. Salutati's authorship was known and admired, and it detracted nothing from the letters' status as the republic's word. The logic here is the logic of office. When a text speaks for an institution, the person who signs it is not claiming to be its composer but to be its authority. The same logic governed the American republic's founding documents. George Washington's Farewell Address of 1796, one of the most influential texts in American political history, was drafted in large part by Alexander Hamilton, working from an earlier draft that James Madison had prepared when Washington first considered retiring in 1792 and from Washington's own instructions and emendations. The address went out under Washington's name alone, and it was Washington's in the sense that mattered: it was his decision to step down, his statement of the principles by which he wished the new nation to govern itself, and his reputation that stood behind it. Hamilton's hand was acknowledged among insiders and documented later. It was not a secret kept from the public so much as a detail the public had no reason to ask about. The invention of the solitary author What changed was not the practice of shared composition but the value placed on a particular idea of authorship. Several developments converged across the eighteenth century. The first was legal. The Statute of Anne, passed in Britain in 1710, is usually described as the first modern copyright law. It vested the right to print and reprint a book in its author and the author's assigns for a limited term, rather than in the guild of printers and booksellers who had previously held perpetual rights. The statute was driven largely by booksellers' commercial interests, and in practice authors typically sold their rights to booksellers at once. But it made the author the legal origin of a property right. The historian Mark Rose, in Authors and Owners, traces how the ensuing litigation over literary property forced courts and pamphleteers to articulate what an author was and why an author's work should belong to him. The answer that emerged was that a text was the expression of its author's individual mind, and that this individuality was the source of the property. The second was aesthetic. The poet Edward Young's Conjectures on Original Composition, published in 1759, argued that genuine literature grew organically from the author's own genius rather than being assembled from inherited models. The Romantic movement that followed made this the ruling ideal. The poet was a singular sensibility, and the work was the trace of that sensibility on the page. Martha Woodmansee, in a series of studies of German and English authorship in this period, argued that the Romantic conception of the author as solitary originating genius was in large part a response to the market conditions of professional writing: writers who now had to live by selling their work needed a theory of why their work was uniquely theirs. The third was the periodical press. Well into the nineteenth century, most articles in British and American magazines and newspapers were unsigned. The great quarterly reviews spoke in an institutional "we," and a young writer's essay might appear under no name at all, its authority borrowed from the journal. Over the second half of the century, the practice of signing articles spread, driven in part by arguments that readers had a right to know who was addressing them and that writers deserved credit for their work. Signature became a norm in journalism, and with it came the expectation that the name at the top of an article identified the person who wrote it. The combined effect was to make the solitary composer the default meaning of authorship in literature and journalism. The older meaning, in which a name identified the authority behind a text rather than the hand that wrote it, survived in government, in law and in commerce. The two meanings have coexisted ever since, and much of the confusion about ghostwriting comes from applying one of them where the other is in force. The novel factory The strongest evidence that the solitary author was an ideal rather than a description is how quickly the most commercially successful writers of the nineteenth century departed from it. Alexandre Dumas produced a torrent of novels, plays and travel books, many in collaboration with other writers. The most important of these was Auguste Maquet, a historian and playwright who researched and drafted large portions of The Three Musketeers and The Count of Monte Cristo in the 1840s. Dumas typically reworked and dramatised Maquet's drafts, and there is general agreement that the energy of the finished books owes much to him. But the books were published as Dumas's alone. In 1845 a pamphleteer named Eugène de Mirecourt published an attack titled, in translation, Novel Factory: The House of Alexandre Dumas and Company, accusing Dumas of running a workshop of hired hands. Dumas sued him for defamation and won. More than a decade later, after the two men fell out, Maquet himself went to court seeking recognition as co-author of the novels they had produced together. He lost. The court treated the arrangement between them, including the money Dumas had paid, as settling the matter. The episode anticipates, with uncanny precision, the legal and ethical tangle this book explores in later chapters: a writer who had willingly worked unnamed, who was paid, and who later came to feel that the bargain was unjust because what he had sold turned out to be worth far more, in reputation, than anyone had priced. A darker case followed at the turn of the century. Henry Gauthier-Villars, a Parisian man of letters who published under the name Willy, married a young woman from Burgundy named Sidonie-Gabrielle Colette. At his urging she wrote down stories of her schooldays, which he edited and published in 1900 as Claudine at School under his own name. The book was a sensation and spawned sequels, a stage adaptation and a line of merchandise. By Colette's own later account in her memoir of those years, Willy kept her writing under pressure and treated the income and the reputation as his. After their divorce she fought for years to establish her authorship of the Claudine novels and went on to become one of the most admired French writers of the twentieth century under her own name. The Colette case is what ghostwriting looks like when the ghost's invisibility is extracted rather than bargained for, and it is a useful reminder that the ethics of the practice concern the writer as well as the reader. Syndicates and house names In the United States, the industrialisation of popular fiction produced the purest form of the ghost system. Edward Stratemeyer, a writer of boys' adventure stories, founded what became known as the Stratemeyer Syndicate early in the twentieth century. The syndicate devised series characters and plot outlines, then paid freelance writers a flat fee to produce each book to specification, publishing them under house pseudonyms. The Hardy Boys appeared under the name Franklin W. Dixon; Nancy Drew, from 1930, under the name Carolyn Keene. The writers signed away all rights and agreed never to reveal their involvement. Mildred Wirt Benson, a young journalist from Iowa, wrote most of the early Nancy Drew books, and the independent, resourceful character that generations of girls admired owed much to her. For decades her role was unacknowledged in public, and "Carolyn Keene" was presented as a real person. The fiction held until 1980, when a lawsuit between publishers over the rights to the series brought the syndicate's methods into court, and Benson testified about her work. She had been paid what she agreed to be paid. What she had not been given, and what the arrangement was designed to deny her, was any public connection to the most successful thing she ever wrote. The syndicate model looks exploitative to modern eyes, and in some respects it was. But it also reveals something about what readers of series fiction were actually buying. Children who loved Nancy Drew were not relying on a promise that a woman named Carolyn Keene had composed each book. They wanted another Nancy Drew story that behaved like the others. The house name functioned less as an author's signature than as a brand, a guarantee of consistency. The deception was real, since the syndicate invented a fictional author and presented her as real; but the thing the deception concealed was not, for most readers, the thing they cared about. That distinction, between concealing something the audience relies on and concealing something it does not, is the key to the rest of this book. What the history shows Three lessons emerge from this brief history, and each will be developed later. First, the separation of composition from attribution is the historical norm, not a modern corruption. Speechwriters, secretaries, chancery clerks and workshop assistants have always written under other people's names, and societies have usually tolerated or even admired the practice where it served an office, an institution or a public purpose. Second, the idea that a name on a text identifies the person who composed it is itself a historically specific convention, strongest in literary writing, journalism and scholarship, which developed alongside modern copyright and the Romantic idea of genius. Where that convention is in force, ghostwriting sits in tension with it. Where it is not, ghostwriting is largely unproblematic. Third, the practice has always had two distinct ethical faces. One looks outward, towards the audience, and asks whether they were misled about something they had a right to know. The other looks inward, towards the ghost, and asks whether the arrangement was fair to the person whose work was absorbed into another's name. Maquet and Colette complained about the second; the readers of Dumas and Willy, for the most part, did not complain about the first. A satisfactory account of ghostwriting has to explain both kinds of wrong and show why they can come apart. To do that, it is necessary to take authorship itself apart and look at its components. Chapter 2. What Authorship Is Made Of Every year, millions of people buy a greeting card, sign their name under a verse composed by a salaried writer at a card company, and send it to someone they love. Nobody calls this ghostwriting, and nobody feels deceived on receiving it. In Edmond Rostand's play Cyrano de Bergerac, first staged in 1897, a handsome but tongue-tied soldier named Christian wins the heart of Roxane with love letters secretly written by his eloquent friend Cyrano. The play's audiences have always understood this as a deception, and a painful one: Roxane falls in love with a soul she has been shown in someone else's words, and she discovers the truth only as Cyrano is dying. In both cases one person composes words that another person signs and sends to a beloved. The difference between them is the whole subject of this chapter. It lies not in who wrote the words but in what the act of signing them was taken to assert. The card sender asserts only that she chose this card and means its sentiment; the recipient knows how cards work. Christian's letters asserted, and were read as asserting, that the passion and wit on the page came from the mind of the man who signed them. Roxane was relying on exactly the thing that was false. To see why the same act can mean such different things, it helps to recognise that "authorship" is not one relation between a person and a text but a bundle of several, which usually travel together and which ghostwriting pulls apart. Goffman's three roles The most useful starting point comes not from literary theory but from sociology. In an essay called "Footing," collected in his book Forms of Talk in 1981, Erving Goffman observed that the everyday idea of "the speaker" runs together three distinct roles. The animator is the person who physically produces the utterance, the "sounding box" who speaks the words aloud or puts them on the page. The author is the person who selected the sentiments and composed the words in which they are expressed. The principal is the person whose position is established by the words, whose beliefs are being told, and who is committed to what the words say. In ordinary conversation one person occupies all three roles at once. But Goffman noticed how often they come apart. A newsreader animates words that a script-writer authored on behalf of a broadcaster that is the principal. An actor animates a playwright's words and is principal of nothing. A spokesperson reading a prepared statement is animator; a communications team is author; the company is principal. A person reading a greeting card's verse aloud to a friend is animator of someone else's authorship and yet principal of its sentiment, which is precisely why the card works. Ghostwriting, in Goffman's terms, is an arrangement in which the author role is filled by one person while the principal role, and often the animator role, is filled by another, and in which the public attribution names only the principal. A president delivering a speech written by staff is animator and principal; the speechwriter is author. A celebrity whose memoir was ghostwritten is principal; the ghost is author; and in a book, the animator role more or less disappears, because the page does not care whose hand typed it. This already dissolves the naive charge that ghostwriting is simply lying. The name on a speech or a memoir can truthfully identify the principal even when it does not identify the author, and in many contexts the principal is the role that matters. When a head of state speaks, the question the audience needs answered is not who chose the adjectives but whose commitments are being made. The speechwriter's contribution is real, but it is not what the audience is relying on. Unbundling further Goffman's scheme is a good start but it is built for speech, and texts involve more. For the purposes of this book it is useful to separate authorship into five components. Origination is being the source of the substance: the experiences recounted, the ideas argued, the data reported, the decisions announced. In a memoir, origination lies with the person whose life it is. In a scientific paper, it lies with whoever conceived the study and produced the findings. Composition is producing the actual words, sentences and structure. This is what ghosts do, and what editors and co-writers do in varying degrees. Endorsement is adopting the text as one's own: reading it, approving it, and presenting it to the world as expressing one's views or one's account. Endorsement is what a signature performs. It corresponds roughly to Goffman's principal. Accountability is standing behind the text once it is public: answering for its claims, bearing blame for its errors, being the person who can be challenged, sued, questioned or voted out because of it. Credit is the public recognition, and often the professional and financial reward, that attaches to having produced the text. In the idealised solitary author, one person holds all five. A ghostwritten text distributes them. Origination may be shared between the principal, who supplies the life or the policy, and the ghost, who supplies structure, emphasis and sometimes ideas the principal never had. Composition lies mostly with the ghost. Endorsement, accountability and credit are assigned to the principal. What makes ghostwriting ethically distinctive is that the public attribution routinely reports the last three and says nothing about the second. Table 1 shows how the components are distributed across some of the arrangements this book examines. Table 1. How the components of authorship are distributed in different writing arrangements. Arrangement Origination Composition Endorsement and accountability Public credit Solitary author Named author Named author Named author Named author Political speech Leader and staff Speechwriter Leader Leader Ghostwritten memoir Principal's life, ghost's shaping Ghost Principal Principal, ghost sometimes noted Judicial opinion drafted by clerk Judge's decision Clerk, revised by judge Judge Judge Purchased student essay Hired writer Hired writer Student, falsely Student Industry-drafted medical paper Sponsor's data and message Medical writer Named academic, often thinly Named academic Reading down the columns shows where the trouble lies. In the first four rows, whatever the audience is primarily relying on is truthfully reported by the name. A reader of a judicial opinion needs to know that this judge decided the case and is accountable for the reasoning; the clerk who drafted the text is a professional convenience, well known to the legal profession, and the judge's signature truthfully reports the judicial act. In the last two rows the name reports something false about the very component the audience relies on. An essay is graded as evidence that the student originated and composed it; the purchased essay's name is false in both respects. A medical paper's named author is presumed to have designed, conducted or at least critically evaluated the research; in industry-ghosted papers of the kind examined in a later chapter, the named academic may have done little more than lend a reputation. What a signature does It is worth dwelling on endorsement, because it is the component that most defenders of ghostwriting lean on and the one most critics underrate. Signing a text is not merely a report. It is an act, and like the acts philosophers of language call performatives, it changes the signer's normative position. When a person signs a contract drafted by lawyers, nobody thinks the signature falsely claims that the signer wrote the contract. The signature binds the signer to it. When a head of state signs a treaty, the same is true; nobody expects the head of state to have composed a single clause. The signer does not claim composition; she assumes the obligations. Many ghostwritten texts function this way. The principal, by signing, takes on the text's commitments and the risks that come with them. If the text contains a defamatory statement, it is the principal who may be sued. If a speech makes a promise, it is the leader whose credibility depends on keeping it. If a memoir contains an error of fact, it is the named author who will be asked about it on television. The ghost's relative safety from these consequences is part of the price of the ghost's anonymity. In these arrangements, the signature is truthful about the thing it most directly asserts: this is mine now, and I answer for it. Endorsement can, however, be thin or thick. A thick endorsement follows real engagement with the text: the principal read it, argued with it, changed it, and could defend its contents in her own words. A thin endorsement is little more than permission to use a name. Much of the variation in how ghostwriting feels, morally, tracks the thickness of endorsement. A president who revises a speech draft line by line and a president who reads it for the first time on the teleprompter are both principals in Goffman's sense, but only the first has made the speech his in the sense audiences tend to assume. At the extreme, an endorsement can be so thin that the principal becomes little more than a label, and the promise that she stands behind the text becomes as empty as the promise that she wrote it. Voice and the thing that cannot be delegated There is one component of authorship that the five-part scheme does not capture well, and it is the one that makes memoir and personal writing so difficult. It is voice. In most texts, voice is instrumental. A good speech has a voice suited to its speaker and its occasion, but the audience does not take the voice as evidence of anything beyond the speaker's competence in choosing staff. In personal writing, voice is not instrumental; it is the point. When a reader of a memoir feels that she has come to know the person whose life it describes, she is responding largely to voice: the texture of attention, the choice of what to notice and what to pass over, the jokes and hesitations, the specific way a mind moves. Roxane, in Rostand's play, falls in love with a voice. The difficulty is that voice is the very thing a skilled ghost produces. A good ghostwriter does not write in her own voice; she listens for hours to a principal talk and constructs a written voice that sounds like the principal at his best. Sometimes this is fidelity: the ghost catches patterns of speech and thought that are genuinely the principal's and renders them in prose he could not have written himself. Sometimes it is invention: the ghost gives the principal a wit, a lyricism or a reflective depth he does not possess. The reader usually cannot tell the difference, and the principal sometimes cannot either. Whether constructed voice counts as deception depends on what the reader took the voice to certify. If the reader took it to certify that this is how the principal thinks and feels, a constructed voice faithful to the principal's actual patterns of mind is not a lie, and an invented voice may be. If the reader took it to certify that the principal composed these sentences, both are false. The ethics of memoir therefore depends heavily on an empirical question about readers: what do they take the voice of a celebrity memoir to be evidence of? That question returns in a later chapter. Authorship as a function The philosopher Michel Foucault, in a lecture titled "What Is an Author?" delivered in 1969, argued that the name of an author is not simply a proper name designating the individual who wrote something. It performs what he called an "author function." It groups texts together, assigns them a status, organises how they are to be read and interpreted, and marks them as belonging to a particular kind of discourse. Not every text has an author function in this sense; a shopping list or a private note does not. And the function has varied historically: scientific texts once derived authority from named authors and later came to derive it from method, while literary texts came to be read increasingly through their authors' biographies. Foucault's point, stripped of its larger philosophical ambitions, is useful here. It suggests that what a name does is determined not by the bare fact of who wrote the words but by the institutional and cultural practices that govern a genre. The name "Barack Obama" on the transcript of a State of the Union address performs one function; the same name on the cover of Dreams from My Father performs another; and the name of a first-year student on an essay performs a third. To ask whether ghostwriting is honest, one must ask what function the name is performing in that genre, for that audience. This is the idea that the next chapter develops under the heading of the attribution contract. Two errors the unbundling prevents Taking authorship apart in this way guards against two common mistakes. The first is the purist error: the view that because a ghostwritten text was not composed by the person named, it is necessarily fraudulent. The error lies in assuming that a name always certifies composition. It frequently does not, and in many genres everyone involved understands that it does not. The purist cannot explain why nobody objects to greeting cards, legal contracts, company reports, judicial opinions or presidential speeches, all of which are routinely signed by people who did not compose them. The second is the cynical error: the view that because the practice is common, any use of a ghost is permissible so long as the principal signs off. The error lies in assuming that endorsement can always substitute for composition. It cannot where the audience relies specifically on composition, as in assessment, where a teacher is measuring what a student can do, or in certain kinds of literary recognition, where a prize honours a writer's craft. Nor can a thin endorsement substitute for the thick engagement an audience may reasonably assume. The cynic cannot explain why Christian's letters to Roxane are a betrayal, or why a student with a purchased essay has cheated even though the essay may be excellent and she may agree with every word of it. Between these errors lies the real question: in a given genre, which components of authorship does the name report, and is the report true? The answer is never given by the bare fact of ghostwriting. It is given by the conventions of the genre and the reasonable expectations of the audience, which is to say, by the terms of the attribution contract. Chapter 3. The Attribution Contract In November 1990 the pop duo Milli Vanilli, winners of that year's Grammy award for Best New Artist, admitted that they had not sung a note on their hit album. The voices on the record belonged to session singers hired by their producer, Frank Farian; the two men who danced in the videos and accepted the award had been lip-syncing all along. The Recording Academy withdrew the Grammy, record buyers filed lawsuits, and the pair became a punchline for a generation. What made this a scandal was not that other people had been involved in making the records. Pop records are always the work of producers, engineers, arrangers and songwriters, and the duo's songs were written by others, which nobody minded. The scandal was that the voice itself, the one thing a listener takes a singer's name to guarantee, had come from someone else. The listener's contract with a pop singer is roughly this: the song may be written by anyone, but the voice you hear is the voice of the person whose face is on the cover. Milli Vanilli broke that contract. Session musicians behind a real singer do not. Every genre of text has a contract of this kind. It is rarely written down, and it is never negotiated between the particular writer and the particular reader. It is a background understanding, shared across a community of readers and producers, about which components of authorship the name on a text reports. This chapter develops that idea, which is the core of the book's argument, and sets out the conditions under which it genuinely excuses the use of a ghost. Deception and what the reader is owed Start with what makes ghostwriting wrong when it is wrong. The obvious answer is deception: readers are led to believe something false about who produced the text. But deception, in the sense that matters morally, is not merely the causing of false beliefs. People form false beliefs all the time from texts that are entirely honest, because they make careless assumptions. The philosopher Sissela Bok, in Lying, published in 1978, argued that the wrong of deception lies in its manipulation of another person's choices by distorting the information on which those choices rest. Later work, notably Thomas Carson's Lying and Deception of 2010, refined the analysis: to deceive is to intentionally cause, or knowingly exploit, a false belief that the other person has not consented to and would object to. Two features of this analysis matter for ghostwriting. First, deception requires that the false belief be one the audience was entitled to form given the conventions in play. If a reader believes that the chairman of a multinational bank personally composed the letter to shareholders at the front of the annual report, she is mistaken; but she has not been deceived, because nothing in the conventions of annual reports entitled her to that belief. Second, deception is graver the more the false belief matters to the reader's purposes. A false belief about who chose the adjectives in a speech matters little to a voter deciding whether to trust a candidate's policies. A false belief about who wrote an essay matters enormously to a teacher deciding what grade to give. The attribution contract is the name for the set of conventions that determine which beliefs about a text's production a reader is entitled to form from its attribution. A ghostwritten text is deceptive when it exploits a belief the contract entitles the reader to hold, and the gravity of the deception depends on how much that belief matters to what the reader is doing with the text. Three conditions For a genre convention to excuse ghostwriting, three conditions must hold. Each can fail independently, and most real controversies turn on one of them. The first is that the convention must actually be known to the audience relying on the name. It is not enough that insiders know. A convention that ghosts draft judicial opinions is known to lawyers and law students, who are the principal audience of those opinions, and so it does not deceive them. A convention that ghosts write celebrity novels might be known within publishing, but if the readers who buy such novels believe the celebrity wrote them, the convention does not protect the celebrity. A practice becomes a convention in the relevant sense only when it is common knowledge among the audience: when readers know, and know that others know, that names in this genre do not certify composition. The second is that the name must truthfully report whatever component of authorship the audience primarily relies on. A leader's name on a speech reports endorsement and accountability, and those are what voters rely on. A student's name on an essay reports origination and composition, and those are what an assessor relies on. If the relied-on component is false, no amount of general awareness about ghostwriting will save the text, because the audience is still being handed a false signal about the thing it is using the text to judge. The third is that the endorsement must be real. Even in genres where the name reports only endorsement, the principal must actually have done the endorsing. A chief executive who puts her name to an opinion column she has not read, or a scientist who signs a paper whose data he has never seen, is not using a legitimate convention; he is counterfeiting the one component the convention says his name guarantees. A map of contracts Table 2 sets out the attribution contracts of several common genres, as they generally stand in English-speaking countries today. The entries are generalisations, and the edges of each are contested, but the pattern is clear. Table 2. Attribution contracts in common genres. Genre What the name mainly certifies Is ghosting commonly known? Ghosting generally acceptable? Political speech Endorsement, accountability Yes, widely Yes Corporate letter or report Institutional authority Yes, widely Yes Celebrity memoir Life story, endorsement, truthfulness Partly Yes, if disclosed or clearly conventional Literary novel Imagination and composition Rarely No, unless credited Signed opinion column Views and, often, composition Partly Contested Student assessment Individual origination and composition Irrelevant No Scientific paper Contribution and accountability Partly Only for disclosed writing help The table's third column shows why the "everyone knows" defence varies in strength. Almost everyone knows that presidents have speechwriters. Fewer know that many signed opinion columns in newspapers are drafted by communications staff; the practice is standard in politics and business but many readers assume the named person wrote the piece, particularly when it is written in a personal register. Very few readers of literary fiction assume a ghost, which is why the discovery that a celebrity's novel was written by someone else tends to provoke more scorn than the discovery that the same celebrity's memoir was. The fourth column shows why the answer to "is ghostwriting acceptable?" can never be given in general. The novel and the memoir are both books with a name on the cover, but what the name certifies is different. A memoir's value lies substantially in the life it recounts, which the ghost cannot supply; a novel's value lies in its imagination and prose, which the ghost does supply. If a celebrity novelist's book was written by someone else, the thing readers were paying for came entirely from a person they were not told about. Institutional voices The clearest cases of legitimate ghostwriting are those in which the name functions as an institutional signature. The medieval chancery letter, the Renaissance republic's diplomatic correspondence and the modern corporate report all speak with the voice of an office. The name of the king, the chancellor or the chief executive is a way of indicating which institution is speaking and who within it bears final responsibility. Judicial opinions are an instructive modern example. In the United States federal courts, judges employ law clerks, usually recent law graduates, who research cases and in many chambers draft opinions for the judge's revision. The extent of clerk drafting varies enormously; some judges write every word themselves, and the late Judge Richard Posner of the Seventh Circuit, a prolific writer, was known for drafting his own opinions and was openly critical of the practice of delegating drafting to clerks. But the practice is well known throughout the legal profession, and the name on an opinion is understood to certify that this judge decided the case and adopts the reasoning as the court's. Critics, including Posner, have argued that clerk drafting degrades the quality of judicial reasoning and inflates opinions with boilerplate, and that it risks thin endorsement, in which judges sign reasoning they have not fully tested. Those are serious objections. But they are objections to thin endorsement, not to deception. A lawyer reading the opinion has not been misled about anything the convention entitled her to believe. The personal register The attribution contract becomes most fragile when a text written in an institutional setting adopts a personal register. The standard corporate letter to shareholders is written in the institutional "we," and nobody takes it for a personal composition. A chief executive's post on a professional social network, written in the first person, describing a personal realisation about leadership prompted by a conversation with her daughter, is a different matter. The register signals intimacy and individual composition, which the convention of institutional speech does not support. One sign that people sense this distinction is how some public figures have tried to mark it. When Barack Obama's campaign organisation ran his social media accounts, it adopted a practice of signing messages written personally by Obama with his initials, while the rest were written by staff. The practice implicitly acknowledged that the account as a whole was an institutional voice while signalling to readers which messages carried a personal guarantee. It was a small, practical renegotiation of the attribution contract, and it was sensible precisely because it gave readers a truthful way to distinguish the two. The same fragility appears in letters to newspaper editors, a genre whose contract is strongly personal: a signed letter is presumed to express its signer's own views in the signer's own words. In 2003, reporters for the Gannett newspaper group discovered that newspapers across the United States had printed near-identical letters, each signed by a different soldier serving in Iraq, praising progress in the war. The letters had been drafted within the soldiers' unit and circulated for signature. Several soldiers said they agreed with the sentiments; at least one said he had not signed the letter sent in his name. Even for those who agreed, the letters broke the contract of the genre: an editor who publishes a letter from a soldier does so because it purports to be one person's independent testimony, and a campaign of identical testimonies is something else. Mixed audiences The first condition, that the convention be known to the audience relying on the name, raises a practical difficulty. Audiences are not uniform. Any widely read text reaches some readers who understand its genre's conventions perfectly and others who do not. Whose understanding sets the terms? Consider a worked example. A member of a national legislature publishes an opinion column in a regional newspaper, under her own name, arguing for a new bridge in her district. The column was drafted by her communications director, and she read it, changed two sentences and approved it. Among its readers are the newspaper's editor, who knows perfectly well how such columns are produced; a political journalist, who assumes a staffer drafted it; a retired teacher who has followed the legislator's career and believes she writes her own columns because they sound like her; and a teenager who has never thought about the matter at all. Has anyone been deceived? The editor and the journalist plainly have not. The teenager has formed no belief either way. The retired teacher holds a false belief, but it is not obvious that the column caused it, or that she was entitled to it. What she relies on the column for, if she relies on it at all, is knowing where her representative stands on the bridge, and that the column reports truthfully. Her false belief about composition does no work in her judgement of the representative's position. On the analysis given here, the column is honest, because what the genre's name mainly certifies, the legislator's position and her accountability for it, is true, and because the convention that legislators' columns are staff-drafted is widely enough known that a reasonable reader is not entitled to assume otherwise. Now change one detail. Suppose the column is not about a bridge but is a personal essay about the legislator's experience of her father's death, written in the first person, full of specific memories and reflections, and published on the anniversary of his death. The communications director drafted this too, from a short conversation. The retired teacher is moved by it and feels she has come to know her representative better. This time the false belief does real work. The value of the essay to her lies in its being the legislator's own reflection, and the register of the piece invites exactly that reading. The convention that staff draft policy columns does not extend, in most readers' understanding, to staff drafting personal grief. The general principle is that the relevant audience is the reasonable reader for whom the text is designed, and that the relevant convention is the one that reader would apply to a text of this kind in this register. A principal cannot shelter behind insiders' knowledge when the text is aimed at outsiders, and cannot shelter behind a convention that governs one register when she has chosen another. The more a text is built to produce a sense of personal access, the less it can rely on general knowledge that public figures have staff. When contracts change Attribution contracts are not fixed. They shift as practices become more or less visible, and they can be renegotiated deliberately. Three mechanisms matter. The first is exposure. When a hidden practice is revealed, the contract either expands to include it, as happened with presidential speechwriting in the twentieth century, or hardens against it, as happened with the discovery of industry-ghosted medical research. Which way it goes depends on whether audiences, once informed, decide that the concealed component matters to them. The second is disclosure conventions. Credit lines such as "with," "as told to" and acknowledgements to a named writer are devices for making the contract explicit. They have become more common in memoir and in sports autobiography, and they shift what the name on the cover certifies: "by X with Y" tells the reader that X is the principal and Y a principal composer, and removes any basis for complaint about composition. The third is changes in the audience's purposes. The contract for student writing, for example, is strict because assessment measures individual capacity. If educators change what assessment is meant to measure, as some are now doing in response to machine-generated text, the contract changes with it. A course that explicitly allows students to use drafting help and assesses their ability to direct, evaluate and revise that help has a different contract from one that assesses unassisted composition. What the contract does not settle The attribution contract answers the outward-facing question: whether an audience has been deceived. It does not answer the inward-facing one: whether the ghost has been treated fairly. A convention can be perfectly well understood by readers while still being exploitative of writers, and a writer can be fairly paid and freely consenting while the text she produces deceives its audience. The syndicate writers who produced children's series books under house names were deceiving young readers about the existence of Carolyn Keene, but most of them had made a bargain they understood. Colette's early novels deceived readers about their author, and her husband took from her what she had not agreed to give. The next four chapters test the attribution contract against the arenas where ghostwriting is most visible and most disputed. Throughout, both questions stay in view: what the name promised the reader, and what the arrangement owed the writer. Hashtags: #TheEthicsOfGhostwriting #Ghostwriting #AuthorshipEthics #LiteraryLabor #LiteraryEthics #WritingEthics #AuthorialVoice #AuthorshipAndIdentity #LiteraryStudies #GhostwriterRights #CreativeLabor #WritingProfession #PublishingIndustry #BookPublishing #CollaborativeWriting #LiteraryAttribution #AuthorialCredit #IntellectualProperty #CopyrightLaw #MoralRights #LiteraryAuthenticity #MemoirWriting #PoliticalSpeechwriting #AcademicIntegrity #ResearchEthics #ScientificGhostwriting #ProfessionalWriting #AIAndAuthorship #ArtificialIntelligenceInWriting #EthicsOfPublishing

Download the Book (PDF): Introduction Every foreign army that has ever tried to hold ground among people who do not speak its language has needed someone to stand in the middle. The soldier at the checkpoint, the officer at the village council, the doctor at the field hospital, the intelligence analyst across the table from a detainee: none of them can do their work without a person who carries meaning from one side to the other. That person is almost always the least protected member of the team. He or she is usually local, often young, frequently hired in a hurry, paid in cash or on a short contract, and recognisable to everyone in the district as the one who stands beside the foreigners. When the foreigners leave, the interpreter usually stays. This book is about the moral situation of that person. It is not a history of military linguistics or a manual of interpreting technique, though it draws on both. Its subject is the tangle of obligations that surrounds the interpreter in war: what the interpreter owes to the people who hire them, to the people they speak with, to their own community and to the truth of what is said; and, just as important, what the institutions that use interpreters owe to them in return. The argument in brief The argument can be stated plainly. Civilian interpreting has long been governed by an ideal of the interpreter as a neutral conduit, an instrument that transfers words from one language to another without adding, subtracting or taking sides. That ideal has real virtues in a courtroom or a conference hall. In a war zone it becomes a convenient fiction. It allows armies, intelligence services, contractors and even humanitarian agencies to treat the interpreter as a piece of equipment, present when needed and invisible when responsibility is assigned. It hides the fact that the interpreter is a party to the encounter, seen by every other party as aligned with someone, and exposed to danger precisely because of that perceived alignment. Once the fiction is set aside, the ethics of war-zone translation look different. The central question is no longer only whether an interpreter rendered a sentence faithfully. It is who created the risk the interpreter now carries, and who is bound to answer for it. The answer, in most cases, is the employer. An army that places a local civilian at its side in public, in front of cameras, in hostile villages and in interrogation rooms has made that person a target as surely as if it had painted a mark on their door. The obligations that follow from this are not charity. They are the ordinary moral consequence of having put someone in harm's way for your own purposes. That shift in emphasis does not excuse interpreters from their own responsibilities. It clarifies them. An interpreter who knows that they are a moral agent rather than a machine can decide in advance what they will and will not do, can recognise when they are being used to disguise coercion, and can claim the right to refuse. The neutral-conduit model, by contrast, leaves the interpreter with no vocabulary for refusal: a conduit does not choose. So the book argues in both directions. Those who employ interpreters in war owe them far more than they have usually given, before, during and after their service. Interpreters, in turn, owe it to themselves and to the people across the table to act as the agents they already are. Why it matters now The wars in Iraq and Afghanistan made the plight of interpreters briefly visible to Western publics. Interpreters were killed on their way to work, threatened through letters left at their homes, and hunted after their contracts ended. Resettlement programmes were created, underfunded, delayed and reopened. In August 2021 the collapse of the Afghan Republic turned years of slow administrative failure into a scramble at the gates of Kabul airport, broadcast worldwide. In Britain, it later emerged that a Ministry of Defence spreadsheet containing the details of Afghans who had applied for relocation had been leaked in early 2022, exposing thousands of people and their families; the government kept the breach secret under a court order until July 2025. These episodes are sometimes told as scandals, as though something unusual had gone wrong. The deeper lesson is that nothing unusual went wrong. The same pattern of reliance, exposure and abandonment can be traced through the colonial wars of the nineteenth and twentieth centuries, through Vietnam, through the Balkans, and back as far as the conquest of Mexico. It recurs because the structure that produces it recurs. Understanding that structure is the precondition for breaking it, and the conflicts of the coming decades will need interpreters as much as any in the past. Scope and terms The book concentrates on spoken interpreting in face-to-face encounters, because that is where the moral and physical hazards are sharpest. Written translation in war raises its own questions, about propaganda, intercepted communications and the manipulation of documents, and these appear where they bear on the main theme. The word "interpreter" is used for people who render speech; "translator" for those who render writing; and "linguist" in the broad military sense that covers both, together with cultural advisers who may do little formal interpreting at all. In everyday usage, and in much official documentation, these terms blur, and where a source uses one loosely the book follows it. The focus is on two kinds of employer: military forces, including the contractors who recruit linguists on their behalf, and humanitarian organisations, including United Nations agencies and non-governmental organisations. These are very different institutions with very different ethical codes, yet the interpreter often moves between them, and the people they meet often cannot tell the difference. Journalists' fixers, who combine interpreting with logistics and local knowledge, are discussed where their experience illuminates the wider pattern. A word about evidence. The subject is poorly documented in exactly the places where documentation matters most. No authoritative count exists of interpreters killed in Iraq or Afghanistan. Advocacy groups have circulated estimates, some widely quoted, but none rests on a systematic register, and governments did not keep one. Resettlement statistics are published irregularly and revised often. Where firm figures exist, the book gives them with their source; where they do not, it says so. The absence of reliable numbers is itself part of the story, since what institutions do not count they find it easier not to answer for. The shape of the book The first chapter sets out the neutral-conduit model and explains why it breaks down under the conditions of war. The second places the modern interpreter in a long historical line of go-betweens, from Malintzin in sixteenth-century Mexico to the dragomans of the Ottoman court and the interpreters of the Nuremberg trials, to show how old the dilemmas are. The third describes who war-zone interpreters actually are, since the ethical position of a uniformed military linguist differs sharply from that of a local civilian hired by the week. The middle chapters take up the hardest problems. The fourth examines divided loyalties: how interpreters are seen by their employers, their communities and the enemy, and how each form of suspicion shapes what they can safely do. The fifth enters the interrogation room, where the question of complicity in coercion is most acute. The sixth turns to humanitarian settings, where the principle of neutrality has a different meaning and a different set of traps. The seventh chapter traces the pattern of abandonment across several wars and the resettlement schemes that followed. The eighth examines what the law does and does not provide. The ninth sets out what is owed: a practical account of the obligations of employers across the whole life cycle of an interpreter's service, and of the ethical commitments interpreters can reasonably make for themselves. The conclusion draws out what follows for anyone who will plan, fund, fight or report on the next war. Throughout, the aim is to treat interpreters not as victims to be pitied or heroes to be praised, but as people doing morally serious work under conditions that others have created. They deserve the same seriousness in return. Chapter 1. The Conduit and the Party In the professional world of interpreting, one image has dominated for most of the past century. The interpreter is a window, a pipe, a bridge, a channel; in the technical literature, a conduit. Words enter in one language and leave in another, unchanged in meaning, unaltered in tone, uncoloured by the interpreter's own views. The best interpreter, on this account, is the one nobody notices. If the parties leave the room feeling that they spoke directly to each other, the interpreter has succeeded. This image did not arise by accident, and it is not foolish. It protects real goods. It protects the parties from an interpreter who might distort their words for private reasons. It protects the interpreter from being blamed for what others say. It supports a professional identity grounded in skill rather than allegiance. To understand why it fails in war, one must first understand what it was built to do. Where the conduit model comes from Modern professional interpreting grew up in three settings: international conferences, courts of law and, later, public services such as hospitals and immigration offices. Each setting shaped the ethical codes that now govern the profession. The conference interpreter, working from a booth with headphones and a microphone, is physically separated from the speakers. The International Association of Conference Interpreters, known by its French acronym AIIC, was founded in Paris in 1953 and developed a code of professional ethics centred on confidentiality, competence and professional conduct. In the booth, invisibility is not a metaphor. The interpreter is literally unseen, and the parties relate to one another rather than to the person rendering their words. The court interpreter works in a setting where the law has a strong interest in the exact words spoken. A witness's hesitation, a defendant's choice of term, the difference between "I hit him" and "he got hit" can decide a case. Court interpreting codes in many jurisdictions therefore insist on rendering everything, including profanity, errors and evasions, and on refraining from any explanation or advice. The interpreter is an officer of the court whose only loyalty is to accuracy. Community or public-service interpreting, which expanded rapidly from the 1970s onward as immigrant populations grew in Western countries, inherited much of this framework. Codes for medical and social-service interpreters typically list accuracy, completeness, impartiality and confidentiality as core duties, often in that order. The underlying logic is the same: the interpreter should enable communication between parties without becoming a party. Scholars of interpreting have been questioning the conduit model for decades, and their critique matters for what follows. Cecilia Wadensjö's study of dialogue interpreting, Interpreting as Interaction (1998), showed through close analysis of recorded encounters that interpreters constantly coordinate conversation: they decide who speaks next, ask for clarification, manage overlap and repair misunderstandings. Claudia Angelelli, in Revisiting the Interpreter's Role (2004), surveyed working interpreters and found that most saw themselves as visible participants, not neutral pipes, even when their codes told them otherwise. The conduit, these studies suggested, was never an accurate description even of peaceful settings. It was a normative ideal, useful as a discipline, misleading as a picture. Four assumptions that war removes The conduit model rests on assumptions that are usually left unstated because in peacetime they are usually true. War removes them one by one. The first assumption is that the interpreter is an outsider to the dispute. The conference interpreter rendering a trade negotiation between two governments is not personally affected by the outcome. The court interpreter has no stake in the verdict. In war, the local interpreter is almost never an outsider. They belong to one of the communities affected by the conflict, sometimes to one of the factions fighting it. Their family lives in the district where the patrol is operating. The village elder across the table may know their father. The detainee may be a neighbour's son. Whatever the interpreter says will have consequences for people they know. The second assumption is that the parties understand and accept the interpreter's role. In a courtroom, everyone knows what the interpreter is for and what they are not for. In a village in Helmand or a checkpoint in Baghdad, the people addressed by a foreign soldier through a local interpreter often have no concept of professional neutrality. They see a local man in foreign body armour, speaking for the foreigners, and they draw the obvious conclusion. So, frequently, do the soldiers. To the patrol, the interpreter is part of the team. To the villagers, the interpreter is a collaborator. Neither side sees a conduit. The third assumption is that the interpreter's physical safety is not at stake. Codes of ethics written for peaceful settings say almost nothing about danger, because danger is not part of the job. In war it is the defining feature. The interpreter goes where the patrol goes and is often the first person a hostile crowd identifies. Interpreters were killed alongside soldiers in roadside bombs and ambushes, and they were also killed on their own, off duty, precisely because they were known to work for foreign forces. The threat did not end when the shift ended. The fourth assumption is that the institution employing the interpreter is itself committed to lawful and ethical conduct in the encounter. A court is bound by rules of procedure; a hospital by medical ethics. The interpreter can assume that what they are asked to render is, broadly, legitimate. In war, that assumption can fail catastrophically. The interpreter may be asked to carry threats during an interrogation, to relay false promises, to render words spoken during the abuse of a prisoner. The conduit model tells the interpreter to render faithfully whatever is said. It has nothing to say about whether they should be in the room at all. As Table 1 sets out, each of the core peacetime norms has a corresponding reality in the war zone that either undermines it or turns it into something else. Table 1. Peacetime interpreting norms and war-zone conditions. Norm Peacetime assumption War-zone reality Ethical consequence Impartiality Interpreter has no stake Interpreter belongs to an affected community Perceived alignment regardless of conduct Invisibility Role is understood by all Role is read as allegiance Interpreter becomes a target Accuracy Content is lawful Content may include threats or deception Fidelity can mean complicity Confidentiality Protects the client Information has military value Interpreter pressured by several sides Professional distance Work ends at the door Threat follows interpreter home Duty of care extends beyond the job The interpreter as a party If the interpreter is not a conduit, what are they? The most useful answer is that they are a party: a person with interests, relationships, a moral conscience and a position in the conflict, whose presence changes what happens in the encounter. This is not a claim that interpreters are partisan in the sense of taking sides in the fighting, though some do. It is a claim about how they are situated. A party is someone whose standing in the encounter is recognised by others and who can be held responsible, rewarded or punished for what occurs. In the war zone, interpreters are held responsible constantly. They are blamed by villagers for the patrol's demands, suspected by soldiers of passing information to insurgents, threatened by insurgents for helping the foreigners, and sometimes accused by their own employers of mistranslating when an encounter goes badly. They carry the consequences of other people's words. Only a party can do that. Recognising the interpreter as a party has three immediate implications. The first is that the interpreter's own judgement becomes ethically relevant. A conduit has no judgement to exercise; a party does. When an interpreter decides to soften an officer's insult so that a village meeting does not collapse, or to warn a patrol that a man's gesture means something different from what they think, or to decline to repeat a threat, they are exercising judgement. Those decisions can be right or wrong, and they should be discussed as decisions, not concealed as lapses from a supposed neutrality. The second implication is that the interpreter's interests become ethically relevant. Their safety, their family's safety, their future in the country, their standing in their own community: these are not background conditions but part of the moral situation. An employer that plans an operation without asking what it will cost the interpreter has left out a party to the operation. The third implication, and the one that drives much of this book, is that the obligations run both ways. If the interpreter were a conduit, the employer's only duty would be to maintain it, like any piece of equipment. Because the interpreter is a party, the employer owes them what one owes to any person one has recruited into a dangerous undertaking: honesty about the risks, protection proportionate to the danger, fair treatment, and a share of responsibility for what happens afterwards. Why institutions prefer the conduit If the conduit model fits war so poorly, why has it persisted in military and humanitarian practice? Part of the answer is simply that it is the model interpreters themselves are trained in, and that the profession's codes offer no worked-out alternative. But a larger part is that the conduit model suits the institutions that employ interpreters. A conduit is cheap. It requires no special protection, because a conduit is not a target. It requires no consultation, because a conduit has no views. It requires no long-term commitment, because when the operation ends the conduit is simply returned to store. In this sense the conduit model is not merely an ethical ideal. It is an accounting convention. It allows an institution to rely heavily on a person without recording that reliance as a liability. The same convention appears in the way war-zone interpreters have been contracted. In both Iraq and Afghanistan, many local interpreters for Western forces were employed not directly by the military but through private contractors, sometimes several layers removed. The contracting chain served real administrative purposes, but it also distanced the military from the people who stood beside its soldiers every day. When those people later sought resettlement, they frequently discovered that proving their service required letters from officers who had since rotated home, records held by contractors who had gone out of business, or badges that the insurgents would have killed them for carrying. The paperwork of abandonment was prepared long before the abandonment itself. The conduit model also protects institutions from moral responsibility for what happens in the room. When an interrogation becomes abusive, the conduit model locates the interpreter outside the event: they merely relayed words. The same logic, extended upward, allows the institution to treat abuse as the act of a few individuals rather than a product of the environment it created. It is no accident, as a later chapter shows, that interpreters at Abu Ghraib were both participants in abuse and among the witnesses whose statements helped expose it. They were in the room, and they were parties to it, whatever the organisational chart said. A meeting in a village A composite example, built from situations that interpreters in Afghanistan described again and again, shows how quickly the conduit model runs out. A platoon commander arrives at a village to meet the elders about a culvert that insurgents have been using to plant bombs. He wants the villagers to report anyone they see near it. Through the interpreter, he explains that the patrol is there to help, that reporting will keep the village safe, and that if another bomb is found in the culvert the patrol will have to assume the village is cooperating with the insurgents. The interpreter faces several decisions in the space of a minute. The last sentence, rendered literally, is a threat of collective suspicion, and in the local idiom it may sound like a threat of collective punishment. The elders will hear it in the interpreter's voice. The interpreter knows that two of the elders have sons who fight with the insurgents and that one of them is related to his own mother's family. He knows that whatever the elders say in reply will be discussed in the village that evening, along with his name. And he knows that the commander has no idea how the sentence will land. The conduit model says: render it exactly. A good professional might add a request to the commander, before rendering, to confirm that he means what he has said, or might afterwards explain to the commander how it was likely received. Either of those steps goes beyond the conduit role, and either is plainly better practice than silent literal rendering. What the interpreter should not do is quietly rephrase the sentence into something gentler and let both sides believe that the other said it. The difference between these responses is the difference between an agent who is open about exercising judgement and one who exercises it covertly. The conduit model forbids both, and so in practice drives judgement underground. An objection A serious objection to abandoning the conduit model runs as follows. The whole value of an interpreter lies in their fidelity. Once interpreters are told that they are moral agents who may exercise judgement, some will use that licence to manipulate: to settle scores, to advance their own faction, to shade their rendering of a detainee's statement or an elder's complaint. The conduit model, whatever its descriptive failings, sets a clear standard against which such manipulation can be measured and condemned. Remove it, and nothing prevents an interpreter from substituting their own views for the words of the parties. The objection deserves a direct answer, because the danger it names is real. Interpreters in Iraq and Afghanistan were sometimes accused, occasionally with justice, of using their positions to direct raids against rivals or to extract money from people who needed the foreigners' help. The answer is that the professional-agent model does not relax the standard of accuracy. It keeps accuracy as the core duty and adds to it an explicit account of when and how the interpreter may step outside the rendering role: openly, by speaking in their own voice and saying so, rather than covertly, by changing what others said. Covert alteration remains a breach under the agent model, and a more clearly identifiable one, because the model gives the interpreter a legitimate alternative. The conduit model, by offering no legitimate way to act on conscience, arguably encourages covert alteration, since it is the only form of judgement available. What replaces the conduit It would be a mistake to discard everything the conduit model protects. Accuracy remains essential. An interpreter who routinely rewrites what others say, for whatever good reason, destroys the trust that makes interpreting possible. Confidentiality remains essential. Impartiality, understood as fair treatment of all parties in the encounter, remains a genuine professional virtue. The problem is not with these norms but with the picture of the interpreter that has been used to justify them. A better picture treats the interpreter as a professional agent operating under moral constraints, like a doctor or a lawyer. A doctor is committed to the patient's health but is not a neutral instrument of whoever pays the bill; there are things a doctor will not do, whatever the instruction. A lawyer is committed to the client but also bound by duties to the court. In the same way, an interpreter can be committed to accuracy and to the success of the communication while also recognising limits: they will not carry threats of torture, will not relay deliberate deceptions in certain contexts, will not render false promises of safety to people who are about to be harmed. These limits do not compromise professional integrity. They constitute it. This model also clarifies what the employer owes. A professional agent under moral constraints needs to know, before the assignment, what they will be asked to do. They need a recognised right to refuse, without losing their livelihood. They need protection when the assignment exposes them, and support when it harms them. They need their employer to acknowledge afterwards that their service was real and that its consequences are shared. None of this is extravagant. It is what any serious profession asks for its members, and what any serious institution provides to those it asks to take risks on its behalf. The rest of the book tests this picture against the evidence: against history, against the actual diversity of war-zone interpreters, against the pressures of divided loyalty and the interrogation room, against humanitarian practice, and against the record of what happened to interpreters when the wars they served in came to an end. The conduit model tends to fail each test in the same way. It assumes away precisely the features of the situation that make it morally hard. Chapter 2. The Long Line of Go-Betweens The interpreters of Iraq and Afghanistan often described their situation as unprecedented. In one sense they were right: no earlier generation had faced mobile phones that could carry a photograph of them across a province in minutes, or biometric databases that could fall into the hands of their enemies. In another sense they stood at the end of a very long line. For as long as armies and empires have crossed language boundaries, they have depended on people from the other side who could speak for them, and those people have faced recognisably the same dilemmas: suspicion from their employers, hatred from their neighbours, exposure when power shifted, and a reputation that outlived them. History does not settle the ethical questions of the present. What it does is show which features of the interpreter's situation are structural rather than accidental. If the same pattern appears in sixteenth-century Mexico, in the Ottoman capital, in colonial North Africa and in twentieth-century tribunals, then it is not the product of one army's carelessness or one government's bureaucracy. It is built into the role. Before the modern state Malintzin and the making of a traitor The most famous interpreter of the early modern world was a Nahua woman known in Spanish sources as Doña Marina, in Nahuatl as Malintzin, and in later Mexican memory as La Malinche. In 1519, after a battle near the Grijalva River in the Maya region of Tabasco, local lords presented Hernán Cortés with a group of enslaved women. Malintzin was among them. She spoke Nahuatl, the language of the Mexica empire, from her childhood, and Yucatec Maya from her years in bondage. Cortés already had with him Jerónimo de Aguilar, a Spaniard who had been shipwrecked years earlier and had learned Maya in captivity. For a time the Spaniards spoke to the Mexica through a chain: Cortés to Aguilar in Spanish, Aguilar to Malintzin in Maya, Malintzin to the Mexica in Nahuatl. Within months she had learned enough Spanish to cut Aguilar out of the chain. Her position shows several features that recur throughout this book. She had not chosen her employer; she had been handed over. Her value lay not only in language but in knowledge of how the people on the other side thought, negotiated and signalled intent, and the surviving accounts suggest she used that knowledge actively, not as a passive relay. She was indispensable, and her indispensability made her conspicuous: Indigenous artists who depicted the conquest often placed her at the centre of the scene, between the Spaniards and their interlocutors, larger than the men around her. And after the conquest her reputation was rewritten. In post-independence Mexico the word malinchista came to mean someone who prefers the foreign to the native, a betrayer of their own people. The historian Camilla Townsend, in Malintzin's Choices (2006), argues that this reputation is anachronistic. Malintzin did not belong to the Mexica; she came from a people who had been subordinated to them and who had sold her into slavery. The idea that she owed loyalty to a unified "Mexican" nation that did not yet exist is a projection of later nationalism. Yet the projection matters because it is so typical. Communities in conflict tend to read the interpreter's position through the lens of the eventual outcome. An interpreter who served the losing side is remembered as a hero or forgotten; one who served the winners, if the winners were foreigners, is remembered as a traitor. The judgement is made after the fact, by people who did not face the choice. The dragomans: interpreters as a caste A very different model of the interpreter developed in the Ottoman Empire and the diplomatic world around it. From the sixteenth to the nineteenth centuries, relations between the Ottoman court and the European powers were conducted largely through dragomans, a word derived ultimately from the Arabic tarjuman, translator. Dragomans were not freelance intermediaries. They formed a professional caste, often hereditary, concentrated in a small number of families in Istanbul and in the Levantine port cities. The Ottoman state had its own dragomans, the most senior of whom, the Grand Dragoman of the Porte, became a powerful office in the seventeenth century and was for long periods held by Greek Orthodox families of the Phanar district of Istanbul. The European embassies had their dragomans too, often drawn from the same local Christian and Levantine families. Venice trained young men for the role in a programme known as the giovani di lingua, and France under Colbert established a school for jeunes de langues in the later seventeenth century, precisely because the powers wanted interpreters whose loyalty they could trust rather than locals whose loyalty they could not. E. Natalie Rothman's study The Dragoman Renaissance (2021) shows how much these interpreters shaped European knowledge of the Ottoman world, and how thoroughly their position straddled the boundaries it was supposed to mediate. A dragoman working for the Venetian embassy might be an Ottoman subject, a Catholic, related by marriage to dragomans in the service of France and to officials at the Porte. The embassy relied on these connections and feared them at the same time. Accusations of double-dealing were routine. Dragomans could be arrested by the Ottoman authorities for the actions of the embassies they served, and could be disowned by those embassies when convenient. The danger of the role became starkly visible in 1821, when the Greek War of Independence broke out. The Ottoman authorities, suspecting the Phanariot Greek elite of complicity with the revolt, executed a number of prominent Greeks in Istanbul, among them the serving Grand Dragoman, Konstantinos Mourouzis. After 1821 the office passed out of Greek hands. The episode is an extreme case of a pattern that the modern war-zone interpreter knows well: a person whose position depended on being trusted across a boundary became, when the boundary hardened into open conflict, the first to be suspected by the power they served. The dragomans also illustrate the attempt to solve the problem of loyalty by institution-building. The European schools for young linguists were early versions of the military language schools of the twentieth century: an effort to replace untrustworthy locals with trained nationals. That effort never fully succeeded, because a trained foreigner rarely acquires the local knowledge, social networks and cultural fluency that made the local intermediary valuable in the first place. Every modern army faces the same trade-off. Its own linguists are trusted but often limited; local interpreters are fluent but suspected. Colonial interpreters and the politics of dependence The colonial empires of the nineteenth and twentieth centuries relied on interpreters on a vast scale. In French Algeria, the army formed a corps of military interpreters soon after the invasion of 1830, recruiting from Arabic speakers of many backgrounds, including Levantine Christians, North African Jews and Europeans who had learned Arabic. In British India, the East India Company and later the Raj depended on munshis, language teachers and secretaries, and on a large class of intermediaries who translated between the administration and the population. In colonial Africa, the interpreter attached to a district officer often held great practical power, since he controlled what the officer heard and what the population was told. Colonial administrators were acutely aware of this power and of their dependence. Complaints about corrupt or manipulative interpreters are a constant theme of colonial writing, and they reflect real abuses as well as the prejudice of officials who resented being dependent on their subjects. For the populations under colonial rule, the interpreter was frequently the most visible face of the regime: the man who announced the tax, relayed the sentence, called out names for forced labour. When colonial rule ended, many such intermediaries found themselves exposed. The most painful example in the twentieth century is the fate of the harkis, the Algerian auxiliaries who served with the French army during the Algerian War of 1954 to 1962. Most were not interpreters in any formal sense; they were soldiers, guards and auxiliaries. But their situation was structurally the same as that of the local interpreter, and on a much larger scale. When France agreed to Algerian independence in 1962, the French government restricted the evacuation of harkis to France, and many who remained were killed in reprisals in the months that followed. Estimates of the number killed differ by an order of magnitude between sources and remain contested. Those who did reach France were often held for years in isolated camps. French presidents acknowledged the country's responsibility only slowly, and in 2022 France passed a law recognising the nation's debt to the harkis and establishing a scheme of reparation. It had taken sixty years. The twentieth century Interpreters of occupation The Second World War multiplied the number of people doing language work for foreign armies on a scale never seen before, and it did so on every side. The German forces that occupied much of Europe and the western Soviet Union relied heavily on local interpreters, recruited from ethnic German minorities, from émigrés, and from local people who had learned German at school or in trade. They interpreted at interrogations, at requisitions, at the announcement of reprisals, and at the selection of civilians for forced labour. When the occupation collapsed, many of them were treated as collaborators. In the Soviet Union, service as an interpreter for the occupying forces was among the kinds of conduct that could lead to long sentences in the labour camps, and the question of what a given interpreter had actually done, whether they had softened orders, warned neighbours or eagerly served, was often of little interest to the tribunals that judged them. The Allied occupation of Germany and Austria after 1945 reversed the direction of dependence. British and American military government, as Hilary Footitt and Michael Kelly and their colleagues have shown in their research on languages at war, could not function without German speakers, and in the early months many of those recruited were Germans themselves, some with compromised pasts. The occupiers' dilemma was the same one the German army had faced a few years earlier: the people most able to speak for them were people they had reason to distrust. Military government officers complained that interpreters controlled what they heard, favoured their friends and filtered petitions. Germans complained that interpreters used their access to the occupiers to settle scores and secure privileges. Both complaints were sometimes true. What the wartime and post-war experience adds to the longer history is scale and ambiguity. Millions of people passed through occupations as interpreters, clerks and intermediaries, and their conduct ranged from heroism to atrocity. After each occupation, the societies that had lived through it had to decide how to judge them, and generally did so without much attention to what the role had actually required. The interpreter was judged by the side they had spoken for, not by the way they had spoken. Tribunals and the problem of trust The Second World War produced both an enormous expansion of military interpreting and a new kind of interpreting setting: the international criminal tribunal. At Nuremberg in 1945 and 1946, simultaneous interpretation was used on a large scale for the first time, with interpreters working through headsets in four languages. Francesca Gaiba's history, The Origins of Simultaneous Interpretation (1998), describes how the system was devised under the direction of Léon Dostert, a French-born American army officer, and how the interpreters, many of them recruited hastily, worked under intense strain. Some had personal connections to the events being tried. Several interpreters had fled Nazi persecution; they now rendered, word for word and in the first person, the testimony of the men responsible. Nuremberg is often told as a triumph of professional neutrality, and in one sense it was: the interpreters' work was accepted by all sides as accurate enough to support a legitimate trial. But it also showed the psychological cost of neutrality for people who were anything but outsiders. The interpreter speaking in the voice of a defendant must say "I" for someone else, including when that someone else is describing, excusing or denying atrocities. That burden has since been recognised in the study of trauma among interpreters at later tribunals, including those for the former Yugoslavia and Rwanda. The Tokyo war crimes trial, which ran from 1946 to 1948, shows the problem of trust in a different form. Kayoko Takeda's study, Interpreting the Tokyo War Crimes Tribunal (2010), describes a three-tier structure. The actual interpreting was done largely by Japanese nationals, because there were too few non-Japanese with the necessary fluency. Their work was checked by monitors who were Japanese Americans, many of whom had served in United States military intelligence. Disputes were referred to a language arbitration board headed by a United States military officer. The structure expressed, in organisational form, the distrust that every occupying power feels toward local interpreters: they were needed because of their fluency and watched because of their origins. The Japanese American monitors, for their part, occupied an ambiguous position of their own, having been drawn from a community many of whose members had been interned by the United States during the war. Vietnam and the rehearsal of abandonment The war in Vietnam brought the pattern into the era of mass media. The United States and its allies relied heavily on Vietnamese interpreters, both military and civilian, and on a larger population of Vietnamese employees of American agencies and firms. As American forces withdrew and the South Vietnamese state collapsed in April 1975, the question of what would happen to these people became urgent. The final evacuation from Saigon, conducted by helicopter from the embassy compound and other sites, rescued many but left very large numbers behind, including people who had worked closely with Americans for years. Many of those left behind were later sent to re-education camps. The United States did eventually admit a large number of Vietnamese refugees in the years that followed, and that resettlement is sometimes cited as a model. But the record of the final weeks of the war, when priority lists were improvised and embassy staff made individual decisions about whom to take, established a pattern that would reappear almost exactly in Kabul in 2021: prolonged reluctance to plan an evacuation because planning would signal defeat, followed by a chaotic scramble in which access depended on luck, personal connections and physical proximity to the gate. What history shows Several lessons emerge from this long record. The first is that the interpreter's dilemma is structural. Wherever a power operates across a language boundary, it must depend on people from the other side, and those people will be suspected by both. No amount of individual good conduct escapes this, because the suspicion attaches to the position, not the person. The second lesson is that the interpreter's fate is decided by the outcome of the conflict, which the interpreter does not control. Malintzin's reputation, the dragomans' safety in 1821, the harkis' survival in 1962 and the Vietnamese employees' futures in 1975 all turned on political decisions made by others. The interpreter's moral choices mattered, but their consequences were determined by events in which they had no voice. The third lesson is that institutions have repeatedly tried to solve the problem of trust by replacing local interpreters with trained nationals, and have repeatedly failed, because the local interpreter's value lies precisely in what cannot be taught. Armies will go on relying on local interpreters. The question is whether they will go on treating them as disposable. The fourth lesson is that acknowledgement comes late. Recognition of the harkis took sixty years. The long delays in resettling Iraqi and Afghan interpreters, discussed in a later chapter, are not an aberration but a continuation. Institutions that rely on local intermediaries have consistently discovered their obligations only after it was too late to meet them for many of the people concerned. The purpose of studying this history is to discover those obligations earlier. Chapter 3. Who Stands in the Middle Public discussion of war-zone interpreters tends to fix on a single image: the young local man in borrowed body armour, face covered by a scarf or sunglasses, walking beside a foreign patrol. That image is accurate for a large number of people, and it is the image that dominated coverage of Iraq and Afghanistan. But the population of people doing language work in and around war is far more varied, and the ethical position of each group differs. Who hired them, under what law, with what training, with what protection and with what future determines what they can be asked to do and what is owed to them. This chapter maps that diversity. It does so not for the sake of completeness but because many of the failures described later arise from confusion between categories: from treating a local civilian as though they were a soldier, or a contractor as though they were an employee, or a humanitarian interpreter as though they were protected by the neutrality of their agency. Soldiers and citizens Military linguists in uniform At one end of the range stand linguists who are themselves members of the armed forces. Most large militaries maintain language training establishments. The United States Defense Language Institute in Monterey, California, is the best known, training service members in dozens of languages through courses that can last more than a year for the hardest languages. Britain, France, Germany and other powers have their own equivalents. Graduates serve as intelligence analysts, signals intercept operators, interrogators and interpreters. Uniformed linguists have a clear legal status. They are combatants under the law of armed conflict, subject to military discipline and military law, and entitled to the protections that come with that status, including prisoner-of-war status if captured. They are covered by military medical care, pensions and compensation schemes. They leave the war zone when their unit does. Their families live far from the fighting. Whatever their other burdens, they are not exposed to reprisal in the way local interpreters are. Their ethical position is shaped by the chain of command. A uniformed linguist who is ordered to take part in an interrogation is bound to obey lawful orders and to refuse unlawful ones, like any other service member. The difficulty, as a later chapter shows, is that the line between lawful and unlawful interrogation was deliberately blurred in the early years of the conflicts after 2001, and a junior linguist was poorly placed to judge where it lay. Trained military linguists also have limits. A year of intensive language training produces competence, not native fluency, and certainly not the cultural knowledge that comes from growing up in a place. Military linguists often struggle with dialect, idiom and the thousand unspoken signals of social interaction. Hence the perennial reliance on locals. Heritage speakers and naturalised citizens A second group occupies a middle position: people born in the region of conflict, or raised by families from it, who hold the citizenship of the intervening power. After 2001 the United States recruited heavily among Arabic, Dari and Pashto speakers in its immigrant communities, both into the armed forces and through contractors. In the mid-2000s the US Army created a dedicated enlisted specialty for interpreters and translators drawn from native and heritage speakers. Other Western militaries made similar, smaller efforts. Heritage speakers bring native or near-native fluency and much cultural knowledge, combined with the citizenship and security clearance that local nationals lack. They are often the most valuable linguists a force has. But their position carries its own strains. They may have relatives in the country where they are serving, and those relatives can be threatened. They may be regarded by local people as traitors of a particularly bitter kind: not foreigners doing a foreign army's work, but sons and daughters of the community who returned in foreign uniform. And they may be regarded with suspicion by their own side, precisely because of their origins. The case of Ahmad al-Halabi, a US Air Force translator of Syrian origin who worked at the detention facility at Guantánamo Bay and was arrested in 2003 on charges that initially included espionage, illustrates how quickly that suspicion can crystallise. Most of the charges against him were later dropped, and he pleaded guilty to relatively minor offences; but the accusation had already been widely publicised. Civilians in military service Contracted linguists The largest group of interpreters used by Western forces in Iraq and Afghanistan were not soldiers at all. They were civilians employed by private companies under government contracts. The United States military classified contract linguists in three categories. The first covered local nationals without a security clearance, the great majority of interpreters in the field. The second and third covered citizens of the United States holding, respectively, a secret or a top secret clearance, who could be used for sensitive work such as intelligence and interrogation. The contracting model had clear advantages for the military. It allowed rapid expansion without changing force levels, shifted recruitment, payroll and administration onto private firms, and kept linguists outside the military personnel system. For the linguists themselves, it had costs that became clear only later. Their relationship with the soldiers they served beside was mediated by an employer they rarely saw. Their contracts could be ended abruptly, sometimes for reasons that were never explained to them. Their records were held by companies that merged, changed names or went out of business: the Titan Corporation, a major supplier of linguists in Iraq, was acquired by L-3 Communications in 2005, and later contracts passed to other firms. When interpreters later needed to prove years of service, those corporate histories became obstacles. The contracting model also complicated accountability. A contract linguist who abused a prisoner was not subject to military discipline in the ordinary way. A contract linguist who was killed or wounded was covered, in the American case, by a workers' compensation regime designed for overseas contractors, which many local interpreters had never heard of and found difficult to access. The linguist was working for the military in every practical sense and for someone else in every legal sense. This gap is not a technicality. It is the mechanism by which reliance was converted into deniability. Locally employed civilians Some forces, notably the British, employed local interpreters directly as locally employed civilians rather than through contractors. This made the relationship clearer and the records better, but it did not resolve the underlying problem. Locally employed civilians were paid local wages, often generous by local standards but modest compared with those of foreign contractors doing similar work. They were employed under local terms, without the rights and protections of home-country staff. And when the operation ended, their employment ended too. The British experience in Afghanistan shows how the definition of the category can decide a person's fate. When the United Kingdom first created a scheme to support Afghan staff after combat operations ended, eligibility depended on being in post on a particular date and having served for a minimum continuous period. People who had resigned earlier because of threats, or who had been dismissed, or whose service fell just short of the threshold, fell outside the scheme. The rules were revised several times over the following decade, each revision admitting some who had previously been excluded. The category was drawn to limit liability and then redrawn, under pressure, to meet obligation. Peacekeeping interpreters Multinational peacekeeping operations add a further layer. When United Nations and later NATO forces deployed to Bosnia and Herzegovina in the 1990s, they recruited large numbers of local interpreters, many of them young, university-educated and fluent in English from school, films and music. Catherine Baker's research on these language intermediaries shows how varied their position was. For some, interpreting was an escape from wartime hardship and a route into international careers. Their salaries, paid in hard currency, could exceed those of doctors and professors in the local economy. For others, the work brought accusations of disloyalty from their own communities, especially where they interpreted for forces perceived as favouring one side. The peacekeeping setting also exposed a problem specific to multinational forces. An interpreter might work successively for battalions from several different countries, each with its own rules, attitudes and obligations. When something went wrong, it was unclear which state, if any, was responsible for them. The fall of Srebrenica in 1995, discussed in a later chapter, turned this ambiguity into a matter of life and death for at least one interpreter's family. Women in the middle Women interpreters occupy a particular place in this landscape. In societies where contact between unrelated men and women is restricted, foreign forces and agencies found that they could not speak to half the population without women to interpret for them. In Afghanistan, both military forces and humanitarian agencies recruited Afghan women for tasks such as searching women at checkpoints, interpreting for female engagement teams sent to talk to village women, and interpreting in health consultations. These women faced every risk borne by male interpreters and some of their own. Working with foreign men, and travelling without male relatives, violated norms that armed groups were quick to enforce and that even supportive families found difficult to defend to neighbours. Many worked under stricter concealment than their male colleagues, and some kept their work secret even from relatives. When the Taliban returned to power in 2021, women who had worked with foreigners faced a double exposure, as collaborators and as women whose working lives now contravened the new authorities' decrees. Beyond the military Humanitarian interpreters and national staff Humanitarian organisations working in conflict zones also rely overwhelmingly on local language workers. The International Committee of the Red Cross, the United Nations refugee agency, Médecins Sans Frontières and hundreds of smaller organisations employ national staff who interpret for expatriate colleagues in medical consultations, refugee registration, protection interviews, food distributions and negotiations with armed groups. Often interpreting is only part of a wider role: the same person may be a driver, a logistician, a community liaison officer and an interpreter in a single day. The humanitarian interpreter's position differs from the military interpreter's in one important way: their employer's legitimacy rests on the claim of neutrality, impartiality and independence from the parties to the conflict. That claim can offer a measure of protection. A known ICRC employee may pass through checkpoints that a military interpreter could not. But humanitarian neutrality protects the organisation's image more reliably than it protects the individual. Armed groups often draw distinctions between international staff, whose killing may bring political costs, and national staff, who can be threatened with less consequence. Data compiled by the Aid Worker Security Database, maintained by the research group Humanitarian Outcomes, have consistently shown that national staff make up the large majority of aid workers killed, wounded or kidnapped in any given year. The risks of humanitarian work are concentrated on exactly the local people who carry its language. Journalists' fixers A final category deserves mention because it shows the pattern in its purest form. Foreign correspondents in conflict zones rely on local fixers who interpret, arrange interviews, navigate checkpoints, assess danger and often determine what story gets told. Fixers are frequently freelance, paid by the day, without insurance, and without any institutional relationship that survives the correspondent's departure. When a story causes offence to an armed group or a government, the correspondent flies home and the fixer stays. Several fixers have been killed in circumstances directly connected to their work with foreign media. Their names rarely appear in the bylines of the stories they made possible. Comparing the categories As Table 2 sets out, the categories differ most sharply in three respects: the legal framework that governs the linguist's relationship with the force or agency, the protection they receive while serving, and their exposure once service ends. The last of these is the most important and the least discussed. Table 2. Categories of language worker in conflict settings. Category Typical employer Legal status Protection in service Exposure after service Uniformed military linguist Armed forces Combatant Full military cover Low; leaves with unit Heritage-speaker linguist Armed forces or contractor Citizen; combatant or civilian Military or contractor cover Moderate; family may be threatened Contracted local national Private contractor Civilian Limited; depends on contract High; remains in country Locally employed civilian Force directly Civilian Limited; local terms High; remains in country Humanitarian national staff Agency or NGO Civilian Agency security rules High; remains in country Journalists' fixer Freelance Civilian Usually none High; remains in country The pattern is plain. Protection during and after service tracks nationality and employment status, not risk. The people with the most exposure, those who remain in the country after their employers leave, have the least protection. The people with the least exposure, uniformed nationals of the intervening power, have the most. This inversion is not the result of any single bad decision. It follows from the way institutions allocate protection: according to their legal relationships, rather than according to the dangers they have created. Why the category matters ethically The categories also shape what an interpreter can legitimately be asked to do. A uniformed linguist has accepted, as part of military service, a set of duties that includes exposure to combat and obedience to lawful orders. A local civilian hired through a contractor has accepted no such duties. When a patrol commander treats a contracted local interpreter as a member of the unit, sending them forward to talk down a crowd or into a building to negotiate, the commander is imposing military risks on someone who never took the military oath and receives none of its protections. This happened constantly. It is hard to see how it could have been otherwise, given the operational pressures. But the ethical consequence is clear. If an institution uses a civilian as though they were a combatant, it owes them what it would owe a combatant: protection, care when wounded, recognition, and a place of safety when the fighting is over. It cannot extract the service of a soldier and pay the obligations of a casual labourer. The same reasoning applies, with modifications, to humanitarian agencies. An organisation that sends national staff into dangerous negotiations because they speak the language, while keeping its international staff in safer roles, is transferring risk along lines of nationality. That may sometimes be unavoidable. It cannot be ethically neutral. The agency acquires obligations proportional to the risks it has transferred. The remaining chapters return repeatedly to this principle: obligation follows exposure. The question is never simply what an interpreter's contract says. It is what risks the employer placed them in, and what it would take to answer for those risks honestly. Hashtags: #TheEthicsOfTranslationInWarZones #WarZoneInterpreters #ConflictInterpreting #TranslationEthics #InterpretingEthics #MilitaryInterpreters #HumanitarianInterpreting #InterpretersInConflict #LanguageMediation #ConflictMediation #TranslationStudies #InterpretingStudies #EthicsOfInterpreting #InterpreterNeutrality #ProfessionalImpartiality #InterpreterSafety #ProtectionOfInterpreters #CivilianProtection #HumanitarianEthics #MilitaryEthics #InternationalHumanitarianLaw #HumanRights #WarAndConflict #CulturalMediation #LinguisticRights #DividedLoyalties #InterpreterResponsibility #DutyOfCare #AfghanInterpreters #PostConflictResettlement

Download the Book (PDF): Introduction: A Workbook With a Theory Inside It Sprint, published in 2016 by Jake Knapp with John Zeratsky and Braden Kowitz, is written as a manual. It tells you what to do at ten past nine on Monday morning, what supplies to buy, how many people to invite, and when to break for lunch. The prose is brisk, the instructions are specific, and the whole thing is designed to be followed rather than analysed. This is a deliberate choice and a successful one. It is also why the book is systematically underrated by people who might otherwise learn a great deal from it. A manual invites the response that manuals invite: try it, and if it works keep it, and if it does not, adapt it. What it does not invite is the question of why any of it should work at all. That question has a good answer, and the answer is more interesting than the procedure. Almost every element of the five-day structure corresponds to a documented failure mode of group problem-solving, and the specific counter-measure Knapp prescribes is, in most cases, one that experimental psychology arrived at independently and for the same reasons. The prohibition on group brainstorming, the silent voting, the single named decision-maker, the compressed timebox, the disposable prototype, the five-person test — each is a response to a known defect in how groups generate ideas, evaluate them, decide between them and learn whether they were right. Read this way, Sprint stops being a workshop format and becomes something more useful: a worked application of decision science to product development, in which the theory has been compiled into a procedure so that people can execute it without understanding it. The purpose of this guide is to decompile it. Why this matters practically The reason to care is not academic. A framework that is followed without being understood cannot be adapted, and adaptation is unavoidable. Nobody runs the sprint exactly as written. Teams have four days, not five. They are distributed across time zones. Their decider is unavailable on Wednesday. Their product cannot be prototyped in a day. Their customers cannot be recruited in a week. Faced with these constraints, a team that has only the procedure will improvise, and its improvisations will be governed by convenience. It will keep the parts that are enjoyable — the sketching, the sticky notes, the sense of shared purpose — and drop the parts that are uncomfortable, which are almost always the load-bearing ones. The silent voting goes first, because discussion feels more collaborative. The single decider goes next, because consensus feels fairer. The customer test goes last, because it is the hardest to arrange. What remains is a workshop. It generates energy, alignment and a shared vocabulary, all of which are real benefits, and it produces no evidence about whether the idea is any good. This is the most common outcome of adopting the sprint, and it is entirely predictable from the fact that the parts most often discarded are the parts that carry the method's epistemic weight. A team that understands why each element exists can make the trade-offs deliberately: this constraint forces me to drop X, here is what X was protecting against, and here is what I will do instead. That is a different activity from improvising, and it produces a different result. What this guide covers The structure follows the sprint's own, because the sequence is not arbitrary and the argument is easier to follow in order. But each day is treated as a set of design decisions with reasons rather than as a schedule. Three chapters precede the daily material. The first establishes what the sprint is actually replacing — the default process it is an alternative to — because the method's value can only be assessed against that baseline. The second sets out the psychology of group decision-making that the whole format is constructed around. The third examines the timebox itself: why compression improves rather than degrades output, when it does, and what the mechanism is. Two chapters follow. One deals with the method's limits — what a sprint can and cannot establish, and the specific errors that follow from over-reading its results. The other deals with adaptation: which elements are load-bearing, which are ritual, and how to modify the format without destroying it. A note on evidence A guide that treats Sprint as applied psychology should be careful about the strength of the underlying evidence, and it will be. Some of the psychology invoked here is very well established. The finding that interacting groups produce fewer and worse ideas than the same number of people working separately has been replicated for over half a century and the mechanisms are understood. Others are less secure. Several results from social and cognitive psychology that circulate widely in business writing have fared poorly under replication, and where this guide relies on them it says so. The sprint's own effectiveness, meanwhile, has never been subject to controlled evaluation. There is no study comparing outcomes for teams that ran sprints against comparable teams that did not. What exists is a large body of practitioner testimony, which is genuinely informative about feasibility and entirely uninformative about effect. This is worth stating early, because the confident tone of the original book can leave the impression that the method has been validated. It has not. Its components have decent theoretical support; the package has none. That is not a reason to dismiss it. It is a reason to understand the components, so that one can judge for oneself which parts are doing work. The team, and why seven One structural feature deserves mention at the outset because it recurs throughout and is easy to treat as arbitrary. The sprint specifies a team of seven or fewer, drawn from different functions: someone who decides, someone who knows the finances, someone who knows the customer, someone who knows the technology, someone who knows how it will be marketed, and someone who designs. The number is stated as a limit rather than a target. The limit has a reason that connects to the material in chapter two. The productivity losses in interacting groups scale with size: production blocking worsens because more people are waiting to speak, social loafing worsens because individual contributions become less identifiable, and the coordination cost of reaching any decision rises. The literature is consistent that these effects grow faster than the benefit of additional perspectives beyond quite a small group. Seven is a practical judgement about where the curve turns, and it is in the range that most research on small-group performance would support. The cross-functional composition serves a different purpose. It is not primarily about the quality of ideas — the evidence that diverse teams generate better ideas is real but modest — but about the completeness of the constraints in the room. A sprint conducted entirely by designers will produce a solution that is infeasible, unaffordable, or unsellable, and will discover this afterwards. Having the engineer, the finance person and the salesperson present means those constraints are applied during the week rather than after it. The tension between these two requirements — small enough to function, broad enough to contain the constraints — is real and the format resolves it by allowing additional experts to appear briefly on Monday without joining the sprint. That is a sensible compromise and it is also the point at which the format is thinnest, as the chapter on Monday discusses. Chapter One: What the Sprint Replaces A method can only be evaluated against an alternative, and the alternative Sprint is aimed at is rarely stated explicitly. It is worth stating, because most of the design decisions in the five-day format only make sense as responses to specific properties of the default. The default process In most organisations, a significant product decision is made roughly as follows. Someone proposes an idea, usually in a meeting, usually verbally. The idea is discussed. Objections are raised and partially addressed. The discussion runs out of time, and the outcome is an action item: someone will look into it and come back. Over the following weeks, the idea is developed through a series of further meetings, each attended by a slightly different group, each beginning with a recapitulation of what was decided last time, and each producing modifications. Documents are written and circulated. Stakeholders who were not present raise concerns that the group had already considered and dismissed, and the concerns are considered again because the stakeholder is senior. Eventually a decision is reached — usually not at any identifiable moment, but by accretion, as the set of live options narrows through attrition. The version that survives is typically the one that offended the fewest people, which is not the same as the best one. Then the thing is built, over a period of months. Somewhere near the end, it is shown to customers, at a point where the cost of learning that it is wrong is very high and the organisational commitment to it is higher. This process has four properties that matter. It is slow, and the slowness is not deliberation. The elapsed time is consumed by scheduling, by context reconstruction at the start of each meeting, and by the serial nature of the discussion, not by anyone thinking harder. Its output is a consensus artefact. Because the decision emerges from repeated discussion among people with different interests, the surviving option is selected for inoffensiveness. Distinctive ideas, which by definition have detractors, are eliminated early. It generates no evidence until very late. Every intermediate decision is made on the basis of opinion, argument and authority. The first contact with reality occurs after the expensive work is done. The cost of being wrong is enormous and rises continuously. By the time evidence arrives, the organisation has spent months of engineering effort and has publicly committed to the direction. The sprint's proposition Against this, the sprint's claim is straightforward: take the same group of people, put them in one room for five days, and compress the entire sequence — problem framing, idea generation, decision, artefact, evidence — into that period. The compression is not achieved by working faster. It is achieved by removing the things that consume the elapsed time in the default process. There is no scheduling delay because everyone is already present. There is no context reconstruction because the work is continuous. The serial discussion is replaced by parallel individual work. And the decision is made once, by a named person, rather than emerging by attrition. The critical move — the one that makes the whole thing possible — is that the sprint does not build the product. It builds a facade convincing enough to test. This decouples the cost of learning from the cost of building, which is the single structural insight the method rests on. In the default process, evidence is expensive because obtaining it requires building the thing. If evidence can be obtained from something that took a day to construct, the entire economics of the decision change. What is actually being economised It is worth being precise about the resource the sprint is designed to conserve, because it is not the one people assume. The obvious answer is engineering time, and that is part of it. But the deeper answer is organisational commitment. In the default process, commitment accumulates continuously: as more people are consulted, as more work is done, as the direction is communicated upward, as reputations attach. By the time evidence arrives, the organisation cannot easily act on it, because reversing requires people to publicly abandon a position they have defended. The sprint's structure attacks this directly. It is short enough that nobody's reputation has attached to the outcome. The prototype is explicitly disposable, which is stated repeatedly in the original text and is not a throwaway remark — it is the mechanism by which the team is permitted to conclude that the idea was bad. And the customer interviews produce evidence early enough that changing course costs almost nothing. Understood this way, the sprint is a device for producing decisions that the organisation is still free to reverse. That framing explains several features that are otherwise puzzling, including the insistence on disposability and the placement of the test at the end of a single week rather than after a period of refinement. The honest comparison Two qualifications keep this comparison fair. The first is that the default process is not purely pathological. Extended discussion across many stakeholders does surface constraints that a five-day sprint will miss: regulatory requirements, technical limitations, commitments to existing customers, interactions with other parts of the product. A sprint conducted by seven people in a room will produce a solution that seven people find good, and the organisation may contain a hundred relevant considerations. The sprint's own answer to this — the expert interviews on Monday — is a partial and rather thin remedy. The second is that the sprint is expensive in a way that is easy to overlook. Five days of seven people's undivided attention is a substantial commitment, larger than most organisations realise when they agree to it. Whether that is cheaper than the default depends entirely on what the default would have cost, and for smaller decisions it is not. The method is therefore properly understood as an instrument for a particular class of problem: important enough to justify seven people for a week, uncertain enough that the answer is not known, and tractable enough that a facade can be built and shown to a customer. Outside that class it is the wrong tool, and a great deal of disappointment with the sprint comes from applying it to problems that are not in it. The intellectual lineage The sprint did not appear from nothing, and placing it in its tradition clarifies what is original about it. Its most obvious ancestor is design thinking as developed and popularised through IDEO and the Stanford d.school from the 1990s onwards — a family of practices organised around empathy with users, rapid ideation, prototyping and testing. The sprint shares the core sequence and differs by being far more prescriptive: design thinking is a philosophy with associated techniques, the sprint is a timetable. Its second ancestor is the lean startup movement, and specifically Eric Ries's formulation of build-measure-learn cycles and minimum viable products, published in 2011. The shared premise is that assumptions should be tested cheaply before they are built expensively. The difference is what "cheap test" means. A lean minimum viable product is a real thing released to real users, generating behavioural data in the market; a sprint prototype is a facade shown to five recruited participants in a room. The lean approach produces better evidence and takes longer; the sprint produces weaker evidence in a week. Neither dominates, and the choice between them should turn on how expensive it would be to put something real in front of real users. Its third and least acknowledged ancestor is the structured group technique literature in social psychology and operations research — nominal group technique, formalised by André Delbecq and Andrew Van de Ven in 1971, and the Delphi method from RAND. These supply the actual mechanisms the sprint uses for generation and aggregation, and the sprint's authors arrived at them, as far as the book indicates, by practice rather than by reading the literature. That convergence is itself interesting. When practitioners iterating on a format arrive independently at the controls that experimental psychology identified decades earlier, it is reasonable evidence that the controls address real problems. It is also a reason to read the literature, since the researchers explored the design space more systematically and found refinements — iteration in Delphi, passing rounds in brainwriting — that the practitioner version does not include. Chapter Two: Why Groups Are Bad at This The sprint's most distinctive design decisions all follow from a single body of research: the experimental literature on how groups generate and evaluate ideas. That literature is old, unusually consistent, and almost entirely ignored in ordinary organisational practice. This chapter sets it out, because everything in the days that follow is a response to it. The brainstorming result In 1953 the advertising executive Alex Osborn published Applied Imagination, which introduced brainstorming: a group technique in which participants generate ideas together under rules forbidding criticism, encouraging quantity, and welcoming unusual contributions. Osborn claimed that a group using his method would produce roughly twice as many ideas as the same individuals working alone. The claim was tested. In 1958 Donald Taylor, Paul Berry and Clifford Block at Yale compared groups of four brainstorming together against four individuals working separately whose non-duplicate ideas were then pooled — what the literature calls a nominal group. The nominal groups produced substantially more ideas, and independent judges rated their ideas as higher in quality. This result has been replicated many times over the following decades, across varied tasks, group sizes and populations. The consistent finding is that interacting groups underperform nominal groups of the same size, and that the gap widens as the group gets larger. It is one of the more robust findings in social psychology, and it directly contradicts the practice that nearly every organisation uses when it wants ideas. The three mechanisms Subsequent work, particularly by Michael Diehl and Wolfgang Stroebe in the 1980s, isolated why. Three mechanisms operate, and knowing which is which matters, because the counter-measures differ. Production blocking is the largest effect. In a group, only one person can speak at a time. While waiting, a participant must hold their idea in memory, attend to what is being said, and manage the social task of finding an opening. All three interfere with generating further ideas. Diehl and Stroebe's experiments, which separated this factor from the others by varying whether participants had to wait to contribute, found it accounted for most of the productivity loss. The implication is stark: the problem is not psychological inhibition but the simple serial bottleneck of conversation. Evaluation apprehension is the fear of being judged. Even under an explicit rule against criticism, participants moderate what they say, because the rule governs what others may say aloud and not what they think. Unusual ideas — which are the ones worth having — are disproportionately suppressed, because they carry the most social risk. The effect is stronger when the group includes people with power over the participant's career, which is to say, in nearly every real organisational setting. Social loafing is the reduction in individual effort that occurs when contributions are pooled and individual output is not identifiable. It is a general finding about group tasks, documented since Max Ringelmann's rope-pulling experiments in the early twentieth century, and it operates in idea generation as it does elsewhere. To these three, a fourth should be added, which is arguably the most consequential in practice. Anchoring and convergence. In a group discussion, early contributions shape everything that follows. Participants who hear an idea generate variants of it rather than alternatives to it, and the range of options considered narrows rapidly around whatever was said first. This is a well-documented effect in group ideation and it means that the order of speaking has a large influence on the outcome — which is not a property anyone would design into a decision process deliberately. The conformity problem Alongside idea generation sits the separate question of evaluation, where a different literature applies. Solomon Asch's experiments in the 1950s established that a substantial proportion of people will give an obviously incorrect answer about the length of a line if several others have given it first. The effect is about public judgement rather than private belief — participants frequently knew the answer was wrong — and it demonstrates how readily expressed opinion converges under social pressure. More relevant to organisational settings is the influence of hierarchy. When a senior person expresses a view early in a discussion, subsequent contributions cluster around it. This is sometimes rational, since seniority may correlate with judgement, and it is frequently not, since it also correlates with distance from the work. Either way, the effect is that the information held by the rest of the group is not surfaced. What looks like agreement is often the absence of dissent rather than its considered withdrawal. Irving Janis's work on groupthink in the 1970s described the extreme version — cohesive groups suppressing dissent to maintain consensus, with catastrophic results in several documented policy failures. Janis's account has been criticised for methodological weakness and its case studies are contested. The narrower conformity findings are on firmer ground, and they are sufficient to justify the sprint's design. The decision problem A third strand concerns how groups convert evaluation into decision, and it identifies a failure the previous two do not. When a group must reach a decision by discussion, the outcome is systematically biased towards options that are acceptable to everyone rather than options that are best. This is not a psychological defect but an arithmetic consequence of how consensus works: an option that half the group thinks is excellent and half thinks is poor will lose to an option that everyone thinks is adequate. For decisions where the downside of error is large and the upside is capped, this is a reasonable selection rule. For decisions about what product to build, where the returns are heavily skewed and the cost of a mediocre choice is high, it is close to the worst possible rule. Distinctive options are precisely the ones with detractors. The organisational literature has a name for the alternative failure — decision by the highest-paid person's opinion — and the sprint's answer is neither. It is a third structure, examined in the chapter on Wednesday: individual judgement collected without influence, then a single named person deciding with that information in front of them. What the sprint does about all this Every countermeasure in the format can now be read off the diagnosis. Against production blocking: individuals work in parallel and silently, so nobody waits for a turn. This is the "work alone together" principle, and it is the single most important structural feature of the method. Against evaluation apprehension: sketches are produced individually and reviewed anonymously, with the author's name concealed during the critique. The idea is separated from the person. Against social loafing: each participant must produce a complete, individual, self-explanatory artefact. There is nowhere to hide. Against anchoring: nothing is said aloud before individual work is done. The lightning demos on Tuesday deliberately expose the group to external stimuli rather than to each other's proposals, and the sketching that follows is silent. Against conformity in evaluation: voting is silent and simultaneous, using dots placed on a wall, so that nobody's choice is visible before their own is made. Against consensus dilution: one person decides. The group's role is to inform that decision, not to reach it. Seen together, these are not workshop conventions. They are a systematic set of controls, each addressing a specific documented defect. That is the strongest thing that can be said for the sprint, and it is a considerably stronger claim than "this format works for us." A necessary caution Two of the results cited above have caveats worth stating, since a guide that treats this material as science should be accurate about its status. The brainstorming and nominal group findings are robust and have survived replication over decades. The mechanisms — particularly production blocking — are well isolated. This part of the case is secure. The broader literature on group decision-making is less uniformly solid. Groupthink as Janis formulated it is contested. Some widely cited effects in social psychology have failed to replicate in recent years, and business writing has been slower to update than the field has. Where a claim in this guide rests on such results, it is flagged. The sprint's core design does not depend on the shakier material. Its central controls follow from production blocking, evaluation apprehension and the arithmetic of consensus, all of which stand. Why organisations keep brainstorming anyway A puzzle worth addressing, since the evidence has been available since 1958 and the practice is universal. Part of the answer is that groups enjoy brainstorming and consistently overestimate its productivity. This has been measured directly: participants in interacting groups rate their session as more productive than participants working individually rate theirs, even when the individual condition demonstrably produced more and better ideas. The illusion has several sources. Group members hear a large number of ideas, including everyone else's, and attribute the collective output partly to themselves. The session is socially pleasant, and pleasantness is misread as effectiveness. And nobody experiences the ideas they failed to have while waiting for a turn to speak, so the cost is invisible. Part of the answer is that group sessions serve functions other than idea generation, and those functions are real. They build shared understanding. They signal inclusion, which matters politically. They produce commitment to whatever emerges, because participants feel ownership. An organisation that replaced all group ideation with individual work would generate better ideas and would find them harder to implement. The sprint's resolution is worth noticing: it keeps the group in the room, together, for the whole week, so that the social and commitment functions are served, while making the generative work individual. The participants experience a collaborative week. The idea generation is nominal-group. This is a more sophisticated design than either the traditional workshop or a purely individual process, and it is probably the reason the format has been adopted where the underlying research has not. The lesson generalises. When a practice persists despite evidence against its stated purpose, it is usually serving an unstated purpose, and the productive move is to find a design that serves both rather than to argue the practice away. A note on what the research does not say One clarification prevents a common overreach. None of this establishes that groups are worse than individuals at everything, or that collaboration is generally counterproductive. The finding is specific: interacting groups underperform nominal groups at generating ideas. Groups outperform individuals at other things, including evaluating a set of options, catching errors, integrating specialised knowledge from different domains, and reaching decisions that people will actually implement. The sprint's design reflects this division rather than a blanket preference for individual work. Generation is individual. Evaluation is collective, though structured to prevent contamination. The decision is individual again, for reasons about consensus arithmetic rather than about cognition. And the observation of customers is collective, deliberately, because the shared experience is what makes the evidence stick. Getting this division right is the substance of the method. A team that concludes from chapter two that people should work alone has misread it as thoroughly as the organisation that puts seven people at a whiteboard. Chapter Three: The Timebox The most conspicuous feature of the sprint is its duration, and the most common assumption about it is wrong. Five days is not chosen because five days is how long the work takes. It is chosen because a fixed, short, non-negotiable deadline changes how the work is done. What deadlines do The best-known statement of the effect is Parkinson's law — that work expands to fill the time available for its completion — published by C. Northcote Parkinson in The Economist in 1955 as satire about bureaucratic growth. It is a witticism rather than a finding, and it is quoted far more often than it is examined. But the underlying observation has support from more careful sources. Research on time allocation and task completion consistently finds that people do not distribute effort evenly across an available period. Effort is back-loaded, concentrating near the deadline, and the amount of work accomplished is substantially determined by how much time remains rather than by how much has elapsed. Studies of self-imposed deadlines by Dan Ariely and Klaus Wertenbroch found that people who set themselves intermediate deadlines performed better than those with only a final one, and that evenly spaced externally imposed deadlines produced the best performance of all — evidence that the constraint itself, rather than the total time, is doing the work. The related finding is the planning fallacy, documented by Daniel Kahneman and Amos Tversky: people systematically underestimate how long tasks will take, and the underestimate persists even among those who know about the bias and have experience of their own past overruns. A consequence relevant here is that longer allocations are consumed regardless, because the estimate that justified them was wrong in the first place. Why compression improves quality The stronger claim implicit in the sprint's design is not just that a deadline concentrates effort, but that a short deadline produces better output. This is counterintuitive and requires an argument. Three mechanisms support it. Satisficing over maximising. Herbert Simon's distinction between choosing the best available option and choosing the first adequate one is usually presented as a concession to bounded rationality. In creative and design work it is frequently the superior strategy, because the search for the optimum consumes resources with diminishing returns and because the criteria for optimality are not known in advance. A time constraint forces satisficing, and the work that results is typically not much worse than what unlimited time would have produced, while costing a fraction as much. Barry Schwartz's work on maximising as a disposition found it associated with worse outcomes and greater dissatisfaction than satisficing in a range of decisions. Constraint as generative. There is a substantial body of work in design and creativity research suggesting that constraints improve rather than restrict output, by reducing the search space to something a person can actually explore and by forcing the abandonment of conventional solutions that do not fit. The intuition is familiar from formal verse and from any design brief with a hard limit. The empirical literature here is suggestive rather than conclusive, and the effect is plausibly non-monotonic — too little constraint produces paralysis, too much produces triviality — but the direction is well supported for moderate constraints. Deferred commitment. A long process allows more of the organisation to attach to the emerging answer, which raises the cost of abandoning it. A short one does not. This is not a psychological effect on the individual but a structural effect on the organisation, and it is the mechanism identified in the previous chapter as what the sprint is really economising. The specific structure of the sprint's timeboxes The five-day frame is subdivided, and the subdivision does more work than the total. Individual exercises are bounded to minutes rather than hours. Crazy Eights — eight variations sketched in eight minutes, one per fold of a sheet of paper — is the extreme case, and its design is instructive. Sixty seconds is far too little time to produce a considered idea. That is the point: it is enough time to produce an unconsidered one, and the exercise's purpose is to move a person past the two or three obvious solutions they arrived with, into the region where the interesting options live. Under a one-minute constraint the internal critic has no opportunity to operate. Discussion is bounded even more tightly. The speed critique on Wednesday allows three minutes per sketch, timed. The purpose is to extract the group's observations without permitting the discussion to become a negotiation, and the time limit is what prevents the drift from evaluation into advocacy. Decisions are bounded to a moment. The vote is simultaneous. The decider's choice is made and announced. There is no reconsideration. The general principle is that each timebox is set to permit the activity's productive part and to cut it off before its unproductive part begins. Idea generation becomes unproductive when it turns into refinement of a favoured option; critique becomes unproductive when it turns into persuasion; decision becomes unproductive when it is reopened. The lengths are chosen accordingly, and this is a considerably more sophisticated design than the arbitrary-seeming numbers suggest. The limits of the argument Three honest qualifications. The compression argument applies to a specific kind of work: exploratory, divergent, judgement-heavy work where the criteria are unclear and the search space is large. It does not apply to work that has an irreducible duration. Building a database migration does not go faster under time pressure; it goes wrong. Knapp is careful about this in one respect — the sprint produces a facade, not a product — and less careful in another, since teams routinely apply sprint logic to work that has real duration. The evidence for the quality claim is weaker than the evidence for the effort claim. That deadlines concentrate effort is well established. That short deadlines produce better creative output is supported by theory and by practitioner experience, and has not been demonstrated in a controlled comparison of design outcomes. This is a place where the sprint's confidence exceeds its warrant. And compression has costs that the framework does not price. Five consecutive days of intensive facilitated work is genuinely demanding, and the quality of thought on Thursday afternoon is not what it was on Monday morning. The format's own remedy — the prototyping day is largely execution rather than judgement — is a partial acknowledgement of this. Teams that run sprints repeatedly report diminishing returns, which is consistent with a real fatigue cost that the single-instance framing conceals. The facilitator as timekeeper One practical implication of the timebox deserves separate treatment, because it explains a role that would otherwise look like overhead. The sprint requires a facilitator whose primary function is not expertise but enforcement. They keep time, move the group between exercises, cut off discussion at the limit, and refuse requests for extension. The book is explicit that the facilitator should be someone comfortable being mildly unpopular. The reason a person is needed rather than a timer is that every timebox will be challenged, and the challenges will be reasonable. The group is mid-discussion and making progress; five more minutes would help; this particular sketch deserves longer. Each request is individually justified and collectively fatal, because the compression is the mechanism and a format that yields to good arguments for extension has no compression. The facilitator's second function is to prevent the group from reverting to its default behaviour, which it will attempt continuously. Someone will propose that the group discuss the sketches before voting, because that seems natural. Someone will suggest combining two solutions rather than choosing. Someone will want to reopen Monday's target on Wednesday. All of these are the ordinary organisational process reasserting itself, and each is a request to remove one of the controls. This is why the facilitator should ideally not be a participant with a stake in the outcome. A facilitator who also has views about what should be built cannot reliably enforce the constraints against their own preferences, and the group will detect the asymmetry. The general point is that the sprint is a set of constraints on behaviour that people find uncomfortable, and constraints on behaviour do not enforce themselves. Every element of the method that works does so because someone is preventing the group from doing the thing it wants to do. Parkinson's law and its evidential status A short note on the most-cited claim in this area, because a guide treating the framework rigorously should not repeat a witticism as though it were a finding. C. Northcote Parkinson's essay of 1955 was satire about the British Civil Service, and his supporting evidence was an observation that Admiralty administrative staff grew while the number of ships fell. It is a good joke supported by an anecdote, and it has been repeated for seventy years as though it established something. The underlying phenomenon has better support from other sources, and it is worth distinguishing which parts are secure. That people concentrate effort near deadlines rather than distributing it evenly: well supported, and observable in any dataset of submission times. That tasks given more time take more time: supported by the deadline research cited earlier and by the extensive literature on the planning fallacy, though the mechanism is a combination of effects — procrastination, scope expansion, and the fact that longer allocations were justified by estimates that were wrong. That the additional time produces no additional quality: this is the strong version and it is not established. Some tasks genuinely benefit from more time. The defensible claim is narrower: that the additional quality obtained from additional time diminishes, often sharply, and that for many tasks the marginal return is close to zero well before the time allocated is exhausted. The sprint's design is compatible with the narrow claim and does not require the strong one. Its timeboxes are set at the point where each activity's returns are judged to flatten, and the judgement is practitioner experience rather than measurement. A team adapting the format should feel free to lengthen an exercise it believes is being cut short and should notice that the belief is what the format is designed to override. Hashtags: #TheFiveDayFramework #Sprint #JakeKnapp #JohnZeratsky #BradenKowitz #DesignSprint #GoogleVenturesSprint #FiveDaySprint #DesignThinking #ProductDevelopment #ProductInnovation #RapidPrototyping #UserTesting #CustomerValidation #UserCenteredDesign #DecisionScience #GroupDecisionMaking #CreativeProblemSolving #InnovationManagement #StructuredBrainstorming #SilentVoting #CrazyEights #Timeboxing #TeamCollaboration #CrossFunctionalTeams #LeanStartup #MinimumViableProduct #EvidenceBasedDesign #ProductStrategy #BusinessInnovation

Download the Book (PDF): Introduction In 2025, according to UN Tourism, the United Nations agency responsible for the sector, international tourist arrivals around the world reached about 1.52 billion. That figure counts only trips that crossed a border. Add the far larger number of domestic trips — families driving to the coast, students taking a train to a festival, business travellers flying between cities in the same country — and tourism becomes one of the most widespread human activities on the planet. It moves people across oceans and continents, supports hundreds of millions of jobs, shapes the economies of small islands and great cities alike, and leaves marks, good and bad, on cultures and landscapes everywhere. Studying tourism for the first time can therefore feel like trying to drink from a fire hose. An introductory textbook has to cover the history of travel, the psychology of why people travel, the airlines, railways and cruise ships that carry them, the hotels and restaurants that host them, the agencies and websites that sell to them, the attractions and events that draw them, the governments and organisations that promote and regulate them, the economics of what they spend, the effects they have on communities and the environment, and the prospects for the decades ahead. Each of these topics comes with its own vocabulary, its own statistics, and its own academic debates. Tourism: Principles, Practices, Philosophies by Charles R. Goeldner and J. R. Brent Ritchie is one of the longest-established textbooks that attempts this task. It traces its origins to a 1972 text by Robert McIntosh and has been revised through many editions since; its twelfth edition runs to twenty chapters covering the whole field. Goeldner, a long-time professor at the University of Colorado, and Ritchie, of the University of Calgary, are among the most influential figures in tourism scholarship — Ritchie in particular for his work on how destinations compete. The book’s great strength is its comprehensiveness. For a first-year student, that is also its challenge. Why tourism matters It is worth pausing on why tourism deserves serious study at all. The first reason is economic. The World Travel & Tourism Council, which represents the private sector, estimates that travel and tourism — counting not only direct spending but its knock-on effects through supply chains and wages — accounts for roughly one-tenth of global economic output and a similar share of jobs. For many small island states and developing countries, tourism is the largest source of foreign exchange. The second reason is social and cultural. Tourism brings people from different cultures into contact on a scale never seen before, with consequences for understanding, identity and heritage that can be enriching or damaging. The third reason is environmental. Tourism depends on attractive natural and cultural environments and also places pressure on them; one widely cited study, by Manfred Lenzen and colleagues in 2018, estimated that tourism accounted for about eight per cent of global greenhouse gas emissions once the full supply chain was included. The fourth reason is political. Governments at every level promote, regulate, tax and plan for tourism, and argue about how its benefits and costs should be shared. Because it touches so many aspects of life, tourism is studied from many disciplines at once: economics, geography, sociology, anthropology, psychology, management, marketing, environmental science and planning. That is part of what makes it demanding for a new student, and part of what makes it interesting. Goeldner and Ritchie’s textbook draws on all of these perspectives, which is why it can feel so wide-ranging. The argument of this guide This guide offers a way through. Its controlling idea is that tourism is a system, and every concept you meet belongs somewhere on its map. Tourism is not a single industry but a set of connected parts. At one end are the travellers, with their motivations, their means and their choices. At the other end are the destinations, with their attractions, their communities and their environments. Between them run the transport routes that move people and the distribution channels that sell trips. Around them sit the businesses that provide accommodation, food, entertainment and services; the organisations and governments that promote, plan and regulate; and the economic, social and environmental consequences that follow. Once you can see this system as a whole, the mass of terminology and statistics stops being a blur. Each new term is simply a label for one part of the map, or for a connection between parts. The system view is not an invention of this guide. It runs through the academic study of tourism, from Neil Leiper’s influential model of the tourism system in the late 1970s to the models Goeldner and Ritchie themselves use to show how the components of tourism fit together. What this guide does is make the system the organising principle of your learning, so that you always know where you are. How the guide is organised The textbook’s twenty chapters are grouped here into nine, following the logic of the system. Chapter 1 sets out the foundations: what tourism is, how it is defined and measured, and the models that show it as a system. Chapter 2 traces how tourism developed over time, because today’s system is the product of that history. Chapter 3 turns to the travellers — why people travel and how they choose. Chapters 4 and 5 examine the supply side: first the transport that moves people and the organisations that govern the system, then the hospitality businesses, attractions, events and distribution channels that serve them. Chapter 6 explains how tourism is measured and what it contributes to economies. Chapter 7 considers the relationships between visitors and the places they visit — the social, cultural and environmental effects of tourism. Chapter 8 examines how destinations are steered through policy, planning, marketing and research, including Ritchie’s model of destination competitiveness. Chapter 9 looks ahead to tourism’s future and the careers it offers. A short conclusion brings the system back together. Each chapter ends with two study tools. A key terms list gives concise definitions of the vocabulary you are most likely to need in examinations and assignments. Review questions test your understanding and give you practice for the kinds of questions you will meet in assessment. Several chapters also include stakeholder matrices and summary tables that organise complex information at a glance. How to use this guide Read the relevant chapter of this guide before tackling the corresponding chapters of the textbook, so that you know where each topic fits in the system and what to look for. Then read the textbook for the detail, the examples and the depth. Return to this guide when revising: the key terms and review questions are designed for exactly that purpose. As you work, keep asking one question: which part of the system am I looking at, and what is it connected to? A question about airline deregulation is also a question about the growth of demand, the fortunes of destinations, and the environmental impact of flying. A question about a local festival is also a question about motivation, the economics of events, and the relationship between visitors and residents. The students who do best in introductory tourism are not those who memorise the most facts, but those who can see how the facts connect. This guide is designed to help you become one of them. Chapter 1: What Tourism Is — Definitions and the Tourism System Every subject has to begin by defining its object of study, and tourism has found this unusually difficult. Is a business traveller a tourist? Is someone visiting relatives? A student spending a semester abroad? A day-tripper who never stays overnight? A migrant worker? The answers matter, because they determine what gets counted in tourism statistics, which in turn shape how governments see tourism’s importance and how businesses plan. This chapter, which corresponds to the opening chapter of Goeldner and Ritchie’s textbook, sets out the key definitions, the basic units of measurement, and the models that present tourism as a system. It is the foundation on which the rest of the guide builds. Defining tourism Goeldner and Ritchie offer a broad definition that emphasises relationships. In their account, tourism consists of the processes, activities and outcomes that arise from the relationships and interactions among tourists, tourism suppliers, host governments, host communities and the surrounding environments involved in attracting and hosting visitors. The strength of this definition is that it treats tourism not simply as what tourists do, but as a web of interactions among several groups — which is exactly the system view this guide adopts. For statistical purposes, a more precise definition is needed, and the international standard is set by UN Tourism (known until 2024 as the World Tourism Organization, UNWTO). Its recommendations, set out in the International Recommendations for Tourism Statistics 2008, define tourism in terms of visitors. A visitor is a traveller taking a trip to a main destination outside their usual environment, for less than a year, for any main purpose — business, leisure or another personal purpose — other than to be employed by a resident entity in the place visited. Tourism is the activity of visitors. Several elements of this definition deserve attention, because examination questions often turn on them. The idea of the usual environment excludes routine travel — commuting to work, regular shopping trips, visits to a local doctor. Tourism begins when a person leaves the geographic area within which they conduct their regular routines. The time limit of less than a year separates visitors from migrants and long-term residents. The purpose criterion is deliberately broad. Business travel, visiting friends and relatives, attending a conference, making a pilgrimage, receiving medical treatment and studying for a short course all count as tourism, alongside holidays. What is excluded is travel to take up employment paid by an organisation in the place visited. Within visitors, a further distinction is essential. A tourist, or overnight visitor, is a visitor whose trip includes at least one overnight stay. A same-day visitor, sometimes called an excursionist, is one whose trip does not. A cruise passenger who spends a day ashore at a port and sleeps on board is a same-day visitor to that port. The distinction matters because overnight visitors typically spend far more, particularly on accommodation. Forms of tourism Tourism statistics also classify trips according to the relationship between the visitor’s country of residence and the country visited. The basic forms can be combined into broader categories, and the terminology is a frequent source of confusion. Table 1 sets it out. Table 1. Forms and categories of tourism in international statistics. Term Who it covers Example, from the viewpoint of the United Kingdom Domestic tourism Residents travelling within their own country A Manchester resident on holiday in Cornwall Inbound tourism Non-residents travelling in the country A visitor from Japan touring Scotland Outbound tourism Residents travelling to another country A London resident on holiday in Spain Internal tourism Domestic plus inbound All tourism taking place within the UK National tourism Domestic plus outbound All tourism by UK residents, at home or abroad International tourism Inbound plus outbound All tourism crossing the UK’s borders The distinctions matter for policy. A government seeking foreign exchange focuses on inbound tourism, since inbound visitors bring money into the economy from abroad. A government concerned about money leaving the country may watch outbound tourism. Domestic tourism, often overlooked in favour of the more glamorous international figures, is in most large countries far bigger than international tourism in volume, and it proved the industry’s lifeline during the pandemic, when borders closed and residents holidayed at home. Measuring tourism: the basic units Tourism is measured in several ways, and each measure tells a different story. Arrivals count the number of times visitors arrive in a country or destination. International arrivals are the headline figure reported by UN Tourism; the 1.52 billion arrivals recorded in 2025 is an example. Note that arrivals count trips, not people: a business traveller who visits France six times in a year is counted six times. Trips count journeys taken by residents, and are the usual unit for domestic and outbound tourism. Overnight stays or nights count the number of nights spent, which is closely related to demand for accommodation. Expenditure measures what visitors spend. For international tourism, international tourism receipts measure the spending of inbound visitors, which UN Tourism reported at around US$1.9 trillion in 2025. Length of stay is the average number of nights per trip, calculated by dividing nights by arrivals or trips. No single measure is sufficient. A destination whose arrivals are rising but whose average length of stay and spending per visitor are falling may be attracting more people while earning less from them. Chapter 6 of this guide returns to measurement in more detail. Tourism as a system: Leiper's model A definition tells us what tourism is; a model tells us how it works. The most widely taught model of tourism as a system was developed by the Australian scholar Neil Leiper in 1979 and refined in later work. Leiper’s model has a clear geographic structure with three regions. The traveller-generating region is where the tourist lives and where the trip begins and ends. This is where the demand for tourism originates: where people decide to travel, plan their trips, and buy many of the services they will use. The tourist destination region is where the tourist goes — the place that attracts them and where they spend most of their time and money. This is where the most visible effects of tourism, economic, social and environmental, are felt. The transit route region connects the two. It includes not only the physical routes — airports, flight paths, motorways, railway lines — but the places travellers pass through along the way, which may themselves be affected by tourism. Within this geographic frame, Leiper placed three further elements: the tourists themselves, the tourism industry — the businesses and organisations that serve tourists, located in all three regions — and the wider environment — physical, cultural, social, economic, political and technological — which surrounds and influences the whole system. The model’s great value for students is that it makes connections visible. A change in one region affects the others. A recession in a major generating region, for example, reduces demand at destinations thousands of miles away. A new airline route changes the transit region and can transform a destination’s accessibility. A crisis at a destination — a natural disaster, political unrest — affects businesses in the generating region that sell trips there. When an examination question asks about any tourism phenomenon, locating it on Leiper’s model is often a good way to begin. Tourism as a system: the components view Goeldner and Ritchie present a complementary way of seeing the system, focused less on geography and more on the components that together make up the tourism phenomenon. In essence, their model places the traveller at the centre, surrounded by the resources and sectors that serve them: the natural resources and environment that attract visitors; the built environment of infrastructure and facilities; the operating sectors of the industry, such as transportation, accommodation, food services, attractions, events, adventure and outdoor recreation, entertainment and the travel trade; the spirit of hospitality and cultural resources of the host community; and the planning, development, promotion and policy through which the whole is managed. This components view is especially useful for understanding the supply side of tourism — what a destination must have and do in order to attract and host visitors — and for recognising that tourism is not a single industry but a combination of many. It is why the textbook devotes separate chapters to transport, hospitality, distribution and attractions, and why this guide examines them in Chapters 4 and 5. Why people travel: purposes of trips International statistics also classify trips by their main purpose, and the categories reveal how much wider tourism is than holidays. UN Tourism’s recommendations distinguish personal purposes — holidays, leisure and recreation; visiting friends and relatives; education and training; health and medical care; religion and pilgrimage; shopping; transit; and other personal reasons — from business and professional purposes, which include attending meetings, conferences and trade fairs, and working on short assignments for an employer based elsewhere. Two of these categories are often underestimated by students. Visiting friends and relatives, usually abbreviated to VFR, accounts for a very large share of trips in many countries, particularly domestic trips and travel linked to migration. VFR travellers often stay with their hosts rather than in paid accommodation, so they spend less on lodging, but they spend on transport, food, shopping and attractions, and they are less sensitive to fashion and crisis than holidaymakers. Business and professional travel, including the meetings, incentives, conferences and exhibitions sector often abbreviated to MICE, generates high spending per visitor, supports large convention centres and hotels in major cities, and tends to be concentrated on weekdays and outside peak holiday seasons, which helps destinations fill capacity year-round. The purpose of a trip shapes almost everything about it: when it is taken, how far in advance it is booked, how sensitive it is to price, where the visitor stays, and what they spend. Segmenting visitors by purpose is therefore one of the first steps in understanding any destination’s tourism. Who is involved: an introduction to stakeholders Goeldner and Ritchie’s definition of tourism names the groups whose interactions constitute it: tourists, tourism suppliers, host governments, host communities and the surrounding environment. These are tourism’s stakeholders — the people and organisations with an interest in how tourism develops and who are affected by it. It is useful to meet them at the start, because nearly every debate in tourism is, at bottom, a debate among stakeholders with different interests. Visitors want enjoyable, safe, good-value experiences. Businesses — airlines, hotels, tour operators, attractions, restaurants and many others — want profitable demand. Host communities want the jobs and income tourism brings, but also want to protect their quality of life, their culture and their environment. Governments at national, regional and local levels want economic development, tax revenue and employment, and are also responsible for infrastructure, regulation and the public interest. Non-governmental organisations represent interests such as conservation, heritage and workers’ rights. And the environment — natural and cultural — is sometimes described as a stakeholder in its own right, since it cannot speak for itself but is profoundly affected. These groups do not always agree. Chapter 8 of this guide sets out their interests and influence in a stakeholder matrix and shows how destinations try to manage the conflicts between them. Is tourism an industry? A final conceptual question follows from the components view. Economic statistics classify businesses into industries according to what they produce: agriculture, manufacturing, retail, accommodation, air transport, and so on. Tourism does not fit neatly, because it is defined not by what is produced but by who consumes it. A restaurant serves both tourists and local residents; so does a taxi, a museum or a shop. Tourism is therefore sometimes described as a demand-defined sector, cutting across many conventional industries. This is why countries have developed Tourism Satellite Accounts, discussed in Chapter 6, which estimate the share of each industry’s output that is attributable to visitors. It is also why tourism has historically been under-recognised in economic policy: its contribution is spread across many industries and does not appear as a single line in national accounts. Understanding this point will help you make sense of the debates about tourism’s economic importance that recur throughout the textbook. Key terms • Tourism: the activity of visitors; more broadly, the processes and outcomes arising from interactions among tourists, suppliers, governments, host communities and environments. • Visitor: a traveller taking a trip outside their usual environment, for less than a year, for any main purpose other than employment by a resident entity in the place visited. • Usual environment: the geographic area within which a person conducts their regular routines. • Tourist (overnight visitor): a visitor whose trip includes at least one overnight stay. • Same-day visitor (excursionist): a visitor whose trip does not include an overnight stay. • Domestic, inbound and outbound tourism: travel by residents within their country, by non-residents into it, and by residents out of it. • Arrivals: the number of visitor arrivals at a destination, counting trips rather than people. • International tourism receipts: expenditure by inbound international visitors. • Traveller-generating region, transit route region, tourist destination region: the three geographic regions of Leiper’s tourism system. • VFR: travel whose main purpose is visiting friends and relatives. • MICE: meetings, incentives, conferences and exhibitions — the business events sector. • Stakeholder: a person, group or organisation with an interest in, or affected by, tourism. • Tourism Satellite Account: a statistical framework for measuring tourism’s contribution across the industries of a national economy. Review questions 1. Using the UN Tourism definition of a visitor, explain whether each of the following counts as tourism: a business trip to a conference abroad; a weekly commute to an office in another city; a two-year overseas work assignment; a day trip to a theme park in a neighbouring region. 2. Distinguish between internal, national and international tourism, giving an example of each from the perspective of a country of your choice. 3. Why might a destination’s international arrivals rise while its tourism receipts fall? What other measures would you examine? 4. Draw and explain Leiper’s model of the tourism system, and use it to analyse the effects of a new low-cost airline route between two cities. 5. “Tourism is not an industry.” Evaluate this statement. Chapter 2: How Tourism Grew — A Short History of Travel Today’s tourism system did not appear from nowhere. Its structure — who travels, how they travel, where they go and who organises it — is the product of a long history of technological, economic and social change. The second chapter of Goeldner and Ritchie’s textbook traces this history from the ancient world to the present. This chapter of the guide condenses it into a narrative organised around the forces that drove each stage, because understanding those forces is far more useful than memorising dates. The same forces are still at work, and they will shape tourism’s future. Four forces behind tourism's growth It helps to hold four forces in mind throughout the story. Technology, especially transport technology, has repeatedly transformed tourism by making travel faster, cheaper, safer and more comfortable. Railways, steamships, cars, jet aircraft and the internet each opened a new era. Income and leisure time determine who can travel. For most of history, travel for pleasure was confined to a wealthy few. The spread of paid holidays and rising incomes in the twentieth century extended it to the majority in industrialised countries, and more recently to a rapidly growing middle class in emerging economies. Organisation makes travel easier. Innovators who packaged transport, accommodation and activities into a single product, and the institutions that regulated and promoted travel, repeatedly lowered the barriers to taking a trip. Social and cultural change shapes why people travel and what they seek — from religious devotion and health cures to education, relaxation, adventure and self-expression. Travel in the ancient and medieval worlds People have travelled for trade, war, religion and curiosity for thousands of years. In ancient Greece, athletes and spectators travelled to the Olympic Games; in the Roman Empire, a network of roads, a common currency and relative security allowed wealthy Romans to travel to coastal villas, to famous sites and to healing springs. These early forms of travel already display features of modern tourism: attractions that draw visitors, infrastructure that supports them, and services — inns, guides, food — that cater to them. In the medieval period, pilgrimage was the most important form of travel for pleasure and purpose combined. Christians travelled to Rome, Santiago de Compostela, Canterbury and Jerusalem; Muslims undertook the Hajj to Mecca, which remains one of the largest annual movements of people in the world. Pilgrimage routes generated hospices, inns and a market in souvenirs, and the literature they produced, such as Chaucer’s Canterbury Tales, shows that pilgrims combined devotion with sociability and entertainment. The link between religious travel and tourism continues today in the popularity of pilgrimage routes such as the Camino de Santiago. The Grand Tour, spas and the seaside From the seventeenth to the early nineteenth centuries, young men of the British aristocracy, and later other wealthy Europeans, undertook the Grand Tour: an extended journey, often lasting a year or more, through France, Switzerland and above all Italy, intended to complete their education in classical culture, art and manners. The Grand Tour created a demand for guidebooks, tutors, lodgings and souvenirs, and it established the idea that travel was a form of personal and cultural enrichment — an idea that remains central to cultural tourism today. In the same period, spa towns such as Bath in England flourished as places where the wealthy went to take the waters for their health and to enjoy a fashionable social life. In the eighteenth century, doctors began to recommend sea-bathing, and seaside towns such as Scarborough and Brighton became resorts. The shift from spa to seaside is an early example of how changing ideas about health and pleasure can create new destinations. Railways, Thomas Cook and the birth of mass travel The Industrial Revolution transformed tourism in two ways. It created a large urban working and middle class with modest but growing incomes, and it created the technology — the railway — to move them cheaply. Britain’s first public passenger railways opened in the 1820s and 1830s, and within a few decades a national network made it possible to travel in hours journeys that had once taken days. The figure most associated with this era is Thomas Cook, a Baptist preacher and temperance campaigner who, in 1841, arranged for a railway company to carry several hundred people from Leicester to a temperance meeting in Loughborough at a reduced fare. From this modest beginning, Cook developed a business organising excursions, including trips to the Great Exhibition in London in 1851, tours of continental Europe from the 1850s, and eventually journeys around the world. His innovations — negotiating group rates, combining transport and accommodation into a single package, providing guides and printed itineraries, and issuing hotel coupons — made travel accessible to people who would never have attempted it alone. He is often described as the founder of the modern travel industry. Other nineteenth-century developments reinforced the trend. Steamships made sea travel faster and more reliable. Grand hotels appeared in cities and resorts, and figures such as César Ritz established new standards of luxury hospitality. Seaside resorts expanded rapidly to receive working-class day-trippers and holidaymakers arriving by train. The twentieth century: cars, paid holidays and the jet age In the twentieth century, three developments turned tourism into a mass phenomenon in industrialised countries. The first was the motor car. Mass-produced cars, beginning with Henry Ford’s Model T in 1908, gave families the freedom to travel independently, and roadside businesses — motels, service stations, diners, campsites — grew to serve them. The second was paid holidays. Legislation and collective agreements gradually gave workers an entitlement to paid leave; in Britain, for example, the Holidays with Pay Act of 1938 encouraged its spread. Holiday camps, pioneered in Britain by Billy Butlin, whose first camp opened in Skegness in 1936, offered all-inclusive holidays to working families. The third, and most transformative, was air travel. Commercial jet aircraft entered service in the 1950s, and the arrival of wide-bodied jets such as the Boeing 747 around 1970 dramatically lowered the cost per seat of long-distance flights. At the same time, entrepreneurs combined charter flights with hotel accommodation to create the package holiday. In 1950 Vladimir Raitz’s Horizon Holidays flew a group of British holidaymakers to Corsica, an early example of what became a huge industry. Through the 1960s and 1970s, package holidays carried millions of northern Europeans to the Mediterranean, transforming coastal Spain and other destinations into centres of mass tourism. The international institutions of air travel also took shape in this period. The Chicago Convention of 1944 established the framework for international civil aviation, leading to the International Civil Aviation Organization, and airlines formed the International Air Transport Association in 1945. Deregulation and the low-cost revolution For decades, air fares and routes were tightly regulated by governments. From the late 1970s, this changed. The United States deregulated its domestic airline industry in 1978, allowing airlines to set fares and choose routes. The European Union progressively liberalised its aviation market, creating a single market in the 1990s. Deregulation opened the way for low-cost carriers, which followed the example of Southwest Airlines in the United States by simplifying their operations — a single aircraft type, point-to-point routes, secondary airports, rapid turnarounds, direct online sales and charges for extras. In Europe, Ryanair and easyJet grew rapidly from the 1990s onwards. The consequences for tourism were profound. Cheap fares made short breaks to foreign cities affordable to many more people, turned previously obscure cities into popular destinations, and changed patterns of travel from one long annual holiday to several shorter trips. They also contributed to the growth in tourism’s environmental footprint and, in some cities, to the pressures later described as overtourism. The digital era The next transformation was digital. Airlines had used computer reservation systems since the 1960s, and these evolved into global distribution systems used by travel agents worldwide. From the mid-1990s, the internet allowed travellers to research and book directly. Online travel agencies such as Expedia and Booking.com were founded in 1996; review platforms such as Tripadvisor, founded in 2000, gave travellers a powerful voice; and Airbnb, founded in 2008, enabled private individuals to rent their homes to visitors at scale. The spread of smartphones from the late 2000s put all of these tools in travellers’ pockets and made social media a major influence on where people choose to go. The digital era shifted power within the tourism system. Travellers gained information and choice; traditional intermediaries such as high-street travel agents faced intense pressure; and new digital intermediaries became some of the most powerful companies in the industry. Chapter 5 of this guide examines these changes in the distribution chain. Shocks and resilience Tourism’s history is also a history of shocks. Terrorist attacks, notably those of 11 September 2001, disease outbreaks such as SARS in 2003, and the global financial crisis of 2008–09 each caused sharp falls in travel. None compared with the COVID-19 pandemic. As borders closed and travel restrictions spread in 2020, international tourist arrivals fell by around 73 per cent, according to UN Tourism, returning global tourism to levels not seen for three decades. The recovery that followed was also striking. International arrivals rebounded through 2022 and 2023, approached pre-pandemic levels in 2024, and in 2025 reached around 1.52 billion, surpassing the 2019 total. The recovery was uneven — some regions, such as parts of Asia and the Pacific, recovered more slowly than Europe and the Middle East — but it demonstrated the strength of the underlying desire to travel. The pandemic also left lasting changes, including greater use of remote work, blurring of business and leisure travel, and heightened attention to health, flexibility and resilience. A wider view: tourism beyond Europe The standard history of tourism, including much of what appears in introductory textbooks, is told largely from a European and North American perspective, running from the Grand Tour through Thomas Cook to the package holiday. It is worth recognising that other societies have their own long traditions of travel. The fourteenth-century Moroccan scholar Ibn Battuta travelled for nearly three decades across North Africa, the Middle East, Central Asia, India, South-East Asia and China, and his account remains one of the great works of travel literature. In Ming dynasty China, the geographer and writer Xu Xiake spent much of his life travelling through the country’s mountains and rivers, recording his journeys in diaries still read today. In Edo-period Japan, pilgrimage to the shrines at Ise became a mass phenomenon, with ordinary people travelling in large numbers along networks of roads served by inns, guides and souvenir sellers — a well-developed tourism system operating long before the railway age in Europe. These traditions matter for more than historical completeness. The centre of gravity of world tourism has been shifting. Rising incomes in Asia have created vast new flows of domestic and outbound tourism; China became the world’s largest spender on international tourism in the 2010s, and outbound travel from India and South-East Asia has grown rapidly. Destinations and businesses that understood tourism only through the preferences of European and North American travellers have had to learn to serve visitors with different languages, expectations, food preferences, payment methods and motivations. A history that includes non-Western traditions of travel helps explain why tourism in these markets is not simply a copy of the Western model, and why the future of the industry will be shaped increasingly by travellers from outside its historical heartlands. Lessons from history The history of tourism is not merely background. It teaches three lessons that recur throughout the textbook. First, technology and institutions repeatedly reshape the system, often suddenly, creating new destinations and undermining old ones. Second, tourism has steadily democratised, extending from elites to mass markets and from a few wealthy countries to much of the world; the rise of outbound travel from China, India and other emerging economies is the latest chapter of that story. Third, growth brings both benefits and costs, and the tensions between them — which Chapter 7 of this guide explores — are as old as the seaside resort. Key terms • Pilgrimage: travel for religious purposes to a sacred site; one of the oldest forms of tourism. • Grand Tour: an extended educational journey through continental Europe undertaken by young wealthy Europeans, especially from the seventeenth to early nineteenth centuries. • Spa town: a resort developed around mineral springs believed to have health benefits. • Package holiday: a combination of transport, accommodation and often other services sold together at a single price. • Chicago Convention (1944): the treaty establishing the framework for international civil aviation. • Deregulation: the removal of government controls over prices and routes in an industry, notably airlines. • Low-cost carrier: an airline that minimises costs through simplified operations and charges separately for extras. • Global distribution system (GDS): a computerised network through which travel agents search and book airline seats, hotel rooms and other travel services. • Online travel agency (OTA): an internet-based business selling travel services from many suppliers. Review questions 1. Identify the four forces that have driven the growth of tourism and illustrate each with an example from a different historical period. 2. Why is Thomas Cook often described as the founder of the modern travel industry? Which of his innovations are still visible in tourism today? 3. Explain how the combination of jet aircraft and the package holiday transformed Mediterranean destinations in the 1960s and 1970s. 4. Assess the impact of airline deregulation and low-cost carriers on patterns of tourism in Europe. 5. What does the pandemic and the recovery that followed it reveal about the resilience of tourism? Chapter 3: The Travellers — Motivation and Behaviour At the heart of the tourism system is the traveller. Every airline seat, hotel room and museum ticket exists because someone decided to take a trip. Understanding why people travel, how they choose where to go, and what shapes their behaviour is therefore fundamental to understanding tourism as a whole. Goeldner and Ritchie devote chapters to motivation for pleasure travel and to cultural tourism as a source of life enrichment. This chapter distils the key theories you are likely to meet, explains how they relate to one another, and shows why they matter in practice. Why motivation matters Motivation is the internal driving force that leads a person to act. In tourism, understanding motivation serves several practical purposes. It allows destinations and businesses to segment the market into groups with similar motives and needs. It informs the design of products — a holiday for people seeking relaxation looks very different from one for people seeking adventure. It shapes marketing, since messages that speak to travellers’ underlying motives are more persuasive than those that simply list features. And it helps explain patterns of demand, such as why some destinations rise and fall in popularity. The theories below are not rivals, with one right and the others wrong. Each captures part of a complex reality, and the best answers in examinations use them in combination. Needs: Maslow's hierarchy Many introductions to tourism motivation begin with Abraham Maslow’s hierarchy of needs, set out in 1943. Maslow proposed that human needs form a hierarchy: physiological needs such as food and rest; safety needs; love and belonging; esteem; and, at the top, self-actualisation — the realisation of one’s potential. Lower needs must be at least partly satisfied before higher ones become motivating. Tourism can be linked to every level. A beach holiday may meet the physiological need for rest; a trip to visit family meets the need for belonging; a luxury holiday or a visit to a fashionable destination may meet the need for esteem; and a journey of learning, challenge or spiritual discovery may contribute to self-actualisation. The hierarchy is useful for showing that travel can satisfy very different needs, and that the same trip can mean different things to different people. Its limitations should also be acknowledged. Maslow’s model was not developed for tourism, and there is little evidence that needs are satisfied in a strict sequence. Travellers are often motivated by several needs at once, at different levels. The hierarchy is best used as a framework for discussion rather than a precise predictive theory. Push and pull A more tourism-specific framework distinguishes push factors from pull factors. The distinction was developed by Graham Dann in 1977 and has since become one of the most widely used ideas in the field. Push factors are the internal, socio-psychological forces that make a person want to travel at all: the desire to escape routine, to relax, to have new experiences, to spend time with family, to gain prestige. They answer the question “why travel?” Pull factors are the attributes of destinations that attract travellers once the desire to travel exists: beaches, climate, culture, attractions, events, prices, accessibility, the reputation of the place. They answer the question “why travel there?” The framework’s value is in showing how motivation and destination choice connect. A person pushed by a desire for relaxation will be pulled towards destinations that promise rest and comfort; a person pushed by a desire for novelty will be pulled towards the unfamiliar. Destinations can influence pull factors directly through what they develop and how they market it, but they must understand the push factors of their target markets to do so effectively. Crompton's motives John Crompton, in a study published in 1979, interviewed pleasure travellers in depth to identify the motives behind their trips. He identified seven socio-psychological motives — the push factors: escape from a perceived mundane environment; exploration and evaluation of the self; relaxation; prestige; regression (the chance to behave in ways not possible at home, sometimes in a more carefree, childlike way); enhancement of kinship relationships; and facilitation of social interaction. He also identified two cultural motives more closely tied to the destination: novelty and education. Crompton’s list is useful in examination answers because it is concrete, empirically grounded and easy to apply. A family holiday at a theme park, for example, may be driven primarily by the enhancement of kinship relationships and regression; a solo backpacking trip by exploration of the self and novelty; a stay at a luxury resort by relaxation and prestige. Seeking and escaping Seppo Iso-Ahola proposed in 1982 that tourism motivation can be understood through two basic forces operating together: seeking (the desire to obtain intrinsic rewards, such as knowledge, challenge or a sense of competence, through travel) and escaping (the desire to leave behind the everyday environment). Each can operate at a personal level (seeking personal rewards, escaping personal troubles) or an interpersonal level (seeking social interaction, escaping the people one normally deals with). The model is compact and helps explain why the same trip can be both an escape and a quest. Types of tourist: Cohen and Plog Several researchers have classified tourists into types according to their preferences for familiarity or novelty. Erik Cohen proposed in 1972 a typology of four roles. The organised mass tourist buys a fully packaged holiday and stays largely within an “environmental bubble” of familiar comforts. The individual mass tourist uses similar facilities but with more independence and flexibility. The explorer arranges their own trip, seeks to get off the beaten track, but still wants some comfort and security. The drifter avoids the tourist industry altogether, seeking immersion in local life. Cohen described the first two as institutionalised roles, dependent on the tourism industry, and the last two as non-institutionalised. Stanley Plog, working in the early 1970s, proposed a continuum of personality types. At one end are psychocentrics (later called dependables), who prefer familiar, safe, well-developed destinations and packaged experiences; at the other are allocentrics (later venturers), who seek novel, unusual and undeveloped places. Most people fall in between. Plog used the model to suggest that destinations rise and fall as their appeal shifts from venturers, who discover them, to the mid-centric mass, and finally to dependables — by which time venturers have moved on and the destination risks decline. The idea connects to Butler’s model of the destination life cycle discussed in Chapter 7. Both typologies are influential and both have been criticised. Personality alone is a limited predictor of behaviour, travellers may behave differently on different trips, and empirical tests of Plog’s model have produced mixed results. They are best used as illustrative frameworks. The travel career Philip Pearce proposed that people’s travel motivations change over their lifetime as they gain experience — an idea he initially called the travel career ladder and later refined, with Uk-Il Lee in 2005, as the travel career pattern. The core insight is that motives such as novelty, escape and relationship-building are important for most travellers, while more experienced travellers place increasing weight on motives such as self-development and engagement with host cultures and nature. The model links motivation to experience, suggesting that a traveller’s tenth international trip is likely to be motivated differently from their first. Cultural tourism and life enrichment Goeldner and Ritchie give particular attention to cultural and international tourism as a source of personal enrichment. Travel exposes people to other ways of life, languages, arts, histories and beliefs, and many travellers are motivated precisely by the desire to learn and to broaden their understanding. Cultural tourism — travel motivated wholly or partly by interest in the heritage, arts, festivals, lifestyles and traditions of a place — is one of the largest and fastest-growing segments of the market, and includes heritage tourism, arts and festival tourism, religious tourism, and food and wine tourism. The enrichment perspective emphasises tourism’s potential benefits for mutual understanding. It also raises questions that Chapter 7 of this guide addresses: whether culture is respected or commodified when it becomes a tourist attraction, and whether visitors encounter authentic culture or a version staged for them. How travellers decide Motivation explains why people want to travel; decision-making explains how they turn the wish into a trip. Most models describe a sequence of stages: recognising a need or desire to travel; searching for information; evaluating alternatives; making the booking; experiencing the trip; and evaluating it afterwards, which in turn shapes future decisions and the advice travellers give others. At each stage, several kinds of influence operate. Personal factors include age, income, education, life stage and past experience. Social factors include family, friends, reference groups and, increasingly, social media and online reviews. Situational factors include available time, money, health and safety concerns. Marketing factors include the destination’s image and the promotion and pricing of trips. Equally important are the constraints that prevent people from travelling even when they want to. Leisure researchers Duane Crawford and Geoffrey Godbey proposed in 1987 that constraints can be intrapersonal (internal states such as anxiety or lack of interest), interpersonal (the lack of a suitable travel companion) or structural (lack of money, time, access or information). Understanding constraints helps explain why demand varies between groups, and suggests how destinations and businesses can make travel more accessible — for instance, through accessible design, solo-traveller products or flexible pricing. The phases of the travel experience Motivation and decision-making describe what happens before a trip. But the traveller’s experience extends over a longer period than the trip itself. In a classic study of outdoor recreation published in 1966, the economists Marion Clawson and Jack Knetsch proposed that a recreational experience has five phases: anticipation, the period of planning and looking forward to the trip; travel to the site; the on-site experience itself; travel back home; and recollection, the period afterwards in which the experience is remembered, retold and reinterpreted. The model was developed for recreation, but it applies naturally to tourism. Two implications are worth drawing out. First, much of the value of a trip may lie outside the time spent at the destination. Anticipation can be a source of pleasure in itself — researchers have found that people often derive happiness from looking forward to a holiday — and recollection, through photographs, souvenirs and stories, can extend the value of a trip for years. Social media has transformed both phases, allowing travellers to research and imagine trips in vivid detail beforehand and to share and relive them afterwards. Second, each phase offers opportunities and risks for the businesses and destinations involved. Clear, inspiring information supports anticipation; smooth, comfortable journeys protect the travel phases, which are often the least enjoyable part of a trip; the on-site experience depends on everything discussed in Chapters 4 and 5; and follow-up communication, reviews and loyalty schemes shape recollection and the likelihood of a return visit. Thinking in phases helps explain why tourism organisations increasingly attend to the whole “journey” of the traveller rather than only to the time they spend at the destination. From motivation to segmentation Tourism businesses and destinations use their understanding of travellers to divide the market into segments — groups with similar characteristics, needs or behaviour — and to target those they can serve best. Common bases for segmentation include geographic (where travellers come from), demographic (age, income, family structure), psychographic (lifestyle, values, personality), behavioural (frequency of travel, loyalty, booking behaviour), purpose of trip and benefits sought. Motivation research is most directly useful for psychographic and benefit segmentation, which group travellers by what they want from a trip rather than by who they are. Motivation in a connected world The classic motivation theories were developed before the internet, and a contemporary answer should consider how digital media have changed the ways in which motives form and are acted upon. Social media platforms expose people constantly to images of other people’s travel, which can stimulate the push to travel and shape the pull of particular places. Destinations that photograph well have gained visitors through platforms built around images and short videos, sometimes suddenly and in numbers they were not prepared for. The desire to share experiences — and the prestige associated with doing so — gives Crompton’s motive of prestige a new, highly visible form. Films and television have long influenced destination choice, a phenomenon researchers call film-induced tourism. New Zealand’s association with the Lord of the Rings films in the early 2000s is the most frequently cited example, and more recent series have produced similar effects for their locations. Streaming services and social media have made such effects faster and more global. These developments do not invalidate the older theories; they change the channels through which push and pull operate. Escape, relaxation, novelty, social connection and prestige remain the underlying motives. What has changed is the speed at which images of destinations reach potential travellers, the role of other travellers rather than official marketing in creating destination images, and the tendency of travel to concentrate on places that have become popular online — with consequences for crowding that Chapter 7 discusses. Applying the theories: one traveller, several lenses Consider how the theories combine in a single case. A twenty-two-year-old university graduate plans a two-month trip through South-East Asia before starting her first job. Maslow’s hierarchy suggests her trip is aimed at higher-level needs — esteem, and perhaps self-actualisation through independence and challenge. In push–pull terms, she is pushed by a desire to escape routine and explore, and pulled by the region’s reputation for affordability, culture, landscapes and a well-established backpacker trail. Crompton’s framework would highlight exploration of the self, novelty, social interaction with other travellers and, perhaps, prestige. Iso-Ahola’s model would describe her as both seeking (new competence and experience) and escaping (the pressures of the transition to work). Cohen might classify her as an explorer or individual mass tourist — independent, but using the well-developed infrastructure of backpacker hostels and transport. Plog would place her towards the venturer end of the continuum. Pearce’s travel career pattern would treat this as an early-career trip in which novelty and relationships are prominent, and would predict that her motives on later trips may shift towards deeper cultural engagement. Her main constraints are structural — money and time — which is precisely why she is travelling at this point in her life. No single theory tells the whole story, but together they give a rich and structured explanation. Examiners reward exactly this ability to apply several frameworks to one case and to recognise what each adds. Key terms • Motivation: the internal driving force that leads a person to act, including to travel. • Hierarchy of needs: Maslow’s model of human needs arranged from physiological to self-actualisation. • Push factors: internal socio-psychological forces that create the desire to travel. • Pull factors: destination attributes that attract travellers. • Allocentric (venturer) / psychocentric (dependable): Plog’s opposing personality types, preferring novelty and familiarity respectively. • Environmental bubble: Cohen’s term for the familiar comforts within which mass tourists travel. • Travel career pattern: Pearce’s model of how travel motives change with experience. • Cultural tourism: travel motivated by interest in the heritage, arts and ways of life of a place. • Travel constraints: intrapersonal, interpersonal and structural factors that prevent people from travelling. • Film-induced tourism: travel motivated by a destination’s appearance in film or television. • Market segmentation: dividing a market into groups with similar characteristics or needs. Review questions 1. Explain the difference between push and pull factors, and apply the distinction to a destination of your choice. 2. Using Crompton’s socio-psychological and cultural motives, analyse the motivations of two contrasting types of traveller. 3. Compare Cohen’s and Plog’s typologies of tourists. What are their strengths and limitations? 4. How might a traveller’s motivations change over their “travel career”? Why does this matter for destination marketing? 5. Identify the main constraints that might prevent a young family from taking an international holiday, and suggest how a tourism business could reduce them. Hashtags: #TheFoundationsOfTourism #TourismPrinciplesPracticesPhilosophies #CharlesRGoeldner #JRBrentRitchie #TourismStudies #TourismEducation #TourismManagement #TourismIndustry #TourismPrinciples #TourismDevelopment #TourismSystems #LeipersTourismSystem #TourismPlanning #TourismMarketing #DestinationManagement #DestinationCompetitiveness #TouristBehavior #TourismMotivation #PushAndPullFactors #TravelAndTourism #InternationalTourism #DomesticTourism #CulturalTourism #SustainableTourism #TourismEconomics #TourismPolicy #HospitalityAndTourism #TravelIndustry #TourismResearch #TourismStudentGuide

Download the Book (PDF): INTRODUCTION The Argument Behind the Policies Capitalism and Freedom is usually read as a policy manifesto — a list of proposals, some now familiar and some still radical, arranged in loose order. School vouchers. A negative income tax. Floating exchange rates. The abolition of occupational licensing. A fixed rule for monetary growth. The end of conscription. Read that way, the book is a miscellany, and the natural response is to agree with some items and reject others. That reading misses the structure entirely. The proposals are not a list; they are consequences. Every one of them follows from a single argument stated in the first two chapters and applied thereafter, and a reader who has that argument can predict Friedman's position on almost any question without looking it up. This guide exists to make that argument explicit, to test it, and to work through its applications in the three areas the book develops most thoroughly: monetary policy, occupational restriction, and the dispersion of power. The Argument Here it is in compressed form. Freedom, for Friedman, is the absence of coercion by other people. The fundamental political problem is therefore how to obtain the coordination that a complex society requires without giving anyone the power to compel others. Two methods exist. One is central direction, which achieves coordination by command and therefore by coercion. The other is voluntary exchange, which achieves it through transactions each party enters because they expect to benefit — and which therefore requires nobody's permission and nobody's submission. From this Friedman derives his central and most contested claim: economic freedom is a necessary but not sufficient condition of political freedom. The reasoning is not that markets make people rich and rich people demand democracy. It is structural. Political freedom requires that dissent be possible, and dissent requires resources — a printing press, a hall, a salary while one campaigns, an employer willing to hire a heretic. In a society where the state is the only employer, the only landlord, the only publisher and the only source of finance, opposition to the state must be financed by the state, which will not happen. A market economy, by contrast, contains many independent holders of resources, none of whom needs to approve of a project for it to find backing; a dissident needs to persuade only one of them, and the others' disapproval costs him nothing but their custom. Friedman's formulation is that the market removes the organisation of economic activity from the control of political authority, and thereby eliminates this source of coercive power. It enables economic strength to be a check on political power rather than a reinforcement of it. Everything else follows. If concentrated power is the danger, then dispersing it is the objective, and every proposal in the book is an instance of dispersal: replacing a public monopoly of schooling with vouchers that let families choose; replacing discretionary monetary management with a rule that removes the discretion; replacing licensing boards that decide who may practise with certification that merely informs; replacing in-kind welfare administered by officials with cash that recipients direct themselves; replacing a fixed exchange rate maintained by controls with a floating one determined by the market. The Method Notice a pattern in that list, because it is the most useful thing to take from the book and it is frequently overlooked by both admirers and critics. Friedman does not, in most cases, propose abandoning the objective. He proposes achieving it by a mechanism that does not require anyone to exercise discretionary authority over anyone else. He accepts that society should ensure children are educated, and proposes vouchers rather than the abolition of public funding. He accepts that society should relieve poverty, and proposes a negative income tax rather than the abolition of transfers. He accepts that the quantity of money must be governed somehow, and proposes a rule rather than the abolition of the central bank. The recurring move is: keep the goal, replace the administered mechanism with a market or rule-governed one, and give the individual the choice. Recognising this transforms how the book reads. It is not an argument for doing less; it is an argument about how things should be done, and it stands or falls on whether the substituted mechanisms actually work. That is the test this guide applies. In several cases — floating exchange rates, the critique of licensing, the negative income tax — the substituted mechanism has been tried and the record is instructive. In others — vouchers, the monetary rule — the record is more mixed than Friedman's confidence anticipated. Stating the record honestly is more useful than either endorsing or dismissing the framework. What This Guide Covers Chapter 1 sets out the book's provenance and its method. Chapter 2 develops the central thesis about economic and political freedom, and tests it against the obvious objections. Chapter 3 sets out what Friedman thinks government should do, which is more than his reputation suggests and is the necessary corrective to the caricature. Chapters 4 through 6 take the economic policy chapters: the control of money, which is Friedman's own technical territory and the subject of his Nobel citation; international arrangements and the case for floating rates; and fiscal policy, where his argument runs directly against the postwar consensus. Chapters 7 and 8 take the microeconomic applications: occupational licensure, which is the book's most successful single argument and its most vindicated, and the cluster of chapters on discrimination, monopoly and corporate responsibility, which are its most contested. Chapter 9 takes distribution and poverty, including the negative income tax — the proposal with the longest and strangest afterlife of anything in the book. Throughout, the guide distinguishes the argument from the evidence and states where they diverge. Friedman wrote with great confidence, and the confidence was sometimes warranted and sometimes not. Distinguishing the cases is the work. A Note on Reading Friedman Three features of the prose are worth flagging in advance, because they shape how the argument lands. It is exceptionally clear. Friedman wrote better than almost any economist of his generation, in short declarative sentences with concrete examples and no hedging. This is a genuine virtue and it is also a rhetorical device: clarity conveys certainty, and an argument stated without qualification reads as more settled than one stated carefully. Readers should supply the qualifications Friedman omits, and this guide does so systematically. It argues from principle to case. The structure is nearly always: here is the general principle, here is the case, therefore here is the conclusion. This makes the reasoning easy to follow and easy to check, since one can accept the principle and dispute its application, or accept the application and dispute the principle. It also means that empirical evidence enters late and does relatively little work. Where Friedman's positions have been tested since, the results are frequently more equivocal than the original argument implied — which is what one would expect of conclusions derived largely deductively. It was written into a specific moment. 1962 in the United States meant an intellectual climate in which the case for central direction was widely assumed, in which Keynesian demand management was the professional consensus, and in which the university economics departments regarded Friedman's positions as eccentric. The book was reviewed by no major national publication on publication and sold slowly at first; it went on to sell well over half a million copies. Its combative tone reflects the position of a man arguing against a settled consensus, and some of its excesses are the excesses of that position. The reader should discount for it in the same way one discounts for any polemic — by extracting the argument and testing it separately from the rhetoric that carried it. A related caution about the book's afterlife. Friedman became, from the mid-1970s, a public figure of enormous influence, and the policies enacted under his name in several countries were not always the policies the book recommends. Reading Capitalism and Freedom through what was done in its name is as distorting as reading it through its critics. The text itself is more moderate, more systematic, and considerably more interesting than either reputation suggests. CHAPTER 1 The Book, the Lectures, and the Method Capitalism and Freedom began as a series of lectures. In June 1956, Friedman delivered a set of talks at a conference at Wabash College in Indiana, sponsored by the Volker Fund, and repeated variants of them elsewhere over the following years. Rose Director Friedman — his wife, a trained economist, and by his own account the person who turned lecture notes into prose — did the substantial work of converting the talks into a book. It was published by the University of Chicago Press in 1962. Knowing this origin explains several features of the text. The chapters are self-contained, because they were separate lectures. They vary considerably in depth: the monetary chapter reflects a lifetime of technical research, while the chapter on discrimination is brisk and underdeveloped. And the tone is the tone of a speaker before a sympathetic but not expert audience — direct, illustrative, confident, and impatient with qualification. The Position in 1962 To understand the book's combativeness one must recall how isolated its position then was. The economics profession in the United States was overwhelmingly Keynesian. Demand management was assumed to work; the Phillips curve was understood as a menu; fiscal fine-tuning was the standard prescription; the postwar system of fixed exchange rates under Bretton Woods was regarded as settled. The idea that monetary policy mattered much at all was a minority view, and Friedman's position — that it mattered enormously and that discretionary management of it had caused the Depression — was regarded as eccentric. More broadly, the intellectual climate held that the extension of government responsibility was both necessary and benign. The New Deal was recent history and widely regarded as a success; the war economy had demonstrated what direction could accomplish; the Soviet Union's growth statistics, taken at face value, suggested that planning might outperform markets in accumulation if not in variety. Samuelson's textbook, discussed elsewhere in this territory, was the settled statement of the consensus. Friedman was, in this context, arguing against nearly everyone. The book was not reviewed in the New York Times, the Herald Tribune, or any comparable outlet, a fact Friedman noted with some asperity in the 1982 preface, contrasting it with the reception of comparable books making the opposite case. It sold steadily rather than spectacularly, and its influence grew over decades rather than months. That trajectory is itself part of the argument the book's admirers make about ideas: that positions dismissed as marginal can become orthodox within a generation if they are correct and persistently argued, and that the intellectual climate at any moment is a poor guide to what will prove durable. It is a fair point, and it cuts both ways — the positions currently dismissed as marginal include a good many that will remain so. The Prefaces Friedman added prefaces in 1982 and 2002, and they are worth reading because they record what he thought had changed. The 1982 preface is triumphant. Written after the inflation of the 1970s had discredited demand management, after the collapse of Bretton Woods had vindicated his position on exchange rates, and at the moment when governments in Britain and the United States were adopting positions he had argued for two decades earlier, it observes that the climate of opinion had shifted decisively and that ideas which had been regarded as extreme were now common currency. Friedman's account of why is the ideas-lead-events thesis: that a crisis produces action, that the actions taken depend on the ideas lying around, and that the function of intellectual argument is to keep alternatives alive until the crisis makes them politically possible. This is one of the most quoted passages in his work and one worth thinking about carefully, since it is a substantive claim about political change and not obviously correct. The 2002 preface is more measured. Friedman notes that while the rhetorical climate had changed enormously, the actual size of government had not shrunk — spending as a share of national income was higher than when the book was published, in the United States and elsewhere. The gap between the victory of the ideas and the persistence of the institutions is a fact that a Friedmanite framework has some difficulty explaining, and to his credit he states it rather than glossing it. The Method, Stated Formally The introduction to this guide identified Friedman's recurring move. It is worth stating it as a procedure, because it is the framework the guide's title refers to and because it can be applied to problems Friedman never considered. Step one: identify the objective. Not the existing programme, but what it is trying to achieve. Educating children. Relieving poverty. Protecting patients from incompetent practitioners. Stabilising the price level. Step two: identify who exercises discretion in the existing arrangement. A school board deciding what is taught and where children attend. A caseworker assessing eligibility. A licensing board deciding who may practise. A central bank committee deciding the money supply. Step three: ask whether the objective can be achieved by a rule or a market instead. Fund the child rather than the school, and let families choose. Transfer cash rather than in-kind benefits, on a formula rather than an assessment. Certify practitioners rather than licensing them, and let patients choose whether to require certification. Fix the growth rate of money by rule rather than by judgement. Step four: check that the substitute achieves the objective. This is where the argument becomes empirical, and it is the step Friedman conducts least thoroughly. Two things should be said about this procedure. It is genuinely powerful, and it generates proposals that are not obvious. The negative income tax and school vouchers are both non-trivial ideas that emerged from applying it, and both have been influential far beyond the movement Friedman belonged to. It also contains an assumption that does a great deal of unexamined work: that the objective can be specified precisely enough to be pursued by rule or market. Where it can, the procedure is compelling. Where the objective is contested, or where its achievement requires judgement about particular cases, the substitution may fail — not because markets are bad but because the thing being sought was not the kind of thing a rule can deliver. Child protection, criminal justice and clinical triage are cases where discretion is not a defect to be engineered away but the point of the exercise. A student applying the framework should therefore run a fifth step: ask whether the discretion being removed was doing necessary work. Friedman rarely asks it, and his critics rarely give him credit for the four steps that precede it. What the Book Is Not Three misidentifications recur. It is not an argument that markets are efficient. Efficiency arguments appear, but they are secondary. The primary case is about power and coercion, and Friedman is explicit that he would favour dispersed arrangements even at some cost in efficiency, because the value at stake is freedom rather than output. Critics who show that a particular market fails have not touched the argument; they have addressed a claim Friedman does not principally make. It is not libertarianism in the natural-rights sense. Friedman rejects the natural-rights framework. His case is consequentialist throughout: these arrangements are better because of what they produce, chiefly the dispersion of power and the preservation of the ability to dissent. He accepts taxation, accepts a substantial list of state functions, and treats the boundary as a matter of judgement about consequences rather than of principle about rights. He described himself as a liberal in the nineteenth-century sense and disliked the label conservative. It is not a defence of business. Friedman is consistently hostile to businessmen who seek protection from competition, to trade associations that restrict entry, and to the corporate demand for subsidy and tariff. His treatment of monopoly is unsparing about how much of it is created by government at business's request. The book's admirers in the business community have generally read it selectively. How the Chapters Fit A last orienting point. The book's chapter order is not the order of its argument, and readers frequently lose the thread as a result. Chapters 1 and 2 state the framework: the relation between economic and political freedom, and the resulting account of what government legitimately does. Everything else is application. Chapters 3 to 5 apply it to money, international arrangements and fiscal policy — the macroeconomic domain, where the enemy is discretion and the remedy is rules. Chapters 6 to 9 apply it to education, discrimination, monopoly and licensure — the microeconomic domain, where the enemy is restriction and the remedy is entry and choice. Chapters 10 to 12 apply it to distribution, welfare and poverty — the distributional domain, where the enemy is paternalism and the remedy is cash. Three domains, one argument, one method. This guide follows that logic rather than the book's numbering, and readers working with the text alongside it should find the correspondence straightforward. Friedman's Standing as an Economist A short account, because the political reputation obscures the technical one and students should know the basis on which he was taken seriously. Friedman's Nobel citation in 1976 named three contributions: consumption analysis, monetary history and theory, and the demonstration of the complexity of stabilisation policy. The permanent income hypothesis, set out in A Theory of the Consumption Function (1957), argued that households consume in relation to their expected long-run income rather than their current receipts, smoothing transitory fluctuations by saving and borrowing. It resolved an empirical puzzle that had defeated the simple Keynesian consumption function, and it substantially reduced the estimated size of the fiscal multiplier, since temporary income changes would be largely saved. This is the technical foundation of the fiscal policy chapter. A Monetary History of the United States, 1867–1960 (1963), with Anna Schwartz, is a work of enormous scholarship and is the basis of the monetary chapter. Its central and most consequential claim is that the Great Depression was not the failure of capitalism it was taken to be but the failure of the Federal Reserve, which permitted the money stock to contract by roughly a third between 1929 and 1933 and thereby converted a recession into a catastrophe. The claim has been contested, refined and partly absorbed; Ben Bernanke's remark at Friedman's ninetieth birthday — that the Federal Reserve had done it, was sorry, and would not do it again — is the standard acknowledgment of its influence. The natural rate hypothesis, argued in his 1967 presidential address to the American Economic Association, predicted that the apparent trade-off between inflation and unemployment would prove unstable because it omitted expectations. The prediction was made before the event and was borne out, which is rare enough in macroeconomics to deserve notice. The methodology essay, "The Methodology of Positive Economics" (1953), argued that theories should be judged by the accuracy of their predictions rather than by the realism of their assumptions. It is among the most cited and most disputed methodological statements in the discipline, and it explains a good deal about how Friedman argued — he was untroubled by unrealistic premises provided the conclusions held up. The point of this catalogue is not to establish authority but to explain why the policy arguments carried the weight they did. Friedman was not a pamphleteer who happened to have opinions about economics. He was among the most important technical economists of the century, and Capitalism and Freedom is the popular statement of positions he had established, or was in the process of establishing, in the journals. CHAPTER 2 Economic Freedom as a Condition of Political Freedom The book's central thesis, and the one everything else depends on. It is stated in the first chapter and it is more carefully formulated than its critics usually allow and less well supported than its defenders usually claim. The Thesis Stated Precisely Friedman's claim has two parts and the distinction between them is essential. Economic freedom is a component of freedom broadly understood. The freedom to enter an occupation, to buy and sell, to hold property, to contract, is itself part of what we mean by liberty, not merely a means to it. Restrictions on it are restrictions on freedom directly, whatever their consequences. Economic freedom is also an indispensable means to political freedom. This is the instrumental claim and the interesting one. Friedman argues that competitive capitalism is a necessary but not sufficient condition of political freedom — that no society has had political freedom without a substantially market-based economy, but that many have had markets without political freedom. The precision matters. Friedman is not claiming that markets produce democracy; he names examples that refute it, and the record since has supplied more. He is claiming that the absence of markets makes political freedom impossible. That is a much narrower claim and correspondingly harder to refute. The Argument from Dispersed Power The reasoning is structural rather than empirical, and it is worth reconstructing carefully because it is the book's best idea. Political freedom requires the possibility of effective opposition. Opposition requires resources: money to print and broadcast, premises to meet in, a livelihood while one campaigns, employers willing to hire people whose views the government dislikes. Now consider who supplies those resources under two arrangements. Under central direction, the state is the employer, the landlord, the printer, the publisher and the banker. A dissident seeking to organise against it must obtain the state's resources to do so, which requires the state's permission. Since the state has no interest in financing its own opposition, the permission will not be given, and opposition is therefore impossible not because it is prohibited but because it cannot be resourced. Friedman's point is that no formal guarantee of free speech can compensate for this: the right to publish is worthless if the only press belongs to the people you wish to criticise. Under a market economy, resources are held by many independent parties. A dissident needs to persuade only one of them — one publisher, one landlord, one employer, one financier. The others' disapproval costs nothing. And crucially, the person who supplies the resources need not agree with the dissident; they need only expect to profit, or be indifferent, or value the money more than the disapproval. Friedman's striking formulation is that the market is impersonal in a way that protects minorities: the buyer of bread does not know whether it was made by a communist or a fascist, and the transaction proceeds regardless. This last point generalises into an argument about tolerance that is genuinely powerful. Market transactions do not require agreement about anything except the terms of the exchange. Political decisions require agreement, or at least the submission of the minority to the majority. So the larger the domain of decision transferred from the market to politics, the more matters on which a society must reach collective agreement, and the more conflict is generated. Friedman puts it as the proposition that the market permits unanimity without conformity, while the political process requires conformity without unanimity. The Illustrations Friedman offers two illustrations, and they are worth examining because one is strong and one is weaker. The Hollywood blacklist. During the McCarthy period, writers accused of communist affiliation were barred from studio employment. Friedman observes that a number continued to work under pseudonyms and through fronts, because studios found it profitable to buy good scripts and the market provided a route around the political proscription. The market, he argues, protected them where the political process had condemned them. The example is genuinely instructive and it is also incomplete, in a way worth noting. The blacklist was itself substantially a private arrangement — studios acting collectively, under political pressure but through market institutions — and its effectiveness came precisely from concentration in the industry. That some evaded it through the market does not establish that the market prevented it; the market both imposed it and leaked. A fair reading is that dispersion helps at the margin and that the degree of concentration determines how much. The financing of radical causes. Friedman argues that in a socialist society, a person wishing to advocate capitalism would have to persuade the state to fund the advocacy, whereas in a capitalist society a person wishing to advocate socialism need only find a wealthy sympathiser or a publisher expecting sales. He notes, correctly, that radical movements in market economies have generally found funding, sometimes from people with no sympathy for their aims. This is the stronger example, and it is close to unanswerable as far as it goes. The asymmetry is real: capitalism finances its critics routinely and comprehensive state control does not finance its own. The Objections Four objections are standard, and a serious reader should be able to state all four and Friedman's best reply to each. Objection one: the historical record does not support the necessity claim as strongly as it appears. Friedman's evidence is that no politically free society has lacked a market economy. But the sample is small and confounded: the societies that developed markets early are also those that developed representative institutions, common law, universities, and a commercial middle class, and disentangling which caused which is not possible from the record. The correlation is real; the direction of causation is not established by it. Friedman's reply is that the structural argument does not depend on the historical correlation. Even if we had no cases, the reasoning about who finances dissent would stand. That reply is fair, and it means the thesis should be assessed as a conceptual claim rather than an empirical generalisation. Objection two: private concentrations of power coerce too. If the danger is that whoever controls resources controls those who need them, then a company town, a monopoly employer, a dominant platform, or a handful of firms controlling the means of publication pose the same structural danger as a state. Friedman's framework identifies the state as the threat and treats private power as self-limiting through competition, which is true where competition exists and not otherwise. Friedman's reply, and it is a real one, is that private power is limited by the availability of alternatives and by the absence of the power to compel — a dominant employer can decline to hire you, but cannot imprison you — and that most durable private monopoly has been created or protected by the state. Both points have force. Neither disposes of the objection where concentration is severe, and Friedman's own chapter on monopoly acknowledges the problem while offering little that constrains it. Objection three: markets without political freedom are common, and the necessity claim survives them only by being weak. Chile under Pinochet, Singapore, South Korea before 1987, contemporary China — all combined substantial market activity with severe political restriction. Friedman anticipated this by making the condition necessary rather than sufficient, so these cases are formally consistent with the thesis. But the frequency with which markets coexist with authoritarian government limits the practical significance of the claim, and it is worth stating that limit plainly. If economic freedom is necessary for political freedom but does very little to produce it, the argument establishes much less than the rhetoric surrounding it implies. The Chile case deserves particular mention because Friedman's own involvement makes it more than a hypothetical. He visited in 1975, met Pinochet, and advised on inflation; a number of his Chicago students held senior economic positions in the regime. He maintained that his advice was technical and that market reforms would ultimately erode the dictatorship — a claim he considered vindicated by the transition to democracy in 1990. Critics maintain that the association lent legitimacy to a government that tortured and killed its opponents, and that a thinker whose central subject is coercion should have been more troubled by it. Students should know the episode and should form their own view; a guide that omitted it would be incomplete. Objection four: the definition of freedom is too narrow. Friedman's freedom is the absence of coercion by others. A person with no resources and no options is, on this definition, free. The capability tradition, associated principally with Amartya Sen, holds that this misdescribes what matters: what makes a person free is the real ability to do and be things, and that ability depends on health, education, and material means. On that account, provision that expands capability expands freedom even where it involves constraint, and the trade-off Friedman poses between economic freedom and social provision is partly a construction of his definition. This is the deepest of the four objections and it is not resolved by either side restating its definition. Friedman's answer is that expanding "freedom" to include capability makes the word useless as a constraint on power, since any coercion can then be justified as expanding someone's freedom. Sen's answer is that a conception of freedom indifferent to whether people can actually do anything is not worth having. Both are serious. What Survives A fair assessment separates three claims of decreasing strength. Strongest: the dispersion argument. That concentrated control of economic resources makes effective political opposition impossible is close to unanswerable, and the record of comprehensively planned economies bears it out without exception. This is a real contribution and it deserves the standing it has. Weaker: the necessity claim. That economic freedom is necessary for political freedom is probably true, defended structurally rather than empirically, and considerably less useful than it sounds — because the necessary condition is satisfied by a wide range of arrangements including many Friedman opposed. Sweden satisfies it. So does France. Weakest: the extension to particular policies. The dispersion argument establishes that a society requires independent centres of economic power. It does not establish that any particular tax rate, regulation, or programme threatens them, and the inference from the general thesis to specific policy conclusions requires additional premises that are frequently not supplied. This is the point at which Friedman's argument does the least work and is invoked the most. A student who can hold those three apart will read the remaining chapters more accurately than most of the book's commentators, in either direction. A Worked Application To see how the thesis generates policy positions, apply it to a case Friedman did not consider: the concentration of digital communication on a small number of platforms. Run the dispersion argument. Political opposition requires the ability to communicate. If the means of communication are controlled by a small number of entities, a dissident must obtain the permission of one of them, and if those entities coordinate — under political pressure, or from shared commercial interest — the permission may be unavailable. The structural condition Friedman identifies as the danger of state control is reproduced by private concentration. Now run Friedman's own replies. Alternatives exist: a person excluded from one platform can use another, or build their own. The barrier to entry is lower than for a printing press in 1962. And the concentration is not backed by coercive power: no platform can imprison anyone. Then run the objections. The alternatives may be much worse — a message that reaches a thousand people rather than a million has not been communicated in any politically relevant sense. Network effects make the barrier to entry far higher than the absence of legal prohibition suggests. And concentration under political pressure reproduces the coordination problem the Hollywood blacklist illustrates. The exercise is instructive because Friedman's framework generates the concern rather than dismissing it. The dispersion argument is not a defence of whoever currently holds economic power; it is an argument that power should be dispersed, and it applies to private concentration as readily as to public. That his own policy conclusions rarely followed this implication is a fair criticism of Friedman, and not a criticism of the argument. A student should take from this that the framework is more useful than the political programme it was attached to, and that applying it consistently produces conclusions Friedman would not have endorsed. That is the normal fate of a good idea. CHAPTER 3 What Government Should Do Friedman's reputation is for wanting government to do very little. The book's second chapter is where he specifies what "very little" means, and the specification is more substantial than the reputation and is the necessary corrective to reading him as an anarchist. Government as Rule-Maker and Umpire The governing metaphor is a game. Players need rules; rules need an interpreter and an enforcer; and neither can be supplied by the players themselves without dispute. Friedman's formulation is that the role of government is to do something the market cannot do for itself — namely, to determine, arbitrate and enforce the rules of the game. Three functions follow immediately and are not contested even by Friedman's more radical successors. Defining property rights. What may be owned, and what ownership entitles the owner to do, are not given by nature; they are legal constructions requiring continual specification. Friedman gives the example of airspace: whether a landowner owns the sky above their property was a question the arrival of aviation forced, and there was no market answer to it. Enforcing contracts and preventing fraud and coercion. Voluntary exchange requires that agreements be enforceable and that neither party be compelled or deceived. Without this the market does not function at all. Maintaining a monetary framework. Money is a social institution, and its supply must be governed somehow. Friedman treats this as unavoidably a public function, which is why his answer is a rule rather than the abolition of the central bank. The Four Grounds for Further Action Beyond the framework functions, Friedman identifies grounds on which additional government activity may be justified. Setting them out plainly is the most useful thing in this chapter. Technical monopoly. Where the technology of an industry makes a single supplier inevitable — a water network, say — Friedman acknowledges that there is no good solution and lists three bad ones: private monopoly, public monopoly, and public regulation of private monopoly. His preference, stated with unusual candour, is for private unregulated monopoly as the least bad, on the reasoning that it is the only one of the three that technological change can eventually dislodge, whereas regulation and public ownership create constituencies that outlive the conditions justifying them. He adds that the preference is contingent and that the case must be made afresh in each instance. Neighbourhood effects. Friedman's term for externalities: circumstances in which the actions of one person impose costs or confer benefits on others in a way that cannot be charged or compensated through the market. He accepts these as a legitimate ground for action and gives examples including pollution, defence, and the general provision of a stable legal order. He is careful, however, to note that neighbourhood effects can justify almost anything if applied loosely, and insists that the argument requires demonstrating both that the effect is substantial and that government action will improve matters — a caution that is the counterpart of the market-failure analysis in any modern textbook. Paternalism toward those who cannot be responsible for themselves. Children and the mentally incapacitated cannot exercise the choice on which the whole framework depends. Friedman accepts that this justifies intervention on their behalf, and is candid that it is a genuine exception to his principle rather than an application of it: there is no way, he writes, to avoid the paternalistic ground entirely, and he finds it the most troublesome part of his own position. The relief of poverty. Treated in the book's later chapters, and discussed in Chapter 9 of this guide, this is justified on a neighbourhood-effects ground: we are all made better off by the alleviation of poverty around us, and since we cannot each purchase the relief individually — the benefit accrues to everyone whether or not they contribute — the market underprovides it. This is a public-goods argument for redistribution, and it is worth noting that it does not depend on any claim about desert or justice. The List of Things Government Should Not Do Friedman's most quoted passage is a list of fourteen activities then undertaken by the American government which he regards as unjustified. It is worth reproducing in substance, because it defines the position concretely. Agricultural price supports. Tariffs and import quotas. Rent control and general price and wage controls. Legal minimum wage rates and maximum prices. Detailed regulation of industries, including transport and banking. Control of radio and television broadcasting. Social security programmes compelling people to purchase retirement annuities. Occupational licensure. Public housing and subsidies to housing construction. Conscription in peacetime. National parks. The legal prohibition on private carriage of mail. Publicly owned and operated toll roads. Two observations about this list. The first is how much of it has since happened. Conscription ended in the United States in 1973, with Friedman serving on the commission that recommended it and describing it as the public policy change he was proudest of. Airline, trucking and rail transport were substantially deregulated in the late 1970s. Broadcasting regulation was relaxed. Price and wage controls were abandoned. Postal monopolies have been eroded in many countries. Whatever one thinks of these changes, the list was not a fantasy. The second is that the items are of very different kinds, and lumping them together is rhetorically effective and analytically sloppy. Agricultural price supports and occupational licensure are restrictions that benefit organised producers at general expense, and the case against them is strong and widely accepted across the political spectrum. National parks and public housing are provisions with plausible neighbourhood-effect justifications that Friedman dismisses briskly. Social security is a compulsory saving programme whose justification rests on the empirical question of whether people under-save and on the political question of whether the state will in practice let the improvident starve — Friedman addresses both, but in a paragraph. The Argument from Decentralisation Beyond the question of what government should do, Friedman argues about which government should do it, and the argument is independent and worth separating. His preference is for the lowest level of government capable of performing a function, and the reasoning is the dispersion argument applied within the public sector. If a policy is set locally, a person who dislikes it can move; the cost of exit is real but bounded. If it is set nationally, exit means emigration. If internationally, there is nowhere to go. So decentralisation preserves a form of choice even over matters that must be decided collectively, and it also permits variation from which everyone learns — different jurisdictions trying different arrangements, with the results visible. He is candid about the counter-argument, which is that some functions cannot be performed locally because their effects spill across boundaries. Pollution that crosses a border, a currency, defence, and the enforcement of civil rights against local majorities are the standard cases, and the last is the one that gave Friedman's position the most difficulty in 1962, when "states' rights" was the constitutional argument used to preserve segregation. His treatment of this in the discrimination chapter is the weakest passage in the book, and Chapter 8 of this guide addresses it. The general principle has since been formalised in the fiscal federalism literature as the subsidiarity principle, and the analytical statement is that a function should be assigned to the smallest unit that internalises its effects. That is a genuinely useful criterion and it is Friedman's argument made precise. Assessing the Framework Three observations for a reader deciding what to make of this chapter. The framework is more permissive than its reputation. Property law, contract enforcement, monetary arrangements, defence, externality correction, provision for children and the incapable, and the relief of poverty constitute a substantial state. A society organised on these principles would have a government considerably larger than a night-watchman and considerably smaller than any actually existing developed economy. The interesting argument is about the gap, not about the principle. The neighbourhood-effects category does more work than Friedman admits. Almost any government activity can be characterised as correcting an externality, and Friedman's insistence that the argument be applied strictly is a matter of judgement rather than of criterion. He offers no test for when an effect is substantial enough to warrant action, which means the category's boundaries are set by the analyst's priors. This is the same difficulty Keynes identified in Hayek's position — that a line must be drawn and no principle is supplied for drawing it — and it is a real one. The comparative institutional test is the framework's strongest feature. Friedman insists throughout that establishing a market failure does not establish a case for intervention, because the relevant comparison is between imperfect markets and imperfect governments. This is correct, it is frequently ignored on both sides, and it is the analytical habit most worth acquiring from the book. Its converse deserves equal emphasis and Friedman applies it less consistently: establishing a government failure does not establish a case for markets either. Worked Application: Assessing a Programme The framework can be applied as a procedure, and doing so is the best way to check comprehension. Take any government activity and ask, in order: Is it a framework function — defining rights, enforcing contracts, preventing fraud or coercion, maintaining a monetary system? If so it is justified without further argument. If not, is there a technical monopoly, a substantial neighbourhood effect, an issue of capacity to choose, or a public-good aspect to poverty relief? If none applies, Friedman's presumption is against. If one applies, does the proposed action actually address it, and does it do so better than the alternatives including doing nothing? This is the comparative institutional test. Could the objective be achieved by a rule or a market mechanism that removes the discretion? If so, prefer that. Is the discretion being removed doing necessary work — is this a case where judgement about particulars is the point? If so, the substitution may fail. Is this the right level of government — the smallest unit that internalises the effects? Six questions. Applied honestly, they generate conclusions that are not uniformly to Friedman's taste, which is a sign that the framework is doing analytical work rather than merely rationalising a position. That is the test of any framework worth learning. Two Cases Friedman Handles Well Conscription. Friedman's opposition to the draft is the clearest illustration of the framework and the proposal he was proudest of. The argument: conscription is a tax in kind, levied on a narrow group selected by lottery, at a rate they cannot pay in money. It conceals its cost, since the budget records only the below-market wages paid rather than the value of what conscripts forgo. It allocates badly, since it takes people regardless of their comparative advantage. And it is coercion of the most direct kind. The alternative is to pay the market wage and let people volunteer. The military obtains people who want to serve; the cost appears honestly in the budget, where voters can weigh it; and nobody is compelled. The standard objection — that a volunteer force draws disproportionately from the poor — Friedman meets by observing that conscription's burden also fell disproportionately on the poor, since the well-connected obtained deferments, and that the objection is really about the distribution of opportunity generally rather than about military recruitment. He served on the President's Commission on an All-Volunteer Armed Force, which reported in 1970; conscription ended in 1973. The postal monopoly. A smaller case, and useful because the reasoning is transparent. The legal prohibition on private carriage of letters is defended as necessary to fund universal service — profitable urban routes cross-subsidise unprofitable rural ones, and competitors would take the profitable routes and leave the losses. Friedman's response is that if universal service is the objective, subsidise it directly and openly rather than by granting a monopoly whose cost is invisible and whose inefficiency is protected. The general form — replace a hidden cross-subsidy with an explicit transfer, and open the activity to competition — recurs throughout the book and is a genuinely useful analytical move. Both cases show the framework at its best: an objective is identified, the existing mechanism is shown to achieve it opaquely and coercively, and an alternative is proposed that achieves it transparently and by choice. Whether one accepts the conclusions, the reasoning is worth being able to reproduce. Hashtags: #TheFreeMarketFramework #CapitalismAndFreedom #MiltonFriedman #RoseFriedman #FreeMarketEconomics #EconomicFreedom #PoliticalFreedom #ClassicalLiberalism #Capitalism #FreeMarketCapitalism #ChicagoSchoolOfEconomics #Monetarism #MonetaryPolicy #FiscalPolicy #EconomicTheory #PoliticalEconomy #LimitedGovernment #GovernmentIntervention #VoluntaryExchange #IndividualLiberty #MarketCompetition #EconomicPolicy #FloatingExchangeRates #SchoolVouchers #NegativeIncomeTax #OccupationalLicensing #Decentralization #HistoryOfEconomicThought #EconomicEducation #StudentStudyGuide

Download the Book (PDF): Introduction: Why a Swedish Airline Book Still Explains the Service Economy In 1985 a Swedish publisher released a slim management book with a title that translated literally as Tear Down the Pyramids. Its author was Jan Carlzon, then forty-four years old, three years into running Scandinavian Airlines System and already something of a national curiosity: a marketing man with an MBA and no engineering background who had been handed one of the country's most technically minded institutions and told to stop the bleeding. Two years later the book appeared in English as Moments of Truth, and the phrase escaped into the language. It has been on PowerPoint slides ever since. Escaping into the language is usually bad for an idea. A concept that everyone can quote becomes a concept nobody has to understand. Ask a room of business students what a moment of truth is and you will get some version of "the point where the customer meets the company," delivered with the mild boredom of a thing that is obviously true and therefore not worth thinking about. That answer is not wrong, but it is close to useless. It reduces a structural argument about how firms should be built to a piece of customer-service sentiment, and it explains why so many organisations can recite Carlzon's phrase while operating in precisely the way he wrote the book to attack. This guide is written to recover the argument. Here is the claim in its sharpest form. Carlzon was not, primarily, writing about customers. He was writing about power — specifically, about where inside a company the authority to make a decision should sit, and what happens to a service organisation when that authority sits in the wrong place. His central observation was arithmetical rather than sentimental. SAS carried roughly ten million passengers a year. Each of them came into contact with approximately five employees. Each contact lasted an average of about fifteen seconds. That gives fifty million encounters per year, each fifteen seconds long, in which the entire reputation of a company employing twenty thousand people was created or destroyed by one person acting alone, usually without supervision, usually without time to ask anyone's permission, and usually in circumstances the rulebook had not anticipated. Once you accept that arithmetic, a series of uncomfortable structural conclusions follow, and Carlzon followed them further than most executives are willing to. If the company is manufactured fifty million times a year by front-line staff in fifteen-second increments, then the organisation's real product is not the aircraft, the seat, or the schedule. It is the quality of fifty million independent judgements. And you cannot improve the quality of fifty million independent judgements by writing more rules, because rules are made centrally in advance and the moments occur peripherally in real time. You can only improve them by changing who is allowed to decide. That is a claim about organisational design, and it is why Moments of Truth belongs on a syllabus alongside work on decentralisation, delegation and organisational structure rather than in the marketing section next to books about smiling. What this guide does, and what it deliberately leaves out The original book is a hybrid. Roughly half of it is organisational theory and half is executive memoir, and the memoir half is bound tightly to a particular moment in commercial aviation: European airline regulation before liberalisation, the growth of business travel in the early 1980s, the specific politics of a carrier jointly owned by three governments, and the specific competitive threat of carriers with lower cost bases. Carlzon writes about aircraft utilisation rates, about a proposed fleet purchase he cancelled, about negotiations with three national civil aviation authorities. This material is genuinely interesting, and a reader who wants the full story should read the original, which is short and well written. It is also, for a student trying to extract transferable theory, a considerable obstacle. The lessons arrive wrapped in an industry that no longer exists in that form, told by a man describing his own victories, in a decade whose management vocabulary has since shifted. Students reading it for the first time reliably make one of two errors. Either they take the aviation detail as the substance and conclude the book is a period piece about airlines, or they take the anecdotes as the theory and conclude that the lesson is "let staff use their initiative," which is a slogan rather than a design. This guide separates the two. It treats the SAS turnaround as a case — evidence to be examined, including its weaknesses — rather than as a narrative to be admired. It states the underlying propositions explicitly, in the vocabulary that organisational behaviour and service management now use, so that you can connect them to the rest of what you are studying. Where Carlzon's claims have been tested by subsequent research, the guide says what that research found, including where it complicates him. Where his framework needs extension to cover circumstances he could not have imagined — self-service, platforms, algorithmic management, conversational systems standing where a person used to stand — the guide extends it. Three things follow from that approach and are worth flagging now. First, this guide takes Carlzon seriously enough to disagree with him in places. Uncritical admiration is not useful to you. The empowerment literature that developed after 1985 established, fairly convincingly, that empowering front-line staff is not universally correct — that there are service contexts in which a tightly scripted, standardised, low-discretion approach produces better outcomes for customers and for workers alike. Carlzon does not concede this, and a strong essay or examination answer will say so and will be able to specify the conditions under which each approach dominates. You will find those conditions set out in Chapter Six. Second, the guide takes the failure modes as seriously as the successes. Most organisations that announce they are inverting the pyramid do not invert it. They announce it, leave the reporting lines, budgets, incentives and information systems exactly as they were, and produce a workforce that has been told it is empowered while discovering daily that it is not — which is measurably worse for morale than never having been told. Understanding why this happens, and where it usually breaks, is more valuable to you than another retelling of the good years at SAS. Chapters Five and Seven are largely about this. Third, the guide is built to be used. Each chapter closes with a short set of takeaways stating what you should be able to do having read it, and the final chapter is a practical method: how to map the moments of truth in any service organisation, how to identify which of them actually matter, how to audit the gap between the authority staff are said to have and the authority they really have, and how to argue about all of this in a way that demonstrates command of the material rather than familiarity with the phrase. The shape of the argument The nine chapters move from definition to structure to evidence to application. The first three establish the concept and the design problem: what precisely a moment of truth is and how it differs from the neighbouring terms students routinely confuse it with; why conventional hierarchy is structurally incapable of managing such moments well; and what "turning the pyramid upside down" actually requires in operational terms, as distinct from what it sounds like. The fourth reads the SAS turnaround as evidence — what the numbers were, what is fairly attributable to the philosophy, what should be attributed to timing and market conditions, and what happened to the airline afterwards, which matters for how confidently anyone should generalise from it. The fifth, sixth and seventh deal with the machinery that determines whether any of this survives contact with a real organisation: the middle managers whose role is transformed and who most often kill the initiative; the informational and cultural preconditions without which delegated authority is simply abandonment; and the problem of failure, recovery, measurement and accountability, where most well-intentioned programmes quietly strangle themselves. The eighth carries the framework into contexts Carlzon never faced, where the front line is a screen, a scheduling algorithm, or a language model, and where the fifteen seconds may involve no human being at all. The ninth turns the whole thing into a method you can apply, and the conclusion asks what remains genuinely unsettled. One reframing before we start If there is a single mental adjustment that makes the rest of this material fall into place, it is this. Stop thinking of a moment of truth as something that happens to an organisation and start thinking of it as something an organisation manufactures. The fifteen seconds at the check-in desk are not an accident of daily life to be managed reactively. They are the output of a long chain of prior decisions: who was hired, what they were told the company is for, what information their screen shows them, what they are allowed to decide without asking, what happens to them if they decide wrongly in good faith, what they are measured on, and whether the person they report to sees their job as enabling that judgement or policing it. By the time the customer arrives, almost everything has already been determined. The employee is not improvising freely; they are performing within an envelope built for them months earlier by people who will never see the encounter. Carlzon's insight, put plainly, is that management's real work happens in building that envelope — and that most managements spend their time instead on decisions the front line could make better and faster, while neglecting the envelope entirely. That is a claim you can test against any service organisation you have ever dealt with, including the ones you have worked for. It is worth holding in mind from here on. Chapter One: The Fifteen Seconds That Are the Company The phrase did not originate with Carlzon. It came into service management from the Swedish consultant and theorist Richard Normann, who used sanningens ögonblick — the moment of truth — in his work on service organisations in the early 1980s and set it out systematically in his book Service Management, published in 1984. Normann borrowed the image from bullfighting, where the moment of truth is the instant the matador commits to the kill: brief, irreversible, and the point at which everything that came before is either vindicated or exposed. Carlzon, who worked with Normann's ideas during the SAS reorganisation, took the term and gave it a company, a number, and a global audience. The borrowed image is worth pausing on, because it carries the two properties that make the concept analytically useful and that students most often lose. The moment is brief, and it is decisive. Everything upstream — the training, the years of preparation, the equipment, the planning — is compressed into a few seconds during which none of it can be revised. That is what separates a moment of truth from a mere interaction. A working definition Let us state it precisely, because loose definitions produce loose analysis. A moment of truth is any episode in which a customer comes into contact with any aspect of an organisation, however remote, and on the basis of that contact forms an impression of the quality of its service. Three features of this definition do real work. "Any aspect, however remote." The moment of truth is not restricted to conversations with staff. A dirty tray table, a form that asks for information the organisation already holds, a hold message that promises a call-back that never comes, an error page — all are moments of truth. This is why the concept belongs to organisational design rather than to interpersonal skills training. Many of an organisation's most damaging moments involve no employee at all, and can only be fixed by someone with authority over systems. "Forms an impression of the quality." The moment is evaluative. The customer is not merely receiving a service; they are drawing a conclusion, and the conclusion generalises. A passenger whose bag is lost does not conclude that the baggage system failed. They conclude that the airline is careless. This generalisation from a fragment to the whole is the mechanism by which fifteen seconds becomes a brand. It is also, from a management point of view, wildly disproportionate: an organisation that gets ten thousand things right and one thing wrong in front of a customer is judged by the one. Contact, not transaction. A single purchase may contain a dozen moments of truth, and most of them will not involve money changing hands. Conversely, months may pass between transactions while moments of truth continue to accumulate — a renewal notice, a service email, an app update that removes a feature someone relied on. The arithmetic that made it famous Carlzon's contribution was to make the concept countable, and the counting is what gave the idea its force in boardrooms. He reasoned as follows. SAS carried approximately ten million passengers a year. Each passenger came into contact with roughly five SAS employees during a journey. Each of those contacts lasted, on average, about fifteen seconds. Ten million multiplied by five gives fifty million contacts. "SAS is 'created' 50 million times a year," he wrote, "15 seconds at a time." The figure is an estimate, and Carlzon presents it as one. Its value is not precision but reframing. Consider what the number does to a chief executive's understanding of their own job. If the company is created fifty million times a year in fifteen-second episodes, then the chief executive personally participates in approximately none of them. Neither does the board. Neither do the vice-presidents. The entire senior structure of the organisation is, on this reckoning, absent from the event that constitutes the company in the customer's mind. Whatever senior management is doing, it is not making the company — it is, at best, shaping the conditions under which twenty thousand other people make it, fifty million times, unsupervised. This is a genuinely disturbing thought for a traditional executive, and it is meant to be. It relocates the site of value creation from the top of the organisation to the periphery, and in doing so it makes the conventional distribution of authority look not merely inefficient but incoherent. Why would you concentrate decision rights in the one part of the organisation that is never present when the decisions matter? It is worth doing this arithmetic for other organisations, because the ratio is often more extreme than at an airline. A retail bank with two million customers, each of whom has perhaps thirty contacts a year across branches, apps, statements and call centres, is created sixty million times a year. A hospital trust, a university, a municipal authority — each can be counted this way, and the count always reveals the same structural fact: the number of moments vastly exceeds the number of decisions any central authority could possibly review. Why "truth" The word matters. What is being tested in these seconds is the gap between what the organisation claims and what it is. Every service organisation makes promises — explicitly in advertising, implicitly through pricing and positioning. The moment of truth is where those promises meet reality in front of the person to whom they were made. This is why moments of truth are so unforgiving of organisational dysfunction. Internal problems that would remain invisible in a manufacturing firm become customer-visible in a service firm almost immediately. If two departments are in conflict, the customer will be the one shuttled between them. If a policy was written to protect the finance function from a rare form of loss, the customer will be the one asked to produce a document nobody can produce. If the front line has been told to reduce average handling time while also being told to build relationships, the customer will experience the contradiction directly, in the form of someone hurrying them off the phone while using warm language. The moment of truth is a diagnostic instrument: it renders internal structure externally visible. What makes services different, and why it matters here Carlzon's argument only works because services have properties that goods do not. Four are conventionally identified in the services literature, and each one intensifies the problem. Intangibility. A service cannot be inspected before consumption. The customer therefore searches for tangible cues to infer quality — the state of the uniform, the confidence of the answer, the cleanliness of the counter. Trivial signals carry heavy inferential weight because there is nothing else to go on. Inseparability. Production and consumption occur simultaneously. There is no interval between manufacture and delivery in which a defect might be caught. The employee is producing the service in front of the person consuming it, which means quality control cannot be a downstream inspection function. It has to be built into the moment itself, which is to say into the person and their authority. Heterogeneity. Every instance is slightly different, because it involves different people on both sides on different days. Standardisation can narrow the variance but cannot eliminate it. This is why the manufacturing instinct — specify the process tightly enough and the output becomes uniform — has limited reach in services, and why organisations that pursue it too far produce staff who are reliably consistent and reliably unable to help. Perishability. The moment cannot be stored, and it cannot be recalled. There is no product recall for a badly handled complaint. What there is instead is recovery, which is a second moment of truth conducted under worse conditions — a topic that occupies Chapter Seven. Take these four together and you arrive at the structural conclusion Carlzon draws: in a service organisation, quality is determined at the point of contact by the person present, in real time, and cannot be determined anywhere else. Every other function in the organisation is upstream of that point and can only influence it indirectly. Distinguishing the concept from its neighbours Students lose marks by using these terms interchangeably. They are related but not identical, and the distinctions are examinable. Touchpoint. A touchpoint is a channel or location of contact — the app, the branch, the call centre, the email. It is a structural category. A moment of truth is an event that occurs at a touchpoint and is evaluated by the customer. One touchpoint hosts many moments of truth, of varying importance. Mapping touchpoints tells you where contact happens; mapping moments of truth tells you where judgement happens. The second is harder and more useful. Service encounter. In the academic literature this usually means a period of direct interaction between a customer and a service firm, and it is often used more or less synonymously with moment of truth. The useful distinction is that "service encounter" is neutral and descriptive, while "moment of truth" carries the evaluative and decisive connotation. Every moment of truth is an encounter; not every encounter is a moment of truth in Normann's demanding sense, because some are so routine that no judgement is formed. Customer experience. This is the aggregate — the cumulative impression built from many moments across time. Moments of truth are its constituent units. The relationship is not additive in any simple way: research on how people evaluate experiences suggests the peak and the ending carry disproportionate weight, which means a small number of moments do most of the work. This has a direct management implication, developed in Chapter Nine: not all moments deserve equal investment, and organisations that try to make every contact excellent typically make none of them distinctive. Critical incident. In the service quality literature this refers to a specific, memorable encounter — usually strongly positive or strongly negative — that customers recall when asked. Critical incident technique is the standard empirical method for identifying which moments of truth actually matter to customers, as opposed to which ones managers assume matter. It is the research counterpart to the concept. Not all moments are equal This point deserves separating out, because Carlzon's rhetoric occasionally implies that every one of the fifty million matters equally, and taken literally that would make the concept useless as a management tool. Fifty million equally important events cannot be prioritised, and management is prioritisation. In practice moments of truth vary along at least three dimensions. Stakes. A routine boarding-pass scan is low-stakes; a conversation about a missed connection that will cause someone to miss a funeral is not. The same fifteen seconds carry different consequences. Ambiguity. Some moments have a correct answer that a rule can specify in advance. Others are genuinely novel, and the employee must construct a response. Discretion is worth its cost only in the second kind. Emotional load. Moments occurring when the customer is anxious, tired, ill, financially stressed or in the middle of a disruption are weighted far more heavily in memory than the same moment in calm conditions. Airlines, hospitals, insurers and banks concentrate a great deal of their reputational risk in these conditions. A well-designed service organisation identifies the moments that are high on these dimensions and organises around them — investing discretion, training and time there, and standardising ruthlessly everywhere else. That combination, rather than uniform empowerment, is what the mature literature recommends. We return to it in Chapter Six. The design implication Everything so far has been definitional, but the definition already carries the design conclusion that the rest of the book unpacks. If quality is created at the periphery, in real time, in circumstances that cannot be fully specified in advance, then the organisation faces a choice with only two coherent answers. Either it removes the need for judgement at the point of contact, by standardising the service so completely that the employee needs no discretion — the industrialised approach, of which the fast-food counter is the classic example. Or it equips the point of contact to exercise judgement well, by transferring authority, information and confidence to the person who is standing there. What it cannot coherently do is the thing most organisations actually do: place employees in situations that demand judgement, then deny them the authority to exercise it. That configuration produces the interaction every customer recognises — a sympathetic, apologetic person explaining that they are not permitted to do the obvious thing, while the customer's regard for the organisation drains away in real time. The employee is humiliated, the customer is angry, and the organisation has paid a wage for the privilege of damaging its own reputation. Carlzon's whole programme is an attempt to eliminate that configuration. The next chapter examines why it is so persistent. The customer is inside the production process One property of services deserves separate treatment because it complicates everything above and because Carlzon, writing about passengers who mostly behave predictably, does not dwell on it. In a service, the customer is not merely the recipient of production. They are an input to it. The patient who cannot describe their symptoms accurately, the passenger who arrives at the gate eight minutes before departure, the client who supplies the wrong documents, the diner who cannot decide — each is participating in the manufacture of the service they are about to evaluate. The French term servuction, coined to describe this, captures the point: production and consumption are not merely simultaneous but entangled. Three consequences follow, and each has a management implication. First, service quality is partly outside the organisation's control, and organisations that measure staff on satisfaction alone are attributing to them outcomes determined by customer behaviour. A branch serving anxious first-time borrowers and a branch serving experienced investors will produce different satisfaction scores with identical staff quality. Second, customers can be trained, and training them is a legitimate design activity. Self-service check-in, wayfinding, form design, expectation-setting before an appointment — all are investments in customer competence, and they have a measurable return. Much of what looks like poor service is a customer performing an unfamiliar role badly because nobody showed them the part. Third, other customers are part of the environment. In a shared service setting — a cabin, a waiting room, a restaurant, a lecture hall — the behaviour of other customers is a component of the experience that the organisation neither produces nor fully controls, but is judged on. Managing the customer mix is therefore a service design decision, and one of the more visible ways in which segmentation, which sounds like a marketing activity, turns out to be an operational one. Two ways customers judge There is a further distinction that matters for how organisations should allocate their attention, and it is one students frequently miss because the literature uses the two ideas interchangeably. Customers evaluate single encounters and they evaluate cumulative relationships, and the two follow different rules. A single encounter is judged in the moment, largely on its own terms, and is heavily influenced by immediate factors: how long the wait was, whether the person seemed to care, whether the outcome was what the customer wanted. This is the level at which most service measurement operates, because it is the level at which a survey can be sent. A cumulative relationship is judged over time and follows the peculiar arithmetic of remembered experience. Research on how people evaluate extended episodes suggests that memory does not average across duration; it weights the most intense moment and the final moment disproportionately, and is surprisingly insensitive to how long the good or bad parts lasted. A flight in which everything was tolerable but the final interaction was humiliating is remembered as a bad flight. A hospital stay that was difficult throughout but ended with a careful, unhurried discharge conversation is remembered better than the sum of its days. The management implication is direct and counterintuitive: endings are worth disproportionate investment, and most service organisations under-invest in them badly. The end of a service episode is typically where attention is lowest, because the transaction is complete and the commercial interest has moved on. Departure from a hotel, discharge from a ward, the final message of a support case, the last day of a contract — these are the moments the customer will remember, and they are routinely the most perfunctory. The same reasoning explains why organisations should be far more worried about a small number of intense negative peaks than about a broad plateau of mediocrity. Mediocrity produces indifference; a peak produces a story, and stories travel. A short exercise Before continuing, it is worth doing Carlzon's arithmetic for an organisation you know well — an employer, a university, a bank you use. Estimate the number of customers or users. Estimate how many distinct contacts each has in a year, counting remote ones: emails, notices, portal logins, invoices, automated messages. Multiply. Then ask two questions. How many of those contacts does the organisation's senior leadership participate in? And how many of them are governed by a rule written by someone who has never observed one taking place? The answers are almost always, respectively, none and nearly all. That gap is the subject of the rest of this book. Takeaways • A moment of truth is any contact, however remote, from which a customer forms a judgement about the organisation's quality — not merely a conversation with staff. • The concept originates with Richard Normann; Carlzon's contribution was to quantify it and draw the structural conclusions. • The intangibility, inseparability, heterogeneity and perishability of services mean quality is determined at the point of contact and cannot be inspected in afterwards. • Distinguish moment of truth from touchpoint (a channel), service encounter (a neutral description) and customer experience (the aggregate). • Moments vary in stakes, ambiguity and emotional load; treating them as equal makes the concept unusable for prioritisation. • The incoherent configuration to avoid is one that demands judgement at the front line while withholding the authority to exercise it. Chapter Two: The Problem the Pyramid Creates The traditional organisational pyramid is not a bad design. It is a very good design for the problem it was built to solve, and understanding what that problem was is the fastest route to understanding why it fails in services. The hierarchical firm, in the form we inherited it, was built to coordinate large numbers of people performing repetitive physical work whose quality could be assessed after the fact. Its logic is that of the factory: decompose the work into specified tasks, assign each to a worker, supervise conformance, and reserve judgement for a managerial layer that can see across the whole. Decisions are made by those with the widest view. Information travels up so that decisions can be made; instructions travel down so that they can be executed. Inspection happens between production and the customer, catching defects before anyone outside sees them. Every element of that design assumes three conditions. First, that there is time — that a decision can wait for information to travel up and an answer to travel back. Second, that the situation is specifiable — that the range of circumstances is known well enough in advance for rules to cover it. Third, that there is a buffer between production and the customer, in which errors can be caught. Service work violates all three, simultaneously. The latency problem Consider the mechanics of what a hierarchy actually does when a front-line employee encounters a situation the rules do not cover. The employee identifies the problem. They cannot resolve it, because resolution requires an exception to policy. They refer it upward — to a supervisor, who may need to consult a manager, who may need to consult a policy owner in a function elsewhere. Each step consumes time and loses information, because each retelling compresses the situation into a category. Eventually a decision returns, and the employee delivers it. In manufacturing this loop is acceptable; the workpiece waits. In services the customer is standing there. The loop's latency is not a background inefficiency but a visible feature of the service itself. The customer experiences the organisation's decision architecture directly, as delay, as being placed on hold, as being told that someone will call back, as watching an employee walk away to ask. Worse, the loop is usually too slow to complete inside the moment at all. The gate closes; the customer leaves; the call ends. What happens in practice is not that the escalation returns a good answer slowly, but that the employee, knowing the loop cannot complete in time, defaults to the safe response — which is refusal. The rule becomes: when in doubt, say no. That is not a failure of individual attitude. It is the rational behaviour of a person whose authority to say yes has been removed and whose authority to say no has not. This is the first structural indictment. A hierarchy does not merely handle exceptions slowly in a service setting; it systematically converts exceptions into refusals. The specification problem The second condition — that circumstances can be specified in advance — fails in services because of heterogeneity. Every customer arrives with a slightly different combination of needs, history, constraints and emotional state. Organisations respond to this by writing more rules. The rule set grows to cover each newly encountered case, and because rules are written by people who were not present at the events they are meant to govern, each one is a compression of a situation into a category. Over time the manual becomes long enough that no employee can hold it, detailed enough that it contradicts itself in places, and still incapable of covering the next unanticipated case, because the space of possible situations is not finite. There is a further and subtler cost. A dense rule set does not merely fail to cover novel cases; it trains employees not to think about them. A worker who has spent two years being corrected for deviating from procedure has learned, correctly, that judgement is punished. When the genuinely novel case arrives — the one where judgement is exactly what is needed — the capacity to exercise it has been eroded. Organisations then conclude that their front-line staff cannot be trusted with discretion, which is true, and fail to notice that they made it true. The inspection problem The third condition is the buffer between production and the customer. In a factory, quality control sits between the line and the loading dock. In a service, there is no such position to occupy. Production and consumption are simultaneous. Inspection can only happen afterwards, by which time the customer has already formed the judgement. This is why quality-assurance functions in service organisations tend to be strange, unhappy things. They review recordings of calls that already happened, score them against criteria, and feed the results back to individuals days later. The activity has real uses — it supports coaching and detects patterns — but it cannot do what inspection does in manufacturing, because there is nothing to reject. The defective unit has already been delivered and consumed. The only intervention point that exists in a service is before the moment: in selection, training, information provision, cultural norms and the allocation of authority. Everything after the moment is analysis. Carlzon's diagnosis at SAS Carlzon arrived at SAS in 1980, becoming chief executive in 1981, and found an organisation losing money — around seventeen million dollars a year — and ranked fourteenth of seventeen European airlines for punctuality. Both numbers matter, and it is the second that reveals the structure. Punctuality is not primarily a capital problem. It is a coordination problem, resolved through thousands of small, fast, local decisions made by ground staff, cabin crew, engineers and dispatchers acting on incomplete information under time pressure. An airline that is fourteenth of seventeen on punctuality is an airline whose local decision-making is bad — not because its people are bad, but because they are not permitted to decide. Carlzon's more fundamental diagnosis was that SAS was organised around the wrong object. It was an airline built to fly aircraft. Its structures, metrics, career paths and prestige hierarchy all centred on aircraft: their utilisation, their technical excellence, their scheduling efficiency. That orientation had a logic — the airline had been founded and run by people who loved aviation, and technical excellence had genuine value — but it meant that the organisation's internal conversation was about a thing the customer did not care about. Passengers do not buy aircraft utilisation. They buy arriving on time, in reasonable comfort, having been treated as though their journey mattered. The literature calls this the difference between a product-oriented and a customer-oriented organisation, and the distinction is not about attitude. It is about what the organisation's information systems, reward systems and status systems are built to optimise. A product-oriented airline knows precisely what each aircraft cost per block hour and cannot say what proportion of its business travellers arrive at meetings on time. It measures what it was built to measure, and it improves what it measures. The wrong reflex Faced with losses, the conventional response is cost reduction across the board — a uniform percentage cut applied to every budget line, which has the political advantage of appearing fair and the practical disadvantage of being indiscriminate. Carlzon's argument, and it is one of the more genuinely transferable pieces of the book, was that indiscriminate cutting in a service business destroys the very capabilities that generate revenue, because in services the "cost" line and the "product" line are frequently the same line. Staff at the check-in desk are a cost. They are also the service. Cut them and you have reduced expenditure and reduced the product simultaneously, in a way a manufacturer cutting overheads does not. The alternative he adopted was selective reallocation: identify the customer segment the airline intended to serve, cut hard on everything that did not serve it, and spend more — deliberately more — on the things that did. SAS cut roughly forty million dollars of activity while investing around forty-five million in improvements aimed at business travellers, ending up spending slightly more in total while spending it on entirely different things. The point was not that the airline spent more. It was that spending was reorganised around a specific customer rather than distributed evenly across an organisation chart. This required something that most cost programmes lack: a stated position on who the customer is. Without that, there is no criterion for distinguishing muscle from fat, and cutting becomes arithmetic. With it, the cuts become decisions. The pyramid's second failure: it hides the customer There is a further problem with hierarchy in services, less discussed than the latency issue but arguably more corrosive. In a conventional pyramid, seniority correlates with distance from the customer. The most junior staff have daily contact; middle managers have occasional contact; senior executives have almost none, apart from the atypical contact they get as high-status customers themselves. Meanwhile authority correlates with seniority in the opposite direction. The result is a systematic inverse relationship between knowing what is actually happening and being allowed to do something about it. This has a predictable consequence: decisions get made on the basis of abstractions. A policy that looks reasonable in a meeting room — requiring proof of purchase, say, or restricting refunds to the originating branch — is designed against an imagined customer with imagined circumstances. The person who could say "in practice this will produce forty furious people a week and here is why" is not in the room, and has no mechanism for getting into it. Carlzon's own remedy was partly informational: he spent an unusual proportion of his time in airports and cabins, and he made the front line's view of reality a legitimate input to senior decisions. But the durable fix is structural rather than personal. If the people who know cannot decide, and the people who decide cannot know, the organisation's intelligence is permanently degraded, regardless of how conscientious the chief executive is about walking the floor. What the pyramid is still good for It is important not to overcorrect, and strong answers on this material always show awareness of the limits of the critique. Hierarchy remains superior for a set of decisions that services genuinely require: capital allocation, safety standards, regulatory compliance, network-level scheduling, pricing architecture, and anything where consistency across the organisation matters more than fit to the individual case. No sensible reading of Carlzon suggests that a gate agent should decide maintenance intervals or that a branch should set its own capital ratios. Airlines are, in fact, among the most rule-bound organisations in existence in the domain where rules belong — flight operations — and this coexists with high discretion in the service domain without contradiction. The argument is not that hierarchy is obsolete. It is that hierarchy has been applied to a class of decisions for which it is structurally unsuited: the fast, local, situation-specific judgements that constitute service quality. The design task is not to abolish the pyramid but to sort decisions correctly — to identify which class each decision belongs to and place it accordingly. Most service organisations have sorted badly, keeping local decisions central out of habit while paying insufficient attention to the central decisions that genuinely need them. That sorting problem is what the next chapter addresses. Three mechanisms that keep the pyramid in place If hierarchy is so poorly matched to service work, why is it so persistent? The answer is not managerial stupidity. It is that several forces actively sustain it, and each has a respectable justification. Risk asymmetry. The cost of a bad decision made by an empowered employee is visible, attributable and immediate. Someone gave away money they should not have; the loss appears in a report with a name attached. The cost of a refusal is invisible, unattributed and delayed: a customer who leaves, tells others, and never appears in any figure the organisation tracks. Faced with one measurable risk and one unmeasurable one, a rational manager controls the measurable. Centralisation is therefore not a preference for control; it is what happens when the accounting system can see one kind of error and not the other. Regulatory accretion. Every regulated industry accumulates rules, and rules accumulate in one direction. A rule is added after an incident; it is almost never removed after a period without one, because nobody is rewarded for removing a control and everybody is exposed if a removed control turns out to have been load-bearing. Over decades this produces an approval structure that no one designed and no one can justify in full, in which some proportion of the requirements exist because of a specific event that nobody currently employed remembers. Professional identity. Managers are trained, promoted and paid on the basis of judgement. A structure that relocates judgement to the front line is not merely an organisational change; it is a devaluation of the thing the manager was selected for. This is a real cost borne by real people, and the fact that it is in the organisation's interest to impose it does not make it easy or costless for those who bear it. Chapter Five takes it up in detail. Recognising these three matters because it changes what an intervention must address. An organisation that announces empowerment without altering how errors are accounted for, without auditing its accumulated approval requirements, and without redefining what managers are rewarded for has left all three mechanisms operating. They will reassert the pyramid within a year, and the reassertion will look like drift rather than resistance. A worked comparison Consider the same situation in two structures. A customer's flight has been cancelled. They have a connection they will now miss and a meeting the next morning. In the centralised structure, the agent can rebook onto the airline's own next available service, which is tomorrow afternoon. Anything else — another carrier, a hotel, a different routing, a refund — requires authorisation. The agent explains this. The customer asks to speak to someone; the supervisor is handling three similar cases. Twenty minutes pass. The supervisor grants a hotel but not the alternative carrier, because the alternative carrier requires a different authority. The customer arrives too late for the meeting. Cost to the airline: one hotel night, twenty minutes of supervisory time, thirty minutes of agent time, and a business traveller who will now default to a competitor. Only the first of these appears in any ledger. In the decentralised structure, the agent can see availability across partner carriers, knows they may spend up to a stated limit to protect a connection, and rebooks the passenger onto another airline within four minutes. Cost: several hundred pounds, visible and attributable, plus a passenger who tells colleagues the story. The four minutes are also worth noticing — the agent is now available for the next customer, which is a capacity effect that no service-quality argument usually bothers to claim. The comparison is deliberately unfair in one respect: sometimes the empowered agent will spend the several hundred pounds on a passenger who would have stayed anyway, or on one who is exaggerating the urgency. That is the real cost of discretion and it should not be waved away. The claim is that across many such cases the aggregate favours the second structure — and, crucially, that the organisation's existing measurement apparatus is constitutionally unable to demonstrate this, because it counts the concession and not the defection. Product orientation as a measurement problem It is worth being more precise about what "product-oriented" means, because the phrase is used loosely and the underlying diagnosis is sharper than it sounds. An organisation's orientation is legible in three artefacts, and none of them is its mission statement. What appears on the management report. If the weekly pack contains asset utilisation, unit cost and volume, and contains nothing about whether customers achieved what they came for, the organisation is product-oriented regardless of its stated values. What gets people promoted. If advancement follows technical or operational achievement and never follows customer outcomes, the ambitious will optimise accordingly, and they will be right to. Which functions have standing. In every organisation some departments can veto and others must persuade. Where operations can overrule service, the orientation is settled. SAS in 1980 scored badly on all three, and Carlzon's interventions can be read as attacks on each: changing the headline metric to punctuality, reorganising units around routes and customers rather than functions, and elevating the standing of the commercial and service side against the technical. The diagnosis is transferable in a way the aviation detail is not — any student can apply these three tests to an organisation they know, and the answers are usually available in an afternoon. Takeaways • Hierarchy assumes time to escalate, specifiable situations, and a buffer between production and the customer. Services violate all three. • Escalation loops that cannot complete inside the moment do not produce slow good answers; they produce refusals, which is rational behaviour for someone given the authority to say no but not to say yes. • Dense rule sets both fail to cover novel cases and erode the capacity for judgement, after which the claim that staff cannot be trusted with discretion becomes self-fulfilling. • Product-oriented organisations optimise what they were built to measure; SAS measured aircraft rather than journeys. • Uniform cost-cutting is especially destructive in services because staff are simultaneously the cost and the product; selective reallocation requires a stated position on who the customer is. • Hierarchy remains correct for decisions requiring consistency, capital or safety. The task is to sort decisions by type, not to abolish structure. Chapter Three: Turning the Pyramid Upside Down The Swedish title of Carlzon's book was an instruction: Riv pyramiderna — tear down the pyramids. The English edition took its title from the concept instead, which was probably better commercially and certainly worse analytically, because it moved attention from the intervention to the phenomenon. What Carlzon actually did at SAS was a structural intervention, and the image he used to describe it — inverting the organisational triangle — is regularly misunderstood in two opposite directions. The first misreading is that inversion means the front line now gives orders to management. It does not; nobody has ever run an organisation that way and Carlzon did not attempt it. The second, more common and more damaging, is that inversion is a metaphor for attitude — that it means managers should be humble and "serve" their teams in a vaguely supportive sense. That reading is comfortable precisely because it requires no structural change, and organisations adopt it enthusiastically for that reason. Inversion means something specific and inconvenient: the point at which a class of decisions is made moves from the centre to the periphery, and the role of everyone above the periphery changes from deciding to enabling. It is a reallocation of decision rights, and it is only real if you can point to decisions that used to require permission and no longer do. The three transfers For that reallocation to work rather than merely to be announced, three things have to move together. Moving one or two produces predictable pathologies, and most failed implementations can be diagnosed by identifying which of the three was withheld. Authority The first and most obvious: the front-line employee must be able to commit the organisation to a course of action within a defined range, without seeking approval. The critical word is range. Unbounded authority is not what is being proposed; nobody suggests a gate agent should be able to charter an aircraft. What is proposed is an explicit envelope — a stated set of decisions the employee may take alone, with the boundaries visible to everyone. Inside the envelope, no permission is required. Outside it, escalation is legitimate and expected. The envelope has to be stated. An unstated envelope is the worst of all configurations, because the employee must guess where the boundary lies, and the rational guess is always conservative. If the consequences of over-reaching are known and the consequences of under-reaching are not, every ambiguous case resolves toward refusal. Organisations that say "use your judgement" without defining limits have transferred risk rather than authority. Information The second transfer is the one most often neglected, and its absence is fatal. A decision requires information: about the customer's history, about the options available, about what the decision costs, about what the organisation is trying to achieve. In a hierarchy, information is gathered peripherally and consumed centrally. If decisions move to the periphery and information does not follow, the employee is now empowered to decide badly. At SAS this meant, concretely, giving front-line staff access to the operational picture — what other flights existed, what seats were available, what the situation actually was — rather than requiring them to ask someone who had the screen. The modern equivalent is unglamorous and expensive: system access, single customer views, real-time visibility of inventory and status, and the removal of the internal information asymmetries that force employees to say "let me check with someone." Note the sequencing implication. Information provision is usually a systems project with a budget and a timeline. Authority delegation is a memo. Organisations that can issue the memo but cannot fund the systems project routinely do the first and postpone the second, and then wonder why the initiative produced worse decisions rather than faster ones. There is a second, less technical dimension. Employees need to know the economics — what a given concession costs, what a lost customer is worth, what the organisation's margins are. Carlzon was unusually willing to share commercial information with staff, on the reasoning that you cannot ask someone to make a commercial judgement while withholding the commercial facts. Most organisations classify this information as sensitive and then express disappointment that staff do not think commercially. Accountability The third transfer is the one organisations find hardest, because it cuts both ways. Accountability without authority is oppression: being held responsible for outcomes you were not permitted to influence. This is the ordinary condition of front-line service work and it is the single largest source of burnout in the sector. Authority without accountability, however, is not empowerment either. It is abdication, and it produces inconsistency that customers experience as unfairness — the same request granted at one branch and refused at another for no reason the customer can see. Perceived arbitrariness is corrosive to trust in a way that consistent strictness is not. Genuine inversion means the employee owns the outcome within their envelope: they decide, and the decision is theirs, and they are answerable for the pattern of their decisions over time. The distinction that makes this workable — and it is the crux of the whole design — is between being answerable for the pattern and being punished for the instance. An organisation that reviews individual decisions and penalises the ones that turned out badly has destroyed the envelope regardless of what its policy says, because employees will observe what happens to colleagues and adjust. An organisation that looks at an employee's decisions in aggregate, over months, and coaches on the pattern, has preserved it. Carlzon's formulation was that a leader must accept that delegating decisions means accepting some wrong ones, and that the cost of those errors is lower than the cost of the refusals avoided. That is an empirical claim, and in most service settings it is correct — but it requires a management culture willing to absorb visible individual errors in exchange for invisible aggregate gains, which is psychologically and politically difficult. What management becomes If the front line decides, what is left for everyone else? This is not a rhetorical question; it is the practical question on which implementations succeed or fail, and Chapter Five is devoted to the layer that feels it most acutely. But the shape of the answer belongs here, because it is what inversion means. In the inverted structure, the work of management is to build and maintain the envelope. Concretely, that consists of: Setting and communicating the objective. If employees are to decide, they need a criterion. "Get business travellers to their meetings on time" is a criterion; it resolves hundreds of ambiguous cases without a rule for each. Carlzon put enormous weight on this, and the point is not motivational. A clear, specific, non-generic objective is a decision-making instrument. Vague objectives ("delight our customers", "be the best") do no such work, because they cannot adjudicate between competing courses of action. Removing obstacles. Much of what prevents good front-line decisions is internal: a system that does not connect, a policy owned by another function, an approval requirement nobody can justify, a metric that punishes the right behaviour. Only someone with cross-functional authority can remove these. In the inverted model this is management's primary operational task, and it means that the flow of problems runs upward rather than the flow of instructions running downward. Resourcing. Ensuring the right number of people, adequately trained, with functioning tools. Under-resourcing quietly cancels empowerment: a person handling too many customers has no capacity to exercise judgement, whatever their authority. Selecting and developing. If judgement is the product, hiring for judgement and developing it becomes the central human-resource question rather than a support activity. Holding the line on the culture. Specifically, protecting employees who made defensible decisions that turned out badly. This is the visible test everyone in the organisation watches, and it is usually decided in the first few months, in one or two cases that become known. The change in the manager's role is severe. A manager who was previously valued for making decisions and controlling exceptions is now valued for enabling others to make them, which means their contribution is largely invisible and hard to measure. It should surprise nobody that this is where resistance concentrates. Delegation is not the same as inversion A distinction worth being precise about, because examiners probe it. Delegation, in the ordinary managerial sense, means a manager passing down a task or decision that remains, in principle, theirs. The authority is on loan. It can be withdrawn, and the manager remains the owner and the accountable party. Delegation is a bilateral act between a manager and a subordinate, and it depends on that manager's disposition. Inversion is structural. The decision belongs to the role, not to the person who lent it. It is specified in the design of the job, it survives a change of manager, and it does not depend on any individual's generosity. That difference determines whether an initiative survives the departure of the executive who launched it — which is the honest test of whether an organisation changed or merely had a good leader for a while. The cost side, stated honestly Inversion is not free, and a guide that presented it as costless would be misleading you. Consistency falls. Distributed decisions vary. Some of that variation is desirable responsiveness; some is noise that customers experience as unfairness. The variance can be narrowed with training and clear criteria but not eliminated. Some decisions will be worse. A front-line employee with fifteen seconds and partial information will sometimes decide worse than a specialist with an hour. The claim is that the aggregate is better, not that every instance is. Direct costs rise before benefits appear. Training, systems access, and the concessions staff now grant are immediate and measurable. The benefits — retention, reduced escalation volume, lower turnover, reputation — are lagged and harder to attribute. Any organisation running a quarterly cost review will see the costs first. Initiatives frequently die in this gap. The wage bill implication is uncomfortable. If the job now requires judgement, the job has been upgraded, and the labour market will eventually notice. Organisations that want empowered service on minimum-wage, high-turnover employment terms are attempting a contradiction. The service businesses that sustain genuine front-line discretion over decades tend to pay above their sector's median and have markedly lower turnover — not coincidentally, but because judgement is a skill that takes tenure to develop and money to retain. That last point is the one most often omitted from executive presentations about empowerment, and it is worth holding onto. Inversion is a labour strategy as much as an organisational one. Chapter Six examines when it is worth paying for and when the industrialised alternative is genuinely better. Specifying an envelope in practice Because the envelope is the operational core of the whole design, it is worth showing what a well-constructed one looks like. A usable envelope specifies five things, and most organisational attempts specify one or two. The domain. Which categories of decision are covered — service recovery, scheduling, fee waivers, exceptions to eligibility. Domains not listed are outside. The limit. A number, or a clear boundary. "Up to two hundred pounds per customer per incident." "Any rebooking within the same day." "Any waiver of a fee under fifty pounds." The absence of a number is what makes most stated envelopes unusable, because it leaves the employee estimating a threshold whose location they will systematically underestimate. The criterion. What the decision should be optimised for. This is what distinguishes judgement from arbitrary generosity: not "do what seems fair" but "resolve it in a way that keeps this customer's plan intact, at the lowest cost that achieves that." The exclusions. What is explicitly outside, and why. Safety, legal obligations, anything that would create a precedent the organisation could not honour at scale. Naming exclusions is what lets the employee treat everything else as inside. The escalation path. Where to go for what falls outside, and — this matters — an expectation that escalation is a normal professional act rather than an admission of inadequacy. Envelopes fail from both directions: employees who escalate everything, and employees who, having absorbed the message that escalation is weakness, decide things they should not. Written out, an envelope for a hotel front desk might read: You may spend up to two hundred pounds per guest, per stay, to resolve a problem, without asking anyone. Optimise for the guest leaving with their plans intact. This does not cover anything involving safety, allegations against staff, or a demand for compensation above the limit, which go to the duty manager immediately. If you use the authority and it turns out badly, we will discuss what you knew at the time, and that is the end of it. That is five sentences, and it does more work than a fifty-page service manual. Its function is to convert an ambiguous situation, in which the safe move is refusal, into a bounded one in which the safe move is resolution. Four failure patterns Implementations fail in recognisable ways, and being able to name them is useful both diagnostically and in examinations. Empowerment as slogan. Authority is announced, nothing structural changes, and staff discover through experience that the announcement was decorative. The distinctive symptom is a workforce that can quote the values statement and cannot name a single decision they may now make that they could not make before. This configuration is worse than the status quo ante, because it adds cynicism to constraint. Empowerment as abandonment. Authority is transferred, information and training are not, and error is punished. Staff are now exposed: expected to decide, unequipped to decide well, and blamed for the results. Turnover rises among exactly the confident, capable people the organisation most needs, because they are the ones with alternatives. Empowerment as inconsistency. Authority and information are transferred; no criterion is supplied. Decisions vary widely and customers compare notes. The organisation, seeing the variance, concludes that empowerment does not work and withdraws it, when what failed was the absence of the vision component. Empowerment as unfunded mandate. Everything is provided except time. Staffing levels assume the old transaction times; the new role requires longer conversations. Employees resolve the contradiction the only way they can, by processing customers at the old rate and using none of the new authority. Each pattern maps to a missing element, which is why the three transfers of this chapter are worth memorising as a diagnostic rather than as a list. Reading the artefacts A final practical note. When assessing whether an organisation has genuinely inverted anything, the documents will not tell you. Four artefacts will. The system permissions. What can a front-line employee actually do in the software? Permissions are the least sentimental record of an organisation's real distribution of authority, because unlike policies they have to be specified exactly. The approval thresholds. At what value does a decision require a signature, and when was that number last changed? Thresholds set a decade ago and never revised are a reliable indicator of an organisation that has stopped thinking about this. The exception log. How many exceptions were escalated last month, and how many were granted? A high escalation volume with a high grant rate means the threshold is set too low and the organisation is spending managerial time rubber-stamping. The induction material. What is a new employee told in their first week about what they may decide? This is where the organisation states its real position, because induction has to be concrete. Takeaways • Inversion means relocating a defined class of decisions from centre to periphery and converting management's role from deciding to enabling — not a change of managerial tone. • Three transfers must move together: authority within a stated envelope, the information needed to use it, and accountability for the pattern of decisions rather than punishment for individual instances. • An unstated envelope transfers risk rather than authority, and rational employees respond by refusing. • Management's work becomes objective-setting, obstacle-removal, resourcing, selection and cultural protection; the objective must be specific enough to adjudicate real cases. • Delegation is bilateral and revocable; inversion is structural and survives a change of manager. Only the second is durable. • The costs are real: reduced consistency, some worse decisions, front-loaded expenditure, and an implied upgrading of the job that has wage consequences. Hashtags: #TheFrontlineRevolution #MomentsOfTruth #JanCarlzon #RichardNormann #ServiceManagement #CustomerService #CustomerExperience #ServiceExcellence #FrontlineEmpowerment #EmployeeEmpowerment #OrganizationalTransformation #OrganizationalDesign #LeadershipDevelopment #ServiceLeadership #CustomerCentricity #InvertedPyramid #DecentralizedDecisionMaking #DecisionMakingAuthority #StrategicLeadership #ServiceQuality #ServiceEncounters #CustomerTouchpoints #CustomerSatisfaction #ServiceRecovery #EmployeeEngagement #OrganizationalCulture #OperationalExcellence #ScandinavianAirlines #BusinessManagement #ManagementEducation