Download the Book (PDF): Introduction The title is a slogan, and slogans are the enemy of a good paper. Taken at face value — people, not technology, are the real key to digital transformation — it says something everyone agrees with and nobody can act on, and taken literally it is not even defensible, since a firm with no technology transforms nothing. A student who writes three thousand words defending that proposition has defended a platitude, and will be marked accordingly. The book is making a sharper claim than its cover suggests, and stating it precisely is the first thing this companion does. The fallacy is a category error about what kind of thing digital maturity is. A technology is an artefact. It can be specified, procured, installed and signed off; a project delivers it, a milestone closes, and somebody can truthfully say the thing is finished. Digital maturity is not an artefact, and it is not even a state. It is a rate — the speed at which an organisation can keep adapting to conditions that keep changing. Everything follows from that distinction. A rate cannot be purchased, because nobody sells one. It cannot be delivered, because there is nothing to hand over. It has no completion date, because the conditions it responds to do not stop changing. And it does not persist: an organisation that stops doing the things which made it adaptive is not adaptive any more, however mature it was last year. That last property is the one firms find hardest, because an asset acquired stays acquired and a rate does not. Organisations make this error for a structural reason rather than a stupid one. They are extremely good at acquiring things — the business case, the procurement process, the project plan, the capital budget, the milestone report and the benefits review are all instruments for acquisition, and they work. None of them can acquire a rate. So a firm that wants to become adaptive instantiates that ambition as a programme, because a programme is the instrument it has, and a programme is precisely the wrong one: it has a scope, a budget and an end, and an adaptive capacity has none of these. The programme then succeeds on its own terms and fails on the question that prompted it, which is an outcome nearly everyone reading this will recognise. Read through that lens, the research findings stop being a list and become a prediction. If maturity is a rate, then the practices associated with it should be ones that raise the speed of adaptation — cheap experiments, work that crosses functional boundaries, decisions taken without escalation, learning that continues — rather than ones that acquire capability, such as spending more, buying better tools or hiring specialists. That is what Gerald Kane, Anh Nguyen Phillips, Jonathan Copulsky and Garth Andrus report, from a multi-year research programme run jointly by MIT Sloan Management Review and Deloitte. The theoretical framing comes first, and the pattern is what it implies, which is why the framing is worth adopting. There is a second reason this companion exists, and it is the one that matters most for a mark. The book draws on information systems, organisational behaviour, sociology of work and human resource management simultaneously, and papers written about it tend to inherit that breadth as incoherence. The characteristic essay opens at the level of industries and disruption, moves to organisational culture, cites something about individual motivation, concludes that leadership is important, and cannot say what evidence would have obliged a different conclusion. It has changed level of analysis three times without noticing, and each level has different units, different constructs, different data and different standards for what counts as an explanation. So the discipline this companion teaches, alongside the content, is focus: choose a level of analysis and treat the others as context; choose one theoretical tradition and meet its standards; define the construct so precisely that it could fail to apply; and state how it would be measured. The final chapter works through this as a method, with the levels set out explicitly and three worked rewrites turning slogan-shaped theses into claims with a named mechanism and an observable prediction. The third commitment is to treat the evidence seriously, which means neither citing it uncritically nor waving it away. This book's authority rests almost entirely on its research base; it is not a theoretical work and does not pretend to be. So Chapter 2 examines the central measure in detail — respondents are asked to imagine an ideal organisation transformed by digital technologies and to rate their own against it on a ten-point scale, then grouped into early, developing and maturing bands. That is a single-item, self-reported, respondent-anchored measure, and each of those three properties has consequences. The anchoring problem is the deepest and least discussed: because each respondent imagines their own ideal, the scale's zero point moves between respondents, and a person in a more advanced firm has probably seen more of what is possible and therefore holds a more demanding ideal. Chapter 9 extends this to the whole design — cross-sectional data, common method variance, single informants, self-selection — and then makes the balancing point that matters: none of this is unusual, most large-scale management survey research shares it, and a student who treats these as disqualifying has misunderstood the standard. They determine how a claim should be worded, not whether the work is worth reading. That chapter gives the wordings explicitly, because this is where over-claiming costs marks. The chapters run from the argument outward. The first names the fallacy precisely. The second examines the construct on which everything empirical depends. The third treats disruption with the precision the word has lost, replacing it where appropriate with the more useful distinction between change that enhances a firm's existing competence and change that destroys it. The fourth deals with culture as the pattern of behaviour an organisation's incentives actually produce rather than as a values statement, using Schein's levels to make the gap between espoused and observed into an analytical instrument. The fifth handles leadership, including an honest account of why follower-perception measures of leadership correlate with performance partly by construction. The sixth takes talent seriously with self-determination theory, job design and the psychological contract, and insists on separating three problems firms conflate. The seventh covers cross-functional work and its real costs. The eighth deals with organisational learning, which is the tradition the book's continuous-learning material belongs to and rarely names. The ninth is the evidence chapter and the tenth the method chapter. A note on what is not here. No percentages, respondent counts or company outcomes appear anywhere in this book, because none could be verified to a source at the time of writing; the authors' findings are described qualitatively and attributed to them. Every theoretical claim carries an author and a year so that the original can be cited rather than this book being cited for someone else's idea. In a companion whose ninth chapter is about how to evaluate empirical claims, inventing a convincing statistic would be a strange way to proceed. One last observation, offered in the spirit of the book's own argument. The reason its central claim is worth holding onto is that it does not depend on the survey at all. That adaptive capacity is a rate rather than an asset follows from what the two words mean and from how organisations are built, and it would remain true if no firm had ever been surveyed. That is unusual in this genre, and it is why the book has outlasted a great deal of writing published alongside it. Chapter 1: Naming the Fallacy Precisely "People, not technology, are the real key to digital transformation." Put that sentence in front of a room of senior managers and you will not find an opponent. Heads move. Nobody objects. Somebody says that it is exactly what they have been arguing for years. Then the meeting moves on to the platform selection, the vendor shortlist and the implementation timeline, and nothing whatsoever has changed. Universal agreement of that kind is a symptom rather than an achievement. A proposition that no one in the room is willing to contest is usually a proposition that carries no instruction: it tells nobody to stop doing anything, to spend money differently, or to hold a different meeting next Tuesday. It is a sentence that costs nothing to believe. Worse, taken at face value the slogan is not even a defensible claim. Technology plainly matters. A firm with no technology transforms nothing; a retailer whose stock data is three days old cannot make decisions at the speed its competitors make them, however admirable its culture; a bank that cannot expose an interface to a partner cannot participate in the partnerships that are reshaping its market, however empowered its staff feel. The authors of The Technology Fallacy are not confused about this. A multi-year research programme run jointly by MIT Sloan Management Review and Deloitte, combining an annual global survey of managers, executives and analysts with executive interviews, is not a programme conducted by people who believe technology is beside the point. Read the title as a literal proposition and you attribute to four serious researchers a position none of them holds. This matters immediately and practically for anyone writing about the book. A paper that sets out to defend the slogan has set out to defend a platitude, and a platitude cannot be defended because it cannot be attacked. The characteristic result is an essay that assembles supportive material for a claim that no evidence could have contradicted, reaches the conclusion it began with, and receives a mediocre mark for reasons the writer finds mystifying. The problem is not effort or reading. The problem is that the thesis was never a thesis. Something sharper is available, and it is what the book is actually arguing, even where the title obscures it. A rate is not an artefact The fallacy is a category error. It is a mistake not about how much technology matters but about what kind of thing the target of a transformation actually is. Consider what a technology is. It is an artefact. It can be specified in a requirements document, costed, put out to tender, procured, delivered, configured, tested against acceptance criteria, signed off and capitalised on a balance sheet. Somebody owns it. Somebody can stand in front of a steering committee and say that it is finished, and be telling the truth. There is a date on which the enterprise resource planning system went live, a date on which the old platform was decommissioned, a moment at which the project closed and the team was disbanded. Artefacts have edges. That is what makes them manageable, and it is why the entire apparatus of corporate governance is comfortable with them. Now consider digital maturity. It is not an artefact, and here is the step most readers miss: it is not even a state. A state would still be reachable. A state could be achieved, entered, and then maintained with modest effort, the way a building once constructed continues to stand. Digital maturity is a rate. It is the speed at which an organisation can keep adapting as the conditions around it keep changing. Not how well adapted it is, which is a snapshot, but how quickly it can become adapted to something it has not yet encountered. The consequences of that distinction do all of the analytical work in this book, and they are worth stating one at a time because each of them dismantles a familiar corporate practice. A rate cannot be purchased. There is no vendor from whom an organisation can buy the capacity to respond quickly, because what is being bought would have to be the behaviour of thousands of people making decisions the vendor will never see. A rate cannot be delivered, because nothing arrives; there is no crate, no licence key, no go-live weekend. A rate has no completion date, so the question "when will we be digitally mature?" is not a hard question with an uncertain answer but a malformed question, like asking at what point a runner has finished being fast. And most importantly, a rate does not persist without the conditions that produce it. An organisation that stops running experiments, stops forming teams across functional boundaries, stops letting decisions settle where the information is, and stops learning is not an adaptive organisation any more. It does not matter how adaptive it was last year. Last year's rate was a property of last year's conditions, and those conditions were dismantled. The fitness comparison is the obvious one and it is broadly honest: an individual can buy the equipment but cannot buy the cardiovascular capacity, and the capacity decays when the training stops. But the comparison understates the organisational case in one important respect. A person's fitness decays slowly and predictably over weeks. An organisation's adaptive rate can be destroyed in an afternoon by a reorganisation that severs the informal channels through which work actually moved, by a cost programme that eliminates the slack experimentation requires, or by a single public punishment of a team whose sanctioned experiment failed. Rates are fragile in a way that assets are not. Nobody accidentally deletes the warehouse. There is a quiet piece of evidence that the authors understand this, and it sits inside their own measurement instrument. The research programme asks respondents to imagine an ideal organisation transformed by digital technologies and capabilities, and to rate their own organisation against that ideal on a ten-point scale. Respondents are then grouped into three bands: early stage, developing, and maturing. Note the third label. Not "mature", which would name a state that has been reached, but "maturing", a present participle naming something still in motion. The instrument's own vocabulary refuses to describe the destination as arrived at. That choice is not decorative, and later chapters will return to what else this measure does and fails to do, because a single-item, self-reported, respondent-anchored scale carries methodological consequences that any serious paper on this book has to confront. Why capable organisations make the error The error is not a failure of intelligence, and treating it as one produces bad analysis. Executives who make this mistake are frequently the same executives who successfully integrated an acquisition, restructured a supply chain, or navigated a regulatory transition. The explanation has to be structural, and it is. Organisations are extraordinarily good at acquiring things. The entire machinery is built for it. A business case exists to justify expenditure against a defined benefit. A procurement process exists to convert a specification into a contract. A project exists to convert a contract into a delivered thing, within a scope, on a schedule. A capital budget exists to allocate money to assets that can be depreciated. A milestone report exists to demonstrate that the thing is arriving on time. A benefits realisation review exists to confirm, some months after the thing arrived, that it did what the business case said it would. Every one of these instruments is a mechanism for acquisition. Collectively they are one of the more impressive achievements of modern management, and they are the reason large organisations can build refineries and merge balance sheets. None of that machinery can acquire a rate. Not one component of it. There is no line in the capital budget for a shorter feedback loop, no acceptance test for a team that decides without escalating, no benefits realisation review that could confirm the organisation has become faster at responding to things nobody predicted. The predictable result follows without anybody behaving foolishly. A firm decides it wants to become adaptive. That ambition must now be turned into something the organisation can act on, and the organisation's rules of legitimacy are unforgiving: to obtain money you need a business case, a business case requires a defined benefit, a defined benefit requires a scope, and a scope requires an end. So the ambition is instantiated as a digital transformation programme, with a director, a budget, a governance board, a roadmap, and a completion date somewhere around thirty months out. This is not a mistake of judgement. It is the only shape in which the ambition could pass through the organisation's own filters. A programme is the instrument the firm has. And a programme is precisely the wrong instrument, for exactly the reasons already given. It has a scope; an adaptive capacity has no scope, because the point of it is to handle what was not in scope. It has a budget; the thing being built is a pattern of daily behaviour that is not funded from a budget line but from how people spend their ordinary week. It has an end; a rate has no end, and when the programme closes, the conditions it temporarily created, the cross-functional teams, the permission to experiment, the shortened approval chains, are dismantled along with it, because they were project resources and the project is over. This produces the outcome that puzzles everyone involved. The programme can succeed on its own terms and fail on the real question. The systems went in. The milestones were hit. The benefits were signed off. And the organisation is no faster than it was before, because speed was never what was delivered. In the worse cases the programme actively consumed the slack that adaptation requires, since running it absorbed precisely the senior attention, the discretionary time and the tolerance for disruption that experimentation needs. That mismatch between instrument and object, rather than any deficit of will, understanding or commitment, is what the book's title is pointing at. The fallacy is not believing in technology. It is reaching for an acquisition process to obtain something that is not acquirable. The wizard, the curtain and the shape of the argument If maturity is a rate, the practices associated with it are predictable before anyone looks at the data. They should be practices that raise the speed of adaptation: the ability to run cheap experiments and find out quickly which ones fail, the ability to assemble teams across functional boundaries without a reorganisation, the ability to make decisions at the point where the relevant knowledge sits rather than escalating them to a level where the knowledge has been summarised away, and the habit of continuous learning that keeps individual capability moving as fast as the environment. They should not be practices that acquire capability: spending more, buying better tools, hiring specialists. Those raise the stock. They do nothing directly to the rate, and a purchased specialist inserted into an organisation that escalates every decision will simply escalate more expensively. This is exactly the pattern the authors report from their research. The maturing organisations are distinguished by how they work rather than by what they own. The point to hold onto is the order of the reasoning. The prediction comes first. If the finding is encountered as a list of admirable behaviours, it reads as one more set of best practices, and best practices are infinitely extensible and mutually contradictory. If it is encountered as the consequence of a framing, it is doing theoretical work: this is what a rate account of maturity implies, and the data are consistent with the implication. That is the reason to adopt the framing rather than the slogan. It generates predictions the slogan cannot generate, and predictions are what make a paper falsifiable. The intellectual lineage is respectable here too, since the tension the framing describes is recognisably the one James March set out in 1991 between exploration and exploitation, and the capacity being described has a good deal in common with what Wesley Cohen and Daniel Levinthal called absorptive capacity in 1990. The authors reach for the Wizard of Oz to make a related point, and the metaphor deserves better than the dismissal it usually receives. It is worth taking seriously. The great and terrible Oz presents as an overwhelming force, all booming voice and smoke and fire, and the correct response to an overwhelming force is either submission or flight. Behind the curtain there is a man operating a machine. Crucially, the story does not conclude that the threat was imaginary or that nothing was at stake; Dorothy's problems are entirely real and the machine genuinely works. What changes is the category of the thing being faced. It is a mechanism operated by people, and mechanisms can be understood. What this buys analytically is a relocation of the central question. "What will the technology do to the firm?" is unanswerable, because it depends on which technologies emerge, in what sequence, adopted by whom, at what cost, under what regulation. It is also a question that positions the firm as an object to which things happen, and the natural posture it induces is fatalism dressed up as realism, the executive who explains that the sector is being disrupted in the same tone he might use to describe weather. "How does this firm navigate a changing environment?" is answerable. It is a question about the firm's own conduct, over which the firm has authority, and every element of the answer is something someone can decide to do differently on Monday. The metaphor converts a forecasting problem, which cannot be solved, into a capability problem, which can. Nobody can predict which technology will matter. Anybody can ask how quickly their organisation would notice and respond if one did. The book is organised in three parts, and the ordering is not arbitrary. The first part treats the phenomenon of digital disruption itself and how companies should adapt to a changing environment. The second works through what digital maturity implies for leadership, talent and the future of work. The third sets out the conditions organisations need to create in order to adapt successfully. That sequence is diagnosis, implication, prescription: what is happening, what it means for the people inside the firm, and what must therefore be built. The third part carries most of the book's practical weight, since it is where the conditions are named. The second carries most of its academic interest, because that is where the book's constructs run into established literatures on leadership, motivation, job design and the employment relationship, and where its claims are therefore most contestable and most worth a student's attention. The focus problem There is a second reason this companion exists, and it has nothing to do with the book's argument and everything to do with what happens when students write about it. The Technology Fallacy draws simultaneously on information systems, organisational behaviour, sociology and human resource management. For a general management readership this breadth is a virtue; the book covers the territory a practitioner actually inhabits. For a student writing an assessed paper it is a trap, because a paper written about the book tends to inherit the breadth as incoherence. Three failures recur, and they are worth naming in advance so they can be recognised in one's own draft. The first is mixing levels of analysis. An argument begins with an individual's attitude to a new system, moves to how a team coordinates, slides to a firm-level capability, and finishes with a claim about industry structure, with causal arrows running silently between all four. Each of those is a legitimate object of study, and the inferential rules connecting them are not automatic. The second is borrowing constructs from traditions with incompatible standards of evidence. A paper will invoke the technology acceptance model, a variance-based, survey-measured, individual-level tradition following Fred Davis in 1989, in the same paragraph as Edgar Schein's interpretive, organisation-level account of culture from 1985, and treat the two as though they were making commensurable claims about the same world. They are not, and the sentence that joins them is doing no work. The third, which usually follows from the first two, is arriving at a conclusion that nothing in the paper could have falsified. If no imaginable finding would have led to a different last paragraph, the paper has described rather than argued. The discipline the rest of this companion teaches is narrow and can be stated in four moves. Pick a level of analysis and stay on it, or state explicitly how you are crossing between levels and why the crossing is warranted. Pick one theoretical tradition and accept its standards of evidence rather than borrowing whichever construct is locally convenient. Define the construct precisely enough that a reader could disagree with the definition. And say how it would be measured, in terms specific enough that someone could go and do it. The source text makes this unusually practicable, because its own central measure is stated plainly and is therefore available for examination: a single-item, self-reported, respondent-anchored rating against an imagined ideal. Whether such a measure can carry the weight the book places on it is a genuine question, and a genuine question is exactly what a paper needs. The fallacy, then, is not a belief about technology at all. It is the treatment of an ongoing capacity as a one-off acquisition, and it is committed most reliably by organisations that are extremely competent at acquisition. Once that is seen clearly, the recommendations in the book's third part stop looking like a collection of soft cultural preferences and start looking like what they are. Distributed decision rights, cross-functional teams, cheap experimentation, continuous learning: none of these are pleasant working conditions offered to staff as a benefit. Each is a piece of machinery for producing a rate, deliberately constructed because an organisation built for acquisition does not possess such machinery naturally and will not grow it by accident. The book is an argument about how to build an institution capable of changing continuously, addressed to institutions that were designed to change once. Questions for analysis 1. The chapter argues that the slogan "people, not technology, are the key to digital transformation" is indefensible when taken literally, yet the book bearing that title is a serious piece of research. Reconstruct the authors' actual claim in a single sentence that a reader could disagree with, and explain what evidence would count against it. 2. Distinguish an artefact, a state and a rate as candidate answers to the question "what kind of thing is digital maturity?". Which of the three consequences of the rate framing (non-purchasability, absence of a completion date, non-persistence without supporting conditions) does the most damage to conventional transformation governance, and why? 3. The chapter insists that organisations instantiate adaptive ambitions as programmes for structural rather than cognitive reasons. Set out that structural argument in your own terms, then assess it: is there any organisational instrument, existing or imaginable, that could fund and govern a capacity without converting it into an acquisition? 4. The rate framing predicts which practices will be associated with maturity before any data are examined. Explain why the order of that reasoning matters for the strength of an argument, and what is lost when the same findings are presented as a list of best practices instead. 5. Identify a claim from the book that operates at the individual level and one that operates at the organisational level. What would have to be true for the first to license the second, and how would you state a research design that tested the connection rather than assuming it? Chapter 2: Digital Maturity as a Construct The question that produces the book's central variable is worth quoting in substance, because almost everything that follows depends on it. Respondents are asked to imagine an ideal organisation transformed by digital technologies and capabilities, and then to rate their own organisation against that imagined ideal on a ten-point scale. Those who place their organisation low on the scale are classed as early stage; those in the middle band as developing; those at the top as maturing. Every comparison in the MIT Sloan Management Review and Deloitte research programme - between cultures, between leadership qualities, between talent outcomes, between attitudes to experimentation - is a comparison between those three groups. The entire empirical structure rests on one question and the three buckets its answers are sorted into. This is a single-item, self-reported, respondent-anchored measure. Each of those three properties is a design decision, each carries a cost, and the costs are not the same kind of thing. Single-item measurement is a reliability question with a large and mostly reassuring methodological literature behind it. Self-report is a bias question with well-catalogued mechanisms and well-known remedies. Respondent anchoring is something stranger: a property that makes the scale itself vary between the people using it, and one that the standard methods literature does not have a clean solution for. A student who can distinguish these three problems from one another, and say which is serious for which kind of claim, is already doing better methodological work than most of what is written about this research. There are two failure modes to avoid, and they are mirror images. The first is to cite the findings as though the bands were an objective classification - to write that maturing organisations retain talent better, full stop, as if maturity were a measured property like headcount or revenue. The second is to notice the word "self-reported" and dismiss the whole programme as opinion polling. Both are lazy. The measure is not an objective classification, and it is also not noise. It is a particular kind of evidence, with a particular reach, and the productive task is to work out exactly how far that reach extends. That is not a concession made reluctantly at the end of a paper. It is the analytical work itself, and in an assessed piece it is where the marks are. It helps to be clear about what the measure is for. The authors are not certifying organisations; they are sorting a large and varied global sample into rough strata so that the strata can be compared on everything else the survey reports. For that purpose a coarse instrument may be adequate. Whether it is adequate depends on what the construct underneath it is like - and, as the rest of this chapter argues, the construct is unusually awkward, because the book defines digital maturity as an ongoing process of adaptation while the survey measures it as a position at a moment. One item, and what it is being asked to carry The objection to single-item measures is procedural and real. With one item there is no internal consistency to assess: no Cronbach's alpha, no inter-item correlations, no way of showing that several indicators converge on a common underlying factor. The apparatus that Campbell and Fiske set out in 1959 for demonstrating convergent and discriminant validity - showing that a measure agrees with other measures of the same thing and diverges from measures of different things - has nothing to work with inside the instrument. Measurement error cannot be partitioned out, so it stays in the estimate and attenuates observed relationships. And a single item cannot capture a multidimensional construct: if digital maturity has separable components, one number flattens them into an average that may describe no actual organisation. The defence is also real, and a paper that omits it is not being rigorous, only sceptical. A substantial body of measurement research finds that for global, holistic judgements, a single well-worded item performs comparably to a multi-item scale. Overall job satisfaction is the classic case; global self-rated health is another. The logic is that when the thing being assessed is genuinely a summary judgement - the respondent's overall sense of a whole - asking for that summary directly is not a degraded version of asking twenty questions and averaging. It may be a more direct route to the same quantity. And there is a practical argument that carries real weight in survey design: every additional item costs respondent attention, and in a long instrument administered annually to busy managers across many countries, spending fifteen items on the classification variable means fifteen fewer items on everything the classification is meant to explain. Instrument length degrades data quality through fatigue and satisficing. A single item buys accuracy elsewhere. So the honest position is conditional. A single item is a defensible choice for a broad construct and a poor one for a precise construct. If digital maturity is a gestalt - the respondent's overall impression of how far their organisation has travelled - then one item is a reasonable instrument and the objection is largely procedural. If digital maturity is a compound of distinguishable capabilities that can move independently, such that a firm might be advanced in decision rights and primitive in data infrastructure, then one number conceals exactly the variation that matters, and two firms with identical scores may have nothing in common. Which of these digital maturity is turns out to be the substantive question of the book, not a technical aside. The book's own argument leans towards the gestalt reading: it insists that maturity is not a stack of capabilities but a way of operating, an organisation-wide rate of adaptation that shows up across functions at once. If that is right, a holistic self-assessment is a defensible probe of it. But the same argument cuts the other way when the findings are used, because a gestalt measure cannot then be read back as though it decomposed into the specific practices the book recommends. You cannot measure the whole and then report on the parts. The moving anchor The deepest problem with the measure is the one almost never raised, and it follows directly from the wording. The respondent is not rated against a fixed standard. They are asked to construct the standard themselves - to imagine an ideal digitally transformed organisation - and then to say how far their own organisation falls short of the thing they have just imagined. The anchor is supplied by the respondent, and it varies between respondents. Consider two firms that are, by any external description, identical: same sector, same systems, same decision structures, same analytical capability. In one, the respondent's mental picture of an ideal digital organisation is drawn from a mid-market competitor that has recently automated its order processing. In the other, the respondent has spent time inside a firm where product teams ship continuously and pricing adjusts in real time, and that is the picture they hold. The first respondent rates their organisation high. The second rates the identical organisation low. The difference in scores records nothing about the firms and everything about the two imaginations. Worse, the variation is unlikely to be random. A respondent's ideal is probably more ambitious in an organisation that is already more advanced, precisely because working in such a place exposes you to more of what is possible. Sophistication raises aspiration. If that holds, the anchor drifts upward with the very thing the scale is trying to measure, and the two movements partly cancel: advanced firms are rated against sterner ideals, early-stage firms against modest ones, and the observed spread between them is narrower than the real spread. In the limit, if aspiration rises faster than capability, the correlation could invert, and the most advanced organisations could report themselves furthest from their ideal. Nothing in the design rules this out. That possibility has an interesting implication. If the anchor moves with the respondent, then what the item measures may not be a position on any common scale at all. It may be the gap between an organisation and its own aspiration - a measure of felt shortfall rather than of achieved capability. That is not a worthless quantity; it may well be a good predictor of restlessness, of appetite for change, of the sense that there is further to go. But it is a different construct from the one the bands are named after, and findings interpreted under the two readings mean different things. Under the standard reading, maturing organisations have better cultures. Under the gap reading, organisations whose members feel close to their own ideal also describe their cultures favourably - which is a considerably less surprising claim. This problem has no clean fix inside the existing design. Objective anchors would require external benchmarking the survey does not do. Vignette anchoring, in which respondents first rate fixed hypothetical cases to calibrate their scale use, would help and is not part of the instrument. Stating the problem plainly, and saying which of the two readings a particular finding can bear, is the available move - and it is exactly the kind of methodological awareness that separates a strong paper from a competent one. Examiners notice a student who can identify an unresolved problem in a published research design and reason about its likely direction, rather than reciting a list of generic limitations. The same voice on both sides The maturity score and most of the outcomes come from the same person, answering the same instrument, in the same sitting. The respondent who places their organisation at eight out of ten also tells the survey that its culture is collaborative, that its leaders are digitally fluent, that it attracts and keeps good people, and that it performs well. Podsakoff and colleagues set out the consequences of this arrangement comprehensively in 2003: when predictor and criterion share a method, some portion of the observed relationship between them is produced by the method rather than by the world. The mechanisms are worth naming in plain language, because "common method variance" as a phrase is often deployed without content. Consistency motifs: people want their answers to hang together, and having just described their organisation as advanced, they are under mild pressure to describe it as well-led. Implicit theories: respondents carry lay causal beliefs, and someone who believes that adaptive firms have strong cultures will report both in line with that belief, generating a correlation that exists in their head before it exists in their firm. General affect: someone who feels positively about their employer, for reasons that may have nothing to do with digital anything, rates every item on the instrument a little higher, manufacturing correlations across the whole battery. Add scale-format effects and the priming produced by item order, and the inflation is not a marginal concern. The standard remedies are well established. Temporal separation - measuring predictor and outcome weeks or months apart - breaks the consistency motif and the momentary affect. Different sources - maturity from the executive, retention from HR records, performance from financial statements - break the shared-respondent link entirely and are the strongest remedy available. Procedural protections such as guaranteed anonymity and counterbalanced item order reduce, without eliminating, the pressure to look consistent. Statistical diagnostics, including marker variables, attempt to estimate how much is left. The honest account of this design is that it uses some of these and not the most powerful ones. Anonymity is present and matters. The survey draws on multiple respondent types across many organisations, so the sample is not a single homogeneous group. Executive interviews run alongside the survey and give a second kind of evidence, though a qualitative and non-independent one. What the design does not do is separate predictor and outcome in time or in source, and it does not report marker-variable diagnostics. That does not mean the associations are fictitious. It means their magnitude is an upper bound, and any reported difference between bands should be read as the largest the true difference could plausibly be. Two further features of the sample cut in the same direction and deserve evenhanded treatment. Respondents to a voluntary survey about digital business are not a random draw from the world's managers. They are people interested enough in the subject to answer a long questionnaire about it, which tilts the sample towards the engaged, the technically literate, and organisations where the topic is live. And they are describing organisations they belong to, whose digital efforts they may personally have led. Both pressures point the same way: towards flattering descriptions, both of the organisation's progress and of the conditions around it. Social desirability here is not mainly about deceiving the researcher; it is about how people describe work they are part of and invested in. None of this invalidates the research, and a paper that concludes otherwise has misunderstood the design. The comparisons of interest are internal - between groups within the same sample, answering the same instrument under the same pressures. If every respondent inflates, and inflation is roughly constant across bands, differences between bands survive. The risk is specifically that inflation is not constant, which brings the anchoring problem back: the respondents most likely to hold demanding ideals are also, plausibly, those least likely to flatter. What the measure will bear The practical payoff is a clear statement of reach. This measure supports claims of the form: organisations whose respondents describe them as more adapted to a digital environment also describe, on the same instrument, different cultures, different leadership, different talent outcomes and different attitudes to risk than organisations whose respondents do not. That is a real finding about a large and varied sample, and it is not trivial - the pattern is consistent, it recurs across years of the survey, and it holds across sectors and geographies. It does not support three things students routinely claim from it. It does not support the claim that maturity causes performance, since the data are cross-sectional and the causal arrow could as easily run from a healthy culture to a confident self-assessment, or from profitability to both. It does not support claims about movement, since a firm that appears in a later survey in a higher band may have changed, or may have a different respondent with a different imagination. And it does not support the claim that the bands correspond to any externally verifiable state; no auditor could confirm that a given firm is "maturing", because the category exists only relative to a private standard. Table 1 sets out each property of the measure against the reason for it, what it does to inference, and the form of words a careful paper should use. Table 1. Properties of the digital maturity measure and their consequences. Property of the measure Why it was chosen Consequence for inference What a careful paper should say Single item Low respondent burden; suits a holistic judgement No internal-consistency check; dimensions hidden Treat as a global impression, not a capability audit Self-reported No external data on most firms; scale of sample Desirability and affect inflate levels Read levels as perceptions; compare, do not certify Respondent-anchored ideal Allows one item to span sectors and sizes Anchor varies and may rise with capability Differences may be compressed; possibly a gap measure Cross-sectional Annual survey design; broad coverage No direction of causation; no within-firm change Report association, never effect Same respondent for outcomes Single instrument, single sitting Common method variance inflates correlations Treat differences as an upper bound Voluntary sample Practical recruitment for a global survey Engaged, topic-interested respondents over-represented Restrict claims to within-sample comparisons These limits are not fatal, and they are not a reason to avoid the material. They determine wording, and wording is where students over-claim. Compare two sentences. "Digital maturity improves employee retention" is unsupportable: it asserts causation, treats maturity as a measured property, and generalises beyond the sample. "In the MIT Sloan Management Review and Deloitte survey, respondents who placed their organisations closer to their imagined digital ideal also reported a stronger intention to stay with their employers; because both measures come from the same respondent at the same moment, the association cannot establish direction and its size is likely inflated by common method variance" is fully supportable, and is not much longer. The second sentence also does more work: it tells the reader what kind of evidence is on the table, which is the beginning of an argument rather than the end of one. Maturity models as a genre invite a further round of criticism, most of it deserved. Their stages are typically asserted rather than derived - named from consulting experience and then applied, rather than recovered from data. They imply a single developmental path, as though every organisation must pass through the same sequence towards the same endpoint, which fits neither the variety of industries nor the evidence that firms take different routes. And they ask organisations to assess themselves against the model's own categories, so the model tends to confirm its own structure: a firm told that maturity means cross-functional teams will report on cross-functional teams. This particular construct escapes part of the charge, and the escape is worth crediting because it is unusual in the literature. Because the authors frame digital maturity as an ongoing process of adaptation rather than as an achieved end state, the model does not carry the usual implication that maturity is a destination with a finishing line. "Maturing" is deliberately a participle. Most models in this field promise arrival; this one explicitly denies that arrival is available, which is both more honest and more consistent with what organisations actually experience. That denial, though, is exactly where the sharpest criticism of the research becomes available - and it is a criticism a good paper can build on rather than merely assert. If maturity is a rate, an ongoing capacity to keep adapting as conditions keep changing, then a rate is what should be measured. A single question answered at one moment cannot capture a rate; it captures a level, or more precisely a perceived distance from an imagined point. Measuring a speed from one snapshot is not a technical oversight that better survey administration would fix. It is a real difficulty, and no available instrument solves it cleanly. The conceptual claim and the empirical practice pull against each other, and everything the research reports about maturing organisations is therefore a description of firms that feel far along, offered as evidence about firms that move fast. Those may well be the same firms. The design cannot show that they are - which is precisely the space in which a student with a longitudinal design, an external anchor, or a second data source has something new to contribute. Questions for analysis 1. Under what conditions is a single-item measure defensible, and does digital maturity as the authors define it meet those conditions? Argue the case both ways before deciding. 2. If respondents in more advanced organisations hold more demanding ideals, what happens to the observed differences between the three maturity bands? Work through the likely direction and magnitude of the distortion. 3. The chapter suggests the item may measure the gap between an organisation and its own aspiration rather than its position on a common scale. Take one reported finding from the research programme and restate it under each reading. How do the two versions differ in what they would license a manager to do? 4. Which of the three common method variance mechanisms - consistency motifs, implicit theories, general affect - is most likely to be operating in this survey, and why? What evidence would distinguish between them? 5. Design a study that tests one of the book's central associations while breaking the shared-respondent link. Specify your predictor source, your outcome source, and the temporal separation, and state honestly what your design would still be unable to show. 6. The construct is framed as an ongoing process rather than an end state, but is measured at a single point in time. Is this an inconsistency that undermines the research programme, or an unavoidable compromise? Defend your answer with reference to what a rate would require to measure. Chapter 3: Disruption, Carefully Somewhere between 1997 and the present, disruption stopped being a hypothesis and became a mood. It is now applied to a competitor cutting prices, a regulator changing a rule, a new sales channel, a shift in generational taste, a supply shock, and to any development at all that makes an established firm's year harder than it expected. A word that covers every one of those covers nothing. It has no content left to test, no prediction attached to it, and no way of being wrong — which is exactly the property that makes a term useless in an assessed piece of analysis, however well it performs in a boardroom. This matters for a companion to a book with digital disruption among its core concepts. The source text uses the phrase in its broad, popular sense: the arrival of a new competitive environment shaped by digital technologies, and the question of how organisations navigate it. That is a legitimate thing to write about. But a student who carries the popular sense of the word into a paper marked by someone who knows the strategy literature will be read as making a claim about mechanism, and will then be asked to support a claim they never intended to make. The required discipline is therefore small and entirely practical: know which version of the word you are using, and say so. The mechanism, and the things mistaken for it Clayton Christensen's argument in The Innovator's Dilemma (1997) is not a general observation that incumbents sometimes lose. It is a specific mechanism with specific moving parts, and the parts are what make it interesting. An entrant begins by serving a segment the incumbent does not want — smaller, less profitable, less demanding on the performance dimensions the incumbent's main customers care about. The incumbent notices, evaluates, and declines, and the evaluation is correct. Its best customers want more of what they already buy, its margins are higher in the segments it already serves, and its resource allocation process directs investment towards the highest-return opportunities available to it. Every step of this is competent management. Meanwhile the entrant improves along its own trajectory, and because technological improvement in a given product line tends to run faster than the rate at which mainstream customers' requirements rise, the entrant's performance eventually crosses the threshold that mainstream customers need. At that point the incumbent's customers begin to defect, and the incumbent cannot simply follow them down, because its cost structure, its channels, its margin expectations and its organisational attention are all built around the segment it is losing. The crucial feature — the one that gets dropped every time the word is used loosely — is that the incumbent's failure follows from good management rather than bad. That is why Christensen called it a dilemma rather than a cautionary tale. If the incumbent had been lazy, complacent or badly run, there would be no puzzle and no theory; there would only be the ordinary observation that badly run firms do worse than well run ones. The whole argument rests on the claim that doing the textbook thing — listening to your best customers, investing where returns are highest, protecting your margins — produces the failure. The disk-drive evidence that anchors the book was chosen precisely because product generations there turned over fast enough to observe the cycle repeat. This gives the term diagnostic value, which is what an analytical term is for. Three questions test whether an event is disruption in this sense. Was the entrant initially worse on the dimensions mainstream customers valued? Did the incumbent see it and decline to pursue it for reasons that were defensible given its existing business? Did the entrant's improvement trajectory subsequently overtake mainstream requirements rather than the entrant simply winning on the original terms? Most events described as disruption fail at least one of these tests, usually the first. An entrant that arrives better, cheaper and immediately preferred by mainstream customers is not disrupting anyone; it is competing, and winning. An incumbent that saw a threat clearly, understood it, and failed to respond because its leadership would not authorise the investment is not the subject of Christensen's theory either; it is the subject of a much older and less interesting one about organisational inertia. Neither case is less important than disruption. They simply have different causes, different evidence and different remedies, and collapsing them into one word destroys the distinctions that make analysis possible. The practical instruction for a student is therefore blunt. Either use the term precisely, and show the mechanism operating in your case, or use a different term. Entry, substitution, displacement, commoditisation, disintermediation and environmental change are all available, all narrower, and all easier to defend. Reaching for the more dramatic word costs marks rather than earning them, because the examiner will read it as a claim and find it unsupported. Competence-enhancing and competence-destroying change For what the source text actually describes, there is a better frame, and it is the single most useful analytical instrument available for the job. Michael Tushman and Philip Anderson, writing on technological discontinuities and organisational environments (1986), describe technological change as proceeding through long periods of incremental improvement punctuated by discontinuities — sharp breaks that reset the terms on which firms compete. The valuable part of their argument is not the punctuation. It is the distinction they draw between two kinds of break, which turns on the relationship between the new technology and the accumulated capability of established firms. A competence-enhancing discontinuity raises performance while leaving the existing firms' accumulated capability intact and still valuable. The new thing builds on what incumbents already know how to do, so incumbents tend to be strengthened by it, and industry leaders tend to remain leaders. A competence-destroying discontinuity renders that accumulated capability worthless. The knowledge, the tooling, the supplier relationships, the training systems and the hard-won expertise of the established firms stop being assets and become, at best, irrelevant. Incumbents then fail not because they were slow, not because they failed to notice, and not because they were badly led, but because what they were good at stopped mattering. Speed of response is beside the point when the thing you would be responding with has lost its value. The reason this frame beats the disruption frame for most student work is that it asks a question you can actually answer with evidence. Name the firm's core competence — specifically, not as a slogan. Ask whether the new technology raises or nullifies the value of that competence. You can support the answer with descriptions of what the capability consists of, who holds it, how long it took to build and what it is used for. Whereas "was this disruption?" usually degenerates into an argument about whether the incumbent lost badly enough to qualify. Apply the distinction to the digital case and an honest complication appears immediately. Most digital change, in most industries, has been competence-enhancing for firms that adapted. A retailer's knowledge of buying, category management, credit, logistics and property did not become worthless when selling moved partly online; it became more valuable, because the new channel needed all of it and the firms that already had it were better placed than the entrants who did not. The same is true across banking, industrial manufacturing, insurance, healthcare provision and professional services. The technology changed how the capability was deployed without destroying the capability itself. Where digital change has been genuinely competence-destroying, it has typically destroyed competence at the level of a function rather than a firm — a display advertising sales operation, a branch counter network, a physical distribution intermediary, a typesetting department, a class of clerical processing work. Those destructions are real and severe for the people in them. But they sit inside firms whose other capabilities remained intact, which is precisely why so many whole-industry disruption narratives overstate. The unit of analysis for competence destruction is usually the function or the occupation; the unit of analysis in the narrative is the industry; and the mismatch is where the exaggeration enters. A student can put this to work directly. "Digital technology disrupted industry X" is a claim most undergraduates cannot support and should not attempt. "Digital technology destroyed the value of competence Y within firms in industry X, while leaving competences Z and W enhanced" is a claim that can be evidenced, and it is more interesting besides. It also explains something the source text cares about a great deal. When competence destruction is functional rather than firm-wide, the people whose expertise is being written off are inside the organisation, are frequently senior, and are frequently the ones asked to authorise the change. Their resistance is not ignorance or fear of technology. It is a rational response to a correct perception of what the change does to the value of what they know. Two rates, not one The pace argument in the source text is easy to misread as the usual assertion that everything is faster now, and it deserves better treatment than that, because the authors' actual position is sharper and considerably more defensible. The claim is not that technology changes faster than ever in some absolute sense. That claim is hard to operationalise — faster by what measure, against what baseline? — and has been made with equal conviction in every industrial generation since the railway. The claim is about a gap: the rate at which technology changes has pulled away from the rate at which organisations can absorb it. The environment may or may not be accelerating in absolute terms; what matters is that it is moving faster than the institutions inside it can reconfigure themselves. Three things make this the better framing. First, it locates the problem in a relationship rather than in technology alone. A gap is a ratio between two quantities, and both quantities can be investigated. "Everything is faster now" is an atmosphere; "adoption outpaces absorption in this firm, by this much, for these reasons" is a research question. Second, it is consistent with evidence that the simpler story cannot accommodate. Erik Brynjolfsson's account of the productivity paradox (1993) confronted the awkward fact that very large investments in information technology had produced strikingly little in the way of measured productivity gain. If technology did the work on its own, the effect would be prompt: install, measure, observe. The long lag between investment and return is not a measurement curiosity to be explained away. It is direct evidence that something between the technology and the outcome takes years, and that something is organisational absorption. Third, and most usefully, it relocates the actionable variable. No firm can slow the environment. Every firm can, in principle, change its own absorption rate. A theory that puts all the causal weight on external speed leaves managers with nothing to do but brace; a theory about the gap points straight at the side of it they control. Why is absorption so slow? Paul Milgrom and John Roberts, writing on complementarities, supply the mechanism. Two elements of a system are complementary when doing more of one raises the return to doing more of the other. Technology in organisations is almost never a standalone element; its return depends on complementary changes in process design, decision rights, job design, skills, measurement and incentive structures. Adopt the technology alone and you have paid its full cost and collected a fraction of its value — and performance can genuinely fall, because the new tool sits badly against the old process and the old process still governs. Getting the return requires moving a whole configuration of mutually reinforcing practices from one arrangement to another, and configurations cannot be moved one element at a time without passing through a trough where the old fit has been broken and the new one has not yet been made. That trough takes years, and the years are not waste. They are the work. Absorptive capacity and the things that must stop Wesley Cohen and Daniel Levinthal's account of absorptive capacity (1990) is the formal treatment of why some organisations absorb faster than others. They define the capacity as the ability to recognise the value of new external information, assimilate it, and apply it to commercial ends — and they argue it is largely a function of prior related knowledge. You understand what you already have the equipment to understand. The consequence is that absorptive capacity is cumulative and path dependent. It is built by having been engaged with a domain, and it cannot be assembled on demand. A firm that has not been absorbing cannot suddenly start, because the first step — recognising which of the many developments in front of it actually matter — requires exactly the knowledge that only prior absorption produces. Such a firm does not fail to act on the signal; it fails to see that there is a signal. It learns which developments mattered at the point where they have become obvious to everyone, which is the point at which knowing is worth nothing. The uncomfortable implication should be stated plainly, because it cuts against most of what is written about adaptation. The firms best placed to adapt are the ones that have already been adapting. This is a mechanism for divergence, not convergence. It predicts that the distance between adaptive and non-adaptive firms widens over time rather than closing, and that the widening accelerates, since each period of absorption raises the capacity to absorb in the next. It also predicts that the standard remedy — a large one-off investment by a firm that has done little — will underperform, because the money buys the technology and not the recognition. This is a genuinely testable proposition, and it is a far more precise version of what the source text's maturity bands gesture at than the bands themselves provide. What, then, does adaptation actually consist of, stated as capacities rather than as encouragement? Four things, each of which can be absent independently. Scanning the environment, which requires somebody whose job it is to look, with time protected from operational load — scanning that belongs to everybody belongs to nobody and does not happen. Deciding, which requires that authority to act sits at the level where the signal was seen, since a signal that must climb three levels to reach someone empowered to respond arrives degraded, attributed to the wrong person, and late. Reallocating, which means moving money, people and attention out of current uses and into new ones. And absorbing, which means having the capability to use what has been adopted, procurement being the beginning of absorption rather than a substitute for it. Most organisations are weakest at the third, and this is the specific bottleneck that most limits adaptive rate. Starting things is politically cheap: a new initiative creates a sponsor, a budget line and a story. Stopping things is politically expensive, because every existing activity has an owner, a headcount, a history, an internal constituency and often a customer who likes it. Budget processes are incremental and start from last year. Initiatives are launched with objectives but almost never with termination criteria, so nothing ever fails clearly enough to be killed. The result is accumulation, and accumulation is not neutral. Everything that continues consumes the capacity that adaptation requires — not chiefly money, but management attention and the time of the people capable of doing new work, who are invariably the same people already doing the existing work. A firm's adaptive rate is therefore set, more than by anything else, by its rate of stopping. A firm that cannot stop things has a ceiling on what it can absorb no matter what it spends. This is where the source text's Wizard of Oz metaphor earns its place, and it is worth taking seriously rather than treating as decoration. A narrative in which technology is an overwhelming external force arriving to reshape an industry removes agency from the firms in that industry — and, with the agency, the accountability of the people managing them. That is an extremely convenient piece of storytelling. "The environment did it" is the most comfortable explanation available to anyone who allocated resources badly for a decade, and it has the additional advantage of being unfalsifiable, since the environment did in fact change. Treating the environment as something to be navigated rather than something that happens to you is both more accurate and more useful, and it carries a direct analytical consequence: the interesting variance is between firms in the same environment, not between environments. If technology were doing the causal work, firms facing the same technology would show similar outcomes. They visibly do not. Whatever explains the difference is therefore inside the firm, which is also the correct design for a study — hold the environment constant, compare the organisations. Which brings the argument back to where the book's real claim lives. If the problem is a gap between two rates, the environment's and the organisation's, then the only side of that gap a firm can act on is its own. And a rate is not a thing that can be bought. The technology on the far side of the gap can be acquired in an afternoon, by anyone, at a published price, which is precisely why acquiring it confers no advantage. The gap is on your side of the transaction, and nothing in the catalogue closes it. Questions for analysis 1. Take an industry change commonly described as digital disruption and test it against the three diagnostic questions drawn from Christensen's mechanism: was the entrant initially inferior on the dimensions mainstream customers valued, did the incumbent decline it for defensible reasons, and did the entrant's trajectory subsequently overtake mainstream requirements? On the evidence available to you, does the case qualify, and if not, which term describes it more accurately? 2. Using Tushman and Anderson's distinction, identify one specific competence within an organisation you can research, and argue whether digital change has been competence-enhancing or competence-destroying for it. Explain why the answer might differ at the level of the function and at the level of the firm, and what this implies about industry-level disruption claims. 3. The chapter argues that the gap between the rate of technological change and the rate of organisational absorption is a better framing than absolute acceleration. Construct the case against this framing: what evidence would show that absolute speed, rather than the gap, is the operative variable, and how would you distinguish the two empirically? 4. Cohen and Levinthal's account of absorptive capacity predicts divergence between adaptive and non-adaptive firms rather than convergence. What observations would be inconsistent with that prediction, and what does the prediction imply about the likely returns to a large one-off technology investment by a firm with little prior absorption? 5. Of the four capacities described — scanning, deciding, reallocating and absorbing — the chapter claims reallocation is the binding constraint because organisations are poor at stopping things. Evaluate that claim: what would count as evidence that stopping, rather than seeing or deciding, is the true bottleneck in a particular organisation, and how could it be measured? Hashtags: #TheHumanAlgorithm #TheTechnologyFallacy #DigitalTransformation #DigitalMaturity #AdaptiveCapacity #OrganizationalAdaptation #ContinuousLearning #DigitalDisruption #AbsorptiveCapacity #ExplorationAndExploitation #CrossFunctionalTeams #DistributedDecisionRights #CheapExperimentation #OrganizationalLearning #CompetenceEnhancingChange #CompetenceDestroyingChange #OrganizationalAbsorption #TechnologyAdoption #Complementarities #DigitalCulture #DigitalLeadership #TalentAndWorkDesign #OrganizationalAgility #ContinuousAdaptation #FutureOfDigitalMaturity

Download the Book (PDF): Introduction There is a particular kind of confusion that sets in about three weeks into a strategic information systems module. The reading has been done. The textbook has been opened, and it turns out to contain a great many matrices, a great many acronyms, and case studies about companies that were in trouble at various points over the last forty years. Somewhere in the middle of all of it there is a triangle with three words at its corners, and the lecturer has said several times that it is the most important thing in the course. And the honest question forming in the back of the room is: important how? It is three words and three lines. What exactly is it supposed to do? That question deserves a better answer than most courses give it, and answering it properly is what this book is for. The Information Systems Strategy Triangle is a claim, not a picture. The claim is that an organisation's business strategy, its organisational strategy and its information systems strategy are not three separate plans that happen to be written by the same company. They are a single interdependent system. Move one and the other two must move in compensation, or the organisation goes out of balance — and the symptoms of that imbalance will show up somewhere else entirely, usually in a place that looks like a technology problem and is not one. A system that nobody uses. A strategy that was announced and then quietly stopped being mentioned. A market the company could not enter because its core platform was thirty years old and nobody said so out loud. Taught that way, the triangle stops being a diagram to memorise and becomes an instrument. It is a device for converting a vague complaint — our IT is failing us, the transformation isn't landing, the new system was a disaster — into a specific, answerable question about which vertex moved and which one did not follow. That conversion is the whole trick, and it is worth more in an examination, and considerably more in a career, than the ability to reproduce the drawing. The textbook this guide accompanies, Managing and Using Information Systems: A Strategic Approach, has been the standard text on this subject through many editions for good reason. Keri Pearlson, Carol Saunders and Dennis Galletta built it around the triangle and then ran the consequences of that choice through every topic a general manager encounters: strategy, the design of work, architecture, funding, governance, sourcing, projects, security, analytics and ethics. The book is thorough, and its thoroughness is precisely the problem for a student working to a deadline. The controlling idea is stated clearly in the first chapter and then has to survive twelve more chapters of detail, dozens of cases, and a vocabulary of several hundred terms. What tends to happen is that students learn the parts and lose the argument. They can list the five forces and define total cost of ownership and name three sourcing models, and then, faced with a case study and a two-hour exam, they produce a description of the company rather than an analysis of it. This guide is organised the other way round. Every chapter here exists to serve one controlling idea, and that idea is the triangle read as a diagnostic instrument. The first chapter establishes the claim and the three ways a triangle goes out of balance. The next three take each vertex in turn and give it the treatment it needs: what a business strategy actually is and how to read one from a case; what organisational strategy means and why it is the vertex students consistently under-weight; and what an information systems strategy contains, as distinct from a list of technologies somebody would like to buy. Chapter five takes on the question the whole subject circles — whether information technology can create competitive advantage at all, and for how long — and gives Nicholas Carr's famous argument that it cannot a fair hearing before answering it. The second half moves from the analytical to the managerial. Chapter six follows the translation chain from strategy through architecture to infrastructure, and shows how legacy systems run constraints back up that chain to limit which strategies are even available. Chapter seven treats the IS organisation as a business that has to be funded, budgeted and justified, and takes seriously the question of why IT value is so notoriously hard to measure. Chapter eight is about governance, which is to say about decision rights: who gets to decide what, who is consulted, and who carries the accountability when it goes wrong. Chapter nine covers the two decisions that consume most of a chief information officer's working life — where capability is bought from, and how change is actually delivered — and examines why information systems projects fail at rates that would end careers in any other engineering discipline. Chapter ten is the one to read twice. It converts everything preceding it into a repeatable procedure: an ordered method for analysing any case, demonstrated end to end on a worked example, followed by the architecture of a strong essay and, importantly, the serious intellectual criticisms of the alignment model itself. That last section matters more than it might appear. The difference between a competent answer and an excellent one, in this subject, is almost never the amount of material recalled. It is whether the student can use a framework and simultaneously see its limits — whether they notice that the triangle assumes a stable and knowable business strategy, that in a digital-native firm the vertices may not be separable at all because the product is the information system, and that a perfectly aligned organisation may simply be perfectly aligned to a strategy that is dying. A word on how to use this book. It is not a substitute for the textbook and does not pretend to be one; it is a companion that supplies the structure the textbook assumes you will build for yourself. Read it straight through once, early, so that the shape of the subject is clear before the detail arrives. Then return to individual chapters as the module reaches them. Each chapter ends with a section on what examiners actually reward in that area, including specimen questions written out in full, and those sections are worth working through with a pen rather than skimming. The six tables scattered through the book are compression devices for material that is genuinely comparative — generic strategies, funding models, governance archetypes, sourcing options — and they are there to be reproduced from memory as revision aids. Throughout, the examples are real and named. Zara, Ryanair, Walmart, Lidl, Blockbuster, Kodak, Amazon, the UK's National Programme for IT: these are the cases that recur in examination papers and in seminar discussion, and it is more useful to know four of them properly than twenty of them vaguely. Where a fictional organisation appears, in the worked case in the final chapter, it is labelled as such, because the habit of inventing convenient evidence is exactly the habit this subject should train out of you. One last framing, which is the reason this material is worth the effort beyond the assessment. Almost everyone reading this will, within a decade, sit in a meeting where a substantial sum of money is about to be committed to a system, and where the discussion is being conducted entirely in the vocabulary of the technology. The question that will not have been asked is what has to change about the way people work for the investment to produce anything, and who is accountable for making that change happen. Knowing to ask it is what this subject is actually teaching. The triangle is just the shortest way of remembering to. Chapter 1. The Triangle as an Instrument A student meets the Information Systems Strategy Triangle for the first time as a drawing: three words at three corners, three lines between them. It takes about four seconds to copy into a notebook and roughly the same to forget. That is the wrong encounter. The triangle is not a picture of anything; it is a claim about how organisations fail, and it is precise enough to be tested against evidence. Learn it as a claim and it becomes an instrument you can pick up in an exam hall, in a case study, or in the third week of a graduate job when somebody senior says the new system "isn't delivering" and nobody can say why. Three vertices and a single claim The three vertices are business strategy, organisational strategy and information systems strategy. Each deserves a chapter of its own, and each gets one later in this book. What matters at this stage is only what each vertex covers, at the level of a definition you could give in a sentence. Business strategy is the set of choices that determine where an organisation competes and on what basis it expects to win. It answers the questions of which customers, which markets, which products and services, and what it is about the offer that makes a customer choose it rather than the obvious alternative. A business strategy is meaningful only to the extent that it excludes things: a strategy that permits every possible action is a mission statement wearing a disguise. Ryanair's strategy excludes connecting passengers, allocated comfort, and any notion that the base fare should cover the whole journey. That exclusion is what makes it a strategy. Organisational strategy is the set of choices about how work is arranged so that the business strategy can actually be executed. It covers structure and reporting lines, who decides what, how performance is measured and rewarded, which skills are hired or developed, and the harder-to-name matters of culture and norms that determine what people do when no rule applies. It is the design of work. When a firm says it has become "customer-centric" but still pays its sales force on units shifted this quarter, its organisational strategy has told the truth and its business strategy has not. Information systems strategy is the set of choices about the information capability the organisation will have: what systems it will run, who will use them and who will own them, where they will sit, how much will be spent on them, and in what sequence they will arrive. It is emphatically not a list of technologies. A genuine IS strategy is a plan for a capability, expressed in terms that a chief executive can argue with. The triangle's central claim is that these three are not three separate plans that happen to be produced by the same organisation. They are a single interdependent system. Move any one vertex and the other two must move in compensation, or the organisation goes out of balance. This is a stronger statement than it first appears, and it cuts in every direction. It is not merely that information systems must support the business strategy — that much is the conventional wisdom and it is only a third of the claim. It is equally that a change in information systems will force a change in the design of work whether anyone planned for it or not, and that a change in either information systems or organisational design can alter what business strategies are available to the firm at all. Zara is the standard illustration of the three vertices in coherence, and it earns the status. The business strategy is to sell fashion that responds to what is selling this week rather than what a designer predicted last season, at prices that make frequent purchase reasonable. The organisational strategy puts unusual authority in the hands of store managers, who report what customers are asking for and picking up and putting down, and keeps design, sampling and a substantial share of manufacturing close enough to be redirected within days. The information systems strategy supplies the fast, granular, store-level flow of sales and inventory data that makes the short cycle possible, and the logistics systems that move small, frequent consignments rather than large seasonal ones. Remove any one of the three and the other two stop making sense. Give a conventional retailer Zara's systems and it will produce excellent reports about a supply chain it cannot turn. Give Zara's organisational design to a firm with quarterly buying cycles and you have empowered a group of store managers to shout into a void. It follows that alignment is not a state that can be reached and then maintained by vigilance. Every vertex is under continuous pressure from outside. Competitors move, which changes the business strategy. Labour markets and regulation change, which changes organisational design. Technology changes on a cycle nobody in the firm controls, which changes what the IS vertex could be. Alignment is therefore a condition, like the balance of a walking person, rather than an achievement, like the summit of a hill. A walking person is never in balance and never out of it; they are continuously falling forward and continuously correcting. Organisations that appear well aligned are not those that got the answer right in a planning exercise three years ago. They are those whose correction cycle is short. The model behind the model The triangle is a teaching compression of a more careful piece of work: the strategic alignment model developed by John Henderson and N. Venkatraman in the early 1990s. Knowing the original is worth a good deal in an examination, because it lets you say what the triangle leaves out, which is the difference between a student who has memorised a diagram and one who understands a literature. Henderson and Venkatraman work with four domains rather than three. On the business side they distinguish business strategy from organisational infrastructure and processes. On the technology side they make the same distinction, separating information technology strategy — the firm's positioning in the external technology marketplace, its choices about scope, competences and governance of technology — from the internal IS infrastructure and processes, meaning the architecture, the systems that exist, the skills and the ways of working that deliver them. The four domains are then related along two dimensions. Strategic fit is the vertical relationship between what is decided about the outside world and what is built inside the firm to deliver it. Functional integration is the horizontal relationship between the business domains and the technology domains. The model's most useful contribution is its insistence that alignment can be driven from any corner. Henderson and Venkatraman set out several alignment perspectives, each defined by which domain is the anchor and which is to be changed. In one, business strategy drives organisational design, which in turn dictates what the IS infrastructure must be — the classic case, and the only one most students can describe. In another, business strategy drives IT strategy, which then reshapes the internal IS infrastructure, bypassing organisational design as the intermediate step. In a third, an emerging IT strategy makes new business strategies possible, and the business strategy is revised to exploit them. The perspectives differ in what is taken as fixed and what is treated as the outcome, and a firm may be operating under one of them without ever having chosen it. The triangle drops the internal-external distinction, collapses four domains into three vertices, and drops the named perspectives. What it gains in exchange is usability under pressure. Four domains with two orthogonal dimensions and several directional perspectives is a model you can teach but not use in a meeting; three vertices and a claim of mutual dependence is a question you can put to a chief operating officer in twenty seconds and get a revealing answer to. The compression is honest as long as you remember two things it hides. First, the vertices in the triangle are drawn as equals and the lines have no arrows, which is a deliberate refusal to say which vertex leads; the original model makes the direction of drive an explicit variable, and in analysis you should always say which way the causation is running in the case in front of you. Second, the IS vertex is doing the work of two of Henderson and Venkatraman's domains at once, which is why so many student answers slide between "the firm should adopt a cloud-first posture" and "the firm should replace its warehouse management system" as though these were the same kind of statement. They are not, and Chapters 4 and 6 separate them properly. Three signatures of a triangle out of balance Misalignment is not a vague condition. It presents in three recognisable forms, distinguished by which vertex moved first and which failed to follow, and each has its own symptom set and its own corrective move, as Table 1 sets out. Learning to tell them apart is the single most practically useful thing in this chapter, because the three require completely different responses and are routinely mistaken for one another. Table 1. The three signatures of a triangle out of balance. Signature What changed first How it looks from the business side Corrective move Strategy announced, systems unmoved Business strategy New direction declared, then nothing happens; timelines slip without explanation; the old business continues under a new name Fund and sequence the IS and organisational changes the strategy implies, or revise the strategy to what the capability allows System installed, work unchanged Information systems Go-live "succeeds" but benefits never appear; workarounds, shadow spreadsheets, duplicate data entry; users blamed for resistance Redesign roles, decision rights, incentives and measures around the new process; treat adoption as the deliverable, not the go-live Technology leading, strategy following Information systems Product and market choices quietly constrained by what the systems allow; "the system can't do that" becomes a strategic answer Make the direction of drive explicit: either adopt the technology-led strategy deliberately or reclaim the constraint as a decision The first signature is the announced strategy that changes nothing. A new direction is set at board level, communicated with conviction, and then absorbed without trace by an organisation whose information systems continue to support the previous strategy perfectly well. Blockbuster is the standard case. By the middle of the 2000s its leadership had identified the threat accurately and articulated a credible answer: abolish the late fees that customers resented, and combine the store network with a postal and eventually digital service so that a customer could return a disc in a shop and receive the next one by mail. What it required was a single view of a customer's account, inventory and entitlement across thousands of stores and an online channel, running as one system rather than two. The capability was never built at the necessary speed or coherence, and the organisational structure — a store network with franchised outlets whose economics depended on the very fees the strategy abolished — was not rebuilt around it either. The strategy was announced, the other two vertices stayed where they were, and the announcement turned out to be the whole of it. The diagnostic value here is that the symptom is not an IT symptom at all. Nobody reports a system failure. What is reported is unexplained slippage: initiatives that are always about to start, pilots that never scale, and a growing gap between the language used about the company externally and the work being done inside it. The corrective move is genuinely binary and should be stated as such in an essay. Either the organisation funds and sequences the systems and organisational changes the strategy implies, accepting the cost and the time, or it revises the strategy down to what its capability can actually deliver. The one thing it must not do is continue to announce a strategy it has not resourced, because that is how an organisation teaches its own staff that strategy is theatre. The second signature is the reverse: the system arrives and the organisation does not move. This is the most common failure in practice and the one most often misclassified as a technology problem. Lidl's long attempt to replace its inventory and merchandise management systems with an SAP-based platform is an unusually clear example, abandoned publicly in 2018 after some seven years and a sum widely reported to run into the hundreds of millions of euros. The technical account of the failure is well known: Lidl had for decades valued its stock at purchase price, while the standard retail package was built around valuation at retail price. The interesting question is what happened next. Rather than change a deep-seated internal practice to match a standard process that most of the industry used, the organisation directed that the software be customised to match the practice. Each such decision is individually reasonable and collectively fatal; the customisation burden grew until the programme could not be finished. The organisational vertex refused to move, so the IS vertex was bent to it until it broke. The everyday version of this signature is less dramatic and far more widespread. A system goes live on time and on budget, which is declared a success, and the benefits never appear. The tell-tales are always the same: workarounds, shadow spreadsheets maintained by the people who know what is really going on, duplicate entry into the new system and the old one, and a management narrative that settles on user resistance. Nike's problems with a new demand and supply planning system around 2000 followed this shape closely enough to have entered the textbooks — the system and the planning behaviour around it never became one process, and the consequences appeared in inventory and in a profit warning rather than in an IT incident log. The corrective move is to stop treating go-live as the deliverable. The deliverable is a changed way of working, which means redesigned roles, redrawn decision rights, and revised incentives and performance measures. If the measures still reward the old behaviour, the old behaviour is what you will get, and it will be reported as a software problem. The third signature is the quietest and the most dangerous. Here information systems change and business strategy follows them, without anyone deciding that it should. The technology sets the strategy by default. Marks & Spencer spent several years running its online business on a platform provided by Amazon, and the arrangement worked in the narrow sense that a functioning website existed. What it also meant was that the shape of the retailer's digital proposition — how customers were recognised, what could be personalised, how the online and store businesses could be joined — was bounded by decisions made by another company for its own purposes. The move to an in-house platform in 2014 was expensive and cost sales in the short term, and it was at bottom a decision to reclaim a strategic constraint that had been quietly delegated. Technology-led strategy is not inherently a failure. Amazon Web Services began as internal infrastructure work and became a business that changed the company's strategy and a great deal else besides; Netflix's investment in the systems that recorded what people actually watched shaped its commissioning decisions and moved it from distribution into production. Both were IS-led changes to business strategy, and both were deliberate. The signature is misalignment only when the direction of drive is unacknowledged — when a firm cannot enter a market because a core system cannot represent the product, and this is reported as a technical detail rather than as a strategic choice already made. The corrective move is not to reverse the direction but to surface it: to say plainly that the technology is leading, and then decide whether to adopt that strategy or pay to change the constraint. Turning "our IT is failing" into an answerable question The triangle's most valuable property is not explanatory but interrogative. "Our IT is failing" is not a question; it is a complaint with no possible answer, because it has no subject, no verb of change and no counterfactual. Run the same complaint through the triangle and it becomes a sequence of questions that can be answered with evidence: which vertex moved most recently; which of the other two has moved in response and which has not; what the specific compensating change would be; and who has the authority to make it. This is the whole method, and Chapter 10 develops it into a repeatable procedure for cases and essays. Notice what the reframing does to the politics. A complaint about IT is an accusation aimed at a department. A finding that the business strategy changed eighteen months ago and neither the systems nor the incentives have followed is a statement about the organisation as a whole, with a named corrective move and an owner who is usually not the chief information officer. Very few of the failures studied in this book are failures of technology. They are failures of compensating change, and the triangle's purpose is to make the missing compensation visible. Two errors will cost marks and, later, credibility. The first is treating the triangle as a checklist — walking through the three vertices, describing each one in turn, and concluding that all three exist. Every organisation has all three vertices; that is not a finding. The triangle is about the relationships, not the corners, and an answer that describes three vertices without analysing a single dependency between them has not used the instrument at all. The second error is treating alignment as work that the IT department performs on behalf of everyone else. Alignment is a joint condition of three sets of choices, only one of which the IT function owns. A chief information officer can align systems to a strategy that has been made explicit; none can align systems to a strategy that has not been decided, and none can redesign the incentives of a sales force. When alignment is delegated to IT, what is actually being delegated is the blame. What the examiner is looking for Markers reward three things in answers on the triangle, and the first is directional precision. Do not write that the vertices "must be aligned"; write which vertex moved, in what direction, when, and which failed to follow. An answer that identifies the sequence of change is doing analysis; an answer that asserts mutual dependence in the abstract is reciting a definition. The second is the ability to distinguish the three signatures and to attach the correct corrective move to each, since the remedy for a strategy that outran its systems is nothing like the remedy for a system that outran its organisation. The third is intellectual honesty about the model itself: the strongest answers note that the triangle is a compression of Henderson and Venkatraman's strategic alignment model, that the original treats the direction of drive as an explicit variable, and that the triangle's symmetrical drawing hides exactly that question. The reliable ways to lose marks are equally consistent. Describing the three vertices and stopping is the commonest. Assuming that the business vertex always leads is the second, and it is a substantive error rather than an omission, because it makes the technology-led signature invisible. Treating alignment as a project with an end date is the third. Using a case as decoration — naming a company and then not using it to demonstrate anything — is the fourth, and it is avoided by making every example do diagnostic work: say which vertex moved first. Three questions in the style you should expect: 1. "Alignment is a state that well-managed organisations achieve and then maintain." Critically evaluate this statement with reference to the Information Systems Strategy Triangle and to at least two organisations of your choice. 2. A retailer has announced a strategic shift to direct-to-consumer sales but reports that "IT cannot keep up". Using the triangle, diagnose the likely signature of misalignment, identify the evidence you would seek to confirm your diagnosis, and specify the corrective actions and who should own them. 3. To what extent does the Information Systems Strategy Triangle simplify Henderson and Venkatraman's strategic alignment model, and what analytical capability is lost in the simplification? Illustrate your answer with a case in which information systems drove business strategy. Chapter 2. Reading the Top Vertex: Business Strategy A student asked to analyse a case will often begin by describing the company: how large it is, what it sells, what it says about itself. None of that is a strategy, and an analysis built on it will not survive a marker's first question. The top vertex of the triangle asks something harder: what has this firm chosen to do, and what has it chosen not to do, in order to win customers at a profit its rivals cannot match? Until you can answer that in two or three sentences, you cannot say anything useful about the other two vertices, because organisational strategy and information systems strategy have nothing to be aligned to. The tools below are the standard ones, but the aim is not to recite them. It is to open a case, apply them, and emerge with a defensible statement of what the firm's strategy is and what that strategy obliges its information systems to deliver. What a business strategy is, and the three things that are mistaken for one A business strategy is a coordinated set of choices about where a firm will compete and how it intends to win there, made in the knowledge that those choices foreclose others. Porter's formulation is the most useful one to hold in mind: strategy is about deliberately choosing a different set of activities from rivals in order to deliver a distinctive mix of value. The word doing the work is different. If every firm in an industry pursued the same activities more or less competently, there would be no strategy in the industry, only a race in operational effectiveness — and such a race converges, because best practice diffuses. Three impostors appear regularly in student answers and in real corporate documents. The first is the mission statement. "To be the world's most customer-centric company", "to enrich lives through technology", "to be the partner of choice" — these are declarations of aspiration. They contain no choices, and strategy is precisely the part a competitor would decline to copy. Test any mission statement by asking whether a rival could plausibly adopt the opposite. No airline aspires to be the world's least customer-centric carrier; therefore customer-centricity is not a strategic position. The second is a list of goals: grow revenue, enter new markets, improve satisfaction scores, reduce cost-to-serve. These are outcomes the firm would like. A strategy is the theory of how they will be produced — the logic connecting choices to results. Goals without that logic are a budget with ambition attached, and the characteristic failure of organisations in this condition is that every function invents its own private theory of how to hit the numbers. IT invents one too, which is among the commonest origins of a misaligned technology portfolio. The third impostor is a technology. "Our strategy is to become a digital business", "our strategy is AI". Technology can be the instrument of a strategy, but on its own it specifies neither a customer nor a basis of advantage. A firm whose stated business strategy is a technology has collapsed the top vertex into the bottom-right one, and has no independent standard against which to judge its own IT decisions. Ryanair illustrates a real strategy because its choices are so visibly costly. A single aircraft type simplifies maintenance, training and spares at the price of route flexibility. Secondary airports cut landing fees and turnaround times at the price of convenience. Point-to-point flying removes connection complexity and abandons the transfer traveller. High-density seating and aggressive ancillary revenue raise yield per passenger and drive a segment of the market elsewhere. Every one is a trade-off, which is what makes it strategy rather than preference. A rival that admires Ryanair's costs cannot have them without accepting its renunciations. Three ways to win, and the quarrel about the middle Porter's generic strategies reduce the ways a firm can outperform its industry to a small number. Advantage comes either from lower cost or from differentiation customers will pay for, and it is pursued either across a broad market or within a narrow segment. That yields cost leadership, differentiation, and focus — focus splitting in turn into a cost-based and a differentiation-based variety. Cost leadership means being the lowest-cost producer while offering a product customers find acceptable. It is not the same as charging the lowest price; a cost leader may price at the market and bank the margin. Aldi is the cleanest retail example: a few thousand product lines where a full-range supermarket carries tens of thousands, mostly own-label, stocked from the pallet, in small stores with a lean head office. Each choice removes cost from the system rather than merely squeezing suppliers. Differentiation means offering something customers value enough to pay a premium for, and sustaining it. Apple is the obvious consumer case: integrated hardware, software and services, industrial design, a controlled retail experience, an ecosystem that raises the cost of leaving. Rolls-Royce's civil aerospace business is more instructive, because its differentiation is not the engine but what surrounds it. Under long-term service arrangements, airlines effectively buy thrust and availability rather than hardware, with Rolls-Royce retaining responsibility for maintenance. That contract is only writable because the firm instruments its engines and monitors their condition continuously; the differentiation is inseparable from an information system. Focus means serving a narrow segment so well that broad-line competitors cannot match you there. Brompton is a genuine niche player: folding bicycles for urban commuters, made in the United Kingdom, sold on a specific promise about how a bicycle behaves when it must be carried onto a train. A mass-market manufacturer could build a folding bike; it could not easily build Brompton's relationship with that customer or its knowledge of a hinge-critical frame. These positions place quite different demands on the systems that support them, as Table 2 sets out. The fourth column is the one to read closely: the strategy at the top vertex is not a mood, it is a specification. Table 2. The three generic strategies compared. Strategy Source of advantage What the customer is buying What it demands of information systems Exemplar Cost leadership Lowest cost position in the industry An acceptable product at an unbeatable price Process automation; supply chain visibility; low-cost standardised estate Aldi, Ryanair Differentiation Distinctiveness customers pay a premium for An experience, a brand, a guaranteed outcome Rich customer data; cross-channel integration; systems embedded in the offer Apple; Rolls-Royce civil aerospace Cost focus Lowest cost within one narrow segment Segment-specific value at low price Narrow, deep systems for one segment, not general-purpose breadth Ryanair on European short-haul Differentiation focus Deep fit with one segment's needs Specialist expertise and fit Segment knowledge; configuration support; direct customer relationships Brompton Porter's accompanying warning is that a firm which fails to choose becomes stuck in the middle: it carries the cost base of a differentiator without the price realisation, and faces the price pressure of a cost leader without the cost position. The argument is not arbitrary. Low cost demands standardisation, volume, restricted variety and tight overhead; differentiation demands variety, service, research and a willingness to spend. The activity systems conflict, so pursuing both produces a compromise beaten at both ends. Marks & Spencer's clothing business has been described in these terms for years, squeezed by value retailers below and sharper specialists above. The criticism is serious and you should be able to state it. Many admired firms appear to combine low cost with high quality. Toyota showed that defect reduction and cost reduction can move together rather than trading off, undermining the assumption that quality must be bought. Amazon sustains low prices alongside a service proposition — selection, delivery speed, returns — that customers treat as differentiating. There is also a methodological complaint: "stuck in the middle" is easy to apply after the fact. A firm that fails is declared to have been stuck there; a hybrid that succeeds is re-described as having had a dominant logic all along. A proposition that cannot lose is doing little analytical work. The defensible position, and the one that earns marks, is this. The trade-off between cost and variety is real, but it is a curve rather than a wall, and information systems have moved the curve. Zara combines moderate prices with a responsiveness most of the apparel industry cannot match, but only because point-of-sale data flows back from stores to designers in days rather than seasons, production runs are short and near the market, and logistics replenish twice a week. The modern hybrid is less a refutation of Porter than evidence that coordination costs fell. The consequence for the triangle is direct: a firm pursuing a hybrid is betting its strategy on its information systems in a way a pure cost leader is not, and if the systems underperform, the position collapses into exactly the middle Porter warned about. Five forces, worked through the grocery aisle The five forces model asks a different question. It is not about the firm; it is about the industry. Its claim is that average profitability is determined by five structural features, and that a firm's returns come from industry structure plus its position within it. Take grocery retail in a mature Western European market. Rivalry among existing competitors is intense, and structurally so. Market growth roughly tracks population and food inflation, so volume gains must come from other firms. Fixed costs — stores, depots, vehicles — are high, which punishes empty capacity and encourages price-cutting to fill it. The same branded goods sit on every shelf, so the chains are largely undifferentiated, and exit barriers are high because store estates are illiquid. The result is an industry where operating margins sit in the low single digits despite enormous revenue. Threat of new entry looks low if you only count barriers: scale economies in buying, distribution networks that take years and capital to build, planning constraints on sites, established brands. Yet Aldi and Lidl entered and took substantial share. Entry rarely occurs into an industry as a whole; it occurs into a position. Newcomers who accept the incumbents' model face the full barrier, while those bringing a different one face a much lower one. Amazon likewise entered through a different channel rather than the front door of the superstore. Bargaining power of suppliers is not uniform, and the commonest error is to treat suppliers as a single bloc. Fresh produce growers are numerous, small and often dependent on one or two buyers; their power is weak, which is why the United Kingdom created a Groceries Code Adjudicator to police how the chains treat them. Major branded manufacturers are in a different position entirely: a supermarket that does not stock the leading cola, detergent or spread has a visible gap and loses trips. The dispute between Tesco and Unilever in 2016 over price increases following sterling's fall, which briefly removed well-known products from Tesco's website, was this force being tested in both directions. Bargaining power of buyers is the force students most often misjudge. No individual shopper has negotiating power. But buyer power is not only about negotiation; it is about the cost of walking away, and grocery switching costs are close to zero. Price transparency is high and multi-chain shopping is normal, so the power is exercised in aggregate and continuously. Threat of substitutes means alternative ways of satisfying the same need, not alternative firms serving it the same way. Another supermarket is a rival, not a substitute — a distinction worth marks. The real substitutes for a weekly shop are eating out, takeaway delivery platforms, subscription meal kits and food-to-go formats, several of which have grown. The verdict matters more than the inventory. This is a structurally unattractive industry — intense rivalry, weak protection from one class of powerful suppliers, near-costless buyer switching, live substitutes — and it is not unattractive because the firms are badly run. Reading it that way tells you at once what information systems in this sector are obliged to deliver: relentless cost extraction through supply chain and store systems, since margin cannot be won on price; customer data good enough to create switching friction where the product cannot, which is the strategic logic behind loyalty schemes; pricing and category systems fast enough to respond within hours; and fulfilment capability for channels the store estate was never designed to serve. Two limitations deserve a sentence. The model is a snapshot that says little about how structure changes, and it assumes industries have clear boundaries — awkward where platforms blur them, since a delivery platform is channel, rival and substitute at once. From activities to capabilities: the value chain, VRIO, and the end of durable advantage The value chain disaggregates the firm into the activities by which it creates value, so that cost and differentiation can be located rather than asserted. Porter's primary activities are inbound logistics, operations, outbound logistics, marketing and sales, and service; his support activities are firm infrastructure, human resource management, technology development, and procurement. The difference between what customers pay and what the whole chain costs is margin. Note where information systems sit. They fall under technology development and firm infrastructure — the support layer. The consequences of that classification have been large and mostly unhelpful, because support activities are treated as overhead, and overhead is what organisations cut when results disappoint. Yet information runs through every primary activity: inbound logistics is unintelligible without supplier scheduling data, operations without inventory systems, outbound logistics without routing, marketing and sales without customer data, service without case and asset records. In many firms the primary activities are now executed by systems rather than merely recorded by them. A supermarket's replenishment is a decision made by software. Rolls-Royce's service activity, once a cost centre, became the product itself once engine data made outcome-based contracts possible. This produces one of the most reliable pathologies in cases: a firm cuts what its accounts call IT overhead, degrades what its value chain calls operations, then reports the consequences as unrelated service failures. Use the chain as a discipline. For each primary activity, ask what information it consumes, what it produces, and who else needs that output; where nobody passes it on, you have found either a redundant activity or a broken linkage. Nor does the chain stop at the firm's boundary: Porter's value system links supplier chains to the firm's to the buyer's, and much advantage sits in those joins — as when Walmart gives suppliers direct sight of store-level sales and lets them manage replenishment. The resource-based view turns the telescope round. Where Porter looks outward at industry structure, Barney looks inward and asks why firms in the same industry, facing identical forces, perform differently. The answer is that they control different bundles of resources and capabilities. A resource is something the firm has — a patent, a location, a data set, a plant. A capability is something it can reliably do, which requires people, processes and resources working together in a way nobody wrote down. Barney's VRIO test asks four questions of any candidate source of advantage. Is it valuable — does it exploit an opportunity or neutralise a threat? Is it rare? Is it costly to imitate? And is the firm organised to capture the value? Fail the first and it is a weakness; pass value but fail rarity and you have parity; pass value and rarity but fail imitability and you have temporary advantage. Pass all three and fail organisation and you have a wasted asset — the letter students forget, and the one that most often explains why a firm with a genuinely superior capability still loses. Work the test on a concrete case, separating the system from the capability. Consider a grocery loyalty scheme of the Tesco Clubcard type. The scheme itself — cards, points, a transaction database — is valuable, since it identifies the shopper and permits targeted offers. Rare? Not for long; Sainsbury's and others launched competing schemes, and a rival can buy the same technology from the same vendors. Costly to imitate? No. On the system alone the verdict is parity. Now test the capability around it: the accumulated practice of turning transaction data into decisions about range, pricing, store format, promotion and own-label development, with buyers and category managers who trust the analysis enough to act on it. Valuable, clearly. Rare, because it rests on years of data that cannot be bought retrospectively. Costly to imitate for three of Barney's classic reasons: path dependence, since the history accrues only in real time; causal ambiguity, since even insiders cannot fully specify which parts of the practice produce the result; and social complexity, since it lives in relationships between analysts and commercial staff. And organised, if the structure actually routes the insight to people with decision rights. That is the difference between a system and a capability, and it is why you should be sceptical whenever a case claims software confers sustainable advantage. Software is procurable: Ocado licenses its automated fulfilment platform to Kroger and to Morrisons, and the licensees get the platform, not Ocado's accumulated learning about running it. D'Aveni's argument is that all of this is less stable than it looks. In conditions he called hypercompetition, advantages are systematically eroded by rivals' countermoves, so competition becomes a sequence of temporary advantages rather than the defence of a durable position. Firms manoeuvre across cost and quality, timing and know-how, strongholds and financial resources, and each move invites a response that destroys the equilibrium the last one created. The implication is uncomfortable: the correct behaviour is not to fortify a position but to disrupt your own first. Apple cannibalised the iPod with the iPhone. Netflix cannibalised a profitable DVD-by-mail business with streaming, then cannibalised its dependence on licensed content with originals. Kodak, holding genuine digital imaging capability, declined to cannibalise film and was destroyed by the transition it had the resources to lead. Hold the claim with care. Not every industry is hypercompetitive — regulated utilities plainly are not — and the evidence that advantage erodes faster than it once did is contested rather than settled. But the directional point survives. If the top vertex moves every eighteen months while the organisational and technical vertices carry lead times measured in years — architectures, skills, contracts, culture — then misalignment is not an occasional accident. It is the default state, and re-balancing must be continuous rather than performed in an annual planning cycle. That obligation, more than any framework above, is what the business strategy vertex hands down to the other two. What the examiner is looking for Markers reward a small number of distinctions, and they are the same ones every year. The first is strategy against aspiration: an answer treating a mission statement or a set of targets as a strategy has failed at the first step. The second is rivalry against substitutes — competing supermarkets are rivalry, meal kits and restaurants are substitutes, and confusing them is the commonest error in this topic. The third is resource against capability, and within VRIO the letter O, dropped in most answers despite being the reason many firms fail to convert real advantages into returns. Three habits lose marks reliably. Describing all five forces at equal length and stopping, without a verdict on whether the industry is attractive and which force binds hardest — the model is an argument, not a checklist. Calling every large firm a differentiator. And asserting that a technology delivers sustainable advantage without running it through VRIO, when the honest answer is normally that the system is imitable and only the surrounding capability is not. Strong answers handle objections. If you use "stuck in the middle", acknowledge the hybrid cases and explain why falling coordination costs made some viable. If you use the five forces, note that it is a static model with assumed industry boundaries. Specimen questions of the kind examiners set: 1. "A mission statement is not a strategy." Using Porter's generic strategies, evaluate the business strategies of two named firms competing in the same industry, and explain what each strategy obliges its information systems to deliver. 2. Apply the five forces model to grocery retailing. Identify the force that most constrains industry profitability, justify your choice, and explain what your analysis implies for where firms in the sector should direct information systems investment. 3. "A competitor can buy the same system, but cannot buy the same capability." Critically discuss with reference to the resource-based view and VRIO, using at least one real example, and consider whether D'Aveni's hypercompetition thesis weakens the promise of sustainable advantage. Chapter 3. The Second Vertex: Organisational Strategy and the Design of Work A hospital buys an electronic prescribing system. The software is competent, the servers are sized correctly, the interfaces to the pharmacy stock system work. Eighteen months later, junior doctors are still writing on paper during ward rounds and entering the orders later, in batches, from memory, at the nurses' station. Nothing has failed technically. What has failed is the fit between the system and the way the work is organised: who does what, in what sequence, under whose supervision, and with what consequences for being slow. This is the ordinary shape of information systems failure, and it sits on the organisational vertex of the triangle. Students consistently under-weight this vertex: it is less glamorous than business strategy, less concrete than technology, and harder to revise from, because it has no single celebrated framework with a memorable name. The claim the triangle makes is symmetrical. An information systems strategy must be as consistent with the organisation's design as it is with its competitive strategy, and a system introduced without a corresponding change to the organisation will be quietly defeated by it. The three levers a manager can actually pull Organisational strategy, in this context, means the deliberate design of the organisation and of the work inside it. It is not the organisation chart, though the chart is part of it. It covers how people are grouped, who holds which decision rights, how performance is defined and measured, what is rewarded and what is punished, what beliefs are shared about how things are properly done, and — most concretely — how a piece of work flows from the moment it arrives to the moment it is finished. A manager has three levers available here, all distinct from the technology itself. The first is the set of organisational variables: structure, reporting lines, grouping, roles, decision rights and the design of work processes. These are the things that appear in an announcement. A firm can group by function, product, geography or customer segment; it can push a decision down to a store manager or reserve it for a category buyer in head office; it can create a role called "sales operations analyst" that did not exist before, or abolish a layer of supervisors. They are the levers with the fastest visible effect and the shortest half-life, because a structure can be redrawn in a weekend and undone in another one. The second is the set of control variables: measurement, evaluation, targets, incentives, reward and budget. What gets counted, who sees the count, what happens to a person whose count is poor, and how money is allocated on the basis of it. Control variables change more slowly than structures, partly because compensation plans are contractual and partly because changing them is politically expensive. They are also far more powerful, because they determine what people do when nobody is watching and the new system is inconvenient. The third is the set of cultural variables: values, beliefs and the shared assumptions that members of an organisation hold so deeply they no longer notice holding them. Culture is what tells a subpostmaster's regional manager, or a bank's operations director, whether an anomaly in the numbers is more likely to be a person at fault or a system at fault. In the UK Post Office's Horizon affair, the working assumption that the computer was reliable and the humans were not shaped the interpretation of every discrepancy for years. No chart contained that assumption and no control report displayed it, but it governed behaviour more tightly than either. The point of separating the three is diagnostic. A manager facing a problem on this vertex has these levers and no others, yet most managers reach instead for a fourth thing that is not on the vertex at all: the technology. Buying a system is fast, procurable, budgetable and visible; redesigning a bonus scheme is slow, contested and career-threatening. So the technology lever gets pulled alone, the other three are left holding the old behaviour firmly in place, and the result is a triangle out of balance with the symptoms presented as IT problems. Zara is the standard example of the levers being pulled together. The technology — point-of-sale capture, handheld devices in stores, a short data path from shop floor to designers and to the factories in and around Galicia — is not exotic, and competitors bought comparable systems. What is distinctive is the organisational design around it. Decision rights over what to reorder sit unusually close to store managers, who feed judgement as well as data back up the chain. Commercial teams are measured on responsiveness to current selling rather than on the accuracy of a forecast made a year earlier. And the culture treats a stockout as acceptable, even desirable, in a way that would be a firing offence in a traditional retailer measured on availability. Many retailers bought good replenishment systems in the same period and obtained very little from them, because the systems were installed into organisations whose buyers still committed the season's range in advance and were still rewarded for hitting margin on the plan. The incentive problem: why good systems go unused If you had to name a single cause for low adoption of otherwise sound systems, it would be misalignment between what the system asks people to do and what the reward system pays them for. Nothing else comes close — not usability, not training, not "resistance to change" as a personality trait. Take a worked example. A business-to-business distributor with some forty field sales representatives buys a well-known cloud CRM. The stated purpose is forecast accuracy: the finance director cannot plan working capital because the quarterly revenue forecast swings wildly, and the sales director cannot see which deals are real. The system requires each representative to maintain an opportunity record for every live deal, with a value, a close date, a stage and a next action, updated weekly. Now look at the representative's world. Their bonus, a large share of take-home pay, is paid entirely on closed revenue in the quarter. Nothing in the plan pays for the quality of the pipeline record, and maintaining it costs perhaps half an hour a week of time that could be spent selling — small, but strictly negative in reward terms. The cost is worse than the time, because the record creates exposure. A deal entered at a high value and then lost is a visible failure that was previously invisible. A well-populated pipeline invites a manager to raise the quota, or to reassign a fat account that is being under-worked. The rational representative therefore enters the minimum: deals effectively already won, at conservative values, with close dates pushed to the end of the quarter. The pipeline becomes a lagging record of what has already happened rather than a forward view of what might. Six months later the forecast is no more accurate than before, and senior managers conclude that the CRM has failed and the sales force needs more training. Both conclusions are wrong. The system works; it is faithfully recording the behaviour the compensation plan rewards. The defect lies in the control variables, and it was there before the software arrived. Fixing it requires pulling the levers that were left alone. On control: attach a meaningful share of variable pay to qualified pipeline coverage and to record completeness — while recognising that any such measure will be gamed, so "qualified" must mean something a second party verifies. On organisation: create a pricing approval step that cannot be reached except through a CRM record, so the system sits on the path to something the representative actively wants rather than beside it, and cut the cost of compliance by auto-capturing activity from email and calendar. On culture: run the weekly pipeline review from the system and only from the system. If it is not in the system it does not exist, and the first senior manager who accepts a side spreadsheet destroys the rule for everyone. The principle generalises well beyond sales. Whatever a system measures becomes a target, and whatever becomes a target distorts the behaviour it measures: call centres that measure average handling time get calls terminated early and customers who ring back. This is not a reason to avoid measurement, but a reason to treat a new measurement system as an act of organisational design, with the gaming response anticipated rather than discovered. Automating, informating and the shape of the hierarchy Shoshana Zuboff's distinction between automating and informating remains the most useful single idea on this vertex, and it is frequently misremembered as a choice between two kinds of system. It is not. It is an observation that the same system does both at once, and that management chooses which of the two it takes seriously. To automate is to substitute machine capacity for human effort: the task a person used to perform is now performed by the system, faster and more consistently. To informate happens as a by-product. Because the work passes through a system, it throws off a detailed record of itself — a stream of data about the process that did not exist when the work was done by hand. Ocado's warehouses automate the picking of groceries; they also informate, generating a minutely detailed account of demand, throughput and failure that the company has been able to sell as a service to other retailers. Rolls-Royce's instrumented aero engines automate very little of the engineer's work but informate intensely, and that data stream is what makes it possible to sell availability rather than hardware. The engineer's job changes from repairing what has broken to forecasting what is about to, and the commercial relationship with the airline changes with it. The organisational choice is about where the informating stream is allowed to flow. If the new data flows only upward, it becomes an instrument of central control and monitoring: head office now sees what the branch used to know privately, and the branch's discretion narrows. If it flows outward to the people doing the work, it becomes an instrument of upskilling: the operator who can see the whole process can be trusted with decisions that previously had to be escalated. The technology is identical; the organisational design is opposite. This is where the deskilling and upskilling debate belongs, and neither should be treated as the inevitable consequence of computerisation. Scripted contact-centre systems that route the agent through a decision tree genuinely deskill: they lower the knowledge required, which lowers the wage the role commands and raises the tolerable rate of turnover, and that is often exactly what the system was bought to achieve. Field service diagnostics that put the whole machine history in the engineer's hands genuinely upskill. Both are design decisions, taken by managers in pursuit of a business strategy — which is precisely the triangle's claim. A cost-leadership strategy pulls systems towards deskilling and standardisation; a differentiation strategy built on expert service pulls them the other way. Two structural consequences follow. The first is span of control. A supervisor who must inspect work personally can oversee a handful of people; a supervisor whose system reports exceptions can oversee many more, because attention is directed only where the process has departed from the expected. Widening the span of control is arithmetically the same thing as removing layers of hierarchy, and the wave of delayering in large industrial firms in the 1980s and 1990s — General Electric under Jack Welch being the most discussed case — was made practicable in part by management information systems that let fewer managers hold a larger territory. The under-noticed cost is that the middle managers who remain have a different job: unable to check everything, they have to coach, set direction and handle exceptions. Organisations that flattened without changing what they expected of middle managers simply produced overloaded supervisors performing the old job badly. The second consequence runs the other way, from organisation to system, and it is Conway's law: organisations design systems that mirror their own communication structures. A retail bank with separate, long-established business units for branches, telephone banking, the website and the mobile app will tend, over time, to build four customer records, four authentication mechanisms and four views of a balance — not because any architect chose that, but because each unit builds what it can build without negotiating with the others. The integration project that follows is described as a technical problem and priced as one, when it is really an attempt to undo an organisational boundary using software. Amazon's much-discussed insistence that internal teams expose data only through service interfaces, coupled with small autonomous teams, is best read as the deliberate inverse: designing the organisation in order to obtain the architecture. For the triangle, Conway's law is the sharpest statement of interdependence available. If you want a different architecture, you may first have to change the organisation that will build it. Distance, monitoring and the resistance that training cannot fix Hybrid and remote working is the live organisational-strategy question of the present decade, and it is routinely mishandled as a technology question. The technology settled quickly: video conferencing, messaging, cloud storage and virtual desktops are adequate and widely deployed, and the pandemic proved that most information work can be performed away from an office. What did not settle is the organisational design around them. Distance changes how work is coordinated, how people are supervised, how newcomers absorb tacit norms they previously picked up by proximity, how weak ties across departments form, how real estate is used and, awkwardly, whether pay should follow the local labour market of wherever the employee now lives. The technologies both enable and constrain. Persistent chat tools make lateral coordination cheap and interruption cheaper still. Video calls transmit content well and the informal, unplanned encounter badly. Document collaboration removes the version-control friction that made distributed writing painful, while the absence of a shared room removes the overhearing through which junior staff used to learn how a difficult negotiation is handled. The decisive point is a control-variable point. Supervision in an office rests substantially on presence: the manager infers effort from attendance and visible activity. Remove presence and that proxy is gone, and the organisation must either replace it with a defensible measure of output or find a substitute proxy. Many firms did neither, and the return-to-office mandates that followed — Amazon's move to a five-day office requirement being the most prominent — are best understood not as evidence about productivity but as a decision to restore the old proxy rather than redesign measurement. That may be defensible. It is not neutral, and it costs most in the labour market for exactly the staff who have alternatives. The substitute proxy many organisations reached for instead is electronic monitoring: activity scores derived from keyboard and mouse use, application-usage dashboards, idle-time reporting, screenshots, and in physical work the older machinery of rate tracking and "time off task" familiar from Amazon's fulfilment centres. Some of this is legitimate — a warehouse must know where a tote is, a trading floor must record communications by law. Some is corrosive. Barclays, in a widely reported case, installed desk-occupancy sensors and later a staff-tracking system, withdrawing the latter after objections from employees and attention from the regulator; monitoring decisions are governed as well as managed, and in Europe are constrained by data protection law and, in several countries, by works councils. The trust cost is the part students should be able to articulate. Monitoring communicates an assumption about the person monitored, and that assumption tends to be self-fulfilling. Where surveillance is close, discretionary effort — the unpaid extra that makes organisations function — falls, because the employee reasonably concludes that what is wanted is compliance with the measure rather than contribution to the outcome. The measured behaviour rises and the unmeasured behaviour, which frequently includes helping colleagues and flagging problems, falls. Monitoring is also distributed asymmetrically, heaviest on the lowest-paid and least autonomous workers and lightest on the executives who commission it, which is noticed. A defensible position is available: monitor the process for coordination and safety, evaluate people on outcomes, be explicit about what is collected and why, and give the resulting data to the worker as well as the manager — which is to say, informate outward as well as upward. All of this bears on what to do when a system is not being adopted, and here the reflex answer is almost always wrong. When usage is low, organisations run more training. Training is attractive because it is cheap, procurable and adjacent to the technology vertex, and because it converts a political problem into an informational one that nobody need be blamed for. It works only when the cause is genuinely a deficit of ability. The useful diagnostic separates three quite different situations. The first is cannot: people lack the skill or the time to use the system as designed, and training and workload relief are the right responses. The second is will not: people understand perfectly and are declining, because the system costs them time, status, autonomy or money, or makes visible something they preferred to keep private. No amount of training touches this; only the control and organisational levers do, by changing what the behaviour costs and pays. The third, and the one managers least like to consider, is should not: the objection is correct, and the system as configured makes the work worse or less safe. Clinicians who abandon an order set because it adds twelve clicks to an urgent prescription are not being obstructive; they are reporting a design fault. Resistance, on this reading, is not an obstacle to be overcome but information about a mis-designed system or organisation, and the first managerial duty is to establish which of the three it is before spending money. What does work, where the diagnosis is will not, is unglamorous. Involve the people who do the work in configuring it, so the design absorbs their knowledge and they own the result. Secure visible, repeated senior sponsorship, which John Kotter's work on change has long emphasised and which in practice means a leader who keeps asking about the system in public for longer than is comfortable. Close the escape routes: decommission the old system, withdraw the parallel spreadsheet, route a needed approval through the new process. Change the measures and the money so that using the system is the profitable behaviour, and give people time in the schedule for the transition rather than expecting it on top of a full workload. The sequence matters: the organisation usually has to move before, or at worst alongside, the technology, never a year afterwards. What the examiner is looking for Markers want a candidate who treats organisational strategy as a set of specific, nameable design choices rather than as "people issues" or "company culture" used as a residual category for anything unexplained. The strongest answers do three things. They use the three levers — organisational, control and cultural variables — as an explicit diagnostic frame, and say which lever is jammed in the case at hand. They distinguish automating from informating correctly, as two simultaneous properties of one system rather than two types of system, and draw the consequence about who receives the new data. And they trace interdependence in both directions: not only that a new system requires organisational change, but, via Conway's law, that the existing organisation shapes what system gets built. Marks are lost in predictable ways. Attributing non-adoption to vague "resistance to change" without identifying the incentive that makes refusal rational is the commonest. Treating deskilling as an automatic consequence of computerisation rather than a design decision serving a business strategy is another. So is recommending training as the remedy for every adoption problem, and describing monitoring as simply good or bad rather than weighing what it buys against the discretionary effort it costs. Use real organisations and say precisely which lever the example illustrates. Specimen questions: "A regional insurer has spent two years and a large budget implementing a new claims management system. Adjusters continue to keep their own spreadsheets and the system's data is incomplete. The IT director proposes a further round of training. Critically evaluate this proposal and recommend an alternative course of action." "'The same information system can deskill one workforce and upskill another.' Discuss, with reference to Zuboff's distinction between automating and informating." "To what extent is the choice between office-based, hybrid and fully remote working an organisational strategy decision rather than an information systems decision? Support your argument with examples." Hashtags: #TheInformationTriangle #StrategicManagementOfInformationSystems #InformationSystemsStrategyTriangle #BusinessStrategy #OrganizationalStrategy #InformationSystemsStrategy #StrategicAlignment #StrategicFit #FunctionalIntegration #HendersonVenkatramanModel #BusinessITAlignment #DecisionRights #OrganizationalDesign #ControlVariables #CulturalVariables #TechnologyGovernance #InformationSystemsCapability #CompetitiveAdvantage #PortersGenericStrategies #FiveForces #ValueChain #ResourceBasedView #VRIO #ContinuousRealignment #FutureOfStrategicInformationSystems

Download the Book (PDF): Introduction There is a particular expression that crosses a student's face in week three of an IT strategy module. It arrives when they realise that the case assigned for Thursday concerns a company that was acquired in 2004, using a technology that no longer exists, to solve a problem that cloud computing made trivial. The expression says: why am I reading this? It is a fair question and it deserves a real answer rather than an appeal to tradition. Corporate Information Strategy and Management is a Harvard Business School book, built the way Harvard builds books: out of clinical case research conducted inside real firms over decades, with frameworks extracted from what the researchers found. Lynda Applegate, Robert Austin and Warren McFarlan assembled a body of material that has shaped how two generations of executives think about technology. It is also, in its case selection, visibly a product of the period in which it was assembled. There are cases about client-server migrations. There are companies that were at the height of their powers when the case was written and are now footnotes. There are financial figures denominated in a business environment that has since changed twice over. Here is what a student needs to understand, and it is the organising idea of this whole book. The cases date. The frameworks do not. The reason is structural. A framework built around a named technology has a shelf life equal to that technology's. A framework built around a structural condition — a condition about dependence, or about where a firm's boundary should fall, or about how much executive attention a class of decision warrants — survives every technology that comes and goes inside it. This textbook's frameworks are almost entirely of the second kind, which is why they keep working. McFarlan and McKenney's question of 1983 — how much should information technology matter to this particular firm, given its dependence today and what is in its pipeline — is exactly as answerable, and exactly as consequential, for a company deciding what to do about artificial intelligence in 2026 as it was for a company deciding what to do about mainframes forty years ago. The technology in the question changed. The question did not. So this guide has a consistent method, applied in every chapter. Take one framework. State it exactly as its authors did, with the right names and the right year, because getting that right is a marker of having read rather than absorbed. Explain the problem it was built to explain. Then re-apply it, with the same rigour, to a situation happening now — and say honestly where it holds, where it strains, and where it has stopped describing the world. Every chapter contains a section that does this explicitly. That translation is not a study aid. It is the actual skill. A Harvard-style assessment does not reward knowing the frameworks; it rewards selecting the right one for a situation it was not written about and defending the choice. So does an executive committee. The chapters follow the shape of the executive's year rather than the textbook's page order. Chapter one covers the case method itself and the translation discipline, and is worth reading before anything else. Chapter two takes the strategic grid — the most useful framework in the book and the one most often reproduced without being understood. Chapter three covers business models, capabilities and the network economy, and makes the argument that information systems constitute capabilities rather than supporting them. Chapter four is about money: the investment portfolio, appraisal methods and their limits, and the specific difficulty of funding infrastructure whose only return is the options it creates. Chapter five takes operations seriously, and argues that for a large class of firms reliability is the strategy — including a fair statement of Nicholas Carr's argument that technology has stopped mattering, and the serious answers to it. Chapter six covers sourcing as a question about where the boundary of the firm should fall, with the textbook's distinctive framing of outsourcing as an alliance rather than a purchase. Chapter seven covers technology risk at board level, building on McFarlan and Nolan's 2005 argument that this oversight is a director's duty. Chapter eight covers governance and the shape of the technology organisation. Chapter nine covers the adoption problem — the human side, which decides outcomes and which students under-weight because it does not reduce to a matrix. Chapter ten converts everything into an executable analytical method, demonstrates it end to end on a full worked case, and then gives the serious criticisms of this entire framework tradition the weight they deserve. Every chapter closes with guidance for case analysis and essays: how the material appears in assessment, what markers reward, what loses marks, and three specimen questions written out in full. Two commitments about accuracy are worth stating. Nothing here is invented. Where a figure would be convenient and cannot be verified, the text writes around it. Where a company is named, the events described are real and checkable. Where an organisation is fictional — as in the worked case in the final chapter — it says so plainly. The frameworks are attributed to their actual authors with their actual dates, because a student who writes "the McFarlan and McKenney strategic grid of 1983" is demonstrating something that a student who writes "the strategic grid" is not. There are no diagrams in this book. That is a deliberate constraint on a subject whose characteristic vice is the two-by-two matrix reproduced from memory with no idea what its axes measure. Every grid, model and framework here is explained in sentences. If you can say in words what the axes are, what each position means and why a particular firm sits where it does, you understand the framework; if you can only draw it, you do not. A final thought on why any of this is worth the effort. The frameworks in this book are, in the end, a set of questions that senior people fail to ask. Nobody asked how much technology should matter to Blockbuster. Nobody asked, at Equifax, who was accountable for knowing which systems ran a component with a published vulnerability. Nobody asked, before a great many enterprise implementations, what would have to change about how people work for the investment to produce anything. These are not sophisticated questions. They are obvious ones, and they go unasked because asking them requires someone in the room to know that they exist. Knowing that they exist is what this material is for. Chapter 1. Reading an Old Book Well The objection arrives early, and it is a reasonable one. A student opens this textbook and finds an extended treatment of an airline reservation system built in the 1960s, an order-entry terminal placed in hospital storerooms before most of the class was born, and a discussion of whether a firm should own its own private network. The companies have been acquired, renamed or dismantled. The technologies are museum pieces. The student, told that this module is about digital strategy in an age of cloud platforms and generative models, asks what any of it has to do with the world they are about to work in. The objection is right about the surface and wrong about the substance, and that difference is the subject of this chapter. What has aged here is the equipment. What has not aged is the question set: how much should technology matter to this particular firm, what kind of advantage can it produce, who should decide about it, and what happens when it fails. Those questions are answered with frameworks built to describe structural conditions rather than particular machines, which is why they outlive the machines. What a case is, and what it trains A Harvard-style case is not a story with a lesson attached. It is a decision situation, reconstructed from field research, and deliberately left incomplete. It contains more information than is relevant and less than would be sufficient to decide with confidence. The exhibits include figures that do not bear on the decision at all, and omit at least one figure any sensible executive would have demanded before deciding. The protagonist is named, dated and placed in a chair, and the reader is put in that chair with them. This is not sloppiness but a faithful reproduction of the executive condition. No senior decision is made with a complete information set, and none waits for one; the manager who insists on more data is deciding to delay, and will be judged on it. A case therefore trains three things at once. It trains recognition of which analytical lens applies to the problem in front of you, which is much harder than applying a lens you have already been handed. It trains reasoning from partial and contaminated evidence towards a defensible position. And it trains commitment: the willingness to say what you would do, name the conditions under which you would be wrong, and hold the position under challenge from people who read the same pages and reached a different conclusion. That third element is the one students most often resist, usually in the form of the complaint that cases have no right answer. The complaint is true and it is not a defect. The decisions the cases describe had no right answer either. They had a set of options, each carrying a distribution of outcomes, and an executive who had to choose one on a particular Tuesday with the information then available. What followed was partly a consequence of the choice and largely a consequence of everything else in the world, which is why a case cannot be marked against its outcome. It can only be marked against the reasoning: whether the right framework was selected, whether the evidence in the case was used rather than decorated, whether the recommendation follows from the analysis, and whether the analyst knows which of their own assumptions is carrying the most weight. The skill being assessed, then, is not knowing the answer. It is producing a chain of argument that a sceptical and well-informed colleague cannot break in two minutes, which is what the executive chair requires. What dates and what endures Some claims in this literature are permanently useful and some were obsolete within a decade of publication, and the difference is systematic rather than accidental. A claim resting on a structural condition — the concentration of an industry, the cost to a buyer of switching suppliers, the presence of a transaction sitting between two parties that can be captured — survives the technology that first made the condition visible. A claim resting on the properties of a particular machine dies with the machine. Consider the two directions. McFarlan and McKenney's strategic grid, published in 1983, asks how much information technology ought to matter to a given firm: whether the firm's current operations depend on systems that must not fail, and whether its future competitive position depends on systems not yet built. That question is as answerable in 2026 as in 1983, and it produces different answers for a regional insurer, a container line and an advertising agency exactly as it did then. Nothing in the question names a technology. Now set beside it a discussion, entirely typical of the early 1990s, of whether a firm should adopt client-server architecture as a matter of strategy. That discussion was serious and well argued at the time and is now of purely historical interest, because the choice it framed no longer exists. The underlying question — where should computation sit, and who controls it — has resurfaced repeatedly, most recently in the argument about whether to run models in a vendor's data centre or your own. But the 1990s answer travels nowhere, because the answer was about a technology and the question was about a structure. The same distinction runs through the famous cases of technology-enabled advantage. American Airlines' SABRE and American Hospital Supply's ASAP terminals are the two most cited examples in the field, and what made each a durable advantage was not the equipment. In SABRE's case it was the capture of a transaction channel: the travel agent's booking passed through a screen American controlled, and control over the ordering and display of options is control over a market, which is why the ordering of that screen eventually attracted regulatory rules in the mid-1980s. In ASAP's case it was the reorganisation of the buyer's own work: hospital purchasing departments rebuilt their ordering process around a supplier's system, so a competitor had to displace a working routine rather than merely undercut a price. Both mechanisms — controlling the channel through which choice is expressed, and embedding yourself in the counterparty's operating process — are precisely what makes platform businesses defensible today. The instruments, dedicated terminals hard-wired into customer premises, are gone and will not return. This yields a usable test with two parts. First, does the framework's claim name a technology? If it cannot be stated without the word "terminal", "client-server", "mainframe" or, for that matter, "large language model", it is a claim about equipment and it will date. Second, would the logic survive that technology being replaced by any other? Restate the claim with the named technology removed and a blank in its place. "A supplier that embeds its ordering process in the buyer's operations raises the cost of switching" survives the blank. "A firm should place proprietary terminals in customer premises" does not. A third check catches the harder cases: does the claim depend on a cost or a capability that has since moved by an order of magnitude? Much strategic reasoning in the 1980s assumed that building and running systems was ruinously expensive, slow and scarce, which is what made a successful one a barrier to entry. When the cost of a capability collapses, the barrier collapses with it, and a framework resting on scarcity must be re-examined rather than merely re-applied. That is the honest core of Nicholas Carr's argument in "IT Doesn't Matter" in 2003, and the reason it still needs answering rather than dismissing. Five kinds of material recur in a case textbook, and each ages at a different rate and needs different handling. Table 1. What dates and what endures in a case textbook. Element of the textbook Dates or endures Why How to use it now Named technologies (terminals, private networks, client-server) Dates fast Tied to a cost and capability profile that has shifted by orders of magnitude Treat as an instance, not a claim; ask what function it performed, then find today's equivalent Industry structure claims (concentration, channel power, regulation) Dates slowly Structures move over a decade rather than a quarter, but they do move Verify the structure still holds before importing any conclusion resting on it The frameworks themselves Endure Stated over structural conditions, with no technology named in the logic Apply directly: state the condition, then test it against current evidence The cases' company outcomes Dates, and misleads Hindsight attributes the outcome to the one decision the case studies Judge on what was knowable at the date; treat outcomes as weak evidence Financial figures (spend, margins, share, headcount) Dates Absolute values are historical artefacts; price and capacity have moved Convert to ratios and orders of magnitude; re-source current figures The translation discipline Knowing a framework endures is not the same as using it on something current. That takes a procedure short enough to execute under exam conditions. First, identify the framework the case was written to illustrate, which is not necessarily the one you find most interesting. Second, state the structural condition the framework describes, in language containing no technology at all. Third, find a current situation in which that condition holds, testing the condition rather than the surface resemblance. Fourth, test whether the framework's prediction holds there, using present evidence rather than assertion. Fifth, and most important for marks, state where the framework fails and say what is doing the explanatory work instead. Worked through on American Hospital Supply, it runs as follows. The framework is the competitive-forces treatment of information systems McFarlan set out as questions: can the system build barriers to entry, raise customers' switching costs, change the basis of competition, alter the balance of power with suppliers, or generate new products. ASAP is the standard illustration of the second and third. The structural condition, stated without technology, is this. A supplier operates in a market where the buyer's cost of ordering and of comparing options is high relative to the unit price of what is ordered; the supplier is large enough to absorb a fixed investment no individual buyer could justify; and the buyer's own operating process can be rebuilt around the supplier's system, so that changing supplier means re-engineering work rather than re-signing a contract. Where those three hold together, investment in the interface between two firms converts a price relationship into a process dependency. A current situation with the same condition is Ocado's licensing of its fulfilment platform to grocery retailers, among them Kroger, Morrisons, Sobeys, Casino and Aeon. Test the condition rather than the analogy. The buyer's cost problem is real and large: online grocery fulfilment economics are brutal, and the fixed investment in automated warehousing and its software is beyond what most individual grocers will build alone. The supplier absorbs that investment by amortising the platform across many territories. And the retailer's operating process genuinely does rebuild around the platform, since picking, routing, inventory and store roles are all re-specified by it. The condition holds on all three limbs. The framework predicts durable advantage through switching costs and scale economics on a shared asset, and that partly holds: contracts run for many years, territorial exclusivity is normal, and a partner wanting to leave would be replacing physical estate as well as software. Now the honest part, where the analogy strains. ASAP's embedded asset was cheap per unit, so advantage went to whoever installed fastest and captured the base. Ocado's embedded asset is capital-hungry and slow to build, which inverts the logic: diffusion is throttled by financing and construction rather than by sales effort, partners revise build schedules, and the advantage becomes a balance-sheet problem as much as a competitive one. The unit cost of the embedded asset, and its effect on how fast an installed base can be captured, is not in the original framework at all, because in the original setting it was not a binding constraint. Second, ASAP's lock-in decayed once the industry moved to shared ordering standards any supplier could meet; the modern equivalent is standardised automation from rival vendors, which would turn a proprietary platform into a commodity capability. Third, the buyer here is a large retailer with its own technology function, not a hospital purchasing clerk, so the power asymmetry that made the original lock-in stick is much weaker, and durability sits in the contract and the concrete rather than in workflow habit. The framework supplies the right checklist of mechanisms; its implied prediction about first-mover capture does not travel. Saying so is not a failure of the analysis but the most valuable sentence in it. Where the material came from, and what its method cannot do Lynda Applegate, Robert Austin and Warren McFarlan wrote from inside a particular research tradition, and a student should understand it before either trusting or attacking it. Harvard Business School builds theory from clinical case research: a researcher enters a firm, observes a real decision in detail, reconstructs it, and generalises cautiously from a small number of deeply examined instances. McFarlan and McKenney's strategic grid came out of that work, as did McFarlan and Nolan's treatment of outsourcing as an alliance rather than a contract, and their argument about information technology and the board of directors in the Harvard Business Review of October 2005. The method is good at three things. It reaches depth survey work cannot: what the executive believed, what the internal opposition said, what the sequence actually was. It recovers mechanism rather than correlation, which is what a practitioner needs, since you cannot act on a coefficient. And it discovers variables nobody had thought to measure; the grid exists because someone noticed that firms differed systematically in how far their operations depended on systems, at a time when nobody collected that as data. It is equally, and unavoidably, bad at other things. Small purposively chosen samples do not support generalisation, and the cases written up are disproportionately the interesting ones, so the tradition selects on the dependent variable and studies winners. Reconstruction after the event imposes a coherence on decisions that were messier at the time. Most seriously, a framework that classifies situations rather than predicting outcomes is very hard to falsify: any case can be fitted into a quadrant after the fact, and a scheme no evidence could refute is a vocabulary rather than a theory. This is the sharpest criticism of the field, and large-sample work of the kind Erik Brynjolfsson did on the productivity paradox exists precisely because case research could not settle whether technology investment paid at all. Acknowledge this early and in your own words. Markers reward a student who uses a framework while knowing what kind of claim it makes, and penalise one who treats a classification scheme as a law of nature. Two ways to lose marks The first characteristic error is retelling. A weak analysis reconstructs the narrative — the company was founded, the system was built, the competitor responded — and reaches the end without having made an argument. The tell is that most sentences are in the past tense and none contains a judgement. Every fact you repeat from the case must support a claim you are making; if it is not doing that work, cut it and spend the words on analysis. The second is applying a framework because it appears on the syllabus rather than because it fits. This produces the essay that runs every available lens across the case in turn, a paragraph each, concluding that all are relevant. They are not. Framework selection is itself an examined skill, and saying that a lens does not apply here, and why, beats a competent application of one that only half fits. Where two genuinely apply, say which is load-bearing for your recommendation and which is supporting. The framework in 2026 The case method is itself the framework under examination in this chapter, so it deserves the treatment the rest of this book gives to the grid and the portfolio: what still holds, what has changed, what it now under-describes. What holds is the core posture. Executives decide under insufficient information and are judged on the reasoning, and no development in technology has softened that. If anything it has hardened. A firm choosing a model provider, deciding how much of its own data to expose to a vendor, or committing to multi-year compute contracts is making exactly the kind of decision the method was built to rehearse: high fixed cost, uncertain payback, partial information, a competitor moving in parallel. Three things have changed. The first is pace. Cases about platform and AI-era firms can be overtaken within a single term, and students can look up what happened in seconds. The suspense that once did pedagogical work is gone, and what replaces it is a more demanding exercise: judge the decision strictly on what was knowable at the date, then examine separately whether the outcome vindicates the reasoning or merely rewards it, which are different things. The second is that a competent-looking case write-up can now be generated in moments by a model, which shifts the assessed skill towards what a model does not supply: judgement about which lens fits, identification of what is missing from the exhibits, and defence of a position under live challenge. Discussion and viva matter more to the method now, not less. The third change is what the method under-describes. The classical case turns on an identifiable executive at an identifiable decision point. A growing share of consequential decisions in platform and AI-driven firms are not made that way. They are made continuously, by systems retrained on their own outputs, inside firms whose competitive position is set partly by counterparties they do not control and partly by regulators who have not finished writing the rules. There is no Tuesday and no chair. The method handles this awkwardly, and the honest adaptation is to move the decision under examination upstream, from the operating choice to the governance choice about who may set the objective, what the system is permitted to optimise, and what evidence would trigger intervention. That is still a decision an executive makes on a date with insufficient information, so the method still works; but the question it asks has to be reframed for it to work. For the case analysis and the essay This material appears in assessment in two ways. Occasionally it is examined directly, in a question about the value or limits of case-based theory. Far more often it shows up as the quality difference between two scripts covering the same ground, one treating the case as an argument and the other as a story. Markers reward four distinctions from this chapter. The first is between the mechanism and the instrument: a student who writes that ASAP's advantage lay in proprietary terminals has missed it, and one who writes that it lay in re-engineering the buyer's ordering process, of which the terminals were the instrument of the day, has it. The second is between judging a decision and judging an outcome, which requires you to fix explicitly what was knowable at the time. The third is knowing what kind of claim a framework makes — classification, prediction or checklist — and using it accordingly. The fourth is explicit statement of the limits of your own analogy; examiners reliably reward the sentence beginning "the analogy breaks down at the point where", and just as reliably penalise its absence. The errors that cost marks are narrative retelling, framework tourism across the whole syllabus, importing a case's conclusion instead of its reasoning, and treating a company's later collapse as proof that the decision in the case was wrong. Three specimen questions: 1. "Case analysis. Reread the American Hospital Supply case. Stating the structural conditions on which its advantage rested, identify one contemporary firm in a different industry where the same three conditions hold. Assess whether the framework's prediction of durable advantage holds there, and specify the single variable most likely to break it." 2. "Frameworks in this field classify situations rather than predict outcomes, and are therefore difficult to falsify. Does this make them useless to a practising executive? Argue a position with reference to at least two named frameworks." 3. "A newly appointed chief executive dismisses a twenty-year-old strategic framework on the grounds that it predates the cloud. Write the two-page note you would send in response, identifying which parts of the objection are correct and which are not." Chapter 2. The Strategic Grid: How Much Should Technology Matter Here? The prior question most firms never ask Ask a board how its information technology is performing and you will get an answer about projects, budgets and outages. Ask how much technology ought to matter to the company, and the room goes quiet. That question comes first, and almost nobody asks it. It is what the strategic grid was built to answer. The grid is routinely misread as a scorecard: students place the case firm in the top-right box and call it "strategic" as though that were praise. The grid classifies the stakes, not the performance, and what follows from a placement is an allocation decision: how much chief-executive attention, how much board time, how much capital, and what kind of leader the function deserves. That allocation can be wrong in both directions. Under-investment is the famous failure: a firm treats technology as plumbing, a competitor rebuilds the basis of competition on it, and the plumbing firm finds it was in a different industry than it thought. Over-investment costs more than money: ambitious programmes in a business that does not need them consume the scarcest resource the company has, senior attention, and produce capability nobody will pay a premium for. Anxiety is not a strategy. The grid's contribution is to make the judgement explicit, arguable and revisable. Two axes: dependence today, pipeline tomorrow The framework comes from F. Warren McFarlan and James McKenney, set out in 1983 in Corporate Information Systems Management. It survives because its axes describe structural conditions rather than particular technologies. The first axis is the strategic importance of existing information systems to current operations: a question about dependence, best put operationally. What happens tomorrow morning if the systems stop? Not degrade — stop. In some firms people revert to telephones and spreadsheets and the week is recovered; in others, aircraft do not depart, payments do not clear, containers do not move, and the firm is finished within days. This is where managers most flatter themselves: a system can be expensive, complicated and central to the technology department's identity while the business would survive a fortnight without it. The second axis is the strategic importance of systems under development to the firm's future: a question about the pipeline. Not whether the roadmap is full — every roadmap is full — but whether anything in it would change the basis on which the firm competes. Most portfolios fail that test — replacements for ageing systems, regulatory work, post-acquisition integration, incremental efficiency, all necessary and none of it changing who wins. The axis is high only when something being built would alter what customers choose on or what the firm is able to sell. The axes are asymmetric in time, and the four combinations behave so differently that treating them alike is the root of most bad technology governance. The four quadrants and what each one demands The four positions are named Support, Factory, Turnaround and Strategic. Each implies a different management posture, budget shape, board relationship and kind of leader. Table 2 summarises them before they are taken in turn; the reasoning underneath each row is what earns marks. Table 2. The four quadrants of the strategic grid and what each implies. Quadrant Dependence now / impact ahead Management posture Characteristic error Sector Support Low / low Cost control; buy, do not build Over-investing out of anxiety Professional partnerships, property Factory High / low Reliability and continuity Starving the estate for novelty Airlines, utilities, shipping Turnaround Low / high Chief-executive sponsorship, ring-fencing Not noticing it Equipment makers going connected Strategic High / high Board attention, dual capability Assuming it is permanent Banks, insurers, retailers, platforms Support A Support position means low dependence today and low impact from the pipeline. Systems matter — payroll runs, invoices go out, the practice management system holds the client record — but nothing in them differentiates the firm, and nothing being built will. A commercial property investor, a mid-sized law firm, a specialist engineering contractor: these are businesses whose position rests on deal flow, judgement, relationships, land, licences or craft skill. Their systems are genuinely useful and entirely unremarkable. The correct posture is efficiency and cost control, pursued without embarrassment. Buy rather than build. Take the standard configuration of the standard package and change the process to fit it rather than the reverse. Resist customisation, which in a Support firm buys nothing and creates a permanent upgrade liability. The budget should be a low, stable, largely operating-expenditure line, benchmarked against peers, with a deliberately small discretionary component. Governance intensity should be low and the reporting line should reflect it: in a Support firm the technology function very often reports to the finance director, and that is appropriate rather than insulting. The person leading it should be a competent operational manager and a good buyer of services — someone who negotiates well, runs vendors hard and keeps things dull. A visionary in this seat is a hazard, because a visionary will look for a strategic programme to justify the role and will find one. Board attention should be minimal and periodic: an annual review of cost, risk and continuity, unless the position itself is being re-examined. The characteristic error is over-investment driven by anxiety rather than analysis. Partners read that their industry is being transformed, a consultancy confirms it, and a firm with thirty people and a stable client base commissions a platform. The money is recoverable; the eighteen months of partner attention are not. The subtler version is status-seeking inside the technology function: a manager who wants a larger role builds a case that the firm is really in Turnaround, and there is rarely anyone in the room equipped to contest it. The honest Support firm should still be clear about what it owes. Security and continuity obligations do not scale down with strategic importance; a law firm's confidentiality exposure is severe whatever quadrant it occupies. Low strategic importance is not low risk. Factory Factory means high dependence today and low impact from the pipeline. The business stops without the systems, and nothing being built will change how it competes. This is a large and under-discussed quadrant, because it lacks glamour and attracts less case-study attention than it deserves. Airlines are the standard example. An airline without its reservation, crew-rostering, load-planning and maintenance systems does not fly, and recovery takes days because crews and aircraft end up in the wrong places. Yet no reservation system now wins passengers. Utilities are the same: metering, billing and network-control systems are load-bearing and competitively inert. Container shipping belongs here too, as A. P. Moller–Maersk discovered in June 2017 when the NotPetya malware destroyed its Windows estate and the company was reduced to running terminals manually — an episode that illustrates the quadrant exactly, because Maersk's systems could not win it market share but very nearly cost it the business. In Factory, reliability is the whole job. Availability, recovery time, change control, capacity, patching discipline, tested failover and the ability to run degraded are not hygiene items beneath the attention of strategists; they are the strategy for this function. The right questions are how long recovery takes, whether it has been tested this year against a destructive scenario rather than a hardware failure, and who may decide to run manually. The budget should be weighted heavily to running and renewing the estate, with a stated and defended allocation to technical debt and continuity, and only a modest discretionary slice. The leader should be an operator — someone with a service-management temperament who has run large estates under load and is not bored by it. Board attention is real but narrow: continuity, resilience and major-incident readiness belong on the agenda at least annually, usually through the audit or risk committee, and the board should expect evidence of testing rather than assurance. The characteristic error is starving the estate to fund novelty. The pipeline offers nothing exciting, so a chief executive wanting a story redirects money and attention to a digital programme while deferring the unglamorous replacement of a system everything depends on. The second error is treating outages as technical events rather than as the materialisation of a business risk that was accepted, usually implicitly, when the renewal was deferred. Turnaround Turnaround means low dependence today and high impact tomorrow. The systems do not much matter to current operations, but something being built — inside the firm or by a competitor — will change the basis of competition. This is a transitional position by definition, and the most dangerous quadrant to occupy without knowing it. Netflix in about 2007 is the clean illustration. Its operating business was DVDs by post, and the warehouse and logistics systems running it were adequate rather than decisive. The streaming work under development was not yet adequate to anything: small, unproven and commercially marginal. It also redefined the industry. John Deere is the contemporary version — for most of its history a manufacturer whose position rested on engineering, dealer networks and brand, with systems that were operationally important but not decisive, and whose connected-equipment, telematics and precision-agriculture pipeline changes what a tractor is and what the firm sells. The management implication is unambiguous and is the one students most often miss. Turnaround is where the chief executive's personal attention is most required, and it is required because current dependence is low. When the systems do not run the business today, the organisation has no natural reason to care about them, and the new work gets governed like any other project — funded from the ordinary capital process, staffed with whoever is available and measured on cost variance. That treatment kills strategic initiatives reliably, not by rejecting them but by making them ordinary. The right posture is ring-fencing: separate funding with an explicit tolerance for uncertainty, a delivery group insulated from the operating rhythm, and direct sponsorship from the chief executive rather than a steering committee. The budget shape is distinctive — modest run cost alongside a disproportionate discretionary allocation, which will look wrong on any peer benchmark and should be defended anyway. The leader must be a business person with technical fluency and enough standing to argue with the executive committee, not a project manager. Board attention should be high and substantive: this is exactly when a board should ask what the firm is building, what it would do to competitors if it worked, and what the firm's position becomes if a rival gets there first. The characteristic error is simply not noticing. Turnaround is diagnosed retrospectively far more often than in time. Strategic Strategic means high dependence today and high impact tomorrow. Current operations run on the systems, and the systems being built will determine the competitive position. Banks and insurers are here and have been for decades: a bank is a set of information systems with a licence attached, and the work in its pipeline — payments, credit decisioning, fraud detection, onboarding — changes what customers can be offered and at what cost. Large retailers are here; Inditex's ability to move from design to store shelf and Walmart's replenishment infrastructure are competitive facts, not support functions. Platform businesses are definitionally here, since the product is the system. Management intensity must be high on both dimensions at once, which is harder than it sounds because the two demands are temperamentally opposed. The firm must run a Factory-grade operation — a bank that loses its payments rails for a day suffers regulatory and reputational damage no innovation programme offsets, as TSB's 2018 migration failure demonstrated — while simultaneously running a Turnaround-grade change agenda. Organisations tend to be good at one and staff accordingly. The distinguishing capability of a genuinely strategic technology organisation is holding both without letting either colonise the other. Board attention should be structural rather than occasional. McFarlan and Nolan argued in Harvard Business Review in October 2005 that firms in this position need a dedicated board-level mechanism for technology oversight in the way they have one for audit — contested then, now mainstream among banks and large platforms. The point is not the committee; it is that a firm whose competitive position and operational continuity both run on technology cannot govern it through a twenty-minute item in a crowded meeting. The budget should be large, explicitly split between running, renewing and changing the business, and defended as an investment portfolio rather than a cost line. The leader should be a full member of the executive team with a genuine seat at the strategy table. The characteristic error is assuming the position is permanent and therefore beyond argument. Once "we are a technology company" becomes an identity claim, every proposal inherits strategic status and the discipline the grid imposes disappears. The second error is confusing scale with advantage: a very large technology estate that every competitor also has is a Factory in expensive clothing. Movement, and the two transitions that hurt The grid is a photograph, and firms move. Two transitions account for most of the damage done to incumbents. The first is Support to Turnaround, which is what disruption feels like from the inside. Current operations do not change; what changes is that something under development — often by someone else — begins to alter what customers choose on. Blockbuster is the textbook instance: its systems were competent store and inventory support and its position rested on locations and studio relationships, and by about 2004 the pipeline question had a wholly different answer, with the firm managing a Turnaround problem under Support governance. Kodak is the same shape with a longer fuse. The second is Strategic to Factory, which is what commoditisation feels like. American Airlines and SABRE is the definitive case: a reservation system that was a genuine strategic weapon in the 1970s and early 1980s, shaping what travel agents saw, was neutralised by regulatory intervention over display bias, by rival systems and by online distribution. The capability did not degrade; it stopped differentiating. AMR spun Sabre off entirely in 2000, the correct structural response: if a capability is now infrastructure, run it as infrastructure or sell it. American Hospital Supply's ASAP terminals followed the same arc as electronic ordering standardised. Two consequences follow. The assessment must be repeated, annually and whenever a competitor does something unexpected; a position settled once and quoted for a decade carries false authority. And it belongs to the executive team rather than the technology function, which is a point about incentives rather than integrity: a function asked to rate its own strategic importance, knowing the rating sets its budget and reporting line, is not a neutral assessor. It supplies the evidence; the classification belongs to those who must live with it. McFarlan's competitive questions McFarlan also offered questions for testing whether information systems can change competitive position, forcing a claim of strategic importance to be specified rather than asserted. Can the systems build barriers to entry? Raise customers' switching costs? Change the basis of competition, shifting a market from price to service, or from product to outcome? Shift the balance of power with suppliers? Generate genuinely new products? Applied to John Deere in 2026 the answers are concrete. Barriers to entry: an installed base of connected machines generating agronomic data across many seasons and soil conditions is not something a new entrant assembles quickly. Switching costs: a farm holding years of field-level data, prescriptions and equipment configuration inside one manufacturer's platform faces a real cost in moving, which is why right-to-repair and data-portability disputes are strategically significant rather than merely legal. Basis of competition: the sale shifts from horsepower and reliability towards yield outcomes per hectare, a contest an engineering-led rival may not be organised to win. Supplier power: less pronounced, and worth saying so rather than forcing the framework. New products: subscription precision-agriculture services and equipment-as-a-service lines that did not previously exist, in the same family as Rolls-Royce's power-by-the-hour contracts. Answering four of five affirmatively, with the fifth honestly declined, is stronger analysis than answering five of five. Three ways the grid is misused The first misuse is self-congratulation. A technology function preparing a budget submission presents a grid with the firm in the Strategic quadrant, and the funding argument follows. The corrective is to demand evidence for each axis separately: what specifically stops tomorrow, and what specifically in the pipeline changes the basis of competition. The second is applying the grid to a whole conglomerate. A group containing a bank, a property arm and a logistics operation has no single position, and averaging them produces a placement that describes none of the businesses while misallocating attention to all three. The unit of analysis is the business unit competing in a market; a group-level answer is legitimate only when it drives a group-level decision. The third is confusing "strategic" with "important to me". A system a director uses daily, or that cost a great deal, or was difficult to build, is not thereby strategic; strategic means it changes competitive position. Enterprise resource planning implementations are the usual casualty — enormous, painful, necessary and almost always Factory work, to be governed for reliability rather than sold internally as transformation. Lidl's abandoned SAP programme shows what happens when a Factory-class replacement acquires ambitions of a different order. The framework in 2026 The obvious objection is that reality has overtaken the grid: almost every firm now runs its operations on software, so the dependence axis appears uniformly high, and if it has collapsed then only two quadrants remain and the framework has lost half its resolution. The objection is partly right. The Support quadrant has thinned dramatically. A law firm that loses document management and practice systems cannot work. The 2024 CrowdStrike incident made the point across every sector at once: firms that never called themselves technology-dependent were stopped by a software update. On the honest reading of the dependence axis, a great many firms have moved up into Factory — a real change since 1983. But the objection conflates dependence with differentiation, which is exactly what the second axis prevents. The question is not whether a firm needs software; it is whether anything it is building will change what customers choose on. For most firms the answer remains no, and the diagnosis is Factory: high dependence, competitively inert pipeline. This is the structural insight behind Nicholas Carr's "IT Doesn't Matter" (Harvard Business Review, May 2003), which is best read as a claim about where the mass of firms sits: universally necessary, rarely differentiating, to be managed for cost and risk. Carr was wrong about the Strategic quadrant and broadly right about Factory, and the grid explains why both can be true. Generative and agentic systems have made the pipeline axis live again. A firm whose operations depend on software but whose portfolio was competitively inert may now hold something that changes the basis of competition — in underwriting, claims handling, clinical documentation, legal research. That is a Factory-to-Strategic move, the most interesting transition of the current period. It is also where most unjustified claims are now made, which is why specifying the mechanism matters more, not less. What the grid under-describes is real. It says nothing about which capabilities a firm should own rather than rent, a question cloud and model providers have made central. It treats the firm as the unit of analysis when competitive position often sits in an ecosystem. And it does not capture concentration risk: Factory-grade dependence running through a handful of providers is a problem it was never designed to name. For the case analysis and the essay The grid appears in case questions in three reliable forms: an explicit instruction to position the firm; a question about how much board or executive attention the technology agenda deserves; and, most often, as an unstated requirement inside a question about whether a proposed investment is justified. Markers reward three distinctions. Evidence for each axis stated separately and drawn from the case: what fails and how fast, and what is specifically in the pipeline. A position argued rather than declared — "Factory, because X, though there is a case for Turnaround if the Y programme delivers" beats a confident single word. And movement: the best answers identify which quadrant the firm is moving from and towards, and date the transition to something in the case. The errors are predictable. Placing every firm in Strategic because technology is generally important. Treating the grid as a quality assessment of the technology function. Positioning a diversified group as a single entity. Drawing the conclusion but never converting it into management implications: what changes in governance, budget shape, board agenda and leadership. And accepting the technology function's own placement without noticing its interest. Three questions of the kind you should expect: 1. Using McFarlan and McKenney's strategic grid, position the firm described in the case and justify your placement with specific evidence for each axis. Identify the transition, if any, the firm is undergoing, and set out three changes to governance and resource allocation that your placement implies. 2. "The strategic grid has been rendered obsolete by the fact that every firm now depends on software." Evaluate this claim, distinguishing between dependence on technology and differentiation through it. 3. Apply McFarlan's competitive questions to a firm you judge to be moving between quadrants. Specify the mechanism by which its information systems could alter competitive position, and state which question it cannot currently answer affirmatively and why that matters. Chapter 3. Business Models, Capabilities and Value A student asked to describe a company's business model will usually answer with one of three things: what the company sells, how it makes money, or what it says about itself in its annual report. None of those is a business model, and the confusion is not merely terminological: it produces case analyses that praise a clever idea without asking whether the firm can execute it, and essays that treat a pricing change as a transformation. The framing Lynda Applegate brought to Corporate Information Strategy and Management insists that a business model is a compound object with three parts that must hold together, and that the interesting failures are failures of internal consistency rather than of imagination. Strategy, capabilities, value: the three-part anatomy The strategy is the choice set. It names the market the firm intends to address, the position it takes relative to the competitors and substitutes already there, and the value proposition it offers — what the customer gets, why it is better than the alternative, and for whom. This is the territory Porter's generic strategies and five forces describe. The capabilities are what makes the strategy deliverable. Applegate's list is deliberately broad: people, process, technology, partnerships, and the physical and intangible assets the firm controls. Capabilities are the operating system of the business: what a firm has learned to do repeatedly and at a cost that leaves something over. The value is what is returned, and to whom — the part students truncate most often, because they treat "value" as a synonym for profit. A model returns value to the customer, which is what keeps them coming back; to the firm, as margin, growth and option value; to investors, as a return on capital at acceptable risk; and to partners — suppliers, distributors, complementors — who withdraw if the model does not pay them enough to stay. Each return must be measurable, and the measures differ: time saved, return on invested capital, volume stability. A business model is not a strategy, because a strategy is only the first of the three parts. Nor is it a revenue model. A revenue model describes the mechanism by which cash arrives — subscription, transaction fee, advertising, licensing, usage. It sits inside the value component and says almost nothing about whether the firm can build what it has promised. Two firms can share a revenue model and have entirely different business models; two can share a value proposition and differ completely in the capabilities delivering it, which is where the outcome is usually decided. The three parts must be internally consistent because each constrains the others. A premium position requires capabilities that produce genuine differentiation and returns value as margin; a cost-leadership position requires capabilities in scale, process discipline and supply, and returns value through volume and asset turnover. Mixing the components produces expensive incoherence. General Electric's software venture is the cleanest recent illustration. GE's strategy in the mid-2010s was to become a leading industrial software company: it built the Predix platform and said publicly that it meant to be among the world's top ten software firms. The proposition was credible — nobody else had GE's installed base of turbines, engines and medical devices, or its knowledge of how they fail. The capabilities were not. GE knew how to run long-cycle, contract-negotiated industrial programmes; it had none of the software product management, release cadence, developer ecosystem or go-to-market motion a platform business requires, and tried to build them all at once while the parent was under acute financial pressure. Within a few years GE Digital had been sharply scaled back, ServiceMax bought and sold again, and the ambition quietly retired. That is a business model failure, not a technology failure, and no further engineering would have fixed it. Who is the customer, and what job is being done Analysing a value proposition begins with a question that sounds trivial and is not: who is the customer? In a single-sided business the answer is obvious. In a multi-sided business it is genuinely hard, and getting it wrong is the most common analytical error in case work. Take Spotify. The naive answer is the listener, who pays on the premium tier, with advertisers paying on the free tier. But the rights holders — labels, publishers, independent distributors — are not simply suppliers. They supply the catalogue, take the large majority of every pound of revenue, set the terms on which the service can exist at all, and consume promotional and analytical services the platform provides. A student who models Spotify as a firm selling music to listeners concludes that its margin problem is a pricing problem. One who sees three parties with distinct and partly opposed interests sees that the margin is structurally set by licensing terms, and that the moves which matter change the cost base — podcasts and audiobooks, where rights are owned or cheaply licensed. The second question is what job the product does: not what it is, what it does for someone. Spotify's job is not "provides music"; it is "removes the cost of acquiring, organising, storing and choosing music, everywhere, for a fixed monthly sum." The third question is what the customer would otherwise do — the honest alternative, including doing nothing. For Spotify's first decade the alternative was piracy and radio, both free; it had to beat free on convenience, and did. The fourth is what they will pay, anchored on that alternative and on whatever reference price the category has hardened around. Spotify held its headline price near the price of one album a month for roughly a decade, and only from 2023 raised it in significant steps. The tolerance for that told the market how the job had changed: the alternative was now a rival subscription, and switching meant abandoning years of playlists and recommendation history. Run those four questions — who, what job, against what alternative, at what price — on any business in a case and you have an analysis worth marks. Capabilities are the slow part Value propositions are easy to imagine, and a competitor can copy one in a quarter — announce it, price to it and advertise it before the year end. Capabilities take a decade, and that asymmetry is the most useful idea in this chapter. Zara is the canonical demonstration. Inditex's proposition is fashion responsiveness: new designs reaching stores in weeks rather than seasons, in small quantities, refreshed often enough to reward repeat visits. Every competitor understood that proposition by the late 1990s and many announced versions of it. What none could copy quickly was the capability underneath: fashion-sensitive items made in owned or nearby capacity in Spain, Portugal, Morocco and Turkey while stable basics are sourced far away; dyeing and finishing held late so colour decisions can be deferred; deliveries twice a week on a fixed schedule; short runs that make stock-outs a feature rather than a defect; and a replenishment cycle in which store managers transmit hard sales data and qualitative commentary — what customers picked up and put down, what they asked for — back to the design teams in Arteixo on a rhythm measured in days. Notice where the information system sits in that description. It is not supporting the capability; it is the capability. The ordering and feedback loop is what converts thousands of daily store observations into a design decision fast enough to matter. Remove it and the model does not degrade gracefully, it stops. This is the distinction worth carrying into every case: in some firms information technology supports a capability that would exist without it; in others it constitutes the capability, and no organisational or contractual workaround reproduces it. The evidence for Zara's advantage is not its revenue but its markdown behaviour — it has consistently sold a far larger share of output at full price than conventional fashion retailers, which is exactly what a short, accurate replenishment cycle buys. Two shorter cases sharpen the point. Ocado's capability is automated warehousing — grid-based storage with bots picking orders under a central control system — and the firm found that the capability, not the grocery business, was the asset, reconstituting itself as a licensor to Kroger, Morrisons, Casino and Coles. The lesson cuts both ways: a licensed capability's value depends wholly on the licensees' economics, and when partners slowed their rollouts Ocado's equity fell heavily from its 2020 peak and it lost its FTSE 100 place. Rolls-Royce's engine health monitoring likewise constitutes a business model rather than a service feature: power-by-the-hour contracting, in which the airline pays per flying hour while Rolls-Royce retains the maintenance risk, is underwritable only because in-flight sensor data makes failure predictable. It also transfers a risk whose size the firm discovered in 2020, when flying hours collapsed and the revenue with them. What networked information changed Applegate's treatment of the network economy is an argument about economics, not about websites. Four mechanisms do the work. The first is the collapse of the trade-off between reach and richness, set out by Evans and Wurster in Harvard Business Review in 1997. Before cheap networks a firm could communicate richly with a few — a salesperson in a room — or thinly with many, in a broadcast advertisement. Bandwidth and shared standards broke the trade-off, and every business whose position depended on it — branch networks, travel agencies, car dealerships, financial advisers — became vulnerable at once, to firms with nothing else in common. The second is transaction and coordination cost, which takes us to Coase. His 1937 answer to why firms exist at all was that using the market has costs — searching, negotiating, contracting, monitoring — and a firm is worth forming whenever internal coordination is cheaper. It follows that if networked information lowers the cost of market transactions, the efficient boundary of the firm moves inward and what was owned becomes contracted. Malone, Yates and Benjamin made exactly this prediction in 1987, and much of the next thirty years bore it out. Cisco built a business on it, having most of its equipment made by contract manufacturers coordinated through shared systems that made outsourced factories behave, informationally, like internal ones — and demonstrated the risk in 2001, when that tightly coupled system propagated optimistic demand signals through the supply base and produced a multi-billion-dollar inventory write-down. Li & Fung went further, orchestrating dispersed manufacturing across thousands of factories it did not own, assembling a bespoke supply chain per order. What happened since is instructive: as brands built their own sourcing systems and platforms reached factories directly, the orchestrator's margin was squeezed and Li & Fung was taken private in 2020. Falling coordination costs erode the position of intermediaries, including those created by falling coordination costs. The third mechanism is disintermediation and its rebound. Dell's build-to-order direct model removed the reseller, which cut cost and — because customers paid before Dell paid suppliers — produced a negative cash conversion cycle that funded growth internally. But disintermediation rarely ends with fewer intermediaries; it ends with different ones, reforming wherever aggregation, trust or search reduction remains valuable. Dell's advantage narrowed as component prices stabilised and the mix shifted to notebooks bought in shops; it returned to channels, went private in 2013 and re-listed as a substantially different business. The fourth is the emergence of models networked information does not improve but makes possible at all: marketplaces where the platform owns no inventory, subscription and usage-based pricing for physical goods, and outcome-based contracting of the Rolls-Royce kind. Shopify — merchant software plus payments, earning subscription and a share of transactions — is inconceivable without networked infrastructure. Its attempt to add physical fulfilment was a capability of an entirely different kind, and after acquiring its way into logistics it sold that business to Flexport in 2023. Platform economics do not confer warehouse economics. Changing the model, and the arithmetic that decides it Changing the business model is frequently more consequential than changing the product, and incumbents find it disproportionately hard for a reason that has nothing to do with intelligence: the existing model pays everyone's salary. Its metrics are the reporting system, and its margin the standard against which every new proposal is judged. This is the resource-allocation mechanism at the centre of Christensen's account of disruptive innovation: incumbents do not fail because they cannot see the new model, they fail because a rational internal process correctly declines to fund something with a worse margin and a smaller market, right up until the smaller market is the only one left. Kodak is the case, and it is usually told wrongly. Its engineers built a working digital camera in 1975 and the company held substantial digital imaging patents. The failure was not blindness to the technology; it was that Kodak's model returned value through consumable film and chemistry at high margin, and every digital proposal was judged against that margin. The firm could see the future and could not fund it, and filed for Chapter 11 in 2012. Blockbuster has the same shape: late fees were a material part of revenue, and subscription without them wrecked the stores' arithmetic. Adobe is the instructive success. In 2013 it stopped selling perpetual Creative Suite licences and moved its customer base to Creative Cloud subscriptions — a deliberate act of revenue destruction, since a subscription is recognised over time and a licence on sale. What distinguished Adobe from Kodak was not vision but three things. It told investors in advance exactly what the trough would look like and why. It changed the measures the company was run on, reporting recurring revenue and retention rather than quarterly licence bookings, so internal decisions stopped being judged against the model being replaced. And it accepted a lower entry price for a wider base. Microsoft made a structurally similar transition to Microsoft 365 and Azure. The decisive move, every time, is to change what the firm measures before changing what it sells. Which brings us to unit economics. Four numbers carry the argument. Contribution margin is revenue per unit less the variable cost of delivering that unit — what each transaction contributes to fixed costs and profit. Customer acquisition cost is fully loaded sales and marketing spend divided by customers actually acquired. Lifetime value is the discounted contribution a customer produces before churning. Payback period is how long that contribution takes to return the acquisition cost. A model is sound when lifetime value comfortably exceeds acquisition cost and payback is short enough that growth does not consume more cash than the firm can raise. These are scale-dependent, and a model that works at one scale may fail at another in either direction. Density-dependent businesses — grocery delivery, ride-hailing, field service — have contribution margins that turn positive only above a local density threshold, which is why national averages conceal profitable cities subsidising unprofitable ones. Conversely, software firms comfortably profitable renting infrastructure can find the arithmetic inverts at scale: Dropbox's migration of most of its storage off public cloud onto its own infrastructure materially improved gross margin, and would have been wrong at a tenth of the volume. All of this is a technology executive's business. Nearly every significant technology decision — where compute runs, how much is automated, what is bought and what is built, how much inference a feature consumes — changes a unit economic. An executive who frames a proposal as capability, resilience and architectural elegance is making an argument the finance director cannot evaluate. One who says the change cuts cost to serve per active account by a stated amount and shortens payback by a quarter without increasing churn is making an argument that wins. That translation is not a concession to commercial pressure; it is the only form in which a technology argument can be decided. The framework in 2026 Apply the triad to the position every firm is now in with generative and agentic AI and it does most of the work immediately. The strategy layer is where the public noise is: firms announce AI-enabled propositions constantly, and the announcements are close to worthless as evidence, because the underlying model capability is available to everyone through an API at published prices. A proposition built on model access alone is copyable in a quarter, which is exactly the condition under which capabilities decide the outcome. What still holds, harder than before, is the primacy of capabilities. The firms extracting real value have something a competitor cannot rent: proprietary data with the rights to use it, a workflow the model is embedded inside rather than bolted beside, an evaluation apparatus that says whether outputs are improving, and a distribution position that puts the capability in front of users who already trust them. The Zara lesson transfers: the advantage is not the technology component, it is the organisational loop the component sits inside. What has changed is a load-bearing assumption of the network economy argument, written for a world in which the marginal cost of serving one more digital transaction tended to zero — much of the reasoning about scale, free tiers and winner-take-most dynamics depends on it. Inference is not free. A generative feature carries a real, variable, per-request cost rising with usage and with quality, so for the first time in two decades software firms run businesses with a meaningful cost of goods sold per interaction. That puts contribution margin back at the centre of product decisions, and explains why usage caps, tiering and model routing are commercial questions rather than engineering details. Two things the framework under-describes. First, the case where a firm's critical capability is rented from a supplier who also sells to its competitors and can move up the stack into its market: the capabilities column assumes that what you have built, you hold, whereas a dependency on a foundation model provider is held only by contract. Second, the value column needs widening. When a capability is constituted by data drawn from customers, by content whose creators were not party to the arrangement, and by energy consumed at industrial scale, the stakeholders bearing value include parties the original framing never listed. Asking "value to whom, measured how" remains the right discipline; the list of whoms is longer. For the case analysis and the essay Business model questions arrive in three forms: describe and assess the firm's model; explain why a rival cannot simply copy it; advise whether the firm should change it. All three reward the same move — separating the three components and testing them against each other rather than describing the company in narrative order. Markers reward four distinctions. Strategy versus business model: a candidate who treats the value proposition as the whole model has nothing to say about execution. Business model versus revenue model: if your analysis would survive the firm switching from subscription to transaction pricing, you were analysing the revenue model. Proposition versus capability, the highest-value one — which capability carries the advantage, how long it took to build, and whether technology constitutes it or merely supports it. And naming which stakeholder receives value, and by what measure, rather than asserting that a model "creates value". The errors are predictable: describing the technology rather than the capability it constitutes; assuming an attractive proposition is a defensible one; praising a network effect without saying who is on each side and what makes them sticky; treating scale as automatically favourable when contribution margin is negative; and writing about the network economy in the present tense of 1999. Cite Li & Fung, Dell or Cisco by all means, but say what has become of them since, because the marker is testing whether you can date evidence. Three specimen questions: 1. "Value propositions are cheap and capabilities are expensive." Evaluate this claim using the three-part business model framework, drawing on at least two firms in which information technology constitutes rather than supports the critical capability. 2. Case prompt. You advise the board of a mid-sized industrial equipment manufacturer that sells machines outright and earns a further margin on spare parts and service visits. Management proposes an outcome-based contract in which customers pay per unit of output while the firm retains ownership and maintenance risk. Set out the capabilities required, the unit economics that decide whether it works, the stakeholders whose returns would change, and what would have to be true for you to recommend proceeding. 3. Using Christensen's account of disruptive innovation, explain why incumbents find business model change harder than product change. Contrast one firm that made such a transition successfully with one that did not, and identify what distinguished them beyond foresight. Hashtags: #TheITExecutivesPlaybook #CorporateInformationStrategy #ITStrategy #TechnologyGovernance #StrategicGrid #McFarlanStrategicGrid #TechnologyDependence #TechnologyPipeline #SupportQuadrant #FactoryQuadrant #TurnaroundQuadrant #StrategicQuadrant #CompetitiveAdvantage #BusinessModels #TechnologyCapabilities #NetworkEconomy #ITInvestment #TechnologyPortfolio #ITOutsourcing #TechnologyRisk #BoardTechnologyOversight #TechnologySourcing #DigitalTransformation #ExecutiveDecisionMaking #FutureOfCorporateITStrategy

Download the Book (PDF): Introduction Sometime in the autumn of the year 8 CE, the most fashionable poet in Rome received an order from the emperor Augustus to leave the city and go to Tomis, a garrison town on the western shore of the Black Sea, near the mouth of the Danube. Ovid was not tried. His property was not confiscated. He was not formally stripped of his citizenship; the order was a relegatio, a milder form of banishment than the full exilium, and he took pains in his letters home to insist on the distinction. He never learned exactly what he had done wrong, or at least never said. He offered two causes, "a poem and a mistake" (carmen et error), identified the poem as his playful manual of seduction, the Art of Love, and left the mistake in a silence that scholars have been trying to fill for two thousand years. He spent the rest of his life, perhaps nine or ten years, writing verse letters back to Rome: to his wife, to friends who had gone quiet, to the emperor who never relented. They are among the first sustained works of literature to take the condition of being expelled from one's home as their permanent subject. The first poem of the Tristia opens with the poet addressing his own book: "Little book, you will go to the city without me — I don't begrudge it." The joke is sad and exact. The text can travel where its author cannot. It will walk the streets he remembers and be handled by the readers he has lost, while he stays behind among people whose language he does not speak. Nearly everything that later writers would do with exile is already present in that opening gesture: the split between the self and its words, the fantasy of a return conducted by proxy, the home that becomes more vivid the longer one is kept from it, the uneasy suspicion that distance is making one a different person and perhaps a better writer. This book is about that body of writing and the conditions that produced it. Its subject is the literature created by people who were forced out of their countries, or who fled because staying had become impossible, and who then made their displacement into material. The range is wide: Qu Yuan wandering the marshes of the southern kingdom of Chu, Dante tasting "how salty is another's bread" in the courts of northern Italy, Victor Hugo on Guernsey, the Russians of Berlin and Paris after 1917, the Germans who scattered to California and Manhattan after 1933, the Spanish Republicans who crossed the Pyrenees in the winter of 1939, the Latin Americans who fled the juntas of the 1970s, the Palestinian poets who wrote from Beirut and Tunis and Paris, and the Kenyan, Somali and Nigerian novelists who carried their countries abroad in manuscript. It also takes in writers who never left at all and yet described themselves, with good reason, as exiles in their own land. The argument The argument of the book can be put simply. Exile is usually read as a story of loss, and it is one. But the literature it produced is best understood not as a lament for what was lost but as a set of techniques for living, thinking and writing in an interval: between two languages, between a remembered country and an actual one, between the self one was and the self one is being forced to become. These techniques are recognisable across centuries and continents. The exile makes language strange and so becomes acutely conscious of it. The exile reconstructs the homeland in memory and discovers that the reconstruction is an invention, and must then decide whether to defend the invention or to examine it. The exile is compelled to hold two or more frames of reference at once, and this doubled vision, which Edward Said called "contrapuntal," is the most valuable thing exile writing has to offer. That value, however, has a price, and the book insists on counting it. The modern West has a romance of exile. It flatters the displaced intellectual as a figure of heroic lucidity, a seer freed by homelessness from the provincialism of the settled. The romance has some truth in it, but it depends on a small number of famous cases — Joyce, Nabokov, Brodsky, Kundera — and it hides a great deal. It hides the writers who stopped writing. It hides the women who carried the practical burdens of displacement while the men wrote about its metaphysics. It hides the enormous difference between a celebrated dissident received at an American university and a stateless family in a transit camp. And it risks turning a political punishment, imposed by states on people who had displeased them, into an aesthetic opportunity, as though the dictator had done the poet a favour. A serious reading of this literature has to keep both things in view: that exile has produced some of the most searching writing of the last two thousand years, and that it is, in Said's phrase, "terrible to experience." What counts as exile Any book on this subject must decide where its boundaries lie, and the boundaries are contested. In the strictest sense, exile is a juridical act: a sentence of banishment, imposed by an authority, which forbids return. Ovid and Dante were exiles in this sense. So were the Soviet writers stripped of citizenship and deported, such as Aleksandr Solzhenitsyn in 1974 and Joseph Brodsky, pushed out in 1972. But most of the people who have written as exiles were not formally banished. They fled arrest, or war, or a regime they could not live under, and then found that they could not go back. Others left more or less voluntarily and later discovered that the door had closed behind them. Still others, like James Joyce, chose distance as an artistic discipline, and it is a real question whether a man who could have returned to Dublin on any day of his life belongs in the same category as a Chilean poet who would have been arrested at the airport. This book takes a working definition. An exile, for its purposes, is a writer who is separated from a homeland by a force they did not choose, or by a choice made under pressure they could not reasonably resist, and for whom that separation becomes a central condition of the work. The definition is loose at the edges on purpose. It admits the internal exile, the writer silenced or confined within his or her own country, because the literature of internal exile turns out to share much with that of the banished. It admits the self-exiled where the self-exile was a response to real constraint. It treats the neighbouring categories — the refugee, the émigré, the expatriate, the migrant, the member of a diaspora — as related but distinct, and one chapter is given to the question of why the distinctions matter. The scope is also unavoidably selective. The literature of exile is vast and written in dozens of languages. The emphasis here falls on European, Russian, Latin American, Middle Eastern, African and South Asian writing, with some attention to classical China, because these traditions have produced the most sustained reflection on the subject and because the critical vocabulary most readers will meet was built largely out of them. The choice leaves out a great deal, and readers who know the Armenian, Korean, Tibetan, Vietnamese or Haitian literatures of displacement will find those traditions touched on too lightly. The aim is not a survey but an argument, illustrated from cases chosen because they show something clearly. How the book proceeds The chapters move from origins to consequences. The first chapter examines banishment as one of literature's oldest genres, reading Ovid, Qu Yuan, Su Shi, Dante and Hugo as writers who established a set of postures — the complaint to the sovereign, the appeal to posterity, the conversion of punishment into vocation — that later exiles would inherit whether they knew it or not. The second takes up language, the most intimate thing an exile loses: the writers who switched tongues, such as Conrad, Nabokov, Beckett, Kundera and Agota Kristof, and those who refused to, such as Czesław Miłosz and Isaac Bashevis Singer, and what each choice cost. The third chapter turns to nostalgia and the mythology of the lost homeland, drawing on Svetlana Boym's distinction between a nostalgia that wants to rebuild the home and one that is content to ache for it, and following the construction of "imaginary homelands" in Nabokov, Joyce, Rushdie and Mahmoud Darwish. The fourth looks at exile communities as political and literary institutions: the Russian emigration after 1917, the German exile after 1933, the Spanish Republicans in Mexico, and the older precedent of Alexander Herzen's free press in London. The fifth considers the exile who never leaves — Osip Mandelstam in Voronezh, Anna Akhmatova in Leningrad, the writers of the Southern Cone under dictatorship — and the particular experience of women in exile, whose stories fit badly into the heroic template. The sixth chapter addresses hybridity: the negotiated, doubled identities that exile produces, the theories that have been built to describe them, and the objections those theories have met. The seventh draws the lines between exile, refugee, émigré and migrant, and asks what the romance of the exiled artist conceals. The eighth is about return, which almost never happens as it was imagined, and about the writers who discovered that the country they had carried with them no longer existed on any map. The conclusion asks what, after all this, the literature of exile has to say to a century in which more people are displaced than at any time since the Second World War. A note on quotation. Where the words of a writer are well established and short enough to quote, they are quoted; where they are not, they are paraphrased and attributed. Translations are standard ones unless noted. The notes at the end of the book give sources, and the further reading list points to the works with which a curious reader might continue. CHAPTER 1 Banishment as Genre Long before anyone theorised exile, poets had worked out how to write it. The earliest literature of banishment was not a response to a mass movement of peoples but to a precise political act: a ruler removing a single troublesome subject from the centre of power. The writing that resulted was addressed, openly or covertly, to that ruler, and to the capital from which the writer had been cut off. It was petition, complaint, self-defence and self-advertisement at once. Out of these circumstances a genre emerged, with conventions that proved astonishingly durable. A Soviet poet deported in the twentieth century, or a Chilean novelist writing from Caracas, was working, knowingly or not, in a form whose basic moves had been fixed by a Chinese minister, a Roman love poet and a Florentine politician. This chapter reads those founders. Its claim is that the classical literature of banishment established three postures that later exiles would inherit and vary: the loyal complaint, in which the exile protests innocence to the power that expelled him; the appeal to posterity, in which the exile goes over the sovereign's head to future readers; and the conversion of punishment into vocation, in which the exile discovers that separation has made him the writer he was meant to be. Each posture has its own rhetoric, and its own blind spots. The loyal minister and the southern marshes The Chinese tradition supplies the oldest named figure. Qu Yuan, according to the account given by the historian Sima Qian around the start of the first century BCE, was a nobleman and adviser at the court of King Huai of Chu, a large state in the Yangtze basin, in the late fourth century BCE. Slandered by jealous rivals, he lost the king's confidence and was sent away from court; under Huai's successor he was banished again, to the south. He wandered the region of lakes and rivers, composing poems, and finally, despairing of his state's corruption and its looming defeat by Qin, drowned himself in the Miluo River. The Dragon Boat Festival is traditionally said to commemorate the search for his body. How much of this is history is disputed. The poems attributed to him were gathered in the anthology known as the Chuci, the Songs of the South, which reached its received form under the Han dynasty, and modern scholars have questioned whether a single author wrote them, or whether the biography was assembled from the poems rather than the other way round. For the history of exile literature, the uncertainty hardly matters. What matters is the figure that the tradition fixed. The central poem, the Li Sao — usually rendered as "Encountering Sorrow" — is a long first-person lament in which the speaker recounts his noble descent, his cultivation of virtue, symbolised by fragrant herbs worn as ornaments, and the malice of those who drove him from his lord's side. He then embarks on a visionary journey through the heavens, courting goddesses who will not have him, before looking down at his old home and refusing to leave it behind entirely. The Li Sao established what might be called the loyal complaint. The speaker is not a rebel. He does not reject the king; he rejects the slanderers who have come between them. His banishment is a misunderstanding, a failure of the ruler's judgement induced by bad counsel. His poetry is both a demonstration of his virtue, which the king has failed to see, and a plea to be seen again. This posture had enormous consequences in Chinese literary culture, where the banished official writing poetry became a stock figure, and where later exiles consciously modelled themselves on Qu Yuan. Jia Yi, demoted to the south in the second century BCE, wrote a rhapsody lamenting Qu Yuan as he crossed the Xiang River, casting himself as the dead minister's successor. The template allowed a writer to protest injustice without questioning the legitimacy of the order that had punished him. The most famous practitioner in the later tradition shows how much range the template allowed. Su Shi, the Song dynasty poet, calligrapher and statesman better known by his literary name Dongpo, was arrested in 1079 on charges that his poems had slandered the government's reform policies. The episode is remembered as the Crow Terrace poetry case, after the nickname for the censorate where he was held. He escaped execution and was banished in 1080 to Huangzhou, a minor town on the Yangtze, with a nominal post and no real duties. There he farmed a plot on an eastern slope, from which he took the name Dongpo, "Eastern Slope," and wrote some of the most celebrated works in Chinese literature, including the two prose-poems on the Red Cliff composed in 1082. What is striking in the Red Cliff rhapsodies is how far Su Shi has moved from the loyal complaint. The first rhapsody describes a moonlit boating trip on the river near the site of a famous battle of the third century. A guest plays a mournful tune on a flute and reflects that the great heroes of the past are gone and that human life is a mayfly's span against the endless river. Su Shi answers him with a meditation on change and constancy: seen from the point of view of change, heaven and earth do not last an instant; seen from the point of view of what does not change, we and all things are inexhaustible, and the breeze on the river and the moon over the hills belong to no one and may be enjoyed without end. The speaker does not plead to be recalled. He turns banishment into an occasion for philosophical composure. Later in life Su Shi was sent further south, to Huizhou and then, in 1097, to the island of Hainan, at the time regarded as the edge of the civilised world. He was pardoned in 1100 and died the following year on his way back north. Between Qu Yuan and Su Shi lies the whole arc of classical banishment writing: from the lament that insists on return to the serenity that makes return almost irrelevant. Both are responses to the same political fact, and both address the sovereign, one by pleading, the other by demonstrating that the sovereign's punishment has failed to diminish its target. Ovid on the Black Sea The Roman case gives the loyal complaint its most elaborate and most ambiguous form. Ovid had been, until 8 CE, the wittiest and most successful poet in the capital, the author of the Amores, the Heroides, the Art of Love and the Metamorphoses, the last still unrevised when the order came. At Tomis he wrote five books of Tristia, "sad things," and four books of Epistulae ex Ponto, "letters from the Black Sea," as well as a strange curse-poem, the Ibis, against an unnamed enemy at Rome. These poems are, in one sense, a sustained exercise in self-pity. Ovid describes the cold, the barbarian raids across the frozen Danube, the wine that freezes into the shape of the jar and must be served in chunks, the arrows tipped with poison, the absence of books, the absence of anyone to talk to. Historians and archaeologists have noted that Tomis was a Greek city of some age and was probably less wild than he claims. The exaggeration is part of the rhetoric. Ovid is building a case for mercy, and the worse Tomis sounds, the crueller it seems to keep a Roman poet there. He also builds a case for his own innocence, or at least for the smallness of his fault. The famous formula, carmen et error, "a poem and a mistake," in the second book of the Tristia — which is a single long verse letter to Augustus defending the Art of Love — divides the charge in two. The poem he can defend, and does, at length, with a catalogue of earlier poets who wrote about love without being punished. The mistake he refers to only obliquely: he saw something he should not have seen, he says, and his eyes were to blame. The attempt to identify the mistake — involvement in a scandal around Augustus's granddaughter Julia, who was banished in the same year, or some knowledge of a political conspiracy — has generated centuries of speculation and no consensus. A small number of scholars have even proposed that the exile was a literary fiction and that Ovid never left Rome, a view most specialists reject but which has the merit of reminding us how thoroughly Ovid made his exile into a performance. The performance matters because it anticipates something that recurs in almost all later exile writing: the exile's awareness that his suffering is also his material, and that the material is good. Ovid is explicit about the paradox. His poems of exile are worse, he says repeatedly, than his earlier work, because his talent has been dulled by misery and by the lack of Latin speakers around him. But they are also, obviously, crafted with great care, and they sustain his literary identity in the only way still open to him. The first poem of the Tristia, in which the poet sends his book to Rome without him, dramatises the split. The book will enter the city in a shabby state, without a decorated cover, as befits a mourner; it will look for a home on the shelves of the public libraries and may be turned away. The author's body is at Tomis; his textual self goes on living at the centre. Ovid also founded the linguistic complaint that later chapters of this book will follow. He tells his correspondents that he has had to learn the languages of the Getae and the Sarmatians to make himself understood, that he fears his Latin is decaying, and — in one letter from Pontus — that he has even composed a poem in Getic, in praise of the imperial family, which the local audience applauded. Whether or not this happened, the claim is a remarkable one: the Roman poet made barbarian by his surroundings, writing in a language no Roman could read. The two millennia of writers who have worried that exile was eroding their mother tongue begin here. He never came home. Augustus died in 14 CE; his successor Tiberius did not recall him. Ovid died at Tomis around 17 or 18 CE. His exile poetry was read throughout the Middle Ages and the Renaissance as the model of the genre, and when Aleksandr Pushkin was sent south by Alexander I in 1820, to Bessarabia, close to where Tomis had stood, he wrote a poem addressing Ovid as a fellow exile on the same shore, comparing the Roman's sufferings with his own and claiming, with some bravado, that he bore them with less complaint. Dante and the bread of others If Ovid created the loyal complaint in its Western form, Dante transformed it into something larger: an exile that became the organising principle of a cosmic poem. In 1301 Dante Alighieri was one of the leaders of the White Guelph faction in Florence and had served a term among the city's priors. While he was away on an embassy to Pope Boniface VIII, the rival Black Guelphs seized power with papal and French support. In January 1302 he was sentenced in his absence on charges of corruption, fined, and barred from office; in March the sentence was increased, and he was condemned to be burned alive if he ever came within the city's reach. He spent the remaining nineteen years of his life moving between the courts of northern Italy — Verona, the Lunigiana, the Casentino — before settling in Ravenna, where he died in 1321. The Divine Comedy was written almost entirely in exile, and exile runs through it. The fictional date of the journey is Easter 1300, before the banishment, which allows Dante to have the souls he meets in the afterlife prophesy his coming fate. The most famous of these prophecies comes in the seventeenth canto of Paradiso, spoken by his great-great-grandfather Cacciaguida. You will leave behind everything you love most dearly, Cacciaguida tells him; this is the first arrow that the bow of exile shoots. And then the lines that every writer on exile since has quoted: "Tu proverai sì come sa di sale / lo pane altrui, e come è duro calle / lo scendere e 'l salir per l'altrui scale" — "You shall learn how salt is the taste of another's bread, and how hard a path it is to go down and up another's stairs." The image is domestic and exact: the bread of Tuscany was baked without salt, so the bread of other cities literally tasted different. Dependence on patrons, climbing their stairs, eating at their tables, is the daily texture of the exile's humiliation. Cacciaguida goes further. He tells Dante that his fellow exiles, the other Whites, will prove foolish and treacherous, and that it will be to his honour "to have made a party by yourself." This is the decisive move. Dante converts the misfortune of being expelled from one faction and then alienated from his own into a vocation of solitary judgement. The exile belongs to no party, and so can see all parties truly. The Comedy sits in judgement on popes, emperors and Florentine families with an authority that derives, in part, from the author's having been placed outside every earthly allegiance. Banishment becomes the precondition of vision. Dante also produced, in his unfinished Latin treatise on vernacular language, De vulgari eloquentia, one of the earliest theoretical statements of exile cosmopolitanism. Mocking those who think their native town is the finest place under the sun and their dialect the finest language, he writes that "we, whose homeland is the world, as the sea is to fish," love Florence so much that we suffer exile unjustly, and yet judge by reason rather than by feeling. The sentence holds both halves of the exile's condition in tension: an attachment to the lost city so strong that it hurts, and a claim to a wider homeland that the attachment cannot contain. The loyal complaint did not entirely disappear. In 1315 Florence offered an amnesty to exiles willing to pay a fine and undergo a ritual of public penance. Dante refused. In a letter to a Florentine friend he described the terms as unworthy of a man who had preached justice and suffered wrong, and he asked whether he could not look upon the sun and the stars from anywhere, and contemplate the sweetest truths under any sky, without first making himself inglorious before the people of Florence. He would not return except by a way that did not diminish his honour; if no such way existed, he would never return. He never did. Other shores The founders were not only Chinese and Latin. The Hebrew Bible bequeathed to all later Jewish and Christian writing the collective exile of the Babylonian captivity, after the destruction of Jerusalem in 587 or 586 BCE, and Psalm 137 gave that exile its most enduring expression: "By the rivers of Babylon, there we sat down, yea, we wept, when we remembered Zion." The psalm's central question — "How shall we sing the Lord's song in a strange land?" — asks whether art can survive transplantation, and its answer is a vow of memory: if I forget thee, O Jerusalem, let my right hand forget her cunning. It is also, in its final verses, a curse on the captors, a reminder that exile writing has always had its vengeful strain. The Old English elegies preserved in the tenth-century Exeter Book, particularly The Wanderer and The Seafarer, describe a different kind of expulsion: the fate of the man who has lost his lord and his hall-companions and must travel alone over the winter sea. The exile in these poems is a social rather than a political category; he is cut off from the web of obligation and gift that gave life meaning. The Wanderer moves from personal grief to a general meditation on the transience of all earthly things, a turn that made the poem congenial to its Christian copyists. The Arabic tradition offers the case of al-Mu'tamid ibn Abbad, the poet-king of Seville, deposed by the Almoravids in 1091 and carried off to captivity at Aghmat in Morocco, where he died a few years later. His poems from captivity, lamenting the sight of his daughters spinning for wages and his own fetters, became a byword for the reversal of fortune. And France supplied the nineteenth century's grandest instance of the genre. When Louis-Napoléon Bonaparte seized power in December 1851, Victor Hugo, who had opposed him in the Assembly, fled to Brussels and then to the Channel Islands, first Jersey and from 1855 Guernsey. From there he wrote Napoléon le Petit and Les Châtiments, verse denunciations of the new emperor, as well as Les Contemplations and much of Les Misérables. When an amnesty was offered in 1859 he refused it, declaring that he would return when liberty returned. In one poem of Les Châtiments he vowed to hold out if only a thousand remained, or a hundred, or ten — and if only one remained, he would be that one. He came back in September 1870, after the emperor's defeat at Sedan, to a hero's welcome. The major figures of this chapter can be set out together, as in Table 1, which shows how consistently the same few postures recur across very different cultures. Table 1. Founding figures of banishment writing Writer Expelled by Exiled to Key exile work Posture Qu Yuan Chu court Southern Chu Li Sao Loyal complaint Ovid Augustus, 8 CE Tomis Tristia Plea for mercy Su Shi Song court, 1080 Huangzhou, Hainan Red Cliff rhapsodies Composure Dante Florence, 1302 Verona, Ravenna Divine Comedy Solitary judgement al-Mu'tamid Almoravids, 1091 Aghmat Captivity poems Reversal of fortune Victor Hugo Napoleon III, 1851 Jersey, Guernsey Les Châtiments Defiant refusal What the founders left Three features of this early literature deserve emphasis, because they set terms that later exiles would inherit. First, classical banishment writing is addressed to power. Its implied reader is the sovereign, or the city, or the court, and its purpose is to act upon that reader: to win recall, to shame, to assert the exile's continued relevance. This is quite different from the literature of mass displacement in the twentieth century, much of which is addressed to strangers in the host country, or to fellow exiles, or to no one in particular. The single exiled writer confronting the single ruler is a dramatic configuration, and its grandeur is part of what later exiles found attractive. Hugo on his rock facing Napoleon III is a pose borrowed, consciously, from a long line of predecessors. Second, the founders established the idea that exile could be productive. Ovid complains that it has ruined his talent while producing the evidence that it has not. Su Shi turns a provincial demotion into the setting for his finest work. Dante makes banishment the ground of his authority. The claim that separation clarifies, that the exile sees what the settled cannot, is present from the beginning. It is also, from the beginning, a claim made by people with certain advantages: education, reputation, patrons, a readership. None of the founders was poor in the way that most displaced people have been poor. Third, the founders were overwhelmingly men, and their exiles were acts of state against individuals prominent enough to matter. The wives, children and servants who accompanied them, or were left behind, appear only at the edges. Ovid's wife stayed in Rome to manage his affairs and lobby for his recall, and he wrote poems to her urging her to work harder at it; we have none of her replies. Dante's wife Gemma Donati remained in Florence with the children. The literature of exile began as the literature of a certain kind of man in a certain kind of trouble, and it took a long time for the category to widen. The modern era, with its mass expulsions, its refugee camps and its diasporas, would test every one of these inherited assumptions. The first to be tested was the most intimate: the relation between the exile and the language he had brought with him. CHAPTER 2 The Tongue Left Behind An exiled writer can leave behind a house, a library, a family and a landscape, and still keep writing. What cannot be left behind without consequence is the language. The native tongue is the one possession an exile carries across every border, and it is also the one most likely to decay in transit. It stops being spoken in the street. It stops being refreshed by the slang of the young and the idioms of the market. Its new words arrive late and secondhand, if at all. Readers thin out. Publishers lose interest. Children born abroad answer in the language of the host country. The writer who stays loyal to the mother tongue risks writing in a museum; the writer who abandons it risks writing, for years, like a clever foreigner. This chapter examines the choices exiled writers have made under that pressure. Its argument is that linguistic dislocation is not a side effect of exile but its core, and that it produced two opposite and equally revealing responses. Some writers clung to the native language as the last homeland and discovered that loyalty altered the language itself, turning it into something more formal, more deliberate and more elegiac than the language spoken at home. Others crossed into a second language and discovered that their foreignness became a style. Both groups ended up with an unusually conscious relationship to words, and that consciousness is one of exile literature's distinctive marks. The language as the last country Theodor Adorno, who spent the Nazi years in exile in Britain and the United States, wrote in Minima Moralia that for a man who no longer has a homeland, writing becomes a place to live. The remark, from a book assembled out of aphorisms written in California in the 1940s, captures a feeling shared by generations of displaced writers: that the native language is not simply a tool but a territory, the only one left in which they are not strangers. Czesław Miłosz made this loyalty the centre of his long exile. A Polish poet and diplomat who broke with the communist government in 1951 and sought asylum in France, he spent most of his remaining working life in Berkeley, California, teaching Slavic literatures, and continued to write poetry in Polish for a readership that for decades could obtain his books only illegally. In a poem from the late 1960s addressed to his "faithful mother tongue," he describes serving the language for years, setting out little bowls of colours for it each night so that it might keep the birch and the cricket and the bullfinch as preserved in his memory. He admits that the language has become for him a kind of homeland because he lacks any other, and he wonders whether he has been serving it for nothing, since those who might read it are either indifferent or persecuted. The poem ends not in triumph but in a guarded reaffirmation: the language remains, and he remains with it. Miłosz's loyalty was a political as well as an aesthetic choice. To write in Polish from California was to insist that Polish literature did not belong to the communist state that controlled Polish publishing. When he received the Nobel Prize in 1980, the year of the Solidarity strikes, his books were barely available in Poland; the award, and the lines of his poetry later inscribed on the monument to the shipyard workers killed at Gdańsk in 1970, made him a public figure in a country that had officially erased him. The exile's language turned out to be the nation's. Isaac Bashevis Singer presents a starker case. He emigrated from Poland to New York in 1935 and spent his whole career writing in Yiddish, a language whose European heartland was destroyed within a decade of his departure. His readership lived increasingly in translation; many of his English versions were produced in close collaboration with translators and were, in effect, the texts most of the world read. In his Nobel lecture in 1978 he spoke of Yiddish as a language of exile, without a land, without frontiers, not supported by any government, and he defended it against those who called it dead by arguing that it held the wisdom and humility of a persecuted people. He was, in a sense, the exile of an exile language, writing in a tongue that had never had a state and now scarcely had speakers. The case of Paul Celan shows how excruciating this loyalty could become. Born in Czernowitz, in what was then Romania, to a German-speaking Jewish family, Celan lost both parents in the Holocaust and settled in Paris in 1948. He wrote his poetry in German, the language of his mother and of her murderers. In a speech accepting a literary prize in Bremen in 1958 he said, in effect, that among all his losses one thing had remained reachable, close and secure: language. It had had to pass through its own lack of answers, through terrible silence, through the thousand darknesses of murderous speech, and it had come through and emerged enriched by all that had happened. Celan's later poetry, dense with coinages and broken syntax, can be read as a sustained attempt to make German say what German had been used to do. He did not switch languages; he made his native language foreign from within. What these writers share is a recognition that fidelity to the mother tongue under exile is not the same as simply continuing to use it. The language of the exile slowly diverges from the language of home. It freezes at the moment of departure, or it becomes more literary because it is no longer spoken daily, or it is deliberately estranged. Russian émigrés of the 1920s were proud of preserving the pre-revolutionary spelling that the Bolsheviks had reformed; their Russian became, visibly on the page, a relic. Loyalty kept the language alive and changed it at the same time. Crossing over The opposite choice, abandoning the native language for the language of the host country, has produced some of the most admired prose of the last century, and some of the most anguished testimony about what it cost. Joseph Conrad is usually cited first, though he was not an exile in the political sense when he began to write. Born Józef Teodor Konrad Korzeniowski in 1857 in the part of Ukraine then under Russian rule, he was the son of a Polish patriot and poet, Apollo Korzeniowski, who was arrested for conspiracy against the Russian authorities and sent with his wife and small son into exile in northern Russia. Both parents died young, their health broken. Conrad left for the sea at sixteen, learned English in his twenties on British ships, and published his first novel, Almayer's Folly, in 1895. English was his third language, after Polish and French, and he spoke it all his life with a heavy accent. His prose has been described as having an unmistakable foreign cadence, a formality and density that native English writers could not quite reproduce, and it is not fanciful to see in his recurring themes — isolation, divided loyalty, the man who has betrayed or lost his community — the inheritance of a childhood spent in political exile. Vladimir Nabokov is the canonical case, because he was a major writer in his first language before he became one in his second, and because he wrote about the transition with unusual candour. Born in 1899 into a wealthy liberal family in St Petersburg, he left Russia in 1919 as the Bolsheviks consolidated power, studied at Cambridge, and spent the next two decades in Berlin and then Paris, publishing novels in Russian under the pseudonym V. Sirin for a readership confined to the emigration. By the late 1930s that readership was shrinking and dispersing, and Europe was becoming dangerous for him and his Jewish wife. He wrote his first English novel, The Real Life of Sebastian Knight, in Paris around 1938 and 1939, and in 1940 left for the United States, where he would write Lolita, Pnin and Pale Fire. In an afterword to Lolita he described his "private tragedy," which should not, he said, be anybody's concern: that he had had to abandon his "natural idiom," his untrammelled, rich and infinitely docile Russian tongue, for a second-rate brand of English, lacking the apparatus that a native illusionist could use to transcend the heritage in his own way. The statement is typical Nabokov, a boast disguised as a lament, since his English was plainly not second-rate. But the grief behind it was real. His English novels are saturated with the texture of the language he left: puns across languages, characters who are themselves exiles, like the hapless Russian professor Timofey Pnin struggling with American idiom, and a constant, almost obsessive attention to the surface of words. Nabokov's English is the English of a man who never forgot that it was not his first. The same pattern — a crossing that makes the writer permanently conscious of language — appears in writers who crossed later and with less fanfare. Milan Kundera, who left Czechoslovakia for France in 1975 and was stripped of his Czech citizenship in 1979, continued for two decades to write novels in Czech, which were published first in French translation because they could not appear at home. Dismayed by what he regarded as the liberties his translators had taken, he spent years in the 1980s revising the French versions of his novels himself and then declared those revised translations to have the same authenticity as the Czech originals. From the mid-1990s, beginning with Slowness, he wrote his novels directly in French. The switch coincided with a notable shift in his style toward brevity and abstraction, and critics have debated whether the new language released him or diminished him. What is not in doubt is that for Kundera the question of which text was the original had become a question about who he was. Agota Kristof offers the bleakest version. She fled Hungary with her husband and infant daughter in 1956, after the Soviet suppression of the uprising, and ended up working in a watch factory in Neuchâtel in French-speaking Switzerland. She learned French as an adult, slowly and with difficulty, and wrote her novels in it, beginning with The Notebook in 1986, a spare, affectless account of twin boys surviving a war in a country resembling Hungary. In a short memoir, The Illiterate, published in 2004, she described French as an "enemy language" — not because of anything inherent in it but because it was killing her mother tongue. She had spoken French for decades and still made mistakes in it, she wrote; she could not write it without a dictionary. The stripped-down style that made her novels famous is inseparable from that struggle. She writes short declarative sentences because they are the sentences she could be sure of. Eva Hoffman's memoir Lost in Translation, published in 1989, gives the most detailed account of what the crossing feels like from inside. Her family emigrated from Kraków to Vancouver in 1959, when she was thirteen. She describes the moment when her Polish name was replaced by an English one at school and the new name seemed to refer to someone else. She describes lying in bed at night and finding that the inner voice with which she had always talked to herself had fallen silent, because Polish no longer fit her new life and English did not yet fit her inner one. English words, at first, seemed to her cold and weightless: they named things without carrying any of the feeling that the Polish words had absorbed from childhood. The book traces her slow reconstruction of an interior life in English, through reading and university and years in New York, and ends not with a return to Polish but with a hard-won settlement in which the two languages coexist, neither fully at home. Table 2 summarises the range of linguistic choices discussed in this chapter. It is not a typology of better and worse choices; each column records a different price. Table 2. Language choices of selected exiled writers Writer Native language Language of later work Pattern Czesław Miłosz Polish Polish Fidelity as resistance Isaac Bashevis Singer Yiddish Yiddish (read in translation) Fidelity to a stateless tongue Paul Celan German German Estrangement from within Joseph Conrad Polish English Adoption before fame Vladimir Nabokov Russian English Mid-career switch Milan Kundera Czech French Switch after self-revision Agota Kristof Hungarian French Adoption under duress Ngũgĩ wa Thiong'o Gikuyu English, then Gikuyu Return to mother tongue Joseph Brodsky Russian Russian verse, English prose Split by genre Split tongues and self-translation Between loyalty and conversion lies a third option: to write in both languages, or to translate oneself. It is the most exhausting choice and in some ways the most revealing, because it forces the writer to confront the question of which self is the original. Joseph Brodsky, expelled from the Soviet Union in 1972, kept writing his poetry in Russian and wrote his essays in English. He explained the English essays partly as a debt to the language of his refuge and, in one moving case, as a matter of intimacy. In "In a Room and a Half," a long memoir of his parents, whom the Soviet authorities repeatedly refused permission to visit him and who died without seeing him again, he wrote that he chose English because he wished to grant them a margin of freedom, to let them exist in a language that did not belong to their jailers. The choice of language became an act of rescue. Brodsky also translated his own poems into English, or heavily revised other people's translations, and the results provoked a long critical argument. His English versions preserved the rhymes and metres of the Russian at considerable cost to idiom, and some English-language poets found them clumsy. The dispute was, underneath, about whether a poet's authority over his work survives the passage into a language he did not grow up in. Samuel Beckett, who was not an exile in the political sense but an Irishman who chose to live in Paris, provides the purest instance of self-translation as method. From the late 1940s he wrote most of his major work first in French — Molloy, Malone Dies, The Unnamable, Waiting for Godot — and then translated it into English himself, often changing it substantially along the way. He is reported to have said that he wrote in French because it was easier to write without style. Whatever the exact wording, the point was that a second language stripped away the automatic flourishes and literary associations of the first. The French texts and their English twins are best read as two versions of a work that exists between them. Ngũgĩ wa Thiong'o reversed the usual direction. By the mid-1970s he was the most celebrated novelist in East Africa, writing in English. After he co-wrote and staged a play in Gikuyu with villagers at Kamiriithu in 1977, a play critical of the post-independence elite, he was detained without trial for nearly a year. In prison he wrote a novel in Gikuyu, on sheets of toilet paper, and after his release he declared that he would no longer write fiction in English. Threatened with arrest again in 1982, he went into exile in Britain and later the United States, and continued writing in Gikuyu. His polemic Decolonising the Mind, published in 1986, argued that the use of European languages by African writers was a continuation of colonial domination and that a literature in African languages was a condition of genuine independence. Ngũgĩ thus made the exile's linguistic choice into a political programme: exile did not push him toward the language of the host country but deeper into the language of the home that had expelled him. The cost was that his new work reached most readers in translation — often his own. What the crossing teaches Several lessons emerge from these cases, and they complicate the easy picture of exile as simple loss. The first is that exile makes writers conscious of language as material. A writer who has never had reason to doubt that the words she uses are the natural names of things is spared a certain kind of labour. The exile loses that innocence. Whether she stays in the mother tongue or leaves it, she knows that every word is a choice. This is one reason why so many of the great stylists of the twentieth century were displaced: Nabokov's verbal pyrotechnics, Celan's coinages, Kristof's austerity and Beckett's bareness are all, in different ways, the style of people who could not take language for granted. The second is that linguistic exile is often internal to the family. Hoffman's parents never achieved her fluency. Brodsky's parents stayed in Leningrad. The children of Russian émigrés in Paris grew up speaking French. The crossing into a new language opens gaps between generations, and much exile literature is written in the space between a parent who never learned the new language and a child who has half forgotten the old. Some of the most painful passages in this literature concern not the loss of a country but the loss of the ability to talk to one's mother. The third is that the choice of language is never purely aesthetic. It determines readership, income, reputation and political meaning. Miłosz's Polish was a statement of allegiance; Ngũgĩ's Gikuyu was a manifesto; Kundera's French was, among other things, a way of escaping the role of the dissident that his Western readers kept pressing on him. Kristof's French was forced on her by the need to live. The language an exile writes in answers the question "for whom?" — and exile makes that question impossible to avoid. Finally, the exile's language, whichever it is, tends to become the vehicle of something that no longer exists except in the writing. The Russian of the emigration preserved a pre-revolutionary world. Singer's Yiddish preserved the shtetls of Poland after the shtetls had been destroyed. Even Nabokov's English is haunted by the St Petersburg of his childhood. That haunting leads directly to the subject of the next chapter: the lost homeland, and the uses exiles have made of it. CHAPTER 3 The Invented Homeland Every exile carries a country that does not exist. It is assembled from the last images seen before departure, from childhood memories that were already selective when they were formed, from family stories, photographs, songs and smells, and from years of longing that polish some details and erase others. Meanwhile the real country goes on changing without the exile: new buildings rise, old streets are renamed, the people who stayed grow older and make compromises the exile never had to make. The gap between the carried country and the actual one widens every year. The literature of exile is, to a large extent, the record of what writers did with that gap. This chapter argues that the lost homeland in exile writing is always a construction, and that the decisive difference between exile writers lies in how they treat that construction. Some defend it as truth and try to hold the real country to its image; this impulse produces some of exile literature's most moving work and much of its most dangerous politics. Others treat the invented homeland as an invention, examine its seams, and make art out of the knowledge that the country of memory cannot be recovered. The distinction, most usefully drawn by the literary scholar Svetlana Boym, clarifies a great deal about why some exile writing has aged well and some has not. A disease of soldiers The word "nostalgia" is younger than the feeling. It was coined in 1688 by a medical student at Basel, Johannes Hofer, who combined the Greek words nostos, return home, and algos, pain, to name a condition he had observed among Swiss mercenaries serving abroad and among students and servants far from their valleys. Its symptoms included melancholy, loss of appetite, fever and a fixation on the sounds and images of home, and it could, physicians believed, be fatal. For more than a century nostalgia was treated as a curable illness of the displaced; the cure was return. Only gradually, in the nineteenth century, did the word migrate from medicine to sentiment and from place to time, coming to mean a longing not for a location but for a lost era. That migration matters for the literature of exile, because the exile's longing is for both at once. The lost homeland is a place and a time — the place as it was when one left, which is also the period of one's own youth. Many exiles left young; the country they remember is the country of childhood, and the grief of exile blends indistinguishably with the ordinary grief of growing older. Joachim du Bellay, a French poet of the sixteenth century who spent four years in Rome as secretary to his cousin, a cardinal, wrote the most famous sonnet of homesickness in French while surrounded by the grandest ruins in Europe. Happy is he who, like Ulysses, has made a fine voyage and then returned home, he begins, and he goes on to prefer the modest house his ancestors built, its slate roof and its little village on the Loire, to the bold facades of Roman palaces. Du Bellay was not an exile in any political sense, but his sonnet captures the core structure of nostalgic writing: the magnification of the small and familiar against the grand and foreign, and the identification of home with a lost simplicity. Two kinds of longing Svetlana Boym, who emigrated from Leningrad to the United States in 1981 and spent her career studying the culture of displacement, proposed in The Future of Nostalgia, published in 2001, a distinction between two kinds of nostalgia that has become indispensable for thinking about exile literature. Restorative nostalgia, she wrote, stresses the nostos, the return, and attempts a transhistorical reconstruction of the lost home. Reflective nostalgia dwells in the algia, the longing itself, and delays the homecoming. Restorative nostalgia, she observed, does not think of itself as nostalgia at all, but as truth and tradition; it builds monuments, revives rituals and patrols the boundaries of the national past. Reflective nostalgia is ironic, fragmentary and aware of its own distortions; it cherishes shattered fragments of memory without insisting that they be reassembled into a whole. The distinction is not a moral one in any simple sense. Restorative nostalgia can sustain a persecuted community through decades of dispersion; reflective nostalgia can decline into self-regarding melancholy. But the two produce very different kinds of writing, and very different politics. Table 3 sets out the contrast as it applies to exile literature. Table 3. Two modes of nostalgia in exile writing (after Boym) Feature Restorative Reflective Focus The lost home itself The act of longing Attitude to memory Memory as truth Memory as construction Relation to the present Seeks to rebuild the past Accepts the past as past Typical forms Epic, manifesto, national history Memoir, lyric, fragment Political tendency Purity, return, restitution Irony, pluralism, doubt Characteristic risk Myth hardening into dogma Longing sliding into solipsism The country as a book Some of the most ambitious exile writers set out to reconstruct the homeland in literature so completely that it could stand in for the original. The impulse is restorative in form, even when the writer's attitude is ironic. Adam Mickiewicz wrote Pan Tadeusz, the Polish national epic, in Paris between 1832 and 1834, in the aftermath of the failed November Uprising against Russian rule. The poem is set in 1811 and 1812 in the Lithuanian countryside of the poet's youth, among the minor gentry, and it describes their hunts, feasts, quarrels, mushroom-gathering and legal disputes with lavish, affectionate detail. It opens with an invocation to Lithuania as the poet's homeland, which, like health, can be valued only by one who has lost it. Written for an emigration demoralised by defeat, the epic gave Poles a country that existed nowhere else — Poland had been partitioned out of existence in 1795 — and it became, for generations of Poles at home and abroad, the portable image of the nation. Its world was already gone when Mickiewicz wrote it; he knew it, and the knowledge gives the poem its melancholy undertow. James Joyce made the same attempt with a very different city and a very different temperament. He left Dublin in 1904 and, apart from brief visits, never lived there again. Dubliners, A Portrait of the Artist as a Young Man and Ulysses were written in Trieste, Zurich and Paris. Stephen Dedalus at the end of Portrait announces that he will try to express himself as freely and wholly as he can, "using for my defence the only arms I allow myself to use — silence, exile, and cunning." Ulysses, set on a single day in June 1904, reconstructs Dublin with obsessive precision; Joyce consulted street directories and wrote to relatives asking whether it was possible for an ordinary person to climb over the railings of a particular house on Eccles Street. His friend Frank Budgen reported him as saying he wanted to give a picture of Dublin so complete that if the city one day disappeared from the earth it could be reconstructed from his book. The reconstruction was not nostalgic in any sentimental sense; Joyce's Dublin is squalid, comic, paralysed and alive. But it froze the city at the moment of the author's departure, and the Dublin of Ulysses was, by the time the book appeared in 1922, a city that had passed through the Easter Rising, a war of independence and the beginning of a civil war. Joyce's homeland was invented by the precision of its memory. Ivan Bunin, who left Russia in 1920 and became the first Russian writer to win the Nobel Prize, in 1933, spent his exile in France writing about a Russia of country estates, autumn orchards, peasant villages and doomed love affairs. His late collection Dark Avenues, written largely in Grasse during the Second World War, returns again and again to brief erotic encounters in a vanished pre-revolutionary landscape. Bunin was a fierce opponent of the Bolsheviks, and his diary of the revolutionary years, Cursed Days, is a document of horror and contempt. His fiction, by contrast, is almost free of politics. It restores the lost country not by argument but by sensation: the smell of apples, the light on a river. Readers in the Soviet Union, where his work was eventually published in selections, found in it a Russia that official culture had abolished. Knowing the mirror is broken Against this restorative tendency stands a line of writers who understood from the start that the homeland they were rendering was partly fiction, and who made that understanding part of the work. Nabokov's autobiography, Speak, Memory, first published in 1951 and revised in 1966, is the great example. It is a meticulous reconstruction of his childhood on the family estate south of St Petersburg: the butterflies, the tutors, the governesses, the first love, the father assassinated in Berlin in 1922. It is also a book about the workings of memory, full of reflections on how the mind recovers and rearranges the past, and on the patterns — Nabokov calls them themes — that can be traced through a life. He is scornful of the émigré who hates the Soviets only because they took his money and land; his own nostalgia, he insists, is "a hypertrophied sense of lost childhood, not sorrow for lost banknotes." The distinction is revealing. Nabokov refuses the restorative politics of the emigration, with its dreams of a return to property and position, and relocates the loss in a place no revolution could reach and no counter-revolution could restore. Childhood is lost to everyone. Nabokov's special claim is that exile made the loss visible and permanent, and that art could hold it more precisely than any political programme. Salman Rushdie gave the reflective position its best-known formulation in an essay titled "Imaginary Homelands," first published in 1982 and later the title piece of a collection. He describes seeing, in his study in London, an old photograph of the house in Bombay where he was born, and realising that the city he remembers and has written about in Midnight's Children is not the city that exists. Exiles, emigrants and expatriates, he argues, are haunted by the urge to look back, but their physical alienation from the homeland means that they cannot reclaim precisely what was lost; they will create fictions, not actual cities or villages but invisible ones — imaginary homelands, "Indias of the mind." He compares the exile's memory to a broken mirror, some of whose fragments have been irretrievably lost, and argues that the fragments are not inferior to the whole: their very incompleteness gives them a special resonance, and ordinary objects recovered from memory acquire symbolic weight. Rushdie was not a political exile when he wrote the essay; he became one, in a sense, when the fatwa issued against him in 1989 over The Satanic Verses made return to much of the Muslim world impossible and forced him into hiding in Britain. But the essay's argument holds for exiles of every kind: the homeland is a text, and the question is whether the writer knows it. Mahmoud Darwish offers the most complex case, because his homeland was not merely left but, in large part, erased from the map, and because the Palestinian collective memory he wrote for depended heavily on restorative images. Darwish was born in 1941 in the village of al-Birweh in Galilee. In 1948 his family fled to Lebanon; when they returned a year later, the village had been destroyed and they lived as internal refugees within the new state of Israel. He became a celebrated poet in Arabic, was repeatedly arrested, and in 1970 left for Moscow and then Cairo and Beirut, beginning a long exile that took him to Tunis and Paris before he settled in Ramallah in the 1990s. Palestinian exile culture developed powerful restorative symbols: the key to the lost house, kept by refugee families for generations; the olive tree; the orange groves of Jaffa; the village named and mapped from memory. Darwish's early poetry drew on this repertoire, and some of it became the anthems of a movement. His mature work, however, grew increasingly suspicious of the fixed image. Memory for Forgetfulness, a prose work about a single day during the Israeli siege of Beirut in August 1982, moves between the bombardment, the poet's struggle to make a cup of coffee under fire, and fragments of memory, dream and history, refusing any single narrative. Later collections, such as Why Did You Leave the Horse Alone?, return to his childhood village as something to be recovered in language rather than in fact, and question whether the poet can separate himself from the exile that has made him. One of his late poems asks, in its title, "Who am I, without exile?" The question is not rhetorical. For Darwish exile had become constitutive of identity, and the dream of a return to the original place competed with the recognition that the place, and the self that had lived there, no longer existed. Myth and its uses The distinction between restorative and reflective nostalgia can make the second look simply wiser than the first. The history of exile writing suggests a more complicated verdict. Restorative myth has sustained exiled communities through catastrophe. The Jewish liturgical formula "Next year in Jerusalem," repeated for centuries, kept a collective identity in place across a dispersion of extraordinary length. Polish literature of the nineteenth century, written largely in exile while the country did not exist as a state, kept the nation imaginable; Pan Tadeusz was read aloud in Polish households across the partitioned lands. The Armenian and Palestinian diasporas have used restorative images to insist on a claim that the world preferred to forget. For a people whose homeland has been taken, a myth of the homeland is not an indulgence. It is a title deed. The same myth can harden. The political culture of long-term exile communities is notoriously prone to feuds, purity tests and the freezing of positions that no longer match the reality at home. The Russian emigration of the 1920s and 1930s split into monarchist, liberal, socialist and Eurasianist factions whose programmes for a restored Russia grew more elaborate as the prospect of return receded. Cuban exile politics in Miami after 1959 produced a literature of fierce anti-Castro loyalty alongside a literature, such as Guillermo Cabrera Infante's, that remembered Havana through its nightlife, music and puns rather than its politics, and that was sometimes distrusted by both sides. The restorative homeland, carried too long, can become a standard against which the actual inhabitants of the country are judged and found wanting, and the exiles who return to it may find that they are regarded as foreigners with outdated ideas. The reflective mode has its own failures. It can become a manner, a knowing melancholy that treats loss as an aesthetic opportunity and loses touch with the political fact of expulsion. Rushdie's broken mirror is a powerful image; it is also an image available chiefly to someone whose broken homeland is not being bulldozed. The Palestinian poet in Beirut under bombardment cannot afford to treat the lost village as merely a fiction of the mind, because other people are actively denying that it existed. The best exile writing tends to hold both modes in tension. Darwish's late poetry is reflective in its irony and its doubt, but it never abandons the claim that the lost home was real and that its loss was an injustice. Nabokov's Speak, Memory is reflective in its method, but its precision about the physical details of the estate is itself a kind of restoration. Mickiewicz's epic is restorative in design, but its humour and its awareness of the gentry's pettiness keep it from becoming a monument. The invented homeland, in these writers, is neither dogma nor mere fantasy. It is a structure the exile builds knowing that it is built, and lives in because there is nowhere else. Individual memory is not the only place such homelands are built. Exiles have also constructed them together, in communities with their own newspapers, publishing houses, schools and quarrels. Those communities, and the political uses of literature within them, are the subject of the next chapter. Hashtags: #TheLiteratureOfExile #ExileLiterature #Displacement #Nostalgia #FracturedIdentity #BanishmentWriting #ForcedMigration #InternalExile #ExileAndLanguage #MotherTongue #LinguisticDislocation #SelfTranslation #ImaginaryHomelands #RestorativeNostalgia #ReflectiveNostalgia #ContrapuntalReading #Hybridity #CulturalDisplacement #ExileIdentity #MemoryAndHomeland #DiasporaLiterature #ReturnAndHomecoming #ExileAndPower #LiteratureOfDisplacement #FutureOfExileStudies

Download the Book (PDF): Introduction: From Knowing to Running There is a moment, usually in the second year of a hospitality degree, when the questions change. Up to that point, the questions have been descriptive. What is a franchise? What does a concierge do? How does a cruise line differ from a resort? These have answers you can look up, and a student with a good memory does well. Then the questions become operative. Given a hotel running at 68 per cent occupancy with labour at 34 per cent of revenue and a competitive set outperforming it on rate, what do you do? Given a restaurant whose food cost has drifted from 29 to 33 per cent over four periods with no change in menu prices, where do you look? Given a department head who is technically excellent and cannot retain staff, what is the intervention? These questions do not have lookup answers. They have method. And the difference between a student who has memorised a management textbook and one who can actually answer them is not how much they know — it is whether they have a reliable way of thinking about a hospitality business under pressure. That method is what this book is about. The problem every hospitality manager is solving Strip away the sector detail and the management of a hospitality business reduces to one persistent problem: Demand varies enormously and unpredictably. Capacity and most costs do not. A hotel has the same number of rooms on the quietest night of February as on the busiest night of June. It carries the same debt, pays the same property taxes, insures the same building and employs the same salaried managers. A restaurant has the same rent, the same kitchen, the same equipment and the same head chef whether it serves forty covers or two hundred. Meanwhile revenue on any given day is determined by forces — the weather, an event in the city, a competitor's promotion, a conference that moved to another town, an exchange rate — that the manager did not choose and cannot control. Every managerial technique in hospitality is a response to that mismatch. Forecasting exists because you must know demand before you can staff for it. Revenue management exists because varying price is the only way to influence demand in the short run. Flexible scheduling and part-time contracts exist because labour is the only large cost that can be flexed at all. Cost control systems exist because on thin margins the difference between a good month and a bad one is a small number of percentage points. Budgets and variance analysis exist because a manager needs to know, quickly, whether a shortfall came from lower volume or worse execution — because the two demand entirely different responses. Hold that mismatch in view and the syllabus reorganises itself. Every chapter of a hospitality management course becomes an answer to the question: how do you run a business whose demand you do not control and whose costs you cannot easily reduce? The management loop Underneath the specialisms there is a loop that hospitality managers run continuously, at every level, in every sector. It is worth naming, because it is the spine of everything that follows. Forecast. Estimate demand for the period ahead — rooms, covers, delegates, attendance — by segment and by day. Everything downstream depends on this, and forecasting error is the most expensive single failure in hospitality operations, because it propagates: a bad forecast produces bad staffing, bad purchasing, bad pricing and bad expectation-setting all at once. Price. Decide what to charge, to whom, through which channel, under what conditions. Price is the fastest lever available and the only one that acts on demand within hours. Resource. Schedule labour, order inventory, allocate space and equipment to the forecast demand. This is where most controllable cost is committed, usually days before the revenue arrives. Deliver. Run the operation. This is where standards, training, supervision and the countless small judgements of frontline staff determine whether the promised product actually appears. Measure. Compare what happened with what was planned, in enough detail to identify cause. Not "revenue was down" but "revenue was down because transient occupancy missed forecast by four points while rate held, and labour was not flexed down in response, so payroll ran 11 per cent over." Adjust. Feed the finding back into the next forecast, the next price, the next schedule. Every technique in this book sits somewhere in that loop. When you meet an unfamiliar tool — flow-through analysis, a productivity standard, a displacement calculation, a market segmentation matrix — the useful first question is which stage of the loop it belongs to and which decision it is supposed to improve. What this companion does This is a study companion for a course in hospitality management. It is written to be read alongside a comprehensive management textbook, and it makes four commitments. It is organised by managerial role, not by sector. A textbook chapter on restaurant management and a chapter on lodging management will both cover forecasting, staffing, cost control and marketing, in different vocabulary. Rather than learning the same idea four times in four disguises, this book teaches each managerial function once, properly, and then shows how it differs across settings. That is a more efficient use of your revision time and a considerably better preparation for actually managing something. It takes the numbers seriously. Hospitality management is quantitative in a way that the descriptive first year is not. Departmental profit and loss statements, flow-through, labour productivity standards, food cost variance, break-even analysis, budget variance — these appear in examinations as calculations, and the calculations are not difficult, but they are unforgiving. Every one is worked here with real arithmetic and an explanation of what the number is actually telling you. It is honest about what is contested. Motivation theory, leadership models and service quality frameworks are taught in hospitality courses as though settled. Much of it is not. Where a model is weaker than its textbook presentation suggests, this book says so, because the ability to evaluate a framework rather than merely recite it is what separates upper from lower degree classifications. It gives you the questions. Each chapter closes with key terms written for reproduction under examination conditions, and with essay and calculation prompts of the kind actually set at this level. Working these is worth more than rereading. What it does not do It does not replace your set text, which will carry sector detail, case studies and jurisdiction-specific legal content that no companion can substitute for. It does not teach financial accounting from first principles, though it teaches you to read the statements hospitality actually uses. And it does not pretend that management is a matter of applying formulas: a great deal of the job is judgement exercised on incomplete information, and the honest thing a book can do is show you what the good judgements have in common. A word about what management actually feels like Textbooks describe management as planning, organising, leading and controlling. That is accurate and it is also, as a description of a Friday evening in a full hotel, comically incomplete. The reality is that a hospitality manager spends most of their time in short, interrupted, verbal exchanges, making dozens of small decisions with imperfect information, most of which will never appear in any report. Research on managerial work going back to Henry Mintzberg's observational studies in the early 1970s consistently found that managers do not spend long uninterrupted periods on planning; they work in fragments, they rely heavily on verbal and informal information, and they operate at a pace set by others. Anyone who has worked a shift in an operating hotel will recognise the description immediately. This matters for how you should read a management textbook. The frameworks are not descriptions of how the job feels. They are tools for the small proportion of the job where you can step back — the forecast meeting, the budget, the schedule, the monthly review, the difficult conversation you prepared for. That proportion is small, and it is where nearly all the value is created. A manager who is excellent in the fragments and absent from the planning will run a busy operation into the ground slowly. A manager who is competent in the fragments and rigorous in the planning will run a good one. The chapters that follow are about the planning half. Chapter 1 sets out what the managerial job consists of and how decision rights are distributed. Chapters 2 and 3 cover people: leading them, and the harder mechanics of recruiting, scheduling and keeping them. Chapters 4 and 5 cover the commercial core — forecasting and revenue management, then the financial statements through which hospitality performance is actually read. Chapter 6 handles food and beverage cost control in detail. Chapter 7 covers marketing and the sales function. Chapter 8 addresses group and event business, where the management problems are contractual as much as operational. Chapter 9 turns to the executive level: strategy, capital, risk and the governance questions a senior manager cannot delegate. Read a chapter here before the corresponding chapter of your set text, work the calculations by hand rather than following them with your eyes, and plan two essay questions per chapter without notes. That is the whole method, and it works. Chapter 1: What a Hospitality Manager Actually Does Management textbooks open with Fayol's four functions — planning, organising, leading and controlling — and there is nothing wrong with them as a scaffold. The trouble is that they describe management in general, and hospitality management has a specific shape that the general description obscures. Three features distinguish it, and they explain most of what is peculiar about the job. Three features that shape the job The manager is present during production. In manufacturing, management happens away from the line and mostly before or after it. In hospitality, the manager is on the floor while the product is being made, in front of the customer, and is expected to intervene in real time. This produces the fragmented, interrupted working pattern that observational research on managerial work has documented since the 1970s, and it means a hospitality manager must be capable of switching between operating and thinking within the same hour — a genuinely demanding cognitive requirement that no framework prepares you for. Decisions are made continuously and cannot be deferred. A manufacturing manager can take a week over a sourcing decision. A hospitality manager cannot take a week over whether to accept a group, walk a guest, comp a meal, send a section home early, or reopen a closed section of the restaurant. The cost of a slow decision usually exceeds the cost of a slightly wrong fast one, which is why hospitality management selects strongly for decisiveness and why "would rather be roughly right now" is a fair description of the professional temperament. Authority is distributed downward further than the organisation chart suggests. A receptionist deciding whether to waive a late check-out fee, a server deciding whether to replace a dish, a housekeeper deciding whether a stain justifies stripping a bed — these are commercial and reputational decisions made continuously by people at the bottom of the hierarchy. The manager's job is therefore less about making those decisions than about ensuring the people making them have the training, information, authority and incentive to make them well. This is the substantive content of what textbooks call empowerment, and it is why the design of standards, training and discretionary limits is a first-order managerial task rather than an administrative one. Levels of management and what changes between them The three-level model — supervisory, middle, executive — is worth taking seriously in hospitality because the content of the job changes so sharply between levels, and because graduates frequently misjudge what the next level requires. Supervisory management — a front office supervisor, a restaurant shift leader, an executive housekeeper's assistant — is predominantly about execution within a shift. The time horizon is hours. The core skills are technical competence in the department's work, the ability to allocate and pace people, and the confidence to intervene. Most of the day is spent on the floor. The characteristic failure at this level is the supervisor who is superb at the work and does it themselves rather than getting it done through others. Departmental and middle management — front office manager, food and beverage manager, executive housekeeper, director of sales — shifts the horizon to weeks and months. Now the job includes budgeting, scheduling to a labour standard, forecasting, recruitment, performance management and interdepartmental negotiation. Technical skill matters less; the skills that matter are analytical and interpersonal. The characteristic failure here is the department head who manages their own department excellently and treats the rest of the hotel as an obstacle. Executive management — general manager, director of operations, area or regional director — extends the horizon to years and shifts the primary relationship outward: to owners, to brand companies, to the market. The general manager's job is substantially about resource allocation, capital planning, relationships with owner and brand, and the culture of the property. The characteristic failure at this level is the general manager who never stopped being a department head and continues to run the department they came from. Robert Katz's distinction between technical, human and conceptual skills, published in the Harvard Business Review in 1955, remains the cleanest description of this progression: technical skill matters most at the bottom, conceptual skill most at the top, and human skill matters roughly equally throughout. It is old and it is still right. Who decides what: the decision rights problem Here is something introductory courses often skip and examiners increasingly ask about. In a branded, professionally owned hotel, the general manager does not have unilateral authority over most significant decisions. Understanding who holds which decision right is essential to understanding the job. The owner controls capital. Any expenditure above a defined threshold — a refurbishment, new equipment, a technology investment, a change to the physical product — requires owner approval, and the owner's decision will be made on the basis of return on investment and the owner's own holding horizon. An owner planning to sell in eighteen months evaluates a five-year payback quite differently from a pension fund holding for twenty. The brand controls standards. Brand standards specify the physical product, the service sequence, the amenity, the technology platform and frequently the reporting. A general manager who believes a standard is wrong for their market can request a waiver; they cannot simply ignore it, because compliance is contractually enforceable and audited. The management company or the brand's regional structure typically controls senior appointments, approves the annual budget, sets performance targets, and provides the systems within which the property operates. The general manager controls execution: the deployment of the approved budget, the hiring and development of the team below the senior level, the day-to-day commercial decisions within the approved strategy, the culture, and — critically — the quality of the relationships with all of the above. The practical consequence is that a great deal of senior hospitality management is influence without authority. The general manager who wants the lobby refurbished must build a case that persuades an owner whose money it is; the one who wants a brand standard waived must persuade a brand executive whose job is to protect consistency. This is a skill, it is learnable, and it is almost entirely absent from most textbook treatments of the role. The core of it is the ability to translate an operational argument into the language of the person you are asking — return on investment for the owner, brand equity and guest satisfaction scores for the brand company, cost and risk for the corporate office. The planning hierarchy Planning in hospitality runs on a defined cadence, and knowing the cadence tells you what a manager is doing at any point in the year. Strategic planning is the multi-year positioning of the business: the market segments it serves, its competitive position, its capital plan, its brand affiliation. In an owned or managed hotel this involves the owner directly, and it is the point at which the asset's future is actually decided. The annual budget translates strategy into a twelve-month financial plan, built bottom-up from a demand forecast by segment and month, through revenue by department, through cost lines, to departmental and gross operating profit. The budget process typically runs over several months in the autumn and is the single most important planning exercise in the hospitality year, because it sets the targets against which everyone will be measured and the resources everyone will have. The forecast updates the budget with current reality. Most hotels forecast monthly for the coming three months and weekly or daily for the coming fortnight, with increasing granularity as the date approaches. The budget does not change; the forecast does. This distinction matters and students frequently blur it: the budget is the commitment, the forecast is the current expectation, and the gap between them is the management problem. Scheduling and operational planning convert the short-term forecast into rotas, orders, and daily deployment. This is where the forecast becomes money, because labour scheduled is labour paid. The business plan or repositioning plan sits outside the annual cycle and is produced when something changes materially — a renovation, a rebranding, a new competitor entering the market. Standards, systems and the control function Controlling, the fourth of Fayol's functions, has specific content in hospitality. Standard operating procedures document how each recurring task is performed. Their function is not bureaucratic: they are how a business with high staff turnover and continuous production maintains a consistent product. A well-written SOP tells a new employee what good looks like without requiring a supervisor to be present. A badly written one — or one that describes a process nobody actually follows — is worse than none, because it destroys the credibility of the whole system. Performance standards define acceptable output: rooms cleaned per shift, check-in time, food pick-up time, telephone answer time. These are the basis of both productivity management and quality management, and they must be set from observation rather than aspiration. A standard nobody achieves is not a standard; it is a fiction that teaches staff to ignore standards. Quality assurance systems — brand audits, mystery shopping, guest satisfaction surveys, online review monitoring, food safety audits — supply the measurement. The managerial skill is triangulating between them, because each has known distortions. Guest satisfaction surveys over-represent extremes. Mystery shopping is a single observation. Online reviews are self-selected. A manager who runs the property to any one of these measures alone will optimise the measure rather than the business. Financial control systems — the night audit, the daily revenue report, inventory control, purchase authorisation, the monthly close — provide the money picture. Chapter 5 covers what they produce and how to read it. Coordination: the problem the organisation chart hides Hospitality departments are unusually interdependent, and most operational failures are coordination failures rather than departmental ones. Consider what has to align for a single arrival to go well. Reservations recorded the request accurately and coded the rate correctly. Revenue management left inventory available. Housekeeping cleaned and released the room in time, which required knowing the arrival pattern, which required the front office to share it. Engineering closed the maintenance issue that had the room out of order. The kitchen knows there is a late arrival who will want food. Accounting has the corporate billing instruction on file. Each department did its own job competently, and the guest's experience depends entirely on whether the information passed between them. The classic failure points are worth knowing because they recur in every property. Front office and housekeeping. The front desk needs rooms; housekeeping needs time and information. When the two departments manage the relationship through complaint rather than through shared information about arrival patterns and priority rooms, arrivals queue at three in the afternoon and both departments blame the other. The fix is procedural: a shared, live view of room status, agreed priority protocols for early arrivals and VIPs, and a named person on each side responsible for the interface during peak periods. Sales and operations. Sales commits; operations delivers. A sales team that contracts commitments operations cannot meet — a set-up time that is physically impossible, a menu the kitchen cannot produce at that volume, a rate that leaves no margin for the concessions promised — creates failures that guests experience as operational incompetence. The standard control is that operations sees and approves anything unusual before it is contracted, which sales departments resist and which prevents a specific and expensive class of problem. Kitchen and restaurant. The most consistently adversarial relationship in hospitality, and mostly a structural one: the kitchen is measured on food cost and consistency, the restaurant on covers and check average, and those objectives conflict at the margin on specials, substitutions, comps and pacing. The management response is a shared measure — contribution per cover, or departmental profit — rather than exhorting two teams with opposing incentives to get along. Revenue and sales. Revenue management may refuse business that sales has spent months developing. Where the displacement analysis is transparent and both parties understand it, this is a professional disagreement about numbers; where it is opaque, it becomes a status conflict. The general manager's role in all of this is to design the interfaces and then to insist on them. Coordination does not emerge from goodwill between department heads who are each measured on their own department. It emerges from shared information, defined protocols at the points of friction, and at least one measure that only improves when both departments do. The daily rhythm It is worth being concrete about what the job looks like, because abstractions about planning and controlling do not convey it. A hotel general manager's day typically begins with the previous day's results: occupancy, rate, revenue against forecast, any incidents, the day's arrivals including VIPs and groups, and the current position for the days ahead. A morning operations meeting brings department heads together for perhaps twenty minutes to reconcile what is coming — arrivals, departures, functions, maintenance issues, staffing gaps. The rest of the day divides between floor presence, scheduled commercial and financial work, meetings with owners, brand representatives or clients, personnel matters, and the interruptions that constitute a substantial fraction of the total. Two things are worth noticing about this rhythm. The first is that the morning meeting is doing something structurally important: hospitality departments are interdependent in ways that produce failure if information does not cross between them, and the meeting is the mechanism that forces it to. The second is that the scheduled commercial and financial work is the part most easily displaced by operational demands, and displacing it is the most common way a competent operator becomes a poor manager. Key terms Management functions — planning, organising, leading and controlling; Fayol's classification of managerial work. Technical, human and conceptual skills — Katz's classification of managerial competence, with technical skill most important at supervisory level and conceptual skill at executive level. Decision rights — the allocation of authority over particular categories of decision between owner, brand, management company and property management. Brand standard — a contractually enforceable specification of physical product, service sequence, amenity or system required by a franchisor or brand operator. Influence without authority — the practice of achieving outcomes through persuasion where formal authority rests elsewhere. Strategic plan — the multi-year plan for a business's market position, capital investment and competitive strategy. Budget — the annual financial plan, built from a demand forecast, against which performance is measured. Forecast — the current expectation of near-term performance, updated continuously; distinct from the budget, which does not change. Standard operating procedure (SOP) — a documented method for performing a recurring task consistently. Performance standard — a defined level of acceptable output, set from observation, used for productivity and quality management. Quality assurance — the system of audits, surveys, mystery shopping and review monitoring used to measure delivered quality. Operations meeting — the short daily meeting at which department heads reconcile the day's demands and constraints. Essay and exam prompts 1. Explain how the content of a hospitality management job changes between supervisory, middle and executive levels, using Katz's classification. (Short answer) 2. "In a branded, institutionally owned hotel, the general manager's principal skill is influence rather than authority." Discuss, with reference to the allocation of decision rights. 3. Distinguish between a budget and a forecast. Why is the distinction important, and what should a manager do when the two diverge substantially? 4. Explain the function of standard operating procedures in an industry characterised by high labour turnover. What makes an SOP effective, and what makes one counterproductive? 5. "Every quality measurement system used in hospitality has a known distortion." Identify three such systems, explain their distortions, and discuss how a manager should use them together. 6. Observational research finds that managers work in short, interrupted fragments rather than in long planning periods. What are the implications for how a hospitality manager should structure their week? 7. A newly promoted food and beverage manager continues to work service every evening and has not produced a departmental forecast in two months. Diagnose the problem and set out how you would address it. 8. Explain why the daily operations meeting exists, and what specifically fails in a hotel where it is not held. Chapter 2: Leading People Leadership is the part of the hospitality management syllabus most likely to be taught badly and examined well. Taught badly, it becomes a parade of models — trait theory, Blake and Mouton, situational leadership, transformational leadership — each presented as an advance on the last, with no indication of which are well supported and which are not. Examined well, it asks you to diagnose a situation and justify an approach, which requires knowing not just what the models say but how much weight each will bear. This chapter takes the models seriously and is candid about their limits. Why leadership matters more here than in most industries Three structural features make leadership disproportionately consequential in hospitality. The product is produced by people in front of customers, so the disposition of staff is directly visible in the product. A demoralised kitchen produces worse food; a demoralised front desk produces worse arrivals. In few other industries is the internal culture of a business so immediately apparent to the customer. The work is physically demanding, frequently unsocial in its hours, and often modestly paid, which means discretionary effort — the difference between doing the job and doing it well — is not purchased by the wage. It is elicited, or it is not. And the workforce is young, mobile, and frequently working alongside people from a wide range of national and linguistic backgrounds. Hospitality teams are among the most culturally diverse in any industry, which is a genuine strength and also a real communication challenge that a leader has to manage deliberately rather than hope for. What the models are worth Trait approaches attempted to identify the personal characteristics of effective leaders. A century of research has produced modest and inconsistent findings, with the most durable being that conscientiousness, extraversion and openness show small positive associations with leadership emergence and effectiveness. The honest summary is that traits matter somewhat, predict poorly, and explain little of the variation. Present trait theory in an essay as historically important and empirically weak. Behavioural approaches — the Ohio State and Michigan studies, and Blake and Mouton's managerial grid — asked what leaders do rather than what they are, and identified two recurring dimensions: concern for task (initiating structure) and concern for people (consideration). The finding that both matter, and that they are largely independent rather than opposed, is genuinely useful and has held up reasonably well. The grid's prescription that the "9,9" team-oriented style is universally best is the weak part; the descriptive insight that task and people orientation are separable is the strong part. Contingency and situational approaches argued that the effective style depends on the situation. Fiedler's contingency model, Hersey and Blanchard's situational leadership, and House's path–goal theory are the standard trio. Situational leadership — match your style to the follower's competence and commitment on the specific task — is enormously popular in management training and, it must be said, weakly supported by empirical research; its prescriptions have not consistently validated. Path–goal theory, which holds that the leader's job is to clarify the route to valued outcomes and remove obstacles, has fared somewhat better and has the advantage of describing something a manager can actually do on a Tuesday. The defensible position for an essay is this: the situational insight is almost certainly correct — a new commis chef and a twenty-year sous chef require different handling — but the specific models that formalise it are more precise than the evidence justifies. Use them as prompts to think, not as algorithms. Transformational and transactional leadership, developed by Burns and elaborated by Bass, is the framework with the strongest current standing. Transactional leadership operates through exchange: clear expectations, monitoring, contingent reward, correction of deviation. Transformational leadership operates through inspiration, individual attention to development, intellectual stimulation and idealised influence — the leader who makes people want to be better at the job rather than merely compliant with it. The important and frequently missed point is that these are not alternatives. The research consistently finds that transformational leadership adds effect on top of competent transactional leadership, not instead of it. A hospitality manager who inspires the team but cannot produce a working rota, pay people correctly, or address a persistent performer problem is not a transformational leader; they are a poor manager with charisma. Transactional competence is the floor. Servant leadership has gained particular traction in hospitality, for an obvious reason: an industry whose product is service finds intuitive appeal in the idea that a leader's role is to serve the people who serve. The empirical literature is reasonably supportive, particularly regarding service climate and organisational citizenship behaviour. It is worth knowing and worth handling carefully, since the concept can slide into an excuse for a manager who avoids difficult decisions in the name of supporting the team. Motivation: what actually holds up Motivation theory in hospitality courses is dominated by frameworks that are decades old and substantially superseded. It is worth being precise about which are which, because examiners increasingly reward that precision. Maslow's hierarchy of needs is universally taught and has almost no empirical support for its central claims — that needs are arranged in a fixed hierarchy, and that lower needs must be satisfied before higher ones become motivating. Maslow himself never presented it as a validated model. It remains useful as a vocabulary for talking about different kinds of need, and it should be presented in an essay as an influential heuristic whose specific predictions have not been supported. Herzberg's two-factor theory distinguished hygiene factors — pay, conditions, supervision, security — whose absence causes dissatisfaction but whose presence does not motivate, from motivators — achievement, recognition, the work itself, responsibility, advancement — which do. The methodology has been criticised heavily, principally on the grounds that the critical-incident technique used invites people to attribute good outcomes to themselves and bad ones to circumstances. But the practical distinction has proved durable in hospitality specifically: improving a break room does not produce engagement, while giving a cook responsibility for a dish on the menu often does. Expectancy theory (Vroom) is the framework that best survives scrutiny and is the most useful managerially. It holds that motivation is a product of three judgements: expectancy — will effort produce performance? instrumentality — will performance produce the outcome? and valence — do I value that outcome? The power of this is diagnostic. When someone is not putting in effort, the theory tells you there are exactly three places to look, and they demand different responses. If they do not believe effort will produce performance, the problem is training, tools or workload. If they do not believe performance will be rewarded, the problem is the credibility of your reward system — and in hospitality this is very often the real answer, because promises about progression are made casually and remembered precisely. If they do not value the reward, the problem is that you are offering something they do not want. Equity theory (Adams) holds that people assess their input–outcome ratio against comparable others and are demotivated by perceived unfairness. In hospitality this is exceptionally live, because pay, tips, shift allocation and scheduling are all visible, comparable and frequently inconsistent. A rota that consistently gives the desirable shifts to the same people will produce disengagement no amount of recognition can offset. Self-determination theory (Deci and Ryan) is the framework with the strongest current empirical standing and is under-taught in hospitality. It proposes that intrinsic motivation depends on three psychological needs: autonomy (a sense of volition over one's work), competence (feeling effective at it), and relatedness (connection to others). Its practical implications map directly onto hospitality problems: rigid scripting undermines autonomy; inadequate training undermines competence; high turnover and fragmented shifts undermine relatedness. It also explains a finding that troubles simple incentive schemes — that heavy extrinsic reward can crowd out intrinsic motivation for work people previously found satisfying in itself. Delegation, which is where most new managers fail The single most common failure of newly promoted hospitality managers is under-delegation, and it has a predictable cause: they were promoted for being good at the work, they are still better at the work than the people they now supervise, and doing it themselves is faster today. It is also how a manager ends up working ninety hours, developing nobody, and being unable to take a day off without the department degrading. Effective delegation has structure. Assign the whole task rather than a fragment, since fragments teach nothing. State the outcome required and the constraints, then leave the method alone unless the method carries risk. Match the level of oversight to the person's demonstrated competence at that task, not their general seniority. Provide the authority the task requires — delegating responsibility without authority is a common and demoralising error. Agree how and when you will check in, before the work starts rather than by surprising them halfway. And accept that the first few attempts will be worse than yours, because that cost is the price of the person becoming capable. The related discipline is not taking work back. When a delegated task comes back imperfect, the instinct is to fix it. Fixing it teaches the person that bringing you a partial job is sufficient, and within a month you have the work back permanently. Teams, culture and the things that actually change behaviour Culture in hospitality is discussed vaguely and operates concretely. It is the set of behaviours that are actually rewarded, tolerated and punished, which is frequently different from the set described in the values statement on the staff noticeboard. Three mechanisms do most of the work. What the manager notices. Attention is the strongest signal available. A manager who inspects cleanliness daily and mentions guest feedback occasionally has communicated a priority, whatever the values poster says. What happens when standards are breached. A standard that is enforced inconsistently is not a standard, and inconsistent enforcement does more damage than no standard, because it converts a rule into a matter of the manager's mood. Who gets promoted. Nothing communicates the real values of an operation more clearly than which behaviours precede advancement. If the person promoted is the one who hits numbers while burning through staff, every observer has learned what the business actually values. On teams, the most useful recent evidence is the work on psychological safety, developed by Amy Edmondson: the shared belief that the team is safe for interpersonal risk-taking — that raising a problem, admitting an error or asking a question will not be punished. In hospitality this is not a soft matter. A kitchen where a cook will not report that they mishandled a temperature check, or a front office where staff will not escalate a complaint they mishandled, has a safety and reputational exposure created directly by its interpersonal climate. Difficult conversations Finally, the skill hospitality managers most often lack and most need. Performance and conduct conversations are avoided because they are unpleasant, and avoidance is expensive: the problem persists, the rest of the team observes that it is tolerated, and the eventual conversation happens under provocation and goes badly. A workable structure is: prepare the specific evidence rather than the general impression; state the gap between the required standard and the observed behaviour factually and without adjectives; ask for the other person's account and actually listen to it, because in a meaningful proportion of cases there is information you did not have; agree a specific, observable change with a date; and record it. Where conduct is at issue rather than capability, follow the formal disciplinary procedure exactly — hospitality operations lose employment tribunal cases far more often on procedural failure than on the substance of the complaint. Key terms Initiating structure and consideration — the two behavioural dimensions of leadership identified in the Ohio State studies: concern for task organisation and concern for people. Situational leadership — the proposition that effective leadership style depends on follower readiness for the specific task; popular in training, weakly supported empirically. Path–goal theory — the model holding that a leader's role is to clarify routes to valued outcomes and remove obstacles. Transactional leadership — leadership through clear expectations, monitoring and contingent reward. Transformational leadership — leadership through inspiration, individual consideration, intellectual stimulation and idealised influence; adds effect on top of, not instead of, transactional competence. Servant leadership — an approach positioning the leader's primary role as serving the development and needs of the team. Hygiene factors and motivators — Herzberg's distinction between factors whose absence causes dissatisfaction and factors whose presence produces motivation. Expectancy theory — motivation as the product of expectancy (effort to performance), instrumentality (performance to outcome) and valence (value of the outcome). Equity theory — the proposition that motivation depends on perceived fairness of one's input–outcome ratio relative to comparable others. Self-determination theory — the framework identifying autonomy, competence and relatedness as the basis of intrinsic motivation. Delegation — assigning a whole task with the outcome, constraints, authority and agreed oversight required to complete it. Psychological safety — the shared belief that a team is safe for interpersonal risk-taking such as admitting error or raising a problem. Discretionary effort — the difference between the minimum acceptable performance and what a person is capable of giving. Essay and exam prompts 1. Distinguish transactional from transformational leadership, and explain why the relationship between them is additive rather than alternative. (Short answer) 2. "Maslow's hierarchy is taught in every hospitality course and supported by almost no evidence." Assess this claim and explain what, if anything, the model is still useful for. 3. Apply expectancy theory to diagnose a hotel housekeeping team with high absenteeism and low productivity. What three distinct explanations does the theory generate, and what different interventions does each imply? 4. Explain self-determination theory and discuss how the design of frontline hospitality work commonly undermines each of its three needs. 5. "Situational leadership is the most popular leadership model in management training and one of the least empirically supported." Discuss the implications for how such models should be taught and used. 6. Why do newly promoted hospitality supervisors systematically under-delegate, and what are the consequences? Set out a structured approach to delegation. 7. Explain psychological safety and discuss its specific relevance to food safety and complaint handling in hospitality operations. 8. "Culture is what gets rewarded, tolerated and punished, not what is written on the wall." Discuss with reference to the mechanisms through which managers actually shape behaviour. 9. A long-serving restaurant supervisor has become persistently rude to junior staff, though guests remain satisfied. Set out how you would prepare for and conduct the conversation, and what you would do if the behaviour continued. Chapter 3: Human Capital — Staffing, Scheduling and Retention If leadership is the art of the job, staffing is the engineering. It is also where a hospitality manager's decisions have the most direct and measurable financial effect, because labour is simultaneously the largest controllable cost in most operations and the principal determinant of product quality. This chapter is deliberately mechanical. The material here is quantitative, examinable, and the part of people management that graduates most often arrive without. The size of the problem Labour cost in hospitality typically runs between roughly 30 and 45 per cent of revenue depending on segment, with full-service hotels and table-service restaurants at the higher end and limited-service properties and quick service at the lower. Alongside food cost, it forms the prime cost that determines whether an operation is viable. At the same time, turnover in parts of the sector runs several times the economy-wide average, and the cost of that turnover is systematically understated because most operations never calculate it. The components are: recruitment advertising and agency fees, management time in selection, administrative onboarding, training time of both the new employee and whoever trains them, reduced productivity during the learning period, errors and waste during that period, overtime paid to cover the vacancy, and the loss of accumulated knowledge about the operation and its regular guests. Estimates of the total vary widely by role and methodology — anything from a few weeks' pay for an entry-level position to well over a year's salary for a specialised manager — and you should be careful about quoting a single figure without a source. What is not contested is the direction: the cost is large, it lands on the same budget that would have paid for retention, and it is almost never on the report the manager reads. The managerial implication is worth stating flatly. If turnover cost is not measured, retention investment will always look like an expense and never like a saving, and the operation will systematically under-invest in it. Workforce planning and job design Staffing begins before recruitment, with two questions that are frequently skipped. How much labour does this operation actually require? The answer comes from productivity standards — the observed relationship between volume and labour hours. A housekeeping standard might be expressed as minutes per room by room type and stay type; a restaurant standard as covers per server hour; a front desk standard as arrivals per hour per agent. These are established by observation and time study, validated against quality outcomes, and then used both to schedule and to budget. An operation without productivity standards is scheduling by feel, which means it is over-staffed on quiet days and under-staffed on busy ones simultaneously. How should the work be arranged? Job design decisions — how broad each role is, how much variety it contains, how much discretion it carries — have direct consequences for both efficiency and retention. The classic framework is Hackman and Oldham's job characteristics model, which identifies skill variety, task identity, task significance, autonomy and feedback as the dimensions that produce meaningful work. Hospitality roles vary enormously on these: a room attendant working alone with a fixed list scores low on most; a small-hotel receptionist who handles reservations, arrivals, concierge duties and the bar scores high on nearly all. This is a substantial part of why small independent operations often retain staff longer than large ones despite paying less. Multiskilling — training staff across departments so they can be deployed where demand appears — is the standard hospitality response to demand volatility, and it addresses job design and flexibility simultaneously. Its limits are real: it takes training investment, it can dilute expertise, and it requires pay structures that recognise the additional capability, failing which staff correctly perceive it as being asked to do more jobs for one wage. Recruitment and selection The recruitment funnel — attract, screen, assess, select, offer, onboard — is standard. Three points are specific enough to hospitality to be worth attention. Attraction is a marketing problem. Hospitality employers compete for the same labour pool as retail, logistics and care, frequently on comparable wages and worse hours. What the sector can offer credibly is progression speed, variety, transferability of skills internationally, and the tangible satisfaction of the work. Job advertisements that lead with "fast-paced environment" and "team player" communicate nothing; those that state the actual shift pattern, the actual pay, the actual training and the actual route to the next role attract better candidates and fewer early leavers. Selection should test the work. Structured interviews substantially outperform unstructured ones in predicting job performance — this is one of the most consistent findings in personnel psychology — and work sample tests outperform both. For hospitality roles, a short practical assessment (handle this arrival, plate this dish, respond to this complaint) predicts far better than a conversation about strengths and weaknesses. Structure means the same questions, in the same order, scored against defined criteria, for every candidate. Realistic job previews reduce early turnover. Telling candidates plainly about the weekend work, the physical demands and the difficult periods reduces the number who accept and increases the proportion who stay — a trade most operations should take, given the cost of a leaver at week six. Legal compliance in selection — non-discrimination, right-to-work verification, data protection in handling applications — varies by jurisdiction and your course will cover the local requirements. The principle that transfers everywhere is that decisions must be made against job-related criteria, documented, and defensible. Scheduling: where money is committed Scheduling is the point at which the forecast becomes cost. It deserves more attention than it usually receives. The process runs: take the demand forecast for the period; convert forecast volume to required labour hours using productivity standards; distribute those hours across the day according to when demand actually occurs; assign named individuals subject to availability, contracts, skills and fairness; and check the resulting cost against the budgeted labour percentage. The second step is where the errors are. Consider a 180-room hotel forecasting 140 occupied rooms with a housekeeping standard of 28 minutes per departure room and 22 minutes per stayover, plus 20 minutes per attendant per shift for setup, briefing and stocking. If the forecast splits into 85 departures and 55 stayovers: Departures: 85 × 28 = 2,380 minutes. Stayovers: 55 × 22 = 1,210 minutes. Cleaning total: 3,590 minutes, or 59.8 hours. At 7.5 productive hours per attendant shift plus 20 minutes of non-cleaning time, each attendant contributes roughly 7.17 cleaning hours. Required attendants = 59.8 ÷ 7.17 ≈ 8.3, so nine attendants, with the ninth potentially on a short shift. Add supervision and public area cleaning separately. Notice what this makes visible. If the forecast is wrong by fifteen rooms, the schedule is wrong by roughly one attendant — around seven hours of pay committed days in advance and largely unrecoverable. This is the mechanism by which forecasting error becomes cost, and it is why forecast accuracy is a labour cost issue and not merely a revenue one. Three further scheduling considerations matter. Match the shape, not just the volume. A restaurant needs staff distributed according to when covers arrive, not spread evenly across opening hours. Staggered start and finish times, split shifts where legally permitted, and on-call arrangements are the standard tools, each with a cost in employee goodwill that has to be weighed. Fairness is a retention variable. Unsociable shifts, weekends and holidays should be distributed transparently and demonstrably evenly. Perceived favouritism in the rota is one of the most reliable predictors of resentment in hospitality teams, and it costs nothing to prevent. Predictability has become a legal and competitive issue. Several jurisdictions have legislated on advance notice of schedules, minimum shift lengths, compensation for cancelled shifts and restrictions on consecutive close-then-open shifts. Beyond compliance, published-in-advance and stable rotas have become a genuine recruitment advantage in tight labour markets. Measuring labour productivity Three measures are standard and each answers a different question. Labour cost percentage = total labour cost ÷ revenue × 100. The headline control figure, and the one used in budgets. Its weakness is that it moves with rate as well as with efficiency: a hotel that raises its average rate improves its labour percentage without a single change in productivity. Hours per unit — minutes per room, hours per cover, hours per occupied room — measures efficiency independent of price and is therefore the better operational measure. Hours per occupied room (HPOR), covering all hotel departments, is the standard cross-property comparison. Revenue per labour hour = revenue ÷ hours worked. Useful in food and beverage, where it combines efficiency and sales performance in one figure. A manager should watch the physical measure operationally and the percentage financially, and be alert to the divergence between them. Labour percentage improving while hours per occupied room worsens means rate is masking an efficiency problem that will surface the moment rate softens. Training and development Training in hospitality is frequently reduced to induction plus food safety certification, which is a compliance floor rather than a development system. Induction should cover the practical (where things are, who people are, how to be paid, how to raise a problem) and the cultural (what this operation cares about, what good looks like) in the first days, because early experience predicts early leaving strongly. On-the-job training is the workhorse of the sector and is usually delivered by whoever is available rather than by whoever is good at it. Designating and preparing trainers — people who can break a task into steps, demonstrate, observe and correct — is a low-cost intervention with a disproportionate effect on both consistency and new-starter retention. Cross-training builds the flexibility discussed above and is also a development opportunity that costs the operation very little. Development planning — a documented conversation about where someone wants to get to and what they need to demonstrate to get there — is the intervention most directly aimed at the sector's retention problem, and it is the one most often promised and least often delivered. Its value depends entirely on follow-through: a development plan that is never revisited is worse than none, because it converts a promise into evidence that promises are not kept. Evaluation of training is worth knowing in outline: Kirkpatrick's four levels distinguish reaction (did they like it), learning (did they acquire it), behaviour (did they use it) and results (did anything change). Most hospitality training is evaluated only at level one, which measures satisfaction with the session rather than any effect on the operation. Performance management Between selection and retention sits the process most hospitality operations run worst: the ongoing management of how well people actually do the job. The formal apparatus — annual appraisal, rating scales, objectives — is widely disliked and widely ineffective, for reasons worth understanding. An annual conversation cannot correct a problem that arose in March. Rating scales compress a year of varied performance into a number that determines a pay decision, which turns the conversation into a negotiation rather than a development discussion. And in an industry with high turnover and shift-based supervision, the manager conducting the appraisal frequently has not observed most of the year being appraised. What works better is neither complicated nor common: frequent, specific, low-stakes feedback given close to the event, separated from pay decisions, and recorded briefly. "The way you handled the couple at table nine tonight — you checked back before they had to ask, and you took the wine off the bill without making it a discussion" is worth more than any annual rating, because it identifies a behaviour precisely enough to repeat. Three components make a workable system. Clear standards. People cannot meet expectations they have not been told. This is the same argument as for standard operating procedures, applied to individual performance. Regular observation. A supervisor who is present during service has evidence; one who manages from an office has impressions. A supervisor trained to give feedback. Most people promoted into supervision have never been taught how to say something critical without either softening it into meaninglessness or delivering it as an accusation. This is a teachable skill and almost never taught. Documented conversations at defined intervals — quarterly is usually sufficient — covering what is going well, what needs to change, and what the person is working toward. Documentation matters both for development and for the disciplinary process, where an employer that cannot evidence prior conversations is in a poor position. Where performance is genuinely inadequate, the sequence is: establish that the person knows the standard and has the training and tools to meet it; agree a specific, observable improvement with a date; support it; and if it does not improve, move to the formal procedure without delay. The failure mode here is drift — a manager who addresses a problem repeatedly and informally for a year has created a documentary record showing tolerance, not correction. Retention Bringing this together, retention in hospitality responds to a specific and knowable set of levers, in roughly this order of demonstrated effect. The immediate supervisor. The single strongest predictor of whether someone stays is their relationship with the person who manages them directly. Investment in supervisory capability is therefore retention investment, and it is the highest-return people expenditure most hospitality operations can make. Schedule predictability and fairness. Discussed above, and consistently cited in exit interviews across the sector. Pay that is defensible relative to local alternatives. Pay does not buy engagement, but pay that is visibly below what the retail park is offering will lose people regardless of everything else. Visible progression. People stay where they can see a next step and someone credible has told them how to reach it. Being treated as competent. Autonomy within a defined scope, being consulted about changes that affect the work, and not being publicly corrected — these cost nothing and are cited constantly. Onboarding quality. A disproportionate share of leavers go within the first ninety days, which means the return on improving the first two weeks is unusually high. The managerial point is that none of these requires a corporate programme. They are within the gift of a competent department head, which is precisely why the variation in turnover between two departments in the same hotel, on the same pay scales, is frequently larger than the variation between companies. Key terms Productivity standard — the observed labour time required per unit of output, such as minutes per room or covers per server hour. Hours per occupied room (HPOR) — total labour hours divided by occupied rooms; the standard cross-property labour efficiency measure. Labour cost percentage — total labour cost as a percentage of revenue. Revenue per labour hour — revenue divided by hours worked. Multiskilling — training employees across roles or departments to permit flexible deployment. Job characteristics model — Hackman and Oldham's framework identifying skill variety, task identity, task significance, autonomy and feedback as sources of meaningful work. Structured interview — a selection interview using identical questions, order and scoring criteria for all candidates; substantially more predictive than unstructured interviewing. Work sample test — a selection method requiring candidates to perform a representative task. Realistic job preview — accurate disclosure of the demanding aspects of a role during recruitment, reducing early turnover. Turnover cost — the full cost of replacing an employee, including recruitment, training, lost productivity, cover and lost operational knowledge. Split shift — a working day divided into two separated periods, used to match labour to peaked demand. Kirkpatrick's four levels — reaction, learning, behaviour and results; the standard framework for evaluating training. Onboarding — the structured integration of a new employee into the role and the organisation. Essay and exam prompts 1. Define hours per occupied room and explain why it is a better operational measure of labour efficiency than labour cost percentage. (Short answer) 2. A 200-room hotel forecasts 160 occupied rooms, of which 95 are departures and 65 stayovers. Housekeeping standards are 27 minutes per departure and 21 minutes per stayover, with 20 minutes of non-cleaning time per attendant shift and 7.5 paid productive hours per shift. Calculate the number of attendants required, and explain the cost consequence of a forecast that proves 20 rooms too high. (Calculation) 3. "Turnover cost is large, avoidable, and invisible on the reports managers read." Discuss, identifying the components of turnover cost and the managerial consequence of not measuring it. 4. Explain why structured interviews and work sample tests outperform unstructured interviews, and design a selection process for a front office agent. 5. Evaluate multiskilling as a response to demand volatility. What are its benefits, its limits, and its implications for pay structure? 6. Discuss the effect of schedule predictability legislation on hospitality operations, and assess whether stable scheduling can be justified commercially in its absence. 7. Using the job characteristics model, compare the work of a hotel room attendant with that of a receptionist in a small independent property, and discuss the implications for retention. 8. "The strongest determinant of whether a hospitality employee stays is their immediate supervisor." Discuss the evidence and the managerial implications. 9. "The annual appraisal cannot correct a problem that arose in March." Discuss the weaknesses of formal appraisal in a shift-based industry and set out what a workable alternative requires. 10. Most hospitality training is evaluated only at Kirkpatrick's first level. Explain the problem this creates and propose a practical approach to evaluating a customer service training programme at levels three and four. Hashtags: #TheManagersPlaybook #HospitalityManagement #ManagementLoop #DemandForecasting #RevenueManagement #HospitalityOperations #LabourManagement #CostControl #VarianceAnalysis #DecisionRights #HospitalityLeadership #TransformationalLeadership #TransactionalLeadership #SelfDeterminationTheory #ExpectancyTheory #PsychologicalSafety #Delegation #WorkforcePlanning #ProductivityStandards #LabourScheduling #HoursPerOccupiedRoom #StaffRetention #HospitalityStrategy #OperationalControl #FutureOfHospitalityManagement

Download the Book (PDF): Introduction Most students arrive at revenue management from modules on service quality, guest experience and operations, where the questions are about people and the answers are argued in prose. Then the timetable turns over and the questions start arriving with numbers attached. A hotel has 240 rooms and sold 198 of them last night: what was its RevPAR? A group wants sixty rooms for three nights at £95: should you take it? The forecast shows eight no-shows on average: how many rooms should you oversell? A mild dread sets in, and it is rarely about the arithmetic itself. It is the feeling that there is a hidden logic behind the formulas that everyone else seems to grasp, and that the formulas are things to be memorised rather than understood. This booklet is written to remove that feeling. It is an independent companion to Revenue Management for the Hospitality Industry by David K. Hayes and Allisha A. Miller, a textbook whose chapters move from strategic pricing, value and differential pricing through forecasting, inventory and price management and distribution, to the evaluation of revenue management in lodging and in food and beverage. The textbook is comprehensive. What a student often needs alongside it, particularly in the weeks before an examination, is a narrower and more patient treatment of the quantitative core: the handful of formulas that generate most exam questions, the economic reasoning that makes each of them sensible, and enough fully worked examples that the steps become familiar. One question behind every formula The central claim of this booklet is simple. Every calculation in revenue management is an attempt to answer one question: what is this unit of perishable capacity worth if I sell it now, at this price, to this customer, compared with what it is worth if I hold on to it? A hotel room for tonight, a restaurant seat at eight o'clock, a tee time on Saturday morning and a banqueting suite on a June Friday all share the same awkward property. If they are not sold by a certain moment they are gone, and the revenue they could have earned can never be recovered. Because the cost of providing one more unit is small compared with the price, almost any sale looks attractive. And because some customers will pay far more than others, and will often book later, selling cheaply now may mean turning away someone who would have paid more. Once that question is in view, the formulas fall into two families. The first family is made up of measures: occupancy, average daily rate (ADR), revenue per available room (RevPAR), total revenue and gross operating profit per available room (TRevPAR and GOPPAR), and the index measures used to compare a hotel against its competitors. These tell you, after the event, how well the question was answered. Every one of them is a ratio, and almost every mistake students make with them is a mistake about the denominator: what exactly is being divided by what, and why. The second family is made up of decision tools: price elasticity, differential pricing with rate fences, demand forecasting, protection levels and booking limits, displacement analysis for groups, and the overbooking calculation known as the critical fractile. These help a manager answer the question before the event, when the information is uncertain. Every one of them, stripped to its core, compares a certain gain now with an expected gain later. The algebra looks different from tool to tool, but the comparison is always the same one. A student who sees this structure can often reconstruct a formula in an exam rather than recall it. If you forget how to calculate a protection level, you can ask what the last protected room is worth if kept for a high-paying guest, and what it is worth if sold to a discount guest now, and set the two equal. If you forget whether GOPPAR divides by rooms sold or rooms available, you can ask what the measure is supposed to reveal, and the answer follows. How the booklet is organised The chapters are arranged in the order in which the ideas build on one another. Chapter 1 sets out the economics that make revenue management necessary: fixed and perishable capacity, low marginal cost, demand that varies and can be segmented, and the idea of opportunity cost that runs through everything after it. Chapters 2 to 4 cover the measures. Chapter 2 treats occupancy, ADR and RevPAR in detail, including the conventions that trip students up. Chapter 3 moves from revenue to profit through TRevPAR, net RevPAR, GOPPAR and flow-through, and explains why a hotel can raise its RevPAR while making less money. Chapter 4 covers benchmarking against a competitive set with the market penetration index, the average rate index and the revenue generation index. Chapters 5 to 9 cover the decision tools. Chapter 5 deals with price, value and elasticity, and with the calculation every manager should run before cutting a rate. Chapter 6 explains differential pricing and the rate fences that make it work, and why fairness is a real constraint. Chapter 7 covers forecasting, including pickup methods, error measures and the problem of unconstrained demand. Chapter 8 deals with inventory allocation: Littlewood's rule, booking limits, bid prices, length-of-stay controls and group displacement. Chapter 9 treats overbooking as a newsvendor problem and works through the critical fractile. Chapter 10 then carries the same logic beyond the guest room, to restaurants, spas, golf courses and function space, where time becomes part of the capacity being sold. The Conclusion draws out what follows from all of this for practice and for the examination hall. How to use the worked examples The worked examples are the heart of the booklet. Each is set out in display lines, one step per line, so you can follow the arithmetic and check it yourself. All the figures in them are invented round numbers chosen to make the logic visible; they are illustrative and are not data about any real hotel or market. Where the text reports real research findings, the source is cited in author–date form and listed in the References. Work the examples with a calculator and a pencil rather than simply reading them. Revenue management is learned the way a language is learned, by doing it. When you reach the end of an example, try changing one number and predicting which way the answer will move before you recalculate. That habit, more than any formula sheet, is what builds the confidence to face an unfamiliar question. Three habits will serve you throughout. First, write the formula in words before you substitute numbers, so that the examiner can follow your reasoning even if you slip on the arithmetic. Second, keep track of units: rooms, room nights, pounds per room, percentages and percentage points are different things, and confusing them is the most common source of lost marks. Third, finish every calculation with a sanity check. If a hotel's ADR comes out at £9 or its occupancy at 130 per cent, something has gone wrong, and saying so is better than leaving the figure unexamined. Revenue management has a reputation as the most mathematical module in a hospitality degree. It deserves a different reputation: as the module where economic reasoning becomes most concrete. The mathematics is modest. The ideas behind it are powerful, and they are within reach of every student willing to work through them slowly. Chapter 1: Perishable Capacity and the Logic of Opportunity Cost Revenue management did not begin in hotels. Its modern form grew out of the United States airline industry after deregulation in 1978, when established carriers faced low-cost rivals selling cheap seats and needed a way to match them on price without giving the same discount to passengers who would have paid full fare. The response was to sell a limited number of restricted, advance-purchase discount seats on each flight while protecting the rest for later, higher-paying demand. American Airlines built one of the most ambitious systems for doing this, and its analysts later estimated that yield management had produced quantifiable benefits of around $1.4 billion over a three-year period (Smith, Leimkuhler, & Darrow, 1992). Robert Cross (1997), who worked on some of the early airline systems, went on to argue that the same thinking could be applied in any business whose capacity is fixed and whose customers value it differently. Hotels followed through the late 1980s. Early articles in the hotel trade and academic press set out the practice in terms that hoteliers could recognise, including a simple "yield" statistic that compared the revenue actually earned with the revenue that would have been earned if every room had sold at full rate (Orkin, 1988). Sheryl Kimes, whose work runs through much of this booklet, gave the field its most cited definition of when revenue management is worth doing (Kimes, 1989a, 1989b). The reasoning behind those conditions is the foundation for every formula that follows, so it is worth taking slowly. The conditions that make it worthwhile Kimes (1989b) identified a set of characteristics shared by firms that benefit from revenue management. Capacity is relatively fixed. The inventory is perishable. Demand fluctuates. The market can be segmented. The product is sold in advance. And the marginal cost of making a sale is low while the cost of adding capacity is high. Each condition matters for a specific reason, and it helps to see what goes wrong if one is missing. Fixed capacity means a hotel cannot respond to a busy Saturday by building another floor, nor to a quiet Tuesday by lending rooms to someone else. The number of rooms is set for years at a time. If capacity could be adjusted freely, a manager would simply match supply to demand and there would be little to optimise. Perishability means an unsold room night cannot be stored. A retailer who fails to sell a jumper today can sell it tomorrow; a hotel that fails to sell room 214 tonight has lost tonight's revenue from that room for ever. This is what makes timing so important. The value of the room falls to zero at a precise moment, and every decision before that moment is shaped by the approaching deadline. Fluctuating demand means some nights would sell out at almost any sensible price while others would not fill at any price. If demand were constant and predictable, a single well-chosen price would do the job and the rest of the apparatus would be unnecessary. Segmentable demand means different customers place different values on the same room and can be told apart, at least roughly, by how and when they buy. A business traveller booking two days ahead for a Tuesday in the city centre is a different buyer from a couple booking three months ahead for a weekend break, even if they end up in identical rooms. Advance sales mean that the manager must decide whether to accept a booking before knowing what other requests will arrive. This is where uncertainty enters and where forecasting becomes essential. Low marginal cost and high capacity cost mean that once the hotel exists, letting one more room costs very little compared with the price charged, while adding rooms is expensive and slow. This condition is the reason almost any sale looks attractive, and therefore the reason discipline is needed. Take any of these away and the case for revenue management weakens. Put them all together, as hotels, airlines, cruise lines, car hire firms, restaurants, golf courses and event venues do, and the manager faces a recurring dilemma: accept a certain, smaller amount now, or wait for a larger but uncertain amount later. Cost structure: why almost any sale looks good Hotel costs divide, roughly, into those that do not change with the number of rooms sold in a given night and those that do. The fixed costs include the building, its financing or rent, insurance, most management salaries, property taxes and much of the maintenance. The variable costs of an occupied room include housekeeping labour, laundry, guest amenities, a share of energy and water, and transaction charges. For most full-service and select-service hotels the variable cost of an occupied room is a small fraction of the rate charged. The difference between the price and the variable cost of a unit is its contribution margin: the amount each sale contributes towards covering fixed costs and, once those are covered, towards profit. It is the most useful single number in revenue management, and many later calculations rely on it. Consider an illustrative 200-room hotel with fixed costs of £300,000 a month, an average rate of £120 and a variable cost of £30 per occupied room night. How many room nights must it sell each month to cover its fixed costs? Contribution per room night = Price − Variable cost per room Contribution per room night = £120 − £30 = £90 Break-even room nights = Fixed costs ÷ Contribution per room night Break-even room nights = £300,000 ÷ £90 ≈ 3,333.3, so 3,334 room nights Rooms available in a 30-day month = 200 × 30 = 6,000 Break-even occupancy = 3,334 ÷ 6,000 ≈ 55.6% Below about 56 per cent occupancy the hotel loses money; above it, each additional room night adds £90 to profit. That is a high degree of operating leverage: once fixed costs are covered, profit grows quickly with volume, and when volume falls it shrinks just as quickly. It also explains the temptation that revenue management exists to discipline. On a night when the hotel expects empty rooms, a guest offering £45 still contributes £15 above variable cost. Refusing that guest looks like throwing money away. Sometimes it is. The error lies in assuming that the £45 guest is always taking a room that would otherwise be empty. Whether that is true depends on what other demand might arrive for the same room, and that is where the second idea comes in. Opportunity cost: the price of saying yes The opportunity cost of a decision is the value of the best alternative given up by taking it. When a revenue manager accepts a booking, the alternative given up is the chance to sell that room to someone else. If the hotel will not fill tonight whatever happens, the opportunity cost of any booking is zero, and any price above variable cost is worth accepting. If the hotel is likely to sell out, the opportunity cost of a cheap booking is the higher rate that a later guest would have paid, weighted by the probability that such a guest actually turns up. A small illustration makes the logic concrete. A tour operator asks, three weeks before a Friday night, for a room at £90. The revenue manager believes that if the room is held, there is a 40 per cent chance of selling it closer to the date at £150, and a 60 per cent chance it will stay empty. Variable cost is £30 per occupied room. Should the manager accept? Contribution if the room is sold now = £90 − £30 = £60 Expected contribution if the room is held = 0.40 × (£150 − £30) + 0.60 × £0 Expected contribution if the room is held = 0.40 × £120 = £48 £60 > £48, so accept the booking Now suppose that a large conference has just been announced for the same Friday and the manager revises the chance of a later £150 sale to 70 per cent. Expected contribution if the room is held = 0.70 × £120 = £84 £84 > £60, so decline the booking and hold the room The indifference point, where the two options are worth the same, is found by setting them equal. £60 = p × £120 p = £60 ÷ £120 = 0.50 If the chance of a later full-rate sale is above one half, holding is better; below one half, selling now is better. Notice what this simple calculation does. It turns a vague feeling ("I think we might sell out") into a precise threshold that can be compared with a forecast. That transformation, from judgement to threshold, is the essence of every decision tool in the chapters that follow. Littlewood's rule in Chapter 8, displacement analysis for groups and the critical fractile for overbooking in Chapter 9 all have exactly this shape. Notice, too, that the calculation used contributions rather than revenues. Because a room that stays empty incurs no housekeeping or laundry cost, the fair comparison is between what each option adds after its own variable costs. Many textbook formulas are written in terms of revenues or fares alone, which is acceptable when variable costs are small relative to prices, but you should know which you are using and why. In an exam, stating the assumption earns credit. Spoilage and spill Revenue managers use two terms for the two ways of getting this decision wrong. Spoilage is capacity that goes unsold because the manager held out for higher-paying customers who never arrived. Spill is higher-paying demand that is turned away because capacity was already sold to lower-paying customers. A hotel that never discounts suffers spoilage on quiet nights. A hotel that sells cheaply to anyone who asks suffers spill on busy ones. There is no setting that eliminates both. Protecting more rooms for late, high-rate demand reduces spill and increases spoilage; protecting fewer does the opposite. The goal is to balance the expected cost of each, and the balance point depends on the price gap between segments and on how uncertain demand is. The wider the gap between the high and low rates, the more a manager should be willing to risk spoilage. The more certain the forecast, the less risk of either kind remains. Both errors can be priced after the event, and doing so is a useful discipline. Suppose that on a busy Saturday an illustrative hotel sold 30 rooms months in advance to a tour operator at £80, and then, in the final week, turned away 25 requests from guests willing to pay £180. Had 25 of the tour operator's rooms been held back, they would have gone to the late guests instead. Because a room costs the same to service whichever guest occupies it, the variable costs cancel and the lost contribution is simply the difference in rates. Cost of spill = 25 × (£180 − £80) = 25 × £100 = £2,500 Now take a quiet Wednesday on which the same hotel declined the tour operator's request for 15 rooms at £80, expecting late business that never materialised, and the rooms stayed empty. Here the comparison is with an empty room, which incurs no variable cost, so the lost contribution is the rate minus the £30 variable cost. Cost of spoilage = 15 × (£80 − £30) = 15 × £50 = £750 Notice that the two costs are calculated differently. Spill replaces a low-rate guest with a high-rate one, so the variable cost is incurred either way; spoilage replaces a guest with an empty room, so the variable cost is saved. Reviewing a month of such nights in this way shows a revenue manager whether the hotel's errors lean towards holding out too long or selling too early, which is the first step towards correcting them. It is worth dwelling on why the balance is struck at a probability rather than at an expectation. Suppose the forecast says that on average 60 full-rate guests will want rooms on a given night. The instinctive response is to protect exactly 60 rooms. But the 60th protected room is only useful if demand reaches 60, which on an average forecast happens roughly half the time. Whether it is worth protecting depends on whether a coin-flip chance at the high rate is worth more than a certain sale at the low rate. If the high rate is more than twice the low rate, it is; if not, it is not. The right number of rooms to protect can therefore be above or below the average forecast, and Chapter 8 shows how to calculate it. Demand curves and the value of segmentation The final piece of economic groundwork is the demand curve, the relationship between the price charged and the number of rooms that would be sold at that price. For any single night, imagine lining up every potential guest in order of the most they would be willing to pay. A few would pay a great deal, rather more would pay a moderate rate, and many more would come only at a low price. The demand curve slopes downwards because lowering the price brings in guests further down the line. If the hotel must charge one price to everyone, it faces an unavoidable compromise. A high price earns a lot from each guest but leaves rooms empty and turns away guests who would have paid something above variable cost. A low price fills the hotel but gives away money to guests who would happily have paid more. The gap between what a guest would pay and what the guest actually pays is known as consumer surplus. A single price leaves a large amount of it on the table at the top of the demand curve and leaves unserved demand at the bottom. Differential pricing, the practice of charging different customers different prices for essentially the same product, is an attempt to capture more of that value. It sells to the price-sensitive guest at a lower rate without offering the same rate to the guest who would pay more. The difficulty, examined in Chapter 6, is keeping the two groups apart. If everyone can buy the cheap rate, the scheme collapses back into a single low price. The devices that keep them apart are called rate fences, and the question of whether customers accept them as fair turns out to be as important as the arithmetic. Timing and the booking curve One further feature of hotel demand shapes everything else. Different segments tend to book at different times. Leisure travellers, tour operators and groups often commit weeks or months ahead and are sensitive to price. Business travellers and last-minute leisure guests book closer to the date and are, on average, less sensitive to price. The pattern is not universal, and online booking and flexible cancellation have blurred it, but it is strong enough to create the central tension of the field: the low-paying demand arrives first. If the cheap demand arrived last, there would be no dilemma. A hotel would sell to every high-rate guest as they came, and fill any leftover rooms with discounts at the end. Because the order is usually reversed, the manager must decide how much capacity to sell cheaply before knowing how much expensive demand will materialise. The accumulation of bookings over time for a given arrival date is called the booking curve or booking pace, and reading it well is the purpose of the forecasting methods in Chapter 7. These ideas, taken together, explain why revenue management involves so many numbers. Fixed capacity and low marginal cost make every sale tempting. Perishability puts a deadline on every room. Segmentation creates the opportunity to charge different prices. Advance selling and uncertain demand make the opportunity risky. The formulas are simply the tools for measuring how well a hotel has handled these pressures, and for deciding, night by night and rate by rate, what to do next. The next three chapters take up the measures; the rest of the booklet takes up the decisions. Chapter 2: Occupancy, ADR and RevPAR Three numbers dominate the daily conversation in any hotel: occupancy, average daily rate and revenue per available room. They appear in the morning report, the owner's monthly statement, the brand's performance review and almost every revenue management exam. They are easy to define and surprisingly easy to misuse. This chapter sets out each one, shows how they relate, and works through the conventions and traps that cost students marks. The key to all three is to ask of every ratio what sits in the numerator, what sits in the denominator, and why. Occupancy and ADR each capture half of a hotel's rooms performance; RevPAR joins the halves together. Getting the denominators right is most of the battle. Occupancy: rooms sold over rooms available Occupancy is the proportion of available rooms that were sold in a given period. Occupancy = Rooms sold ÷ Rooms available Take an illustrative 240-room hotel on a single Wednesday night. It sold 198 rooms to paying guests and earned £23,760 in rooms revenue. Occupancy = 198 ÷ 240 = 0.825 = 82.5% For a period longer than one night, both numerator and denominator are room nights. A 240-room hotel has 240 × 30 = 7,200 room nights available in a 30-day month; if it sold 5,400 of them, its occupancy for the month was 5,400 ÷ 7,200 = 75 per cent. Two conventions need care. The first concerns rooms that cannot be sold. A room may be out of order because of a burst pipe or a refurbishment. Hotel accounting in the United States and in many international companies follows the Uniform System of Accounts for the Lodging Industry (USALI), now in its twelfth revised edition, which took effect for reporting periods from January 2026 (Hospitality Financial and Technology Professionals [HFTP], 2024). Under the approach USALI has followed since its tenth edition, rooms remain in the available count when they are out of order for short periods; only rooms withdrawn for an extended period, such as six consecutive months or more, or hotels closed for a season, are removed from supply. The logic is that a manager who could reduce the denominator every time a room was out of service would be able to flatter the occupancy figure by neglecting maintenance. The difference matters. If twelve of the 240 rooms were out of order that Wednesday and the manager removed them from the denominator, the reported occupancy would rise. Occupancy excluding out-of-order rooms = 198 ÷ 228 ≈ 86.8% Nothing about the hotel's performance changed; only the convention did. In an exam, if a question tells you that some rooms were out of order, state which convention you are using, and use the full inventory unless the question directs otherwise. The second convention concerns complimentary rooms, rooms occupied by guests who pay nothing, such as a travel writer or a guest compensated for a previous problem. Because they earn no revenue, including them in the rooms-sold figure used for ADR would drag the average rate down. The usual practice is to calculate ADR on paid rooms only, and benchmarking services likewise exclude complimentary rooms from demand. If a question gives you both paid and complimentary rooms, the safe approach is to calculate occupancy and ADR on paid rooms and to note the treatment you have chosen. Be precise, too, about the difference between percentage points and percentages. If occupancy rises from 75 per cent to 78 per cent, it has risen by three percentage points, which is a relative increase of four per cent (3 ÷ 75 = 0.04). Examiners frequently test this distinction, and business reports frequently blur it. Finally, occupancy measures rooms, not people. A room sold to two guests counts once. The number of guests per occupied room, sometimes called multiple or double occupancy, is a separate statistic that matters for food and beverage forecasting and for staffing breakfast, but it does not enter the occupancy ratio. If the Wednesday's 198 rooms held 260 guests, the hotel averaged 260 ÷ 198 ≈ 1.31 guests per occupied room. ADR: rooms revenue over rooms sold Average daily rate is the average price paid for each room sold. ADR = Rooms revenue ÷ Rooms sold For the same Wednesday: ADR = £23,760 ÷ 198 = £120.00 The numerator should contain rooms revenue only. Where a rate includes breakfast, parking or other items, the standard accounting practice is to allocate the package price between departments so that the food element is recorded as food revenue and only the room element as rooms revenue. Taxes collected on behalf of government are not revenue at all and are excluded. Mandatory fees charged per room, such as the resort or destination fees common in some United States markets, raise their own accounting questions; they have also become a matter of consumer law, as Chapter 6 explains. ADR has one statistical property that causes endless trouble: you cannot average averages unless the underlying weights are equal. Consider an illustrative 100-room hotel over two nights. On Friday it sold 95 rooms at an average of £150; on Tuesday it sold 50 rooms at an average of £90. Friday rooms revenue = 95 × £150 = £14,250 Tuesday rooms revenue = 50 × £90 = £4,500 Two-night rooms revenue = £14,250 + £4,500 = £18,750 Two-night rooms sold = 95 + 50 = 145 Two-night ADR = £18,750 ÷ 145 ≈ £129.31 The simple average of the two ADRs would be (£150 + £90) ÷ 2 = £120, which is wrong, because Friday contributed almost twice as many rooms as Tuesday. The correct ADR is always total rooms revenue divided by total rooms sold for the period. Weighted averages appear throughout revenue management, and the discipline of returning to totals rather than averaging ratios will protect you from a whole class of errors. The same rule applies to occupancy when the number of available rooms changes within a period. Suppose a 200-room hotel runs at 80 per cent for the first fifteen nights of a month and then withdraws 50 rooms for a long refurbishment, running its remaining 150 rooms at 90 per cent for the last fifteen nights. Rooms available = (200 × 15) + (150 × 15) = 3,000 + 2,250 = 5,250 Rooms sold = (0.80 × 3,000) + (0.90 × 2,250) = 2,400 + 2,025 = 4,425 Monthly occupancy = 4,425 ÷ 5,250 ≈ 84.3% The simple average of 80 and 90 per cent, 85 per cent, overstates the month because the higher occupancy was achieved on a smaller base. RevPAR: the bridge between rate and volume Revenue per available room divides rooms revenue by all the rooms the hotel had available, sold or not. RevPAR = Rooms revenue ÷ Rooms available For the Wednesday: RevPAR = £23,760 ÷ 240 = £99.00 RevPAR can also be calculated from the other two measures, because it is their product. RevPAR = Occupancy × ADR RevPAR = 0.825 × £120.00 = £99.00 It is worth seeing why this identity holds, because once you see it you will never forget it. Write occupancy as rooms sold over rooms available, and ADR as revenue over rooms sold. Multiply them, and rooms sold cancels. (Rooms sold ÷ Rooms available) × (Rooms revenue ÷ Rooms sold) = Rooms revenue ÷ Rooms available This is why RevPAR became the headline measure of hotel performance. A manager can raise occupancy by cutting price, or raise ADR by turning guests away. Either alone can look impressive. RevPAR captures both and so shows whether a change in strategy actually raised the revenue earned from the building's capacity. Because its denominator is the full inventory, it penalises empty rooms, which occupancy and ADR on their own do not both do. Unlike ADR, RevPAR can be averaged across days when the number of available rooms is constant, because every day then carries the same weight. In the two-night example above, Friday's RevPAR was £14,250 ÷ 100 = £142.50 and Tuesday's was £4,500 ÷ 100 = £45.00. Their simple average, £93.75, equals the two-night RevPAR of £18,750 ÷ 200. When capacity changes, return to totals. Segment mix and the ADR paradox ADR is an average across guests paying very different rates, and averages across groups can behave in ways that surprise. It is possible for every segment's average rate to rise while the hotel's overall ADR falls. Suppose an illustrative hotel sold, on a typical night last year, 100 rooms to corporate guests at £150 and 100 rooms to leisure guests at £100. This year, corporate demand has weakened and the hotel has filled the gap with leisure business: it sells 60 rooms to corporate guests at £155 and 150 to leisure guests at £105. Last year: revenue = (100 × £150) + (100 × £100) = £25,000 Last year: ADR = £25,000 ÷ 200 = £125.00 This year: revenue = (60 × £155) + (150 × £105) = £9,300 + £15,750 = £25,050 This year: ADR = £25,050 ÷ 210 ≈ £119.29 Both segments paid £5 more than last year, yet ADR fell by nearly £6. The reason is a change in mix: a larger share of rooms went to the lower-rated segment. Analysts separate the two influences. The rate effect asks what ADR would have been with this year's rates and last year's mix: with half the rooms at £155 and half at £105, it would have been £130, a rise of £5. The mix effect is the rest: £119.29 − £130.00 ≈ −£10.71. Reporting ADR without this decomposition can lead a manager to conclude that pricing has failed when in fact pricing has succeeded and the mix of demand has shifted. In an exam, whenever segment data are given, calculate the segment rates as well as the overall ADR, and comment on mix. Solving for the unknown Many exam questions give you two of the three measures and ask for the third, or ask what one must become to hit a target. Treat the identity as an equation and rearrange it. A hotel's owner sets a RevPAR target of £105 for next month. The forecast occupancy is 84 per cent. What ADR must the hotel achieve? ADR required = RevPAR target ÷ Occupancy ADR required = £105 ÷ 0.84 = £125.00 Another hotel's RevPAR last month was £99 and its ADR was £132. What was its occupancy? Occupancy = RevPAR ÷ ADR = £99 ÷ £132 = 0.75 = 75% A related question asks how RevPAR changes when occupancy and ADR both change. Because RevPAR is a product, the growth rates combine by multiplication, not addition. 1 + RevPAR growth = (1 + Occupancy growth) × (1 + ADR growth) Suppose occupancy rises from 75 to 78 per cent, a relative rise of 4 per cent, while ADR falls from £120 to £116.40, a fall of 3 per cent. 1 + RevPAR growth = 1.04 × 0.97 = 1.0088 RevPAR growth = 0.88% Check: old RevPAR = 0.75 × £120 = £90.00; new RevPAR = 0.78 × £116.40 = £90.79 The shortcut of adding the growth rates (4 − 3 = 1 per cent) is close when changes are small, but it is an approximation, and the error grows with the size of the changes. Use multiplication in written answers. The yield statistic and what RevPAR hides Before RevPAR became standard, some hotels measured yield: the ratio of the revenue actually achieved to the revenue that would have been earned if every room had been sold at its full published rate (Orkin, 1988). Yield = Actual rooms revenue ÷ Potential rooms revenue Potential rooms revenue = Rooms available × Full rate If the Wednesday hotel's full rate was £160: Potential rooms revenue = 240 × £160 = £38,400 Yield = £23,760 ÷ £38,400 ≈ 61.9% The yield statistic has the attraction of expressing performance as a percentage of an ideal. Its weakness is that the ideal is arbitrary. The full published rate, often called rack rate, is a number the hotel chooses, and in an age of dynamic pricing it may rarely be charged. Raise the rack rate and yield falls without anything changing in the hotel. For this reason RevPAR, which needs no reference price, displaced yield as the standard measure, though the underlying idea of comparing achieved revenue with potential revenue remains useful in exam questions and in thinking about what a night could have earned. RevPAR has blind spots of its own, and they are the subject of the next chapter. It ignores every source of revenue other than rooms, so a resort with a thriving spa and a city hotel with no restaurant are measured on the same narrow base. It ignores the cost of acquiring each booking, so a room sold through a commission-charging intermediary counts the same as one booked directly. And, most importantly, it is indifferent between revenue earned through rate and revenue earned through volume, even though a room sold at a higher rate costs no more to service while an extra room sold incurs housekeeping, laundry and amenity costs. Two strategies with identical RevPAR can produce different profits. These limitations do not make RevPAR a poor measure. They make it a revenue measure, doing a revenue measure's job. The mistake is to treat it as a measure of success on its own. The measures in the next chapter correct its blind spots by moving, step by step, from revenue towards profit. A checklist for exam questions The errors that recur in student scripts on these three measures are few, and all are avoidable. The first is using rooms sold instead of rooms available as the denominator of RevPAR, which simply reproduces ADR. The second is averaging daily ADRs, or averaging occupancies across periods with different supply, instead of returning to totals. The third is confusing percentage points with percentages when describing a change. The fourth is including complimentary rooms, taxes or non-room package elements without saying so. The fifth is adding growth rates rather than multiplying them. A sixth, more a matter of presentation than arithmetic, is failing to state units: an answer of "99" means nothing until it is written as £99.00 per available room. A final sanity check is always worth a line. RevPAR can never exceed ADR, because occupancy cannot exceed 100 per cent. If your RevPAR is larger than your ADR, you have divided by the wrong number of rooms. Chapter 3: From Revenue to Profit: TRevPAR, Net RevPAR and GOPPAR RevPAR tells a manager how much rooms revenue each unit of capacity earned. It does not tell the manager how much money the hotel made. For most of the history of hotel revenue management that gap was tolerated, because rooms revenue was the part of the business the revenue manager controlled and profit was the finance director's concern. Over the past two decades the gap has closed. Owners and asset managers now judge hotels on profit per available room, distribution costs have grown large enough to matter, and hotels with significant food, beverage, spa or meeting revenue have argued, fairly, that measuring them on rooms alone misrepresents their performance. When Kimes (2011) surveyed revenue management professionals about the future of the field, a common expectation was that performance measurement would move away from RevPAR towards total revenue and gross operating profit, with GOPPAR the measure most often named. This chapter follows that shift in three steps. TRevPAR widens the numerator from rooms revenue to total revenue. Net RevPAR subtracts the cost of acquiring the business. GOPPAR subtracts operating costs to arrive at profit. Each step answers a question that RevPAR cannot, and each has its own blind spot. TRevPAR: counting the whole hotel Total revenue per available room divides all operating revenue by rooms available. TRevPAR = Total operating revenue ÷ Rooms available The denominator is still rooms available, because the room inventory is the hotel's defining unit of capacity and the thing that brings guests to the other outlets. The numerator now includes food and beverage, spa, parking, retail, meeting room hire and miscellaneous income. Consider an illustrative 200-room hotel over a 30-day month. It sold 4,800 room nights at an ADR of £125. It also earned £270,000 from food and beverage, £60,000 from other operated departments such as its spa and car park, and £30,000 in miscellaneous income. Rooms available = 200 × 30 = 6,000 Occupancy = 4,800 ÷ 6,000 = 80% Rooms revenue = 4,800 × £125 = £600,000 RevPAR = £600,000 ÷ 6,000 = £100.00 Total revenue = £600,000 + £270,000 + £60,000 + £30,000 = £960,000 TRevPAR = £960,000 ÷ 6,000 = £160.00 Rooms revenue is £600,000 ÷ £960,000 = 62.5 per cent of the total. A close cousin of TRevPAR divides total revenue by rooms sold instead, giving total revenue per occupied room: £960,000 ÷ 4,800 = £200. That figure answers a different question, namely how much each staying guest's room generates across the whole hotel, and is useful when deciding whether a lower room rate might be worth accepting from guests who will spend heavily in the restaurant. TRevPAR corrects RevPAR's narrowness, but it inherits a problem of its own: revenue from different departments is not equally valuable. A pound of rooms revenue typically carries a much higher departmental margin than a pound of food and beverage revenue, because rooms have lower variable costs than kitchens and restaurants. A hotel could raise its TRevPAR by selling heavily discounted banquets that barely cover their food and labour costs. For that reason TRevPAR is best read alongside a profit measure, never instead of one. Net RevPAR and the cost of acquisition Every booking costs something to win. A reservation made through an online travel agency typically carries a commission; one made through the global distribution systems used by travel agents carries transaction fees and often a travel agent commission; a direct booking on the hotel's own website carries payment card fees, search advertising costs and the costs of the booking engine; a loyalty member's stay carries the programme's charges. Collectively these are called customer acquisition costs or distribution costs. Net RevPAR subtracts them from rooms revenue before dividing by rooms available. Net RevPAR = (Rooms revenue − Acquisition costs) ÷ Rooms available Suppose the hotel in the example paid £72,000 in commissions, fees and loyalty charges on its rooms business during the month. Net rooms revenue = £600,000 − £72,000 = £528,000 Net RevPAR = £528,000 ÷ 6,000 = £88.00 Net ADR = £528,000 ÷ 4,800 = £110.00 Acquisition costs absorb £72,000 ÷ £600,000 = 12 per cent of rooms revenue. Two hotels with identical RevPAR could have very different net RevPAR if one relies heavily on intermediaries. The same logic applies to comparing individual bookings. A room sold through an intermediary at £130 with an 18 per cent commission is worth less to the hotel than the same room sold directly at £122 with a 3 per cent card fee and £4 of marketing cost. Net value of intermediary booking = £130 × (1 − 0.18) = £106.60 Net value of direct booking = £122 − (0.03 × £122) − £4 Net value of direct booking = £122 − £3.66 − £4 = £114.34 The direct booking has the lower headline rate and the higher net value. This is the reasoning behind the effort hotels put into winning direct bookings, and behind measures such as the direct revenue ratio, the share of rooms revenue arriving through the hotel's own channels, which the second edition of the textbook discusses alongside net RevPAR. Be careful not to overstate the conclusion. Intermediaries also bring guests who would never have found the hotel otherwise, and a booking that would not have happened at all is worth more at £106.60 than not at all. The question is always what the alternative would have been, which is opportunity cost again. GOPPAR: profit per available room Gross operating profit is the profit a hotel earns from operations before charges that relate to ownership and financing rather than day-to-day management. The Uniform System of Accounts for the Lodging Industry sets out the structure used by most hotel companies (HFTP, 2024). Each operated department, such as rooms, food and beverage or the spa, deducts its own direct costs from its revenue to give a departmental profit. The departmental profits are summed, and then the undistributed operating expenses are deducted: administrative and general, information and telecommunications systems, sales and marketing, property operation and maintenance, and energy and utility costs. What remains is gross operating profit (GOP). Management fees, property taxes, insurance, rent, interest and depreciation come further down the statement and are not part of GOP, which is why GOP is widely used to judge the performance of the operator as distinct from the owner. GOP = Total revenue − Departmental expenses − Undistributed operating expenses GOPPAR = GOP ÷ Rooms available Continuing the example, suppose the rooms department's direct costs were £120,000, food and beverage's were £200,000 and the other operated departments' were £42,000, with miscellaneous income carrying no departmental cost. Undistributed operating expenses were £262,000. Rooms departmental profit = £600,000 − £120,000 = £480,000 Food and beverage departmental profit = £270,000 − £200,000 = £70,000 Other operated departments profit = £60,000 − £42,000 = £18,000 Total departmental profit = £480,000 + £70,000 + £18,000 + £30,000 = £598,000 GOP = £598,000 − £262,000 = £336,000 GOPPAR = £336,000 ÷ 6,000 = £56.00 GOP margin = £336,000 ÷ £960,000 = 35.0% The departmental figures show why the mix of revenue matters. Rooms earned a departmental margin of £480,000 ÷ £600,000 = 80 per cent, while food and beverage earned £70,000 ÷ £270,000 ≈ 26 per cent. A pound of extra room revenue is worth roughly three times as much at the departmental level as a pound of extra food and beverage revenue. One useful by-product is the cost per occupied room (CPOR), the rooms department's direct cost divided by rooms sold. CPOR = Rooms departmental expenses ÷ Rooms sold = £120,000 ÷ 4,800 = £25.00 CPOR is the practical estimate of the variable cost of an occupied room that feeds into the contribution margin calculations used throughout this booklet. It is not a perfect estimate, because some rooms costs, such as the salary of the executive housekeeper, do not rise with each extra room sold, but it is the figure most often used. Rate versus volume: why flow-through matters The clearest way to see why profit measures matter is to compare two routes to the same RevPAR. Take an illustrative 100-room hotel over a 30-night month running at 70 per cent occupancy with an ADR of £100 and a variable cost of £25 per occupied room. Room nights available = 100 × 30 = 3,000 Rooms sold = 0.70 × 3,000 = 2,100 Rooms revenue = 2,100 × £100 = £210,000 Variable costs = 2,100 × £25 = £52,500 Contribution = £210,000 − £52,500 = £157,500 RevPAR = £210,000 ÷ 3,000 = £70.00 Option A raises ADR by 5 per cent to £105 with no change in rooms sold. Option B raises rooms sold by 5 per cent, to 2,205, with no change in ADR. Option A revenue = 2,100 × £105 = £220,500 Option A contribution = £220,500 − (2,100 × £25) = £168,000 Option B revenue = 2,205 × £100 = £220,500 Option B contribution = £220,500 − (2,205 × £25) = £165,375 RevPAR under both options = £220,500 ÷ 3,000 = £73.50 RevPAR cannot tell the two options apart. Profit can. The rate increase adds £10,500 of contribution because every extra pound falls straight through to the bottom line. The volume increase adds only £7,875 because each extra room carries its own £25 of cost. If the extra 105 rooms under Option B were won through an intermediary charging 18 per cent, a further 105 × £100 × 0.18 = £1,890 would be lost, leaving £163,485. None of this means rate is always better than volume; the extra guests under Option B may spend in the restaurant and bar, and a rate increase may not be achievable without losing guests. It means that the comparison must be made on profit, not on RevPAR. The measure that captures this is flow-through: the proportion of a change in revenue that turns into a change in profit. Flow-through = Change in GOP ÷ Change in total revenue If the 200-room hotel's total revenue rises from £960,000 to £1,010,000 next month and its GOP rises from £336,000 to £361,000: Flow-through = (£361,000 − £336,000) ÷ (£1,010,000 − £960,000) Flow-through = £25,000 ÷ £50,000 = 50% Half of every additional pound of revenue became profit. Owners and asset managers watch flow-through closely because it shows whether revenue growth is being bought with costs. Rate-led growth typically shows high flow-through; volume-led growth, particularly in low-margin departments, shows less. When revenue falls, the same measure shows how much of the decline the operator managed to offset through cost control. Owners, operators and incentives The choice of measure is not merely technical, because hotel management contracts often tie the operator's fees to particular measures. A common structure pays the operator a base fee calculated as a percentage of total revenue and an incentive fee calculated as a percentage of some measure of profit. Terms vary widely from contract to contract, but even a simple illustrative version shows why owners care which measures drive decisions. Suppose an operator earns a base fee of 3 per cent of total revenue and an incentive fee of 8 per cent of GOP. It is choosing between two strategies for the coming year. Strategy X, a volume push through intermediaries and discounted banqueting, would add £50,000 of revenue but only £5,000 of GOP. Strategy Y, a rate-led approach, would add £20,000 of revenue and £12,000 of GOP. Strategy X fees = (0.03 × £50,000) + (0.08 × £5,000) = £1,900 Strategy X owner's gain = £5,000 − £1,900 = £3,100 Strategy Y fees = (0.03 × £20,000) + (0.08 × £12,000) = £1,560 Strategy Y owner's gain = £12,000 − £1,560 = £10,440 The operator earns more from Strategy X; the owner gains more than three times as much from Strategy Y. Nothing in the arithmetic is unusual, and it explains why owners and asset managers increasingly insist that revenue decisions be judged on GOPPAR and flow-through rather than on RevPAR or TRevPAR alone, and why contracts are often negotiated to give incentive fees more weight. Choosing and combining measures Each measure answers a different question, and the choice depends on who is asking and why. Table 1 draws the measures of this chapter and the last together. Table 1. Hotel performance measures compared. Measure Calculation What it reveals Main blind spot Occupancy Rooms sold ÷ rooms available Volume of room demand captured Says nothing about price ADR Rooms revenue ÷ rooms sold Average price achieved Ignores empty rooms RevPAR Rooms revenue ÷ rooms available Revenue earned from room capacity Ignores costs and non-room revenue TRevPAR Total operating revenue ÷ rooms available Revenue from the whole hotel Treats all revenue as equally profitable Net RevPAR (Rooms revenue − acquisition costs) ÷ rooms available Rooms revenue after distribution costs Ignores operating costs GOPPAR Gross operating profit ÷ rooms available Operating profit from the whole hotel Affected by cost allocation and timing CPOR Rooms departmental expenses ÷ rooms sold Cost of servicing an occupied room Mixes fixed and variable costs Note: Illustrative summary; definitions follow common industry practice as set out in HFTP (2024). A revenue manager setting tonight's price will still watch RevPAR, occupancy and ADR most closely, because those respond to pricing decisions within days. A general manager will add TRevPAR and net RevPAR, because the balance between departments and channels is part of the job. An owner deciding whether the operator is doing well will look first at GOPPAR and flow-through. The skill examiners look for is not the ability to recite these definitions, but the ability to say which measure answers which question, and to show with a worked example how two hotels, or two strategies, could rank differently depending on the measure chosen. A final caution concerns comparisons between hotels on GOPPAR. Because it depends on how costs are allocated between departments and on the timing of expenses such as maintenance, GOPPAR is most reliable when the hotels being compared follow the same accounting system. That is exactly the purpose of USALI, and the reason benchmarking services that report profit measures collect data in its format. The next chapter turns to benchmarking in its most common form: comparing a hotel's occupancy, rate and RevPAR against those of its direct competitors. Hashtags: #TheMathOfMargins #RevenueManagement #HospitalityRevenueManagement #PerishableCapacity #OpportunityCost #ContributionMargin #Occupancy #AverageDailyRate #ADR #RevenuePerAvailableRoom #RevPAR #TotalRevenuePerAvailableRoom #TRevPAR #NetRevPAR #GOPPAR #CustomerAcquisitionCosts #FlowThrough #PriceElasticity #DifferentialPricing #RateFences #DemandForecasting #InventoryAllocation #GroupDisplacement #Overbooking #FutureOfRevenueManagement Pasted markdown

Download the Book (PDF): Introduction Sometime in the years before the First World War, a young man came to see Martin Buber. Buber had spent the morning in what he later called religious enthusiasm, a state of inward rapture, and he received the visitor kindly. He answered the questions that were put to him. He was attentive, friendly, even generous. What he did not do was hear the questions the young man had not put. Some time later Buber learned that the visitor was dead, and that he had come that day not for conversation but for a decision, for someone to be present to him at a moment when his life was in the balance. Buber had been polite. He had not been there. Buber told this story in a short essay called "Dialogue," published in 1929, under the heading "A Conversion." What changed, he said, was his understanding of religion itself. He gave up the idea that the religious life is a matter of exalted states, of moments lifted out of the ordinary. What remained was the ordinary hour, the claim of the person standing in front of you, and the question of whether you answer it. From that afternoon onward, as he told it, he possessed nothing but the everyday out of which he is never taken. A generation later and in a different country, Emmanuel Levinas described the moment of meeting another person in terms that sound at first like an intensification of Buber's. The face of the other person, he wrote, is not an object I perceive. It is a demand addressed to me. Before I have decided anything, before I have formed an opinion or made a choice, the face says to me, in effect, you shall not kill. And the responsibility it lays on me is not proportioned to what I have done or what I have promised. It is infinite. It grows the more I take it up. Levinas liked to quote a line spoken by a dying young man in Dostoevsky's The Brothers Karamazov: that each of us is guilty before everyone for everything, and I more than the others. These two thinkers are the subject of this book. Both were Jews formed by the collapse of European confidence in reason and progress. Both wrote in the shadow of catastrophe, Buber in the aftermath of one world war, Levinas in the aftermath of a second and of the murder of most of his family. Both insisted that philosophy had misunderstood the most basic thing about human life: that we exist first not as knowers of a world but as beings addressed by one another. And both are commonly grouped together, in syllabi and in popular writing, under a phrase like "the philosophy of dialogue" or "the ethics of the Other," as though they held a single view in two dialects. They did not. Levinas read Buber closely, admired him, and criticized him in print. Buber replied. The disagreement between them, carried on in essays and brief exchanges between the late 1950s and Buber's death in 1965, and continued by Levinas for another thirty years, turns on a question that looks technical and is not. Is the relation between persons, at its deepest, reciprocal or asymmetrical? For Buber, the I-Thou relation is mutual. I say Thou to you and in the saying I become who I am, but you, in the same event, become who you are as well; the relation lives in what Buber called "the between," a space neither of us owns. For Levinas, this picture of mutuality, however beautiful, misses the ethical heart of the encounter. The other person comes to me from a height. She commands; I am commanded. What I owe her is not balanced by anything she owes me, and to ask whether she is equally responsible for me is already to have turned away from her. The argument of this book This book argues that the disagreement between Buber and Levinas is real, and that it cannot be dissolved by saying that each was describing a different aspect of the same thing. But it also argues that the disagreement is productive in a specific way. Buber's reciprocity and Levinas's asymmetry answer different questions. Buber was asking what makes a person a person: how a self comes into being and stays alive in relation to others, to the world, and to God. Levinas was asking what makes a self responsible: why the presence of another human being is not simply a fact about the world but a summons that I cannot decline without guilt. An ethics that forgets Buber's question produces a self that is all obligation and no life, a hostage with no home. An ethics that forgets Levinas's produces a warm mutuality that can quietly exclude those who have nothing to give back: the infant, the dying, the stranger who does not speak our language, the enemy. The sharpest test of both positions is what Levinas called "the third." Real life is never two people alone. There is always someone else, and the moment there is a third person, the question of justice arises: whom do I serve first, how do I compare incomparable claims, what institutions do we need? Buber tended to treat this as the problem of community, a matter of extending the life of the between into social forms. Levinas treated it as a necessary betrayal of the face, a point at which the infinite demand must be measured, weighed, and limited, and yet never simply replaced. How each thinker handles the third tells us more about his philosophy than any definition of the I-Thou or the face. What the reader will find The first chapter sets the scene: the intellectual and religious crisis of German-speaking Jewry around the First World War, the late work of Hermann Cohen, the friendship of Buber and Franz Rosenzweig, and the young Levinas's arrival in Strasbourg and Freiburg, where he studied with Husserl and heard Heidegger. The second chapter reads I and Thou itself, Buber's short, strange, poetic book of 1923, and tries to say plainly what its central distinction means. The third follows Buber's later work, where the vision of I and Thou was tested against therapy, teaching, politics, and the conflict between Jews and Arabs in Palestine. The fourth and fifth chapters turn to Levinas. The fourth traces his early struggle to escape from what he called "being" and its anonymous weight, a struggle conducted partly in a German prisoner-of-war camp. The fifth reads Totality and Infinity, the book of 1961 in which the face of the Other first appears as the foundation of ethics and of philosophy itself. The sixth chapter stages the quarrel between the two men directly and tries to be fair to both sides. The seventh reads Levinas's later masterpiece, Otherwise than Being, with its language of substitution and hostage, and asks what happens to the infinite demand when the third party enters and politics begins, including in Levinas's own troubling remarks about Israel in 1982. The eighth chapter turns to God: Buber's "eternal Thou," addressed in every genuine meeting, and Levinas's God who is never an interlocutor, who withdraws into the face of the neighbor and is found only in the responsibility it commands. A conclusion asks what follows for anyone who wants to think about ethics from the encounter with another person rather than from rules or outcomes. Two limits should be stated at the outset. First, this is a book about two thinkers and the relation between them, not a survey of dialogical philosophy as a whole. Franz Rosenzweig, Ferdinand Ebner, Gabriel Marcel, Mikhail Bakhtin, and others appear where they illuminate the main argument and not otherwise. Second, both Buber and Levinas wrote in languages other than English, and much depends on translation. Buber's Du is the familiar form of address, the word used between lovers, close friends, children and parents, and in prayer. "Thou" in modern English sounds archaic and churchly; "You," which Walter Kaufmann chose for his 1970 translation, loses the intimacy of the German. Levinas's autrui, the personal other, is distinct from l'autre, the other in general, and his translators have used capital letters inconsistently to mark the difference. Where the choice of word matters, the book will say so. Why this still matters It would be possible to treat Buber and Levinas as historical figures, interesting for the light they cast on twentieth-century Jewish thought and on the reception of phenomenology in France. They are that. But the questions they asked have not gone away, and in some fields they have become more pressing. Physicians and nurses who work with patients who cannot speak, teachers who work with children who cannot yet reason for themselves, social workers and therapists whose relationships are structured by power and payment, all encounter daily the tension between mutuality and asymmetry that divided these two men. So does anyone who has cared for a dying parent, where the care runs in one direction and yet something is received that cannot be described as a return. Political life too keeps asking the question of the third: how can a society that must count and classify people remain answerable to each person as someone who cannot be counted? Neither Buber nor Levinas offers rules. Both distrusted systems. What they offer instead is a description of what is at stake when one human being faces another, and a warning about what we lose when we forget it. The chapters that follow try to take both the description and the warning seriously, and to show that the conversation between these two thinkers is not finished. CHAPTER 1 Before Dialogue Philosophies of dialogue did not arise because someone noticed, for the first time, that people talk to each other. They arose because a particular way of thinking about the self had failed, and failed publicly, in the eyes of a generation. To understand why Buber and Levinas wrote as they did, one has to see what they were writing against and what they were writing after. The self that knows The dominant tradition of modern European philosophy, from Descartes through Kant to the neo-Kantian schools that ruled German universities in the late nineteenth century, began with a knowing subject. The first certainty was the certainty of one's own thinking. The world was what that thinking could grasp, organize, and justify. Other people appeared in this picture chiefly as a problem: how could I know that the bodies moving around me had minds like mine? The "problem of other minds" was a genuine puzzle, but the fact that it was framed as a puzzle about knowledge already said something. The other person was, first of all, an object whose inner life I had to infer. Hegel had complicated this picture by making recognition central to self-consciousness. In the famous passage of the Phenomenology of Spirit on lordship and bondage, a self becomes fully a self only when it is recognized by another self. But the Hegelian story is a story of struggle, and its resolution lies not in the meeting of two persons but in the unfolding of Spirit, a totality in which individual encounters are moments to be taken up and surpassed. Both Buber and Levinas would, in different ways, reject this move. For Buber, the meeting between persons is not a stage on the way to anything. For Levinas, the Hegelian totality is precisely the danger: a system that makes sense of everything by absorbing it, including the other person, into a whole. By the early twentieth century, the systems were under strain from several directions. Kierkegaard, rediscovered in German translation in the decades before 1914, had insisted that the single individual standing before God could not be absorbed into any system. Nietzsche had declared the death of God and exposed the will to power beneath the claims of reason. Wilhelm Dilthey had argued that human life must be understood from within rather than explained from without. And Edmund Husserl, in Göttingen and later Freiburg, had launched phenomenology, a method of describing experience as it is actually lived, before theory has classified it. Then came the war. The First World War did not create the crisis of European rationalism, but it made it impossible to ignore. The educated classes of Germany, France, and Britain had marched into catastrophe convinced that their cause was the cause of civilization. German Jews, in particular, had invested heavily in the promise that assimilation into German culture, Bildung, would secure their place in the nation. Many volunteered eagerly. Buber himself, in the first months of the war, wrote with enthusiasm about the experience of community it seemed to create, an enthusiasm he later regretted and for which his friend Gustav Landauer rebuked him sharply. By 1918, the idea that reason, culture, and progress would carry humanity forward had become, for many, a bitter joke. Hermann Cohen and the fellow human One figure stands at the hinge between the old confidence and the new questioning. Hermann Cohen, the founder of the Marburg school of neo-Kantianism, was the most eminent Jewish philosopher in Germany at the turn of the century. His philosophy was rigorously rationalist: ethics was grounded in pure reason, and the idea of humanity was an infinite task toward which history moved. Cohen was also a committed Jew, and in his final years, after retiring from Marburg to teach at the Berlin Academy for the Science of Judaism, he wrote a book that his own system could barely contain. Religion of Reason out of the Sources of Judaism appeared in 1919, a year after his death. In that book Cohen drew a distinction that would echo through both Buber and Levinas. There is the Nebenmensch, the person beside me, the human being as an instance of the species, one among many. And there is the Mitmensch, the fellow human, the person who concerns me. The transition from one to the other, Cohen argued, happens through compassion, and above all through the encounter with suffering. The poor person, the widow, the orphan, and the stranger, the figures the Hebrew prophets return to again and again, are not merely examples of human beings in difficulty. They are the occasion on which the other becomes a Thou for me, and on which I, correspondingly, become an I capable of moral responsibility. Cohen still thought of all this within the framework of reason. But the direction of his late thought pointed toward something his students would take further: the idea that ethics does not begin with a principle I discover in myself but with a person who stands before me in need. Levinas's widow, orphan, and stranger, who appear throughout his writing as the paradigm of the face, are Cohen's figures before they are his. And Buber's insistence that the I comes into being only through the Thou echoes, whether or not Buber would have put it this way, the late Cohen's discovery that the moral self is born in the encounter. Rosenzweig, Ebner, and the new thinking Cohen's most gifted student in his Berlin years was Franz Rosenzweig. Rosenzweig had come close to converting to Christianity in 1913, as several of his cousins and friends had done, and then, after attending a Yom Kippur service in a small Berlin synagogue, decided to remain a Jew. He spent the war as an anti-aircraft gunner in the Balkans and wrote, on military postcards sent home to his mother, much of the draft of The Star of Redemption, published in 1921. The Star opens with an attack on the whole tradition of philosophy from Ionia to Jena, from the pre-Socratics to Hegel, for its attempt to reduce everything to one principle. Against this, Rosenzweig set three irreducible elements, God, world, and human being, and argued that they come into relation not through thought but through events: creation, revelation, and redemption. Revelation, for Rosenzweig, is the moment in which God addresses the soul in love, and the soul, addressed, is able to answer. Language, and specifically spoken language, the language of address and response, is at the heart of this "new thinking." Rosenzweig contrasted it with the old thinking of philosophers who reason alone. The new thinker, he said, needs another person and needs time; he cannot know in advance what the other will say. Rosenzweig and Buber became close collaborators in the 1920s. Buber lectured at the Freies Jüdisches Lehrhaus, the house of Jewish adult learning that Rosenzweig founded in Frankfurt in 1920. It was there, in the winter of 1922, that Buber delivered a series of lectures under the title "Religion as Presence" that contained the core of I and Thou. In 1925 the two men began a new German translation of the Hebrew Bible, one that tried to preserve the spoken rhythm and the root-meanings of the Hebrew. Rosenzweig, paralyzed by amyotrophic lateral sclerosis, worked on it until his death in 1929, communicating at the end by indicating letters on a specially adapted typewriter. Buber completed the translation alone, in Jerusalem, in 1961. Buber also acknowledged, in a later essay on the history of the dialogical principle, the work of Ferdinand Ebner, an Austrian Catholic schoolteacher who published The Word and the Spiritual Realities in 1921. Ebner, who worked in near isolation and in poor health, argued that the human I exists only in relation to a Thou, and that the fundamental Thou is God. Buber read Ebner after most of I and Thou was drafted, and he was struck by how close the two had come independently. The coincidence was not an accident. Several thinkers in the German-speaking world, reacting to the same crisis, had arrived at the same conviction: that the primary reality of human existence is not the solitary thinker but the relation between an I and a Thou. Buber before I and Thou Martin Buber was born in Vienna in 1878. When his parents' marriage broke up, he was sent at the age of three to live with his grandparents in Lemberg, then in Austrian Galicia and now Lviv in Ukraine. His grandfather, Solomon Buber, was a wealthy landowner and a distinguished scholar of midrash, the rabbinic literature of scriptural interpretation. Buber grew up in a household where Hebrew texts were studied seriously but in a modern, critical spirit. He later wrote that the separation from his mother, and a moment in childhood when an older girl told him that his mother would never come back, taught him something he would spend his life trying to name: the "mismeeting," the failed encounter between people. As a student in Vienna, Leipzig, Zurich, and Berlin, Buber studied philosophy and art history and was drawn into the cultural wing of the Zionist movement. He argued, against Theodor Herzl's political emphasis, for a Jewish renaissance: a renewal of Jewish culture, spirit, and creativity, not only the acquisition of a territory. Around 1904 he withdrew from active politics and turned to Hasidism, the popular pietist movement of eighteenth-century Eastern Europe. His retellings of the tales of the Baal Shem Tov and of Rabbi Nachman of Bratslav, published from 1906 onward, made Hasidism known to a wide Western audience for the first time. Buber's early writings are mystical in tone. The book Daniel, from 1913, speaks of moments of unity in which the self and the world are fused. The Hasidic material of these years is shaped by a romantic interest in ecstasy and inwardness. What changed, by his own account, was the kind of experience described in the story told at the opening of this book: the discovery that ecstasy could be a way of not being present to the person in front of you. The move from mysticism to dialogue was, for Buber, a move from the extraordinary to the everyday, from union to relation, and from the self's inner life to the space between persons. Levinas between Kovno and Freiburg Emmanuel Levinas was born in 1906 in Kovno, now Kaunas, in Lithuania, then part of the Russian Empire. His family was traditionally observant but also culturally Russian; his father ran a bookshop, and the young Levinas read Pushkin, Tolstoy, and Dostoevsky alongside the Hebrew Bible. Lithuanian Jewry had its own distinctive intellectual tradition, oriented toward the rigorous study of the Talmud rather than toward the emotional piety of Hasidism. The great eighteenth-century authority, the Vilna Gaon, had been a fierce opponent of the Hasidic movement. Levinas would later remark on the difference between the Lithuanian ethos he grew up with and the Hasidic sources Buber drew on, and it is not fanciful to see the difference reflected in their philosophies. Levinas's ethics is an ethics of study, law, and obligation; Buber's is an ethics of presence and spontaneity. During the First World War the family moved to Kharkov in Ukraine, where Levinas witnessed the revolution of 1917. In 1923 he left for Strasbourg to study philosophy at the university there. At Strasbourg he began a lifelong friendship with Maurice Blanchot, who would become one of the most important French writers of the century. And he discovered Husserl. In 1928 and 1929 Levinas went to Freiburg to study with Husserl directly, in Husserl's last semesters before retirement, and there he encountered the man who was about to eclipse his teacher: Martin Heidegger, whose Being and Time had appeared in 1927. Levinas's response to Heidegger was overwhelming admiration. Decades later he would still call Being and Time one of the finest books in the history of philosophy. In the spring of 1929 he attended the famous encounter at Davos, in Switzerland, between Heidegger and Ernst Cassirer, the neo-Kantian heir of Cohen's school. The students at Davos staged a satirical skit, and Levinas, by his own later rueful account, played Cassirer, mocking the older man's style. Cassirer represented the humanist, liberal, rationalist inheritance; Heidegger represented a new thinking that went beneath reason to the question of being. Levinas was on Heidegger's side then. He would later say that he regretted it. His doctoral thesis, The Theory of Intuition in Husserl's Phenomenology, published in 1930, helped introduce phenomenology to France. Jean-Paul Sartre, by one account, first learned of Husserl through it. Levinas took French citizenship in 1931 and began work for the Alliance Israélite Universelle, the French Jewish organization that ran schools across the Mediterranean world. His philosophical path seemed set: an able expositor of German phenomenology for a French audience. Two events changed that path. The first was Heidegger's public embrace of National Socialism in 1933, when he became rector of Freiburg and delivered a rectoral address in support of the new regime. The second was what that embrace revealed about the philosophy itself. In 1934, Levinas published a short essay in the journal Esprit, "Reflections on the Philosophy of Hitlerism." It argued that Hitlerism was not merely a political aberration but a philosophy, one that bound the human being to the body, to blood, and to fate, and that denied the liberal and biblical idea that a person can break with his past and begin anew. The essay did not name Heidegger. But its question, whether a philosophy of being could protect the dignity of the individual person or whether it would dissolve the person into something larger and more anonymous, became the question of Levinas's life. Two paths toward the Other It is useful to set the main dates side by side, because the chronology matters for the argument that follows. Buber's central dialogical works came before the Second World War; Levinas's came after it. Buber's I and Thou was the work of a man in his forties who had already lived through one catastrophe and was trying to find a way back to living relation. Levinas's Totality and Infinity was the work of a man in his fifties who had survived captivity while nearly all his family in Lithuania had been murdered. Table 1 sets out the principal dates. Table 1. Key dates in the lives and works of Buber and Levinas Year Buber Levinas 1878 Born in Vienna — 1906 First Hasidic retellings published Born in Kovno, Lithuania 1923 I and Thou Begins studies in Strasbourg 1928–29 Lectures on dialogue; "Dialogue" (1929) Studies in Freiburg with Husserl; attends Davos 1935 Leads Jewish adult education in Nazi Germany On Escape 1938 Emigrates to Jerusalem — 1940–45 Teaches at the Hebrew University Prisoner of war in Germany 1947 Between Man and Man (English) Existence and Existents; Time and the Other lectures 1957 Postscript to I and Thou; dialogue with Carl Rogers — 1961 Completes Bible translation Totality and Infinity 1963 Replies to critics, including Levinas Difficult Freedom 1965 Dies in Jerusalem — 1974 — Otherwise than Being or Beyond Essence 1995 — Dies in Paris The two men thus came to the Other by different roads. Buber came from mysticism and the renewal of Jewish culture; his discovery was that the self is not complete in its own inner experience but comes to life in meeting. Levinas came from phenomenology and the philosophy of being; his discovery was that being itself, the anonymous and impersonal "there is," is suffocating, and that escape from it comes only through a relation to someone who cannot be absorbed into it. One was trying to recover presence. The other was trying to break out of a totality. The difference in starting points shaped everything that followed, including their inability, when they finally engaged each other directly, fully to agree. CHAPTER 2 The Two Primary Words I and Thou is a short book, fewer than a hundred and fifty pages in most editions, and one of the hardest to summarize in the history of modern thought. It is written in numbered sections of varying length, some a single sentence, some several pages. Its prose is incantatory, dense with images, and deliberately unsystematic. Buber later said that he wrote it under a kind of compulsion, and that he did not change a word of it for decades because he felt that it had come to him rather than been made by him. Many readers have found it inspiring and few have found it clear. The task of this chapter is to say plainly what it claims. Two attitudes, two words The book opens with a statement about the human being's relation to the world. That relation is twofold, Buber says, in accordance with the twofold nature of the primary words a person can speak. These are not single words but word-pairs: I-Thou and I-It. (One could substitute He or She for It without changing anything; the point is that the other is spoken of rather than spoken to.) The first surprising claim is that there is no I taken by itself. There is only the I of the primary word I-Thou and the I of the primary word I-It. When a person says I, he means one of these two. The self is not a thing that exists first and then enters into relations. It is constituted differently according to how it stands toward what it meets. The I of I-It is an individual, a subject who experiences and uses objects. The I of I-Thou is a person, who enters into relation. What distinguishes the two attitudes? The simplest answer is this. In the I-It attitude, I stand over against something and take it in as an object: I observe it, measure it, classify it, compare it with other things, use it for my purposes. The world of It is the world of experience and use, and Buber insists that it is indispensable. Without it we could not survive, build, know, or plan. Science, technology, economics, and administration all belong to the world of It. The It is always bounded; it has a place among other things; it can be located in space and time and described by its properties. In the I-Thou attitude, I do not experience the other at all, in Buber's technical sense. I meet it. The Thou is not a collection of qualities, not a thing among things. When I say Thou, I do not have something; I stand in relation. The Thou fills the horizon. It is not that nothing else exists, but that everything else lives in its light. Buber is careful to say that this does not mean I stop perceiving the particular features of the other. I may still see the color of your eyes and hear the timbre of your voice. But these are no longer inventory. They are how you are present. Table 2 sets out the principal contrasts Buber draws between the two primary words. The table is a simplification of a book that resists tables, but it gives a map of the terrain. Table 2. The two primary words in *I and Thou Feature I-It I-Thou Mode Experience and use Encounter and relation The other appears as Object with properties Whole presence Time Past; the already-happened Present; what happens now Boundaries Bounded, one among many Unbounded, fills the horizon The self Individual, set over against Person, entered into relation Initiative Chosen by the I Both choosing and chosen Duration Stable, can be stored Fleeting, must lapse into It Indispensable for Knowledge, work, survival Meaning, personhood, faith The tree and the three spheres The most famous passage in the book concerns a tree. Buber lists the ways I can regard it. I can take it in as a picture: a rigid pillar in a flood of light, or a splash of green against the grey-blue sky. I can feel it as movement: the flowing veins around the core, the sucking of the roots, the breathing of the leaves. I can classify it as a species and study its structure and functions. I can subdue its presence so that it becomes an expression of law, of the laws by which forces meet and mingle. I can dissolve it into a number, into a pure relation between numbers. In all of these cases, the tree remains an object, occupying space and time. But it can also happen, Buber says, if will and grace are joined, that as I contemplate the tree I am drawn into relation with it, and it ceases to be an It. This does not require that I give up any of the ways of regarding it. Everything belongs to the relation: picture and movement, species and type, law and number, indivisibly united. The tree is not an impression, not a play of my imagination, not a mood. It is bodied over against me and has to do with me, as I with it, only differently. Readers have often found this passage baffling or sentimental. Does Buber think the tree is conscious? He explicitly declines the question. He does not claim that the tree has a soul. He claims that the relation is real and that it is reciprocal in some sense, but he does not say what the tree's side of it consists of. The point of the example is not botanical but philosophical: the I-Thou relation is not confined to relations between people. It is a way of standing toward whatever one meets. Buber distinguishes three spheres in which relation arises. The first is life with nature, where the relation clings to the threshold of speech: the tree, the animal, the stone cannot answer in words, yet something passes. The second is life with other human beings, where the relation is open and takes the form of speech; here we can give and receive the Thou. The third is life with spiritual beings, with forms of art, thought, and spirit, where the relation is without speech but generates speech. The sculptor encountering the form that wants to become a work, the thinker encountering an idea that demands to be thought, stand in this third kind of relation. In each sphere, and through each, Buber says, we glimpse the eternal Thou, the Thou that by its nature cannot become an It. A second, less discussed example makes the point more intimately. In the essay "Dialogue," Buber recalls that as a boy of eleven, spending a summer on his grandparents' estate, he used to slip into the stable and stroke the neck of a broad dapple-grey horse. What he experienced, he writes, was the element of vitality itself, something that was not he and yet let him approach it, and the horse, very gently, raised its head and snorted as a conspirator might signal to a fellow conspirator. But one day it struck him how much fun the stroking was, and he became conscious of his hand. The game went on as before, but something had changed. The next day, when he stroked the horse, it did not raise its head. Buber reports that at the time he judged himself; he knew he had been found wanting. What he had done was to make the relation into an experience, something he enjoyed and observed in himself. The Thou had become an It at the moment he turned from the horse toward his own pleasure. The between If the I-Thou relation is neither in me nor in the other, where is it? Buber's answer is the concept for which he is perhaps most remembered: das Zwischen, the between. The relation is not a feeling. Feelings accompany it, but they dwell in the person, whereas the relation dwells between persons. Love, for Buber, is not in the I as a feeling it has, with the Thou as its content or object; love is between I and Thou. This is why he says, in one of the book's most-quoted lines, that in the beginning is the relation. The between is prior to either pole. The concept has large consequences. It means that the reality of the human world is not exhausted by individuals and their inner states, nor by collectives and their structures. There is a third reality, the interhuman, which cannot be reduced to psychology or to sociology. Buber would later develop this into a whole account of the interhuman sphere, arguing that psychology misses it by looking inside individuals and sociology misses it by looking at groups. What happens between two people when one of them truly addresses the other is a distinct kind of event, with its own reality. It also means that the I-Thou relation cannot be willed into existence by one party. Buber writes that the Thou meets me through grace; it is not found by seeking. Yet it is also true that I must step into the relation with my whole being. The relation is both chosen and choosing, both active and passive. This double structure, grace and will, recurs throughout the book and is the source of much of its difficulty. Buber is trying to describe something that cannot be manufactured by technique and yet is not simply an accident; something that requires a total commitment and yet cannot be guaranteed by it. Here too lies the root of the reciprocity that Levinas would later question. If the relation lives between, then it belongs to both parties equally. I say Thou; the other, in the same event, is Thou to me and I to it. Buber writes that my Thou affects me as I affect it, and that we are formed by our students and built by our works. Relation is mutuality. The whole architecture of the book depends on this. The sublime melancholy of our lot I and Thou is not a celebration of relation at the expense of the world of It. Its tone is often elegiac. Buber insists that every Thou in this world is doomed by its nature to become an It. The human being who was a moment ago unique and without qualities, present and not available for experience, becomes again a He or a She, a sum of qualities, a quantum with a shape. This, he says, is the sublime melancholy of our lot. We cannot live in the pure present. We need the world of It in order to live, and we cannot stay in the Thou. Nor should we. The problem, as Buber sees it, is not that the It exists but that in modern life it has grown so large that it overwhelms the capacity for relation. He writes that the development of the individual and of culture involves a progressive augmentation of the world of It, and that this augmentation is necessary and is also a danger. The man who lives only in It is not wicked; he is simply not fully a man. He lives in a world that can be relied on, that holds no surprises, that he can use and know. What he lacks is presence. Buber extends the analysis to institutions and economic life. The state and the economy, he argues, belong necessarily to the world of It. They organize, calculate, and administer. The question is not whether they should exist but whether they are animated by the spirit of relation or cut off from it. A statesman or an entrepreneur who treats the people he serves purely as quantities, as bearers of labor or votes, has let the It become autonomous. Buber does not propose that we abolish administration. He proposes that administration be permeated, through the persons who conduct it, by the will to relation. Critics have found this vague, and it is. But it anticipates the concern that runs through both Buber's later political writing and Levinas's analysis of the third: how the impersonal structures that justice requires can remain answerable to the persons they serve. Man becomes an I through a Thou The central anthropological claim of the book is compressed into a single sentence: the human being becomes an I through a Thou. Buber offers what amounts to a developmental account. The infant, he suggests, lives first in a kind of undifferentiated relation to the world; its instinct for contact reaches out before there is any clear sense of self. The child reaches toward the mother, toward things, toward the world, and the I emerges gradually from these relations. The I-Thou is primary. The I-It, the capacity to stand back and treat something as an object, comes later, when the I has separated itself sufficiently to become a subject over against objects. Buber finds the same pattern in the history of cultures. So-called primitive peoples, he argues, relying on the anthropology of his day, live more in relation than in objectification; their languages and rites express encounters with powers rather than knowledge of things. This part of the book has aged badly. The anthropology is dated and the romanticism about "primitive" life is uncomfortable. But the philosophical point does not depend on it. It is the claim that the self is not a given but an achievement, and that it is achieved in relation rather than in isolation. This claim has practical force. It means that a child who is never addressed as a Thou, who is only fed, cleaned, and managed, will not fully become a person. It means that a person who is treated only as an It, as a case, a file, a resource, is being deprived of something essential to his being. And it means, conversely, that saying Thou to another is not merely an ethical act of respect for someone who already exists as a full self. It is participation in the coming-to-be of that self. The eternal Thou The third part of I and Thou turns to God. Buber writes that the extended lines of relations meet in the eternal Thou. Every particular Thou is a glimpse through to it; through every particular Thou the primary word addresses the eternal Thou. God is the Thou that by its nature cannot become an It. We can speak of God in the third person, construct theologies, formulate doctrines, but when we do we are no longer in relation. The God who can be described is not the God who is addressed. This is a distinctive conception of religious life. It rejects both mysticism, in which the self dissolves into God, and rational theology, in which God is an object of knowledge. It also rejects the idea that religion is a separate compartment of life, a set of special experiences or rituals set off from ordinary existence. For Buber, one meets God not by turning away from the world but by turning toward it: toward the tree, the animal, the work of art, and above all the other person. The religious life is the life of relation, lived in the everyday. It also has a critical edge. Buber is suspicious of religion that has hardened into It: doctrine, law, institution, cult. He does not reject these altogether, and his relation to Jewish law was complex, but he consistently refused to accept the halakhah, the body of Jewish religious law, as binding in advance of the moment of address. He wrote to Rosenzweig that he could accept a commandment only when he felt himself addressed by it here and now. Rosenzweig disagreed, arguing that the law was the way in which address was received and made livable across generations. The disagreement between the two friends on this point prefigures, in a different register, the disagreement between Buber and Levinas. Levinas, like Rosenzweig, would insist that the ethical relation must be given form, articulated in law and institution, if it is not to evaporate into moments of fervor. What the book leaves open I and Thou established a vocabulary that has passed into general use, often in forms Buber would not recognize. Its central distinction has been taken up in theology, psychotherapy, education, nursing, organizational theory, and popular self-help. But the book leaves several questions unanswered, and they are the questions that Buber's later work and Levinas's critique would press. First, what is the relation between the I-Thou encounter and ethics? I and Thou is not, primarily, a book about morality. It does not tell us what we owe others. It describes a mode of being that is the condition of personhood and of faith. Buber sometimes seems to assume that ethical behavior will follow from genuine relation, but he does not show how. Second, what about relations that are not mutual? If the I-Thou is essentially reciprocal, what happens when the other cannot or will not respond: the infant, the severely disabled, the hostile, the dead? Buber would take up this question in his postscript of 1957, admitting that some relations, those of teacher and pupil, therapist and patient, pastor and congregant, are marked by what he called a normative limitation of mutuality. That concession, as we will see, opened a door that Levinas walked through. Third, what is the relation between the moment of encounter and the rest of life? If every Thou must become an It, and if relation cannot be sustained, what is the ethical status of the long stretches of ordinary life spent in the world of It? Buber's answer, that the It must be permeated by the spirit of relation, requires a great deal of further work. His later essays, to which we now turn, are that work. CHAPTER 3 Dialogue Tested I and Thou was a vision. Buber spent the remaining four decades of his life trying to show that the vision could be lived, and in the process he refined it, qualified it, and in places quietly revised it. The later work is less quoted than the book of 1923, but it is more precise and, for anyone interested in how the philosophy of dialogue bears on actual human relationships, more useful. It is also where the fault lines that Levinas would later expose become visible from within. Genuine, technical, and disguised The essay "Dialogue," published in 1929 and later collected in Between Man and Man, is Buber's most concrete account of what the I-Thou relation looks like between people. It begins with an image: two men sitting side by side on a bench, strangers, not speaking, not even looking at each other. One of them, a man of reserve, suddenly and without deciding to, releases the constraint within himself, and something passes from him to the other, who receives it. Nothing is said. Yet, Buber insists, this is dialogue. Speech is not what makes a meeting dialogical. What makes it dialogical is that each party turns toward the other and is present to him. Buber then distinguishes three kinds of conversation. Genuine dialogue, whether spoken or silent, is that in which each participant really has in mind the other or others in their present and particular being and turns to them with the intention of establishing a living mutual relation. Technical dialogue is prompted solely by the need of objective understanding: the exchange of information, the coordination of tasks. It is legitimate and necessary, the dialogue of the world of It. And then there is monologue disguised as dialogue, in which two or more people, meeting in space, speak each with himself in strangely tortuous and circuitous ways and yet imagine they have escaped the torment of being thrown back on their own resources. Buber's catalog of disguised monologue is sharp and still recognizable. There is the debate in which thoughts are expressed not as they existed in the mind but so as to strike home in the sharpest way, and without the people spoken to being regarded as present persons. There is the conversation characterized by the need neither to communicate something nor to learn something but only to confirm one's own self-reliance by marking the impression one makes. There is the friendly chat in which each regards himself as absolute and legitimate and the other as relativized and questionable. And there is the lovers' talk in which each partner enjoys his own glorious soul and his precious experience. The modern reader could extend the list without difficulty. What makes this analysis important is that it moves the philosophy of dialogue away from the rare, exalted moment and toward ordinary conduct. Genuine dialogue is not a mystical experience. It is a quality of attention available in the most ordinary exchange, and absent from many exchanges that look, on the surface, like intimate conversation. The story of the young visitor, the "conversion" with which this book began, appears in this same essay. Its lesson is that the test of dialogue is not the intensity of feeling but whether one is present to the claim the other makes. Against the solitary self In 1938, the year he left Germany for Jerusalem, Buber delivered his inaugural lecture course at the Hebrew University under the title "What Is Man?" It was published in Hebrew in 1942 and later collected in Between Man and Man. The lectures survey philosophical anthropology from Aristotle to the twentieth century and conclude with a critique of the two most influential recent thinkers of human existence, Kierkegaard and Heidegger. The critique of Heidegger is especially pointed. Being and Time had described human existence, Dasein, as always already being-with-others. Heidegger explicitly rejected the picture of an isolated subject who must then find its way to other minds. Human beings are with one another from the start, and concern for others, which Heidegger called Fürsorge or solicitude, is one of the fundamental structures of existence. Buber might have been expected to welcome this. He did not. He argued that Heidegger's being-with is a being-with in general, an existential structure rather than an actual relation. Heidegger's Dasein relates to others, but it does not meet them. Its essential relation is to its own being, and above all to its own death, which it must face alone. Authentic existence, for Heidegger, is achieved by resolutely taking over one's ownmost possibilities, which means withdrawing from the "they," the anonymous public world. Buber called this monological. Heidegger's self is closed; it knows solicitude but not dialogue, concern for others but not the essential relation in which an I says Thou. The critique is worth dwelling on because Levinas would make a parallel critique of Heidegger, in more technical terms and at greater length, a decade later. Both men saw in Heidegger the most powerful modern philosophy of existence, and both concluded that it had no place for the other person as such. They drew different conclusions about what should replace it. For Buber, the answer was relation, the between in which two selves become themselves together. For Levinas, as we will see, the answer was the face, which does not complete me but calls me into question. Distance and relation In 1950 Buber published a short essay, "Distance and Relation," which he regarded as the philosophical foundation of his anthropology. Its argument is that the human being is distinguished by a twofold movement. The first movement is the setting at a distance: the human being, unlike the animal, is able to regard the world as something over against him, independent, existing in its own right. The animal lives in its environment; the human being has a world. The second movement is entering into relation with what has been set at a distance. Only a being that can set the world at a distance can relate to it; only what is independent can be addressed. This is a subtle revision of I and Thou. There, the I-It relation seemed to be a falling away from the primary I-Thou. Here, distance, the capacity that makes objectification possible, is recognized as the precondition of relation itself. One cannot say Thou to something one has not first recognized as other, as not-me. The world of It is not only a necessary evil; it is the ground on which the Thou can appear. The essay also introduces a concept that would become central to Buber's later ethics: confirmation. Human beings, Buber writes, wish to be confirmed in their being by other human beings, and wish to have a presence in the being of the other. The deepest need of a person is not to be tolerated, or even liked, but to be confirmed as the person he is and is capable of becoming. Confirmation is not approval. One can confirm another while opposing his views and his conduct. What one confirms is his being, his right to exist and to become who he is, and one does so by making him present, by imagining the real, as Buber puts it: by holding in mind what the other is at this moment thinking, feeling, and willing, as a living process in this particular person. Seeming and being "Elements of the Interhuman," from 1954, extends the analysis. Buber distinguishes the social, which covers every kind of association and collective existence, from the interhuman, which consists only of what happens between persons who have turned toward each other. The interhuman is threatened, he argues, by three obstacles. The first is the duality of being and seeming. Some people live from what they are; others live from what they wish to seem. Most people mix the two. The one who lives from seeming is concerned with the image he produces in the other, and so he is never fully present; part of him is always watching the effect. Buber does not treat seeming as simply a vice. It arises, he suggests, from the need for confirmation that cannot be satisfied in genuine relation and so seeks satisfaction in appearances. The cure is not self-denial but the courage to be what one is in front of the other. The second obstacle is the flood of analytic, reductive thinking that sees a person only as a composite, explicable by psychology or social conditioning. Such thinking is not false, but when it becomes the only way of regarding others it makes the whole person, the one who is more than the sum of his conditions, invisible. The third is the distinction between imposition and unfolding. One can try to influence another person by imposing one's own opinions and attitudes on him, as the propagandist does, treating him as an object to be moved. Or one can try to help him unfold what is already present in him as a possibility, as the educator does, by being oneself present and trusting that what is true and right will find its way. The educator and the propagandist may hold the same views. What distinguishes them is their stance toward the person they address. The teacher and the therapist Buber's writings on education, especially the address "Education," given at Heidelberg in 1925, and "The Education of Character," from 1939, apply these ideas to the relationship between teacher and pupil. The teacher, Buber argues, must practice what he calls inclusion, Umfassung: the capacity to experience the relationship from the other side, to feel how the pupil receives what is taught, without losing one's own side. The teacher stands at both ends of the relation. The pupil, however, cannot and should not do the same. If the pupil began to experience the relation from the teacher's side, to take responsibility for the teacher's task, the educational relation would be destroyed and replaced by friendship. This is a remarkable concession. It means that the relation between teacher and pupil is a genuine I-Thou relation, and yet it is not symmetrical. The teacher includes the pupil; the pupil does not include the teacher. Buber found the same structure in the relation between physician or psychotherapist and patient. The therapist must experience the patient's side of the relation; the patient cannot be expected to experience the therapist's. If he could, he would not need therapy. The question came to a head in a public dialogue held at the University of Michigan in April 1957 between Buber and Carl Rogers, the American psychologist whose client-centered therapy had drawn explicitly on Buber's ideas. The event was moderated by Maurice Friedman, Buber's principal American interpreter. Rogers described moments in therapy when, as he put it, he and the client met as persons on the same level, in something he was willing to call an I-Thou relation. Buber would not accept this without qualification. He pointed out that the client came to Rogers for help, not Rogers to the client. Rogers could see the client, and could experience the relation from the client's side; the client could not do the same for Rogers. The situation itself, Buber insisted, was unequal, and to pretend otherwise would be to falsify it. Rogers was friendly but unpersuaded; he thought that in the best moments of therapy the inequality really did fall away. The exchange is revealing. Rogers, the therapist, wanted to believe in full mutuality. Buber, the philosopher of mutuality, insisted on the limits of mutuality in precisely the relationships where one person is responsible for another. In the postscript he added to I and Thou in 1957, the same year, Buber formalized this as the "normative limitation of mutuality." Some relations are I-Thou relations in which full mutuality is not only absent but would be inappropriate. They remain relations of the between, but the between is shaped by the responsibility of one party for the other. A reader who knows Levinas will already see the difficulty. Once one has admitted that the relations in which one person is responsible for another are asymmetrical, one has conceded that asymmetry and responsibility go together. Levinas would ask: are not all ethical relations like this? Is the reciprocity of friendship and love the model from which the asymmetry of teaching and healing deviate, or is it the other way around? Dialogue in politics Buber did not confine the philosophy of dialogue to private life. From his arrival in Palestine in 1938 until his death, he was a leading advocate of a binational state in which Jews and Arabs would share sovereignty. In 1942, with Judah Magnes, the first chancellor of the Hebrew University, and others, he founded the Ihud (Union) association, which argued that the Jewish national home could be secured only through agreement with the Arabs of Palestine. After the establishment of the State of Israel in 1948, which Ihud had not sought in that form, Buber accepted the state as a fact while continuing to criticize its policies toward Arab citizens and refugees. His political thought was a direct extension of his philosophy. In Paths in Utopia, published in Hebrew in 1946, he argued for a decentralized, federalist socialism built on genuine communities rather than on the centralized state. He saw in the kibbutz movement a partial realization of this vision. Community, for Buber, was not the same as collectivity. A collectivity is a bundle of individuals held together by organization; a community is a group of persons who stand in relation to one another and to a living center. The state, like every institution, belongs to the world of It, and it cannot be abolished; but it can be kept from becoming absolute by the vitality of the communities within it. Two episodes show how Buber tried to practice dialogue under pressure. In 1939 he wrote a long open letter to Mahatma Gandhi, who had suggested that the Jews of Germany should respond to Nazi persecution with satyagraha, nonviolent resistance, and that Palestine belonged to the Arabs. Buber's reply is at once respectful and devastating. He pointed out that Gandhi's comparison between the Indians of South Africa and the Jews of Germany ignored the difference between discrimination and a program of annihilation. He explained why he believed the Jews had a claim to the land, and why he also believed the Arabs had one, and he insisted that the two claims must be reconciled rather than either being denied. Gandhi never replied. The second episode came near the end of his life. In 1962, after the trial of Adolf Eichmann in Jerusalem, Buber appealed publicly for the sentence of death not to be carried out. He did not doubt Eichmann's guilt. He argued that the execution would suggest that the crime had been expiated, which it could not be, and that it was not for the Jewish people, as the victim, to execute the perpetrator. The appeal was rejected, and Buber was widely criticized. Whatever one thinks of the argument, it shows a thinker trying to apply to the most extreme case the conviction that no human being should be reduced entirely to the category of an It, even one who had done the most to reduce others. The shape of the later Buber By the end of his life, Buber's philosophy of dialogue had become more modest and more precise than the vision of 1923. He had acknowledged that distance is the condition of relation; that confirmation, not merely encounter, is what persons need from one another; that some genuine relations are asymmetrical; and that the relation between the interhuman and the social is a problem to be worked on rather than a solution to be proclaimed. What he never gave up was the claim that relation, at its core, is mutual: that the between belongs to both parties, and that the highest form of human meeting is the one in which each says Thou to the other and each is changed. The asymmetrical relations of teaching and healing were, for him, limitations of this ideal, necessary and honorable, but limitations nonetheless. It is exactly this ordering that Levinas would reverse. Before turning to that reversal, we must follow Levinas's own path to the Other, which began not with relation but with the suffocating weight of being. Hashtags: #ThePhilosophyOfDialogue #MartinBuber #EmmanuelLevinas #PhilosophyOfTheOther #DialogicalPhilosophy #IAndThou #IThouRelation #IItRelation #TheBetween #Mutuality #Reciprocity #EthicalAsymmetry #TheFaceOfTheOther #InfiniteResponsibility #TheThird #EthicsAndJustice #RelationalPersonhood #GenuineDialogue #PresenceAndEncounter #Confirmation #NormativeLimitationOfMutuality #DialogicalEthics #JewishPhilosophy #EthicsOfTheOther #FutureOfDialogicalPhilosophy Pasted markdown

Download the Book (PDF): Introduction: The Decision Made Before Anyone Cooks One line on a menu In the second week of March a chef writes nine words on a spring menu: Braised lamb neck fillet, white beans, salsa verde — $28. It is a good line. The cut is one the guests will not have met, the dish braises, which means it can be produced in advance and held, and holding means it will not slow the pass on a Saturday night. She costs it in ten minutes on a legal pad — $7.40 of food on the plate, $20.60 of contribution margin, which is the menu price less the cost of the food used to make it — tells the general manager the number works, and moves on to the next dish. Six weeks later the operation is living inside that sentence. The first discovery is that trimmed lamb neck fillet is not a warehouse item at the broadline distributor, the full-range wholesaler that delivers the bulk of a restaurant's dry, chilled and frozen goods on a fixed route two or three times a week. It is carried by one specialty protein distributor in the region, who brings it in frozen from New Zealand. That is the second discovery: because the product is imported and bought against a landed cost that moves with the carcass market, the freight rate and the exchange rate, the specialty distributor will not quote a fixed price for the season. He quotes weekly. In the first nine weeks of the dish's life the quoted price moves five times, twice by more than eight percent, and the plate cost the chef wrote on the legal pad is accurate for exactly none of those weeks. The third discovery is the pack. The item arrives as a 20-pound case containing four 5-pound vacuum bags. At the 7-ounce portion the chef specified, a bag yields eleven portions and a fraction. Once a bag is opened and thawed it has perhaps three days of usable life. Tuesday demand is six covers; Saturday demand is nineteen. Neither number divides into a bag. Every week the kitchen either opens a bag it cannot finish or refuses the dish to guests who ordered it, and over the first quarter the recorded waste on this one line runs at about nine percent of the product bought. The fourth discovery is lead time. The specialty distributor consolidates his import orders once a week. An order placed Monday arrives the following Tuesday. There is no mechanism — no premium, no favor, no phone call — that puts lamb neck fillet in the walk-in on a Saturday afternoon. When the kitchen runs out at 8:40 p.m. with fourteen covers still on the book, the dish is gone until Tuesday week, and the printed menu still promises it. Now look at where each of those four constraints was decided. The single-source supply was decided by the choice of cut, in March. The weekly price movement was decided by choosing an imported frozen item rather than a domestic chilled one, in March. The waste was decided by pairing a 7-ounce portion with a 5-pound bag in a business whose weekend is three times its Tuesday, in March. The lead time was decided by the origin, in March. Not one of them was decided in April by anybody with the word "purchasing" in their job title. They were decided by a chef with a legal pad who was thinking, entirely reasonably, about flavor. This is the argument of the whole book, and it is worth stating before anything else. Nothing downstream can undo it. Receiving can verify that what arrived matches what was ordered; it cannot make the case size fit the week. Storage can slow deterioration; it cannot extend a thawed bag past Sunday. Recipe costing can tell you the plate now costs $8.90 instead of $7.40; it cannot hold the price. Menu engineering can tell you the dish is a dog and should be removed; that is a confession, not a control. The decision was made, and made completely, at the moment the product was specified. What purchasing decides, and what the parent text does Purchasing is where a hospitality business decides what it is capable of serving, at what cost, and at what risk. Those three things travel together and they are settled early. The capability is settled by the specification, because a product you cannot reliably obtain is a dish you cannot reliably sell. The cost is settled by the specification and the sourcing decision jointly, because price is only one component of what a purchase costs you. The risk — the chance of a stock-out, a substitution, a price shock, a recall, a supplier failure — is settled by how many suppliers can meet the specification and on what terms, which is again a consequence of how the specification was written. Two things follow. The first is that the specification is the lever. Almost every other purchasing decision is downstream of it, and most of the leverage a buyer appears to have in a negotiation was either created or destroyed when somebody decided what to ask for. The second is that the cheapest quotation is routinely the most expensive purchase. A lower price per pound on a product that yields less, takes longer to prepare, portions inconsistently, spoils faster or arrives unreliably is not a saving; it is a cost that has been moved off the invoice, where the buyer is measured, and onto the payroll, the waste sheet and the guest's experience, where the buyer is not. Purchasing: Selection and Procurement for the Hospitality Industry by Andrew H. Feinstein and John M. Stefanelli does three things that make it the right foundation for this. First, it treats purchasing as a full management discipline rather than an ordering routine — a body of decisions about product, quantity, timing, source and price, each with its own analytical method, rather than a clerical sequence performed after the real decisions have been made elsewhere. Second, it spends serious time on the distribution system itself: who the intermediaries are, what each of them actually does for their margin, and why the structure of a supply channel determines what a buyer can and cannot ask for. A buyer who does not understand how a broadline distributor earns money will misread every quotation he is given. Third, and most usefully, the parent text insists that quality means suitability for the intended use, not position on a grading scale. The highest grade is frequently the wrong purchase. A tomato destined for a long-simmered sauce and a tomato destined for a sliced garnish are different products with different correct specifications, and the second is not the better one. What has changed The frameworks hold. The environment they operate in has moved, and this companion is written to say where. Price volatility since 2021 is the largest change, and it has altered contracting itself. A generation of buyers was taught to convert volatility into certainty by fixing a price for a season or a year. Suppliers now price that certainty at a level that frequently makes it a bad trade, decline to offer it at all on exposed commodities, or offer it with escape clauses that return the risk to the buyer precisely when it becomes real. The skill has shifted from locking prices to structuring exposure: choosing which items to fix, which to index to a published basis, which to leave floating with a menu that can absorb the movement, and how to write a clause that survives a shock. Ordering itself has been substantially automated. E-procurement platforms, punchout catalogs — where the buyer's own system opens a session inside the supplier's catalog and returns a priced cart to the buyer's approval workflow — and automated three-way matching of purchase order, receiving record and invoice have removed most of the clerical work and, with it, most of the incidental checking that clerical work used to perform. The controls that mattered have had to be rebuilt inside the software, and a buyer who cannot say where they now live has lost them. Group purchasing organizations, once the province of chains and hospital systems, now reach independent operators directly, which changes the economics of a single restaurant's buying and introduces a new question about whose interest the aggregator serves. Traceability regulation has converted food safety from a paperwork obligation into a data requirement: the Food Safety Modernization Act's Food Traceability Rule obliges firms handling listed foods to capture critical tracking events and key data elements, and the practical consequence for a buyer is that lot-level data interoperability with a supplier becomes a purchasing specification. Sustainability and human rights due diligence have crossed the same line, from policy into law, through deforestation rules, corporate due diligence directives and forced-labour import bans that can stop goods at a border. Labour scarcity in distribution — drivers, warehouse selectors, night crews — has quietly reduced delivery frequency, raised drop-size minimums, widened delivery windows and hardened order cut-off times, all of which change order quantity mathematics that textbooks still present as though delivery were freely available. And third-party delivery has turned packaging from a minor supplies line into material spend with its own specification, sourcing and regulatory problems. How to use this book Every chapter runs the same road: from the decision, to the document that records it, to the cost the decision creates, to the risk it leaves behind. Read it that way. When you meet a worked example, do the arithmetic yourself before reading the result, because the examinable skill in this subject is not the ability to describe a process — anybody can list ten stages of a purchasing cycle — but the ability to put a number on a decision and then say what could go wrong with it. Price the decision. That is the whole assignment. Chapter 1: What Purchasing Is For, and How It Is Organized The five rights, and the trade-off they describe Every purchasing course opens with the same sentence, and it is worth writing down before taking it apart. The objective of purchasing is to obtain the right product, in the right quantity, at the right time, at the right price, from the right supplier. Feinstein and Stefanelli set out these objectives early, and the formulation has survived because it is genuinely comprehensive: there is no purchasing failure that does not fall under one of the five. The trouble begins the moment you ask what "right" means, because the word is empty until an operation fills it. Right for whom, and for what? A 40-count russet potato — forty potatoes to a fifty-pound case, therefore an average of twenty ounces each — is the right product for a steakhouse baking and serving potatoes whole, because the guest expects a large potato and the count guarantees one. It is the wrong product for a kitchen making pommes purée, where a smaller, cheaper, higher-solids potato does the job better. Neither potato is superior. The concept and the standard decide. This is the parent text's insistence on suitability for intended use, and it applies to all five rights, not only to product. The right quantity for a hotel with a loading dock, a cold room and a receiving clerk is not the right quantity for a forty-seat restaurant with a single reach-in. The right time for a bakery that produces at four in the morning is not the right time for a banquet operation. The right supplier for a business whose menu changes weekly is not the right supplier for one that has sold the same nine dishes for a decade. The deeper problem is that the five objectives conflict with one another, systematically and by design. They are not five targets to be hit simultaneously; they are five dimensions of a single trade-off, and management of that trade-off is the job. Consider the pairs. The right price usually rewards volume: distributors price by drop size, manufacturers by truckload, and the deviated price on a contracted item generally requires committing to a quantity. But the right quantity is the smallest amount that safely covers demand until the next reliable delivery, because everything beyond that carries storage cost, capital cost, shrinkage risk and spoilage risk. Price pulls the order up; quantity pulls it down. Price also fights time: the right time — frequent, small, fresh deliveries — is exactly what distributors charge for, through delivery minimums, fuel surcharges and small-drop fees. Price fights supplier, too, because the cheapest quotation in any given week is often from the supplier with the weakest service, and a buyer who chases weekly low price across three purveyors buys away the volume that earns him a concession from any of them. Most sharply, product fights supplier and therefore price. Every additional line in a specification narrows the field of suppliers who can satisfy it. Write "chicken breast," and twenty suppliers compete. Write "boneless skinless chicken breast, 6 oz ± 0.25 oz, air-chilled, never frozen, no added solution, raised without antibiotics, from a single named processor, delivered within 48 hours of processing," and you may have narrowed the field to one — at which point you have no price leverage, no substitute in a shortage, and a dish whose existence depends on one company's production schedule. The specification bought you quality and sold you resilience. That may be the right trade. It is, unmistakably, a trade. So purchasing is not the pursuit of a single optimum. It is the management of a tension between five things that cannot all be maximized. A buyer who only ever wins on price is not a good buyer; he is a buyer who has quietly resolved the trade-off in one direction and pushed the consequences into the kitchen, the waste log and the guest's plate, where he will not be measured for them. Value against price, and the total cost of ownership The single most examinable idea in this subject is that price is one component of cost and usually not the largest. The discipline that formalizes this is total cost of ownership: the full economic consequence of a purchase over its life in the operation, not the number on the invoice. In a food context the components are consistent. There is the purchase price. There is yield — the proportion of what you bought that survives trimming, butchering, peeling, cooking and portioning into something you can sell. There is preparation labor, including the payroll taxes and benefits that make an hour of a cook cost considerably more than the hourly wage. There is waste, both spoilage and overproduction. There is consistency, which converts directly into cost through portion variance: a product that portions to specification every time cannot be overportioned, and a product that does not will be. There is delivery reliability. There are payment terms, which have a real but usually small working-capital value. And there is the cost of a stock-out, which is the largest number in most of these calculations and the one students most often omit. Work it properly on a clean example. Kestrel Grill, a fictional 90-seat neighborhood restaurant, sells a chicken dish at $23.00 and needs a 6-ounce raw boneless skinless breast portion. It sells 180 portions a week, fifty weeks a year — 9,000 portions annually. Two options are on the table. Option A is a 40-pound case of bone-in, skin-on split breasts at $2.40 per pound, so $96.00 per case. Broken down in-house, the yield to trimmed boneless skinless meat is 62 percent, giving 24.8 pounds, or 396.8 ounces. At a 6-ounce portion that is 66 portions per case. The breakdown takes a prep cook 45 minutes; at a fully loaded labor cost of $24.00 per hour, that is $18.00. The bones and skin genuinely go into stock, displacing $6.00 of purchased stock base per case, which is a real credit and should be taken. Net cost per case is $96.00 + $18.00 − $6.00 = $108.00, or $1.64 per portion. Option B is a 30-pound case of individually quick-frozen 6-ounce boneless skinless portioned breasts at $4.20 per pound, so $126.00 per case. Thirty pounds is 480 ounces, which is exactly 80 portions. Cost per portion is $1.58. Option B costs 75 percent more per pound and is already, on this first pass, six cents cheaper per portion. The comparison gets worse for A when the remaining components are added. Consistency comes first. Hand-cut portions vary, and variance is never symmetrical in practice, because a cook who is behind cuts generously rather than stopping to weigh. Assume Kestrel's actual average served portion on the hand-cut product is 6.4 ounces rather than 6.0. Then 396.8 ounces yields 62 portions, not 66, and the cost per portion rises to $108.00 ÷ 62 = $1.74. Option B cannot drift, because the portion is fixed by the manufacturer. Waste comes second. Fresh bone-in product has a short usable life and Kestrel's weekly volume is uneven; assume 3 percent of the fresh product is discarded. The effective cost per sold portion becomes $1.74 ÷ 0.97 = $1.80. The frozen product carries no equivalent loss, because it is drawn from the freezer in the quantity needed. Payment terms come third, and here the discipline is to size the factor rather than to list it. Supplier A offers net 14, supplier B net 30 — sixteen extra days of credit on a weekly spend of roughly $280 on this item. At a 10 percent cost of capital that is worth about $1.23 a year. It is real, and it is immaterial, and saying so is part of doing the analysis properly. Total cost of ownership is not an invitation to enumerate everything; it is an instruction to find the factors large enough to change the decision. The stock-out is the fourth, and it is not immaterial. Kestrel's plate food cost on this dish is $6.15, so contribution margin is $16.85. Assume the fresh line runs short twice a year, each time costing 18 covers, and that half those guests order something else with a $14.00 contribution. The loss per incident is (9 × $16.85) + (9 × $2.85) = $151.65 + $25.65 = $177.30, so $354.60 a year. The frozen product, held with three weeks of cover in a freezer, effectively eliminates this exposure. Put it together. The difference in cost per portion is $1.80 − $1.58 = $0.22. Across 9,000 portions that is $1,980 a year, plus $354.60 of avoided stock-out cost: about $2,335 a year in favor of the product that looked 75 percent more expensive. Two honest qualifications. First, the calculation is only as good as its inputs, and the two soft ones — the 62 percent yield and the 6.4-ounce actual portion — should be measured in the operation, not assumed. Second, and more important, if Kestrel's concept promises in-house butchery and the menu says so, the calculation loses to the concept, and it should. Total cost of ownership tells you the price of a standard. It does not tell you whether the standard is worth its price. That is a management decision, and it belongs to the people who own the concept. Who buys, and how the function is organized In a large operation the buyer is a specialist whose product is not a low price but a reliable stream of the right thing at a predictable cost. He knows the market, maintains the supplier file, runs quotations, negotiates terms, places orders, chases shortages, resolves credits and reports variance. What he does not own is the standard. The specification belongs to the person accountable for the guest's experience. Where the buyer reports matters more than students expect, because reporting lines determine which of the five rights gets resolved in a conflict. A buyer reporting to the executive chef will tend to optimize product and supplier reliability and let price drift. A buyer reporting to the controller will tend to optimize price and let quality drift, because price variance is visible on a monthly report and a slightly tougher steak is not. Reporting to the food and beverage director, or in a chain to a supply chain director who is measured on landed cost, service level and quality rejections together, is a deliberate attempt to hold the trade-off in one job. The chef and the food and beverage director own the specification and the standard; the buyer owns the market and the terms. Where that split is not explicit, it collapses, usually toward whoever shouts. Centralized purchasing concentrates the decision: one department, or one person, buys for multiple units or departments. It aggregates volume, standardizes specifications, professionalizes negotiation and makes control straightforward. It also removes local judgement, slows response, and produces the familiar complaint that the contracted product does not suit this unit's menu or this city's guests. Decentralized purchasing leaves the decision with the unit or the department head. It is fast, locally sensitive and motivating; it also fragments volume, produces a different specification for the same item in every unit, and makes fraud considerably easier to commit and harder to see. Most real organizations sit between the two: specifications and supplier selection centralized, order quantity and timing decentralized. That split is the sensible one, because it centralizes the decisions that benefit from volume and expertise and decentralizes the ones that depend on knowing what is in the walk-in. Chains formalize this through a corporate purchasing department and, typically, a distribution services agreement. A distribution services agreement is a contract between the chain — or a purchasing cooperative acting for its franchisees — and one or more broadline distributors, under which the distributor buys, stores and delivers agreed products to units at an agreed price mechanism, almost always cost-plus: the distributor's landed cost for the item plus a defined markup, expressed as a fee per case, per pound or as a percentage. The agreement also fixes service levels, fill rate obligations, inventory commitments on proprietary items, and the audit rights that let the chain verify the landed cost it is being charged. Those audit rights are the operative clause. A cost-plus agreement without the right to inspect the cost is a percentage of a number the supplier chooses. Group purchasing organizations extend something similar to operators with no volume of their own. A GPO aggregates the purchasing volume of unaffiliated members, negotiates contracts with manufacturers, and makes the resulting deviated prices — prices below the distributor's standard list, funded by the manufacturer — available to members, usually through their existing distributor. The economics are worth understanding precisely, because they are not what a new member assumes. The member typically pays no fee, or a token one. The GPO is paid an administrative fee by the manufacturer, generally a small percentage of the value purchased on contract. This is a legitimate and disclosed model, and for an independent restaurant it can produce genuine savings on branded and commodity items that no single operator could negotiate. It also creates an interest: the organization earns more when members buy the contracted item, whether or not the contracted item is the best buy that week. The correct posture for an independent is to use the GPO and verify it — check delivered prices on the top twenty items against a market quotation two or three times a year, and read what the membership agreement says about exclusivity and about whether fee income is disclosed or shared. Separation of duties Whatever the structure, one control is not negotiable. The person who orders, the person who receives and the person who pays must not be the same person. Purchasing is the most exposed function in a hospitality business because it combines the authority to commit money, the discretion to choose who receives it, and a stream of transactions too numerous for anyone to inspect individually. Collapse the three roles into one and every classic scheme becomes available: the phantom vendor that invoices for goods never delivered; the real vendor whose invoices are padded in exchange for a share; the substitution of a cheaper grade against a premium specification with the difference split; the short delivery signed for in full. Each of these requires control of at least two of the three roles. Separation is what makes them require a conspiracy rather than a decision. Small operations object that they do not have three people, and they are right. The answer is compensating controls rather than surrender. The owner or general manager reviews every invoice against the corresponding order and receiving record before payment and signs the checks personally. Receiving is done blind where possible — the receiving copy of the order shows items but not quantities, so the clerk must count rather than confirm. The person who reconciles the bank statement is not the person who enters payables. Deliveries are received by rotating staff rather than always the same one. And prices are spot-checked against an outside quotation at unpredictable intervals, which is the cheapest control in existence and the one most often skipped. Purchasing in different sectors Discretion narrows as scale increases, and the buyer's job changes shape accordingly. The independent restaurant has the widest discretion and the least leverage. It can buy anything from anyone, change specification on Tuesday, and take advantage of a farmer with a glut. It also buys in quantities no supplier competes for, pays close to list, and absorbs volatility directly. Its purchasing skill is concentrated in specification and menu design — choosing to sell things it can obtain at a cost it can predict. The branded chain unit has almost none. Suppliers are mandated, specifications are corporate, and the contracted item is the only permitted item, because brand consistency across units is the product being sold. The unit manager's remaining decisions are quantity and timing: order accurately against a forecast, hold as little as safety allows, receive properly, and report exceptions. That is not a trivial job — most of the controllable cost in a chain unit lives in forecast error, over-ordering and waste — but it is a different job from sourcing. The hotel with multiple outlets has a structural complication the others do not: one storeroom serving several departments with different menus, different standards and different profit responsibilities. Central purchasing and central receiving are near-universal, and the real difficulty moves to issuing and transfer pricing — making sure the cost of a case of shrimp lands on the outlet that consumed it, that banquet requisitions are costed to the event, and that inter-outlet transfers are recorded rather than absorbed. Hotels also buy categories restaurants do not: operating supplies and equipment, guest amenities, capital items, and contract services, each with its own cycle. The Uniform System of Accounts for the Lodging Industry, in its 12th Revised Edition and mandatory from 1 January 2026, is the framework that makes these departmental costs comparable between properties. Contract catering buys inside somebody else's contract. The client may nominate suppliers, mandate local or sustainable sourcing, or require open-book accounting in which the caterer discloses actual purchase costs and earns a stated management fee rather than a margin. The live issue in these arrangements is rebate transparency: volume rebates and GPO administrative fees earned on the client's spend are, contractually, often the client's money, and whether they are disclosed and passed through is a routine subject of audit and dispute. Institutional and public sector buying is governed by tender rules. Requirements are published, bids are submitted formally by a deadline, award criteria are fixed in advance, and the award goes to the lowest compliant bid or to the best score against published criteria, with an audit trail that will survive challenge. Relationship counts for nothing and documentation for everything. The skill here is almost entirely in specification writing, because the specification is the only instrument the buyer controls once the tender is issued: a badly written one will be satisfied, lawfully and cheaply, by a product nobody wants to serve. Where the supplier is already chosen, the buyer's job becomes contract enforcement rather than sourcing. That means auditing landed cost and markup against the agreement, monitoring fill rate and claiming the credits the contract allows, verifying that deviated prices are actually appearing on invoices, testing delivered product against the written specification, managing the forecast the supplier is committing inventory against, and handling exceptions and substitutions. It is unglamorous and it recovers more money than most negotiations. The cycle, and how purchasing is measured The ten stages, and what each one forecloses The rest of this book unpacks the purchasing cycle stage by stage. In outline it runs: identify need, specify, source, negotiate, order, receive, store, issue, pay, evaluate. What matters at this stage is what each step decides and what it can no longer change. Identifying need decides whether the item is bought at all, and in what category and rough volume. It is driven by the menu and the forecast, and once it is settled the argument about whether the operation should be serving this thing is over. Specifying decides quality, form, pack and therefore the size of the supplier field, the price mechanism available and the waste built into the pack; it cannot change the forecast. Sourcing decides which suppliers may compete, and it is constrained entirely by the specification — a sole-source specification makes sourcing a formality. Negotiating decides price mechanism, terms, service levels and remedies; it cannot widen a field the specification has already narrowed. Ordering decides quantity and timing, and is the last stage at which the cost of this delivery can be influenced. Receiving decides only whether what arrived matches what was ordered — it can reject, and that is its entire power; it cannot change the price or the pack. Storing decides how much of what was accepted survives to be sold. Issuing decides which department bears the cost and when, and is where inventory becomes a food cost figure. Paying decides cash timing and captures discounts; it cannot recover a quality failure that receiving accepted. Evaluating decides only what happens next time, which is precisely why the loop back into specification is the stage most often skipped and the one that makes the difference between a purchasing function and an ordering routine. The measures that mean something, and how each is gamed Seven measures carry most of the useful information about a purchasing function. Every one of them can be gamed, and knowing how is part of knowing the measure. Price variance against standard compares what was actually paid against the standard cost used to build the recipe. It is gamed by setting soft standards in the first place, by quietly rebasing the standard after an increase so the variance disappears, by buying a lower grade and booking the difference as a favorable variance, and by pulling purchases forward or pushing them back across a period end. Fill rate is the proportion of ordered lines or cases actually delivered. It is gamed by counting substitutions as fills, by measuring against the order as the distributor's system edited it rather than as the operation submitted it, and by excluding items the salesperson advised against ordering because he knew they were out. On-time delivery is gamed by widening the delivery window until almost nothing is late, and by measuring the truck's arrival rather than the moment product is accepted — which hides an hour of sorting and rejection at the dock. Quality rejection rate looks like a quality measure and is often a receiving measure. It is gamed by not rejecting: a kitchen that accepts substandard product because it needs it for lunch and complains verbally instead produces an excellent rejection rate and a bad supplier. A falling rejection rate with rising kitchen complaints means the dock has stopped checking. Invoice accuracy is gamed by measuring only errors that were caught, so a low error rate can mean the matching process is weak rather than the supplier is good. The honest version is to sample invoices independently. Stock turnover — cost of goods used divided by average inventory value — is gamed by running deliberately low at count date, by timing a large delivery for the day after the count, and by excluding awkward categories. It is also distorted by menu mix in ways that have nothing to do with the buyer, so it should be read by category rather than in total. Cost as a percentage of sales is the most gamed of all, because it has a denominator. Raise menu prices and the percentage improves without a single purchasing decision changing. It also moves when cost is shifted to another line — trimming labor reclassified, packaging moved to operating supplies, transfers timed across a period. Read alongside cost per cover and absolute spend against forecast, it is informative. Read alone, it is a number a competent manager can produce on demand. For the exam and the purchase order Three definitions must be exact. The five objectives of purchasing are the right product, quantity, time, price and supplier, and you gain marks by stating them and losing them by stopping there: say that each is defined by the operation's concept and standards and that the five conflict, so purchasing manages a trade-off rather than pursuing a single optimum. Total cost of ownership is the full economic consequence of a purchase over its life in the operation — price, yield, preparation labor, waste, consistency, delivery reliability, payment terms and the cost of a stock-out — not the invoice price. Separation of duties means that ordering, receiving and paying are performed by different people, and you should be able to name the fraud each separation prevents. The calculation most likely to be examined is the one worked above: converting two differently priced, differently formed products into a comparable cost per sold portion. The method is fixed. Convert the case to usable units by applying yield; add preparation labor at a fully loaded rate; adjust the portion count for actual served portion size rather than specified size; adjust for waste by dividing rather than subtracting; then value stock-out risk separately and annualize the result against volume. Show the working, state your assumptions, and say which of them you would measure before committing. Two applications. First: take a dish on any menu you know and identify which of the five rights its specification has sacrificed, then say what that sacrifice is worth per year. Second: an independent operator is offered GPO membership with no fee and a promised eight percent saving on branded goods. Set out what you would verify before signing, whose money funds the eight percent, and what the organization's revenue model gives it an interest in. Chapter 2: The Supply Chain Behind the Plate A buyer who does not understand the channel cannot understand the price. This is the single most useful thing to carry out of this chapter. When a quotation arrives at $3.95 a pound and the farmer thirty miles away will sell the same bird at $3.40, the temptation is to conclude that fifty-five cents has been stolen by somebody in the middle. Sometimes it has. Usually it has been spent, on work that will still have to be done and still have to be paid for if the middle is removed. The difference between a student who can recite the purchasing sequence and a buyer who can defend a decision to a general manager is largely a matter of knowing what that fifty-five cents buys. Feinstein and Stefanelli treat the channel of distribution as foundational, and they are right to. What has changed since the parent text settled into its familiar shape is not the structure but the concentration: fewer and larger distributors, more of a kitchen's spend running through one truck, and a set of regulatory and data requirements that now bear directly on which suppliers a buyer can even consider. This chapter walks the channel in order, states what each participant is paid for, shows with arithmetic why direct is sometimes the more expensive route, explains how distributors actually earn, and ends with the volatility and traceability questions that make channel knowledge a live commercial skill rather than a list to memorize. The route from producer to operator Begin at the origin. Growers and producers — farmers, ranchers, fishers, dairies, orchards — hold the biological risk. They are paid for taking a crop or an animal from input to harvest across a season during which weather, disease, feed cost and labor availability can all destroy the margin. A grower's price reflects that risk plus a return on land and equipment that was committed months before anyone knew what the market would pay. Primary processors convert the raw commodity into something that can be moved and stored: slaughter and chilling, milling, shelling, freezing at sea, washing and cooling produce within hours of harvest. This step is where most of the food safety and shelf-life outcome is determined, and it is capital-heavy. A processor is paid for plant, for regulatory compliance, for yield management — the difference between a 72 per cent and a 74 per cent carcass yield is the processor's profit — and for absorbing the mismatch between when a crop is ready and when a kitchen wants it. Manufacturers take processed inputs and make branded or specified goods: the frozen dough, the base sauce, the portioned patty, the shelf-stable dressing. They are paid for formulation, for consistency across production runs, for packaging, and for the brand promise that a case bought in March will behave exactly like the case bought in September. Much of what a hospitality buyer treats as a "product" is really a manufacturer's guarantee of repeatability. Brokers and manufacturers' agents sell but never take title. This is the point students most often miss. A broker represents a manufacturer's line to distributors and to large operators, secures listings, runs demonstrations, handles the samples and the cuttings, and chases a specification problem when one arises — but the goods never sit on the broker's balance sheet and the broker never invoices the operator. The broker is paid a commission by the manufacturer, typically a small percentage of sales, which is embedded in the manufacturer's list price. Removing the broker does not remove the selling cost; it moves it to the manufacturer's own sales force, which is usually more expensive per call, not less. Importers take title to goods crossing a border and carry the specific risks of doing so: customs classification and duty, currency movement between order and payment, port congestion, inspection holds, and the compliance obligations attached to the origin of the goods. An importer's margin looks large until you count a container held three weeks at an inspection facility. For a buyer, the importer is also the party who can answer where a product actually came from, which matters enormously once traceability and forced labor rules are in play. Broadline distributors are the workhorses of foodservice. A broadliner carries a wide assortment across most categories — produce, meat, dairy, frozen, dry goods, chemicals, disposables, small equipment — and delivers it to the operator's door on a scheduled route. The service being bought is breadth plus frequency: one order, one truck, one invoice, several times a week. The cost is that breadth is not depth. A broadliner stocking forty thousand items cannot be the deepest source in any of them. Specialty and niche distributors go the other way: a narrow category, carried in depth, with staff who know it. The artisan cheese house, the seafood specialist running its own fleet relationships, the produce distributor with a genuine forager, the coffee roaster who will cup with you. They are paid for product knowledge, for access to items a broadliner will not list, and for the willingness to handle small quantities of fragile things. The cost is higher per unit, smaller drops, and another delivery window in an already crowded morning. Systems distributors serve chains and multi-unit operators with a limited, contract-specified assortment supplied to every unit at an agreed price. The service is uniformity: a burger in one market tastes like a burger in another because the same distributor is pushing the same twelve hundred items through every door. The cost is rigidity. A unit manager cannot buy off-system without breaking the contract, and the chain has traded flexibility for the scale economics that make the price work. Cash-and-carry and club operations sell at a warehouse to whoever turns up, on payment, with no delivery and no credit. They are paid for holding stock close to the operator and for stripping out everything else. The cost is that the buyer supplies the truck, the driver, the labor and the working capital, which is why the shelf price is low. A cash-and-carry run at eleven on a Friday is not free; it costs whatever the person doing it is worth for the ninety minutes. Produce and seafood markets and direct farm sales are the oldest routes and still the sharpest. A terminal market, a dock, or a farm gate offers freshness, price discovery and the chance to see the actual goods before buying. What they do not offer is delivery, dependable supply, credit, or a credit memo when something is wrong. The buyer takes those risks personally. E-commerce channels now sit across all of the above: distributor ordering portals, punchout catalogs that drop a supplier's live catalog into the operator's own purchasing system, marketplaces that aggregate small producers, and delivered-to-door platforms for non-food and small-wares. What e-commerce changes is the transaction cost of ordering and the visibility of price, not the physical economics. Somebody still has to pick, pack, chill and drive. One channel is structurally different and worth naming, because students meet it in the same module. Alcohol distribution in the United States runs on a three-tier system created after Prohibition: producers sell to licensed wholesalers, wholesalers sell to licensed retailers, and retailers sell to consumers, with wide state-by-state variation and with control states in which the state itself acts as wholesaler or retailer. A beverage buyer therefore has no legal option to go direct in most jurisdictions, whatever the economics say. Table 1 sets out the six routes an operator realistically buys through, what each performs, where it fits, and what it costs. Table 1. The main routes from producer to operator Channel What it does for the buyer Typical use What it costs you Broadline distributor Breadth of assortment, scheduled multi-weekly delivery, credit terms, one invoice, credit memos for rejections, usage data The backbone of a kitchen's spend: dry goods, dairy, frozen, disposables, chemicals, mid-grade proteins Gross margin built into every line; depth sacrificed for breadth; drop minimums and fuel surcharges; concentration risk as the share of spend rises Specialty distributor Depth and expertise in one category, access to items a broadliner will not list, tolerance of small quantities Signature and high-visibility items: cheese, charcuterie, fine produce, fish, coffee, pastry Higher unit price, smaller and less frequent drops, additional receiving window, extra supplier to manage Systems distributor A fixed contracted assortment delivered identically to every unit at an agreed price Chains and managed multi-unit estates needing product uniformity Rigidity: no off-system buying, slow menu change, dependence on a single contracted network Cash-and-carry or club Immediate availability, no minimum, low shelf price, no commitment Emergency fill-ins, low-volume items, short-notice covers Your truck, your driver, your labor hours, your cash up front; no credit, no delivery, no recourse Direct from producer, farm or market Freshness, provenance, price discovery, a story the menu can use, a relationship with the person who grew it Seasonal produce, local proteins, eggs, honey, specialty items where origin is the selling point Collection cost or a high delivery minimum; no credit; no substitute when supply fails; storage and cash tied up; volume pulled out of your distributor tier E-commerce and marketplace platforms Low-friction ordering, visible pricing, catalog integration with the purchasing system, access to small producers Non-food, small wares, specialty dry goods, supplementary sourcing Fulfillment economics still apply and are priced in; weaker service recovery; fragmented invoicing and receiving What the middle of the chain is paid for Students dismiss intermediaries as markup because markup is the only part of them that appears on the invoice. The functions are real, and it is worth naming all eight precisely, because in an examination they are frequently the difference between a description and an answer. Breaking bulk is the conversion of production-scale quantities into kitchen-scale quantities. A processor runs forty thousand pounds; a restaurant wants forty. Somebody must buy the forty thousand, split it, and carry the unsold remainder. Assortment is the aggregation of many producers' output into one orderable list, so that a chef places one order rather than nineteen. Credit is the extension of payment terms — the distributor pays its suppliers before the operator pays the distributor, financing the operator's inventory in the gap. Storage is the holding of stock between production and consumption, which is what allows a kitchen to run a walk-in rather than a warehouse. Transport is physical movement, and in foodservice it is movement in small, frequent, awkward drops to premises with no loading dock. Temperature integrity is the maintenance of the cold chain end to end, documented, which is where most food safety failure is actually prevented. Information runs both ways: usage reports, price trend advice and product knowledge flowing to the buyer, demand signals flowing back up the chain. Risk absorption is the willingness to own inventory that may not sell, to take back a rejected delivery, and to be the party the operator sues if something goes wrong. Remove any of these and the function does not disappear. It relocates, usually to the operator, who performs it worse because it is not the operator's business. Consider a worked comparison. The Larkspur Room is a ninety-seat independent restaurant using 140 pounds of whole chicken a week, a stable volume across a stable menu. Its specialty distributor quotes $3.95 a pound delivered, on Tuesdays and Fridays, on thirty-day terms, with a credit memo for anything rejected at the door and no separate delivery charge because the account comfortably clears the $600 drop minimum on its total order. Weekly cost of goods for chicken is 140 × $3.95 = $553.00. Halloran Farm, thirty-four miles out, will sell the same bird at $3.40 at the gate. The gap is $0.55 a pound, or $77.00 a week, and that is the number that gets quoted in the staff meeting. Take the first route: collect it. Product cost is 140 × $3.40 = $476.00. The round trip is 68 miles, and the operation costs its van at $0.70 a mile as a planning convention covering fuel, wear, insurance and eventual replacement, which is $47.60. A cook is off the line for two and a half hours at a fully loaded $24.00 an hour, which is $60.00. Total delivered-to-kitchen cost is $476.00 + $47.60 + $60.00 = $583.60. Against the distributor's $553.00 that is $30.60 a week more expensive, or $1,591.20 a year, and the operation has also lost 130 hours of a cook's time. The $77.00 saving was real; the $107.60 of collection cost was larger. Take the second route: let the farm deliver, which it will do only on orders of 300 pounds or more. That means a fortnightly order of 300 pounds against a fortnightly need of 280 pounds, at $1,020.00. Per pound of actual need that is $1,020.00 ÷ 280 = $3.64, genuinely below the distributor's $3.95, a saving of $0.31 a pound or $43.40 a week. On cost of goods, direct wins. Now count what else moved. The farm is paid on delivery, not in thirty days, so roughly $2,186 of working capital that the distributor was financing is now the restaurant's, costing about $197 a year on a nine per cent credit line — small, but not nothing. Two full shelves of the walk-in are now committed to one item for a fortnight, displacing whatever else would have sat there. The last birds are being cut on day eleven or twelve, so the specification has quietly drifted from what the menu promises. There is no second call: if Halloran has a bad week, there is no substitute arriving Friday and no credit memo, only a chef changing the menu at four o'clock. And then the decisive number, which most students miss entirely. The distributor's $3.95 is not a price for chicken; it is a price for an account. That quote assumes the Larkspur Room spends about $6,500 a week across the whole list. Pull $553 of chicken out and the weekly spend falls to $5,947, which drops the account into a lower pricing tier and lifts the price of everything else by roughly two per cent. Two per cent of $5,947 is $118.94 a week. The restaurant saved $43.40 on chicken and paid $118.94 more for everything that is not chicken — a net loss of $75.54 a week, or $3,928.08 a year, achieved by a decision that looked like a $77.00 weekly saving on the whiteboard. None of this is an argument against direct sourcing. It is an argument against arithmetic that stops at the sticker price. Direct buying works when the price gap is wide enough to swallow the fixed costs, when the volume is large enough to clear the producer's delivery minimum without overbuying, when the item's shelf life tolerates the order cycle, when the menu can genuinely move if supply fails, and when the volume withdrawn is small enough not to disturb the distributor relationship that carries the other ninety per cent of the kitchen. Test those five conditions before the meeting, not after it. How a distributor makes money A buyer negotiates better against a supplier whose economics are understood, so it is worth being explicit about the five places a foodservice distributor earns. The first and largest is gross margin on landed cost. Landed cost is what the distributor paid for the goods plus freight inbound plus any duty, handling and shrink. The distributor then prices to a target margin, and the exam-relevant subtlety is the difference between margin and markup. A case landed at $42.00 sold at a 22 per cent gross margin prices at $42.00 ÷ 0.78 = $53.85, not $42.00 × 1.22 = $51.24. The margin of 22 per cent is a markup on cost of 28.2 per cent. Distributors quote margin; operators, if they are careless, hear markup, and the gap is the distributor's. The second is manufacturer allowances and promotional funding. Manufacturers pay distributors to push their lines: volume rebates, listing fees for shelf space in the catalog, off-invoice deductions during a promotion, marketing development funds, and payment for sales-force incentives. This income is often invisible to the buyer, and it is the reason a distributor sales representative can be enthusiastic about a brand switch that offers the operator nothing. Ask, plainly, whether the item being recommended carries promotional support. The question is legitimate and the answer tells you what you are being sold. The third is private label. A distributor's own brands — usually tiered as a premium, a standard and an economy line — are packed by the same manufacturers that supply national brands, and they carry a materially higher margin because there is no brand owner taking a cut and no advertising to fund. Private label is frequently good value, and it is simultaneously the distributor's most profitable shelf. Both statements are true. The buyer's job is to specify precisely enough that a private label offer can be compared to a national brand on identical terms rather than on the label. The fourth is delivery economics: drop minimums below which a delivery charge applies, fuel surcharges that move with a published index, small-order fees, and charges for off-schedule or after-hours delivery. These are not incidental. A distributor's cost per drop is largely fixed, so an account ordering twice a week at $1,500 is far more profitable than one ordering four times at $750, and the pricing reflects it. Order consolidation is one of the few levers an independent operator can pull that costs nothing and is genuinely valued on the other side. The fifth is payment terms as a financing product. Thirty days of credit is a loan, and the distributor prices it into the margin whether or not it is itemized. This is why prompt-payment discounts exist — a term such as 2/10 net 30, meaning two per cent off if paid within ten days with the full amount due in thirty, is an offer to buy back the financing. Taken across a year, that two per cent for twenty days early is an annualized return in the high thirties, which is why taking the discount is nearly always right if the cash exists, and why a distributor offers it only to accounts it wants to keep. Against that background, the difference between the two main pricing arrangements becomes clear from the distributor's side. Under a cost-plus agreement the distributor opens its landed cost on agreed items and adds a disclosed fee, either a percentage or a fixed amount per case. Its income is predictable and its incentive shifts from buying cheaply to selling volume, since the plus is earned per unit shipped. Cost-plus requires audit rights to mean anything, because "cost" can be defined generously, and it usually applies to a specified basket rather than the whole catalog. Under a market-price arrangement the distributor quotes a delivered price and keeps whatever spread it can achieve between its buying and its selling. Its income is variable and its incentive is to buy well and hold the sell price when the market falls. Neither is inherently better for the buyer. Cost-plus rewards an operator with the discipline to audit and the volume to justify the negotiation; market price rewards an operator who compares quotes frequently and is willing to move. What loses money is signing a cost-plus deal and then never auditing it. Concentration, volatility and the traceability requirement Foodservice distribution has consolidated substantially, and the consequences for a buyer are practical rather than abstract. Fewer and larger distributors means better logistics, wider assortment and more sophisticated data — and it also means fewer people to call. The most damaging loss is what experienced buyers call the second call: the ability, when a supplier fails, to pick up the phone to a comparable alternative who already knows the account, already has a credit line in place and can be on the dock the next morning. In a consolidated market that second call often does not exist, and the buyer is negotiating with an organization that knows it. For independents the leverage problem is severe. An operation spending a few hundred thousand dollars a year is not a meaningful account to a national distributor, and it receives national-distributor pricing accordingly. The principal response is the purchasing group — a group purchasing organization or cooperative that aggregates the volume of many independents and negotiates contracted pricing on their behalf, funded by administrative fees and by supplier rebates. These work, and they work best on the branded and commodity center of the list where specifications are identical across members. They work least well on the items that make a restaurant distinctive, which is where the buyer must still negotiate personally. A buyer should also read the funding model: a group paid principally by suppliers has an interest in directing volume, which may or may not align with the member's interest. The other consequence is risk concentration. When one distributor supplies eighty per cent of a kitchen, that distributor's labor dispute, system outage, warehouse fire or credit decision is the kitchen's problem too. The mitigation is not to shatter the spend into six accounts — the price penalty is real and the receiving burden is worse. It is to hold a live, transacting secondary account, however small, on the categories that would stop service: proteins, dairy, and the two or three signature items with no substitute. A supplier who has invoiced you within the last month will take your emergency call. One you have not bought from in two years will not. Since 2021 the volatility has been continuous rather than episodic, and a buyer needs a working account of where it comes from. Commodity prices have moved sharply and in both directions, driven by energy and fertilizer costs feeding into grain and protein, by currency movement, and by demand that rebounded unevenly. Freight has been its own shock, with container rates, fuel and route disruption all moving independently of the goods being carried. Labor scarcity in warehousing and driving has raised distribution costs structurally and, more disruptively for kitchens, has degraded service reliability: late trucks, incomplete pallets and substituted items are a labor problem before they are a supply problem. And specific commodities have taken specific hits — avian influenza in poultry and eggs, drought and frost in coffee and citrus, disease in cocoa, heat events in shellfish waters. These are not general inflation; they are item-level events that arrive without warning and last a season or longer. What buyers actually do about it is a short list, and each item has an honest limit. Dual sourcing means qualifying a second supplier for critical items before you need one, and it costs volume discount and management time; it also fails when both suppliers are drawing from the same constrained origin, which happens more often than the organization chart suggests. Specification flexibility means writing the specification so that a defensible substitute is already approved — a grade band rather than a single grade, a size range rather than a count, two acceptable cultivars — and it works only if the flexibility was agreed with the kitchen in advance, because a substitution decided at the receiving door is not flexibility, it is capitulation. Forward contracting fixes a price for a defined volume over a defined period, and it transfers risk rather than removing it: the buyer who fixed at the top of a market pays above spot for the whole term and has to defend that to a general manager reading a falling index. It also requires the operator to take the contracted volume, which is a commitment about future covers. Menu design that can substitute is the most powerful of the four and the least used: building dishes so that the protein, the starch or the garnish can rotate without reprinting, costing, or apology, and holding the menu's price architecture rather than its literal contents. Its limit is the signature dish, which by definition cannot substitute — and the correct response there is not flexibility but inventory and a contract. Traceability has now moved from food safety paperwork into supplier selection, and this is the change that most affects how a buyer evaluates a distributor. The Food Safety Modernization Act's Food Traceability Rule, section 204, requires additional records from firms that manufacture, process, pack or hold foods on the Food Traceability List. Those records are organized around critical tracking events — the defined points in a product's journey, such as harvesting, cooling, initial packing, shipping, receiving and transformation, at which records must be created — and key data elements, the specific pieces of information that must be captured at each event, including traceability lot codes, quantities, locations and dates. The Food Traceability List names the foods in scope, and it is a list of higher-risk categories rather than everything in the walk-in. The original compliance date was 20 January 2026; in August 2025 the FDA proposed extending it by thirty months to 20 July 2028. A student should check the current status before relying on any date, because this rule has moved more than once. The purchasing consequence is straightforward and does not depend on the date. A buyer sourcing a listed food needs suppliers who can create, hold and transmit lot-level data in a form the operator's own records can receive. That is a capability question, and it belongs in supplier evaluation alongside price, service level and food safety audit: can this supplier give me a traceability lot code on the invoice or the case label, in a machine-readable form, consistently, for every listed item? A small producer with beautiful product and a paper ledger may fail that test. So may a distributor whose systems were built for order entry rather than for data exchange. Increasingly, supplier selection turns partly on data interoperability — a sentence that would have sounded absurd in a purchasing textbook a generation ago and is now simply a description of the job. For the exam and the purchase order Be exact about three definitions. A broker or manufacturer's agent sells on behalf of a principal and never takes title; a distributor takes title, holds inventory and carries the risk of it. Confusing the two is a marked error. Landed cost is purchase price plus inbound freight, duty, handling and shrink, and it is the base on which a distributor's margin is calculated. Gross margin is expressed as a percentage of selling price, markup as a percentage of cost, and the two are different numbers for the same transaction; be able to convert between them in both directions. The calculation most likely to be examined is a direct-versus-distributor total cost comparison. Build it in a fixed order: product cost at the required quantity; delivery cost or collection cost including vehicle and labor; the effect of any minimum order on quantity purchased, holding period and waste; the working capital effect of the payment terms; and finally the effect on pricing elsewhere if the withdrawn volume changes the buyer's tier with an incumbent supplier. Students who stop after the first two steps produce the answer the Larkspur Room nearly acted on. Two questions to work. First: an operation buys 140 pounds of an item a week at $3.95 delivered, or can collect at $3.40 with a 68-mile round trip, a van costed at $0.70 a mile and two and a half hours of a cook at $24.00 fully loaded. At what weekly volume does collection become the cheaper route, and what does that tell you about when direct sourcing scales? Second: your largest distributor supplies eighty per cent of your food spend and has just told you its Friday delivery is moving to Saturday. Set out, in order, what you would change in the next fourteen days, distinguishing what protects service this month from what reduces the concentration that caused the exposure. Chapter 3: Product Identification and the Specification A restaurant's menu is a set of promises. The specification is the document in which those promises are converted into something a supplier can quote, a receiving clerk can check, and a controller can cost. Everything in the rest of this book depends on it. You cannot compare three bids unless all three are quoting the same product. You cannot reject a delivery unless you can point to a written standard the delivery failed. You cannot run a yield test whose result means anything beyond the single box you tested. You cannot cost a recipe. You cannot evaluate a supplier, because evaluation is the measurement of performance against an expectation, and an unwritten expectation is a feeling. Feinstein and Stefanelli place product identification early in the purchasing sequence for exactly this reason: it is the step at which the buyer's discretion is largest and its consequences most permanent. After the specification is written, purchasing becomes administration. Before it is written, purchasing is design. Most operations spend enormous energy on the administration and almost none on the design, which is why so many of them are surprised by their own food cost. Quality is suitability, not superiority The single most important idea in this chapter is also the one students resist most, because it contradicts the way the word is used everywhere else. In purchasing, quality means suitability for an intended use. It is not a ranking. There is no such thing as a good ingredient in the abstract. There is only an ingredient that is appropriate to a particular use, at a particular price point, prepared by cooks of a particular skill level, for guests with a particular expectation. Change any one of those four and the correct product changes with it. Consider beef. USDA quality grades — Prime, Choice, Select, and below them Standard, Commercial, Utility, Cutter and Canner — measure two things: marbling, meaning flecks of intramuscular fat, and physiological maturity, an assessment of the animal's age from bone and lean characteristics. Marbling predicts juiciness and flavor in cuts cooked by dry heat. It predicts very little about a cut that will be braised for four hours, because in a braise the eating quality comes from collagen converting to gelatin, and connective tissue is abundant in the cheaper grades and cheaper cuts precisely because those animals worked. Buying Prime chuck for a short-rib braise is paying a premium for an attribute the cooking method will render irrelevant. Now take the opposite end of the same animal. A hotel banquet department serves a 6-ounce tenderloin medallion, cooked to medium, sauced, held in a hot box for twenty minutes and carried across a ballroom. Prime peeled, side-muscle-on tenderloin is quoted at $34.00 a pound; Choice at $24.50. The department uses 400 pounds a month. The premium costs $9.50 a pound, $3,800 a month, $45,600 a year. And the tenderloin is the muscle in which marbling differences express themselves least — it is the least marbled cut at any grade, prized for texture rather than fat — served at a doneness and a holding time that would flatten the difference even if it existed. That $45,600 buys a word on a purchase order. The pattern repeats across categories. USDA egg grades — AA, A and B — measure albumen height and spread, yolk firmness and shell condition. Those attributes are visible in a poached or fried egg, where a thin white spreads across the pan and looks wrong. They are annihilated the moment the egg hits a mixing bowl. A pastry kitchen using 120 dozen a week and paying $4.85 for Grade AA large instead of $4.40 for Grade A large spends $54 a week, $2,808 a year, on a structural property destroyed by the first turn of the whisk. Produce grades — US Fancy, US No. 1, US No. 2 — are largely cosmetic and defect-based. US Fancy apples belong in a fruit bowl in the lobby; a pie that will be peeled, cored and sliced can take US No. 1 or orchard-run at a substantially lower price, and the guest will never know. Jumbo lump crab meat justifies itself in a cocktail where the lumps are visible; in a crab cake that will be bound, formed and fried, backfin or special does the same job for a fraction of the money. Sashimi-grade tuna is a defensible purchase for crudo and an indefensible one for a tuna melt. Over-specification is therefore a real and measurable cost, and it has a particular signature: it is invisible, because nothing goes wrong. Nobody complains about Prime. The loss shows up only in the food cost percentage, where it is usually blamed on portioning. Under-specification has the opposite signature. It is also invisible, but it costs more and it eventually breaks something. Take a specification that reads "shrimp, white, peeled and deveined, tail-on, individually quick frozen, 5-pound bag." It names no count, and — more expensively — it names no maximum glaze. Glaze is the protective layer of ice applied to frozen seafood, and it is water you are buying by the pound. At 20 percent glaze, a 5-pound bag contains 4.0 pounds of shrimp; at 10 percent it contains 4.5. At a quoted $9.20 a pound, the bag costs $46.00 either way, so the true cost of shrimp is $11.50 a pound in the first case and $10.22 in the second — a 12.5 percent difference that no receiving clerk can see without thawing and draining a sample. An operation buying 40 pounds gross a week, 2,080 pounds a year, receives 1,664 pounds of actual shrimp under the heavy glaze and 1,872 under the light one. The 208-pound gap is worth about $2,100 a year, and it was created by a sentence nobody wrote. The same failure mode runs through poultry. "Chicken breast, boneless skinless, 6 ounce" with no statement about enhancement invites a product injected with up to 15 percent of a solution of water, salt and phosphates. At $3.10 a pound the meat is really costing $3.65, the kitchen's seasoning is now wrong, and the cooked yield has changed. A specification that fails to close a door has, in commercial terms, opened it, because the supplier's margin lives in the gap between what you asked for and what you would have asked for had you thought about it. This is not dishonesty. It is the predictable result of asking a vendor to interpret an ambiguous instruction in a competitive bid. The elements of a specification A useful specification is short — one page, or one screen — and complete. Length is not rigor; a three-page specification is a specification nobody reads at six in the morning. What matters is that each element that could vary has been fixed. The itemized elements below are the standard set, and Table 2 sets out six of the load-bearing ones alongside the characteristic failure that follows when each is left out. Product name and intended use. The name should be the one the trade uses, not the one the menu uses. "Strip loin, boneless" is a product; "steak for the bistro special" is not. The intended use is stated in a single line — "grilled, 10-ounce portion, à la carte" — because it is the justification for every other line in the document and the first thing to consult when someone proposes a change. Grade or quality standard. Where a recognized public grade exists, cite it. Where none exists, state the measurable attribute you actually care about: Brix for melons, moisture for scallops, fat content for ground beef, solids for potatoes, protein for flour. Size, count or weight range. Portion cuts by ounce; primals and subprimals by a weight range; produce and seafood by count. A range must have both ends: "10 to 12 pounds," not "about 11 pounds." Packaging and pack size. The case configuration — 6 by #10 cans, 4 by 5-pound bags, a 40-pound tray-pack carton — and any requirement about the packaging material itself, including recyclability, case labeling and lot-code visibility. Unit of purchase and unit of issue. You buy a 50-pound sack and issue by the pound; you buy a case of six and issue by the can. Recording both prevents the classic inventory error in which a case is valued as a unit and a unit is counted as a case. Point of origin, where it matters. It matters when origin is a proxy for a functional property (Idaho russets for their solids and their behavior in a baking oven), when it is a marketing claim you are making to guests, or when it carries regulatory consequence. Note that mandatory country-of-origin labeling in the United States binds retailers, not foodservice operators; if origin matters to you, it must be a contractual term of your specification, not something you assume will arrive on the label. Degree of preparation or fabrication. Whole, drawn, dressed, filleted, portioned; whole head, cored, chopped, washed and bagged; shell-on, peeled, deveined, tail-on. This is where cost transfers between the invoice and the payroll, and it deserves the arithmetic set out later in this chapter. Condition on delivery, including temperature. Refrigerated product at or below 41°F, frozen at 0°F with no evidence of thawing and refreezing, live shellfish alive and with tags intact, produce free of decay and within a stated defect tolerance. Acceptable brands, or explicit permission of substitutes. Either name the brand and mean it, or name it as a reference standard followed by "or approved equal" — and then define who approves, against what test. Inspection and acceptance criteria. How the delivery will be checked, by whom, on what sample, and what happens when it fails: full refusal, partial acceptance, or acceptance against a credit memo. Certification required. A current audit certificate under a scheme benchmarked by the Global Food Safety Initiative, a continuing letter of guarantee, a certificate of analysis, allergen control documentation, organic or chain-of-custody certification, kosher or halal certification, and — for any item on the FDA's Food Traceability List — the critical tracking events and key data elements that section 204 of the Food Safety Modernization Act requires. That last item has quietly moved traceability out of the food safety binder and into the purchase specification, because the records only exist downstream if the buyer demands them upstream. Table 2. What a purchase specification must state, and what goes wrong when it does not Element What it fixes Typical failure when omitted Intended use The standard against which every other line is judged, and the test for any proposed substitution Specifications drift upward over time; nobody can say why a grade was chosen, so nobody can defend lowering it Grade or quality standard The eating and handling characteristics the operation is paying for Bids are not comparable; the lowest bidder wins by quoting the cheapest defensible interpretation Size, count or weight range Portion consistency, plate appearance and portion cost Portion cost moves with each delivery; the plate looks different week to week and the recipe cost is fiction Degree of preparation Where the labor sits — in the supplier's plant or your kitchen Prep hours are scheduled for work that has already been paid for, or not scheduled for work that has not Condition and temperature on delivery Safety, shelf life and the receiving clerk's authority to refuse Product is accepted because there is no written basis to reject it; shrink appears later and is blamed on storage Packaging, pack size and net weight basis What you are actually paying for per pound, and how it is counted in inventory Glaze, brine, ice or drained weight is purchased as product; inventory valuation and food cost are both wrong The public languages a buyer borrows No operation writes its specifications from nothing. It borrows a vocabulary that suppliers already speak, and the buyer's skill lies in knowing what each borrowed term actually guarantees. In the United States the largest of these vocabularies is USDA grading, administered by the Agricultural Marketing Service. Two points about it are examinable and widely misunderstood. First, grading is voluntary and is paid for by the applicant, whereas inspection for wholesomeness is mandatory and is carried out under the Food Safety and Inspection Service. A grade shield and an inspection legend are different marks meaning different things; ungraded product is not unsafe product. Second, each grading system measures a specific, narrow set of attributes and is silent on everything else. Beef quality grades measure marbling and maturity, not tenderness in every cut and not flavor from breed or feed. Beef yield grades, numbered 1 to 5, measure something else entirely — the proportion of saleable retail cuts a carcass will give — and matter when buying primals rather than portion cuts. Poultry grades A, B and C assess conformation, fleshing, fat cover and defects such as bruising, broken bones and discoloration; they say nothing about flavor, breed or welfare. Egg grades measure interior and shell quality, while egg size is a separate classification defined by minimum net weight per dozen: Jumbo 30 ounces, Extra Large 27, Large 24, Medium 21, Small 18, Peewee 15. A US Large egg is therefore two ounces. Butter carries Grade AA, A and B based on flavor, body, color and salt. And "Grade A" on fluid milk is not a palatability tier at all — it is a sanitation standard under the Pasteurized Milk Ordinance, qualifying the milk for fluid consumption. Knowing which question each grade answers is what stops a buyer paying for an answer to a question nobody asked. For meat, the indispensable second language is the Institutional Meat Purchase Specifications, published by the Agricultural Marketing Service and reproduced in the meat trade's standard buyer's reference. IMPS assigns a number to a defined cut: Series 100 for fresh beef, 200 for lamb and mutton, 300 for veal and calf, 400 for pork, 1000 for portion-cut products. IMPS 189A is a full beef tenderloin, peeled, side muscle on, defatted — the cut the trade calls a PSMO. IMPS 180 is a boneless strip loin, 112A a lip-on boneless ribeye roll, 184 a boneless top sirloin butt. The system also standardizes the options a buyer must still choose: maximum fat thickness, a weight range, the state of refrigeration, and the packaging. The value of this is that "IMPS 189A, Choice, 5 to 6 pounds, fresh chilled, maximum surface fat 0.25 inch, vacuum packaged" means precisely one thing to every supplier in the country, and a dispute about it can be resolved by reference to a published document rather than by argument. Produce and seafood use counts, which are the trade's compact way of encoding size. A count is the number of pieces in a standard container, so the count and the size move in opposite directions: 88-count apples in a 40-pound carton are larger than 113-count; a 90-count carton of Idaho potatoes contains potatoes averaging 8.9 ounces, and a 70-count carton contains larger ones. Tomatoes are sized 5x6, 6x6, 6x7 and so on from the rows across and down a two-layer lug. Shrimp are counted per pound — U/15, 16/20, 21/25, 26/30, 31/40 and downward, where "U" means "under" — and a professional specification states the basis, because counts are established on raw headless shell-on product and the piece count per pound rises once the shrimp is peeled. Scallops run U/10, 10/20, 20/30, 30/40, and any scallop specification worth writing also states "dry pack, no phosphates," because scallops soaked in sodium tripolyphosphate absorb water, leach it in the pan, steam instead of searing, and are sold to you by the pound. Other markets use different grids, and the temptation to translate them is a trap. EU marketing standards classify fresh produce as Extra Class, Class I and Class II, with specific standards for a short list of products including apples, pears, tomatoes, table grapes, citrus, kiwifruit, lettuce, peaches and nectarines, strawberries and sweet peppers, and a General Marketing Standard covering the rest. EU and UK eggs are Class A or Class B, with weight grades S, M, L and XL — Medium 53 to 63 grams, Large 63 to 73, Extra Large above 73 — and, usefully for a buyer, a farming-method digit stamped on each shell: 0 organic, 1 free range, 2 barn, 3 cage. Beef, however, is where comparison collapses. The EU's EUROP carcass classification grades conformation from E to P and fat cover from 1 to 5. It measures the shape of the carcass and how much fat is on the outside of it. It does not measure marbling at all. A European buyer who wants the eating characteristics an American buyer obtains by writing "Choice" cannot obtain them by writing a EUROP letter; they must specify breed, age, finishing regime, or an assured scheme such as Red Tractor or a breed society certification — none of which is a grade in the USDA sense either. The lesson generalizes: identify which attribute the local public grid actually measures, and specify everything else by contract. Brands are the fourth language, and the shortest. A brand is a specification compressed into a name. It buys the operator batch-to-batch consistency, a known formulation, an absence of spec-writing labor, sometimes genuine menu pull — a guest looking for a particular cola or a particular ketchup — and a transfer of reputational risk to a company with more to lose than your supplier. A distributor's private label is a product packed to that distributor's own specification, frequently in the same plant as a national brand and frequently offered in honest tiers, premium through economy. It is a rational purchase when the item is an ingredient the guest cannot identify, when you have tested the tier against the branded product and found the difference immaterial to the intended use, and when you accept the two risks it carries. The first is reformulation: a private label can change its co-packer without telling you, and the first evidence is a dish that behaves differently. The second is structural and more serious. A private label can be bought from exactly one distributor. Writing it into the specification converts a competitive line into a captive one and quietly weakens your position on every other line in the basket, because the distributor now knows you cannot move the order without rebuilding your recipes. The disciplined form of brand specification is therefore attribute-first: state the functional requirements, name the brand as a reference standard, and add "or approved equal," with the approval procedure written down. Public and institutional buyers are frequently required to do this by their own procurement rules, and they are right to be. Keeping the specification honest A specification written once and never revisited becomes a description of what the operation wishes it were buying. The discipline that prevents this is value analysis: a structured, periodic review that asks of each significant item what function it performs, what that function costs, and whether a cheaper item performs the same function equally well. The questions are blunt. Does this need to be this grade, given the intended use? Does it need this degree of fabrication? Is the pack size right for our usage, or are we paying for a case we discard half of? Are we paying a supplier to perform a preparation step and then paying a cook to redo it? Is the packaging doing work we pay for and throw away? Value analysis is not cost-cutting; it is the removal of cost that buys nothing, which is a different and more durable activity. Its most consequential application is the make-or-buy decision, and the only way to do it correctly is to include labor at its loaded rate. Consider a 180-seat restaurant using 60 pounds of diced yellow onion a week. Whole onions cost $0.68 a pound and yield 82 percent after peeling and trimming, so 60 pounds of diced product requires 73.17 pounds as purchased, at $49.76. A prep cook produces 20 pounds of finished dice an hour, so the job takes 3.0 hours. The wage is $19.00 an hour; add 22 percent for payroll taxes, workers' compensation and benefits and the loaded rate is $23.18, giving $69.54 of labor. Making costs $119.30, or $1.99 a pound. Pre-diced onion delivered costs $2.35 a pound, or $141.00. Making wins by $21.70 a week, $1,128 a year. Now change one number. In a kitchen where the same job runs at 12 pounds an hour rather than 20 — less skill, worse knives, more interruption — the labor becomes 5.0 hours at $115.90, the total becomes $165.66, and the made product costs $2.76 a pound. Buying now wins by $24.66 a week. The correct answer is not a property of onions. It is a property of this kitchen's productivity and this kitchen's loaded wage, and it changes when either changes. Two cautions complete the calculation. First, a labor saving is only real if it is avoidable. If the prep cook is on a fixed 40-hour schedule and would otherwise be doing other necessary work, buying the diced onion does not remove the wage; it relocates the cook. The saving is realized only when it removes scheduled hours or absorbs work for which hours would otherwise have to be added. Second, the make case is strongest where the inputs are already sunk. Stocks are the classic example: bones and vegetable trim have already been paid for inside other purchases, and the oven and range are already hot, so the incremental cost of a stock is close to the labor of straining it. The make case is weakest in bakery, where it demands dedicated skill, dedicated equipment, dedicated space and dedicated overnight hours — four fixed commitments in exchange for a variable saving. Prepared vegetables sit between the two, and the arithmetic above is how you decide. Governance is the unglamorous other half. A specification is drafted jointly: the chef or food and beverage director defines the intended use and the quality attributes, the buyer translates them into commercial language and checks that the market can actually supply them, the controller tests the cost implication, and whoever owns food safety signs off on condition and certification. It is approved by the person who owns the cost line, so that the specification has an owner and not merely an author. It carries a number, an effective date, an author, an approver and a revision history, because a specification amended in conversation by a supplier's representative is not a specification. It lives attached to the item master record in the purchasing system rather than in a binder, so that it travels automatically onto the order guide, the bid sheet and the receiving screen — a point that has become urgent now that punchout catalogs return distributor SKUs directly into the ordering system, where a specification that exists only on paper is simply outvoted by whatever the catalog offers. Every approved supplier receives the current version. The receiving clerk receives an abstract of the acceptance criteria, because a standard nobody at the dock has seen is unenforceable at the only moment it matters. And the whole set is reviewed on a schedule — annually at minimum, and additionally on any menu change, any repeated receiving failure, any supplier change, and any regulatory change. The standard failure is easy to describe because it is nearly universal: specifications written during pre-opening, filed, never revised, contradicted within eighteen months by the actual order guide, and ignored at receiving because the person signing the invoice at six in the morning has neither a copy nor the authority to refuse a truck. An operation in that condition has not abandoned specifications. It has delegated them to its suppliers, who are writing them, competently, in their own interest. For the exam and the purchase order Three definitions must be exact. Quality is suitability for an intended use, not superiority on an absolute scale. A specification is a written description of a product, its intended use and the conditions of its acceptance, sufficient for a supplier to quote and a receiver to check. Value analysis is the structured review of a purchased item's function against its cost, seeking a cheaper item that performs the same function. Keep grading and inspection separate in your mind and in your answers: USDA grading is voluntary, applicant-funded and measures defined quality attributes; federal inspection for wholesomeness is mandatory and measures safety. Know what each grading system actually measures — marbling and maturity for beef quality grades, saleable yield for beef yield grades, interior and shell condition for eggs with size handled separately by minimum weight per dozen — and know that the EU's EUROP grid measures conformation and fat cover and therefore does not translate. The calculation most likely to be set is a make-or-buy comparison with labor at a loaded rate, or the net-weight correction that converts an as-quoted price into a true cost after glaze, brine or drained weight. Both reward the same habit: never compare two prices until you have reduced them to the same denominator. Two applications. First, take a single dish from an operation you know and write the full specification for its principal ingredient, then justify each line by reference to the intended use alone; any line you cannot justify that way is over-specification, and you should price what it costs per year. Second, choose one item your operation currently buys pre-prepared and one it currently makes, and run the arithmetic in both directions at your own kitchen's real productivity and loaded wage. If either answer surprises you, you have found the reason value analysis is scheduled rather than left to instinct. Hashtags: #TheProcurementPipeline #HospitalityPurchasing #HospitalityProcurement #PurchasingManagement #FiveRightsOfPurchasing #ProductSpecifications #TotalCostOfOwnership #SupplierSelection #StrategicSourcing #CentralizedPurchasing #DecentralizedPurchasing #GroupPurchasingOrganizations #SeparationOfDuties #FoodserviceSupplyChain #BroadlineDistributors #SpecialtyDistributors #CostPlusPricing #LandedCost #GrossMargin #Markup #ProductYield #StockoutRisk #FoodTraceability #EProcurement #FutureOfHospitalityProcurement

Download the Book (PDF): Introduction The SAGE Handbook of Tourism Studies weighs more than most laptops. Seven hundred and thirty-six pages, thirty-seven commissioned chapters, three parts, two editors and an international cast of contributors who between them represent anthropology, sociology, geography, economics, political science, history, cultural studies, development studies, architecture, transport planning and management. It was published in 2009 and it remains the most complete single account of what tourism studies contains. It is also, for the student who has just been handed it and told to write a dissertation, close to unusable. That is not a failure of the book. It is a consequence of what the book is. A handbook is a reference work, and reference works are designed to be entered at a point of need and left again. The student who begins at page one intending to finish is doing something the editors never imagined and did not provide for: the chapters do not build on one another, they do not share a vocabulary, and they frequently disagree about what a fact is. John Fletcher's chapter on the economics of international tourism and Naomi Leite and Nelson Graburn's chapter on anthropological interventions are not two perspectives on a common object. They are two different ideas about what would count as knowing something, sitting a hundred pages apart in the same binding. Which points directly at the problem this companion exists to solve. Tourism studies is not a discipline. It is a subject, claimed simultaneously by a dozen disciplines, each of which arrives with its own ontology, its own methods, its own journals, and — this is the part that decides degree classifications — its own standards for what would count as a good answer. A sample of twelve interviews is generous in one tradition and worthless in another. A regression on secondary data is rigorous to an economist and superficial to an ethnographer. Neither is right in general. They are right relative to a set of commitments, and the commitments are not interchangeable. Nearly every weak dissertation in this field fails for the same underlying reason. It takes a question from one tradition, a method from another, and an ambition from a third, and it assembles them without noticing that no single reader exists for whom the combination adds up. The student who writes an interpretive question about how residents experience visitor pressure, answers it with a two-hundred-response online survey, and then claims their findings generalise to coastal towns in general has not made three small errors. They have made one large one, and it was made before any data was collected, at the moment the question was written without a decision about where it belonged. So the argument of this book is simple to state and demanding to act on: locate your question in a discipline, adopt the standards of adequacy that come with it, and borrow from other traditions deliberately and with a declared reason. The Handbook's structure is the best available guide to what those disciplines are and what each brings, which is why this companion is organised around it rather than around a generic research-methods syllabus. Three things follow from that purpose. The first is that this companion does not summarise the Handbook chapter by chapter, and is not a substitute for it. A summary of a review is a third-hand account of the literature, and it is detectable in a bibliography at a glance. What this book does instead is synthesise the Handbook's material into modules that correspond to the decisions a researcher actually faces — where does my question live, what paradigm does it commit me to, what design does that paradigm license, what would count as evidence, what will an examiner attack. Where a specific Handbook chapter is the place to go, it is named, with its author, so the reader can go there directly and read the original. The second is that the methodological chapters here are technical rather than inspirational. A great deal of research-methods writing for students consists of definitions followed by encouragement. That is not useful at the point where somebody has to decide how many interviews to conduct, whether their sampling was purposive or merely convenient, what to do when the survey and the interviews disagree, or how to answer an examiner asking why they used structural equation modelling. The chapters on qualitative design, on measurement and inference, and on literature review are written to be worked from, and they say plainly where the conventional advice is impractical — member checking frequently is, probability sampling of visitors almost always is, and pretending otherwise in a methodology chapter is a good way to invite the question you least want. The third is that the Handbook's age is treated as a fact rather than as an embarrassment. Published in 2009, its topical chapters predate the platform economy at scale, the pandemic, and the current politics of visitor pressure; Ulrike Gretzel and Daniel Fesenmaier's chapter on information technology describes a landscape that has since been rebuilt. Its disciplinary and methodological chapters have aged far better, because paradigms move slowly and the difference between an interpretivist and a positivist commitment has not changed since 2009 or since 1985. The rule this companion applies throughout is to treat Part One and the methodological material as current, to treat Part Two as a baseline against which to measure change, and to update every topical claim against literature from the last five years. The order of the chapters follows the order of the decisions. The first establishes what kind of field this is and how a handbook is properly used. The second supplies the philosophical apparatus that G. R. Jennings's methodological chapter presupposes, in a form that can actually be deployed in a methodology section rather than recited in it. The third, fourth, fifth and sixth work through the four great clusters of approach the Handbook maps — the anthropological and sociological tradition that gave the field its founding theory; the geographical and mobilities tradition that took space and movement seriously; the economic, developmental and political tradition that deals in money and power; and the critical tradition of Part Three, where the word "critical" is explained as the technical term it is rather than as a synonym for disapproving. The seventh and eighth are the operational methods chapters, qualitative and quantitative, each written at the level of specificity a person needs when they are designing an instrument rather than describing one. The ninth deals with the literature review and the theoretical framework, which between them determine more of a dissertation mark than any other component and which are most often executed as summary rather than as argument. The tenth takes the project from proposal to defence: alignment, scheduling, writing for an assessor who cannot ask you anything, and the four questions every viva contains. Every chapter ends with questions answerable from its own content. Every named author, chapter title and framework in this book corresponds to something that genuinely exists, and where a source is uncertain it is described rather than cited. That is not a courtesy; it is the standard the reader is about to be held to, and a companion that fabricated a plausible-looking reference while telling its reader not to would deserve the obvious response. One last thing, addressed to the reader with a deadline. The instinct when facing a book of this size is to look for the shortcut through it. There is one, and it is not the one most people take. The shortcut is not to skim thirty-seven chapters; it is to read three of them properly — the disciplinary chapter that fits your question, the topical chapter that covers your case, and Jennings on methodology — and then to spend the time you saved reading the primary sources those chapters point you to. A dissertation built on ten works read closely will beat one built on eighty works cited from their abstracts, every time, in every tradition. The Handbook is at its most valuable not as a source of findings but as a curated bibliography assembled by people who read the field so that you would not have to read all of it. Use it that way. Chapter 1: A Field Without a Centre Pick the book up. It weighs something. Seven hundred and thirty-six pages, thirty-seven chapters, an editorial introduction and a conclusion, in three parts. Open it in Part One and run your eye down four consecutive contributions. David Bell writes on tourism and hospitality, a chapter concerned with encounter, service, and the cultural meanings of being hosted. A few pages on, Adrian Franklin writes the sociology of tourism, and the questions change: now the subject is social order, modernity, the tourist as a social type produced by particular historical conditions. Then John Walton writes histories of tourism, and the evidence becomes archival — timetables, guidebooks, municipal records, the slow accretion of resort towns. Then John Fletcher writes the economics of international tourism, and the page fills with leakage, multipliers, elasticities and the balance of payments. Four chapters in sequence. Four incompatible ideas of what a fact is. Nobody reads this book. That is not a criticism; it is a description of the genre. A handbook is not written to be read front to back, and the student who attempts it is doing roughly what a person does who reads a road atlas for the plot. The atlas contains everything, but it was assembled on the assumption that you already know where you are trying to get to. A handbook is entered at a point of need: you arrive with a question, find the chapter nearest to it, take what that chapter offers — less than students expect and more useful than they realise — and leave. The skill that makes a handbook valuable is the skill of entering it in the right place, and that skill depends entirely on understanding why the book has the shape it has. The shape is not an editorial preference. It is forced by the condition of the subject. Tourism studies has no centre, and a field with no centre cannot be summarised; it can only be mapped by sending a dozen different surveyors out and printing all their maps side by side. That is what The SAGE Handbook of Tourism Studies is: a collection of maps drawn to different projections, bound together, with a preface explaining that the projections do not agree. The indiscipline The standard reference for this condition is John Tribe's argument, published in 1997, that tourism is an indiscipline. The word was chosen with care. Tribe was not saying that tourism research is undisciplined in the loose sense of being sloppy. He was saying something more precise and more permanent: that tourism does not possess the features that make a discipline a discipline. Consider what a discipline supplies. It supplies an agreed object of study — economics the allocation of scarce resources, linguistics language — and while boundaries are contested at the edges, nobody is confused about the centre. It supplies shared methods, or at least a shared argument about methods, so that practitioners can evaluate each other's work without first negotiating the terms of evaluation. It supplies a canon, so that a citation functions as shorthand rather than as an introduction. And it supplies journals that everyone in the field reads, so that an argument published in one place enters a single conversation rather than dispersing into a dozen. Tourism has almost none of this. Its object of study is a phenomenon, not a class of questions: people travelling away from home for reasons that are not work or migration, and everything that follows from their doing so. That phenomenon can be examined economically, anthropologically, geographically, historically, politically, ecologically, semiotically and managerially, and it is. There is no shared method because the methods arrive attached to the disciplines that lend them. There is no canon that everyone has read, though there are texts that recur — Dean MacCannell's The Tourist of 1976, John Urry's The Tourist Gaze of 1990, Valene Smith's edited Hosts and Guests of 1977 — and their recurrence is partial and tradition-specific. An economist of tourism may never have read MacCannell and will not be embarrassed by the omission; an anthropologist of tourism may never have opened a paper on demand elasticity and will feel no gap. There is no single set of journals: the literature is published across hospitality, geography, development, leisure, marketing and general social-science titles, and no working researcher reads them all. What tourism has is subject matter. Everything else is borrowed. The temptation is to read this as a diagnosis of immaturity — a field that has not yet grown up, that will consolidate in time, that needs only a few more decades and a few more theorists before it becomes a discipline like the others. That reading is wrong, and believing it does real damage to a dissertation. The condition is structural, not developmental. It follows directly from the fact that the field is organised around a phenomenon rather than around a way of knowing. Disciplines are constituted by their mode of inquiry: what makes economics a discipline is not that it studies money but that it has a characteristic way of converting questions into tractable problems. Fields organised around phenomena — tourism, education, criminology, management, media — inherit their modes of inquiry from elsewhere and therefore inherit several at once. They do not converge, because a phenomenon does not select for a method. Tourism will still be an indiscipline in fifty years, and that is not a failure. It is also not, on its own, a problem. Plurality is only a problem when it is unorganised — when the person doing the research does not know which of the several available traditions they are standing in. What a discipline supplies that a subject cannot Here is the consequence, and it is the argument on which everything else in this companion rests. A discipline supplies theories, which students know, and it supplies methods, which students know. It also supplies something students almost never have named for them: standards of adequacy. A standard of adequacy is the internalised sense of what would count as a good answer — not a correct answer, a good one, the kind a competent reader in that tradition would accept as having done the job. An economist confronted with a claim about the effect of exchange-rate movements on arrivals knows, without deliberating, what evidence would settle it, what sample would be laughable, and what a referee would object to. An ethnographer confronted with a claim about how a guiding community understands its own work knows, equally without deliberating, that the answer lies in sustained presence and in an account thick enough that a reader can see how the interpretation was reached. These two standards are not merely different. They are incompatible, and they contradict each other on specifics that matter enormously to a student's decisions. Take sample size. Twelve interviews is ample for an interpretive study: with a well-chosen group, twelve long conversations can support a rich and defensible reading of how a particular practice is understood, and an examiner working in that tradition would ask about depth, reflexivity and analytic transparency rather than about numbers. Twelve is worthless for an inferential study: it licenses no generalisation and supports no test. The same number is simultaneously generous and negligible, and which it is depends on nothing about the number and everything about the tradition asking. Take secondary data. A regression on national arrivals and expenditure series is rigorous work within economics, where the data are the standard instruments of the field and the craft lies in specification, identification and the honest treatment of what the series can and cannot show. Presented to a critical or interpretive examiner, the same regression can read as superficial — a set of aggregates that has never made contact with anybody's actual experience, answering a question about lived reality with a proxy. Neither reader is being unfair. They are applying the standards that make their own work accountable. This is why the most damaging dissertation failure is not weakness in any component. It is incoherence between components. The classic version runs like this. The student takes their question from sociology or critical tourism studies — something about power, representation, the construction of authenticity, the experience of being gazed at. They take their method from the management school, because that is where they were taught and because a survey is administratively simple: a questionnaire, a convenience sample, a set of Likert items, some descriptive statistics. And they take their ambitions from development studies or policy, concluding with recommendations for how the destination management organisation should proceed. Every part is individually defensible — sociologists ask that question, management researchers run that instrument, policy scholars make those recommendations — but the combination adds up for nobody. The sociologist wants to know how a Likert scale could possibly capture the construction of authenticity. The management researcher wants to know why the sampling was not designed to support the inference. The policy scholar wants to know what evidence licenses the recommendation. There is no examiner in the room for whom the work coheres, because coherence in research is not the sum of adequate parts — it is the alignment of question, method and claim within a single standard of adequacy. The decision that prevents this is made early, and almost nobody makes it consciously. It is the decision about which disciplinary home the question belongs to. Plurality organised: the editors' claim and the book's architecture Tazim Jamal and Mike Robinson open the Handbook with a chapter titled "The Evolution and Contemporary Positioning of Tourism as a Focus of Study", and it is worth reading before any other chapter in the book, including the one you came for. Their account traces the field's growth out of applied and vocational concerns — hotel and catering training, travel-trade instruction, destination promotion — and its slow, uneven acquisition of theoretical seriousness as social scientists began to treat tourism as a significant object rather than a trivial one. That double origin has left a lasting tension. The field is institutionally housed, in most universities, in business and management schools, which impose an expectation of usefulness: research should improve something, serve an industry, inform a strategy. It is intellectually housed, for a substantial part of its literature, in the social sciences, which impose an expectation of explanation: research should account for why something is as it is, whether or not the account helps anybody sell anything. A dissertation is graded somewhere in the field of force between those two expectations, and the student who has not noticed them is navigating without instruments. The editors' own position is the animating claim of the book, and it is more than a diplomatic gesture towards diversity. It is that the field should be understood as plural, and that plurality should be organised rather than lamented. The alternatives are both worse: pretending the field has a unified theory, which produces students who cannot explain why their method suits their question, or treating the disorder as a scandal and spending the literature review complaining about it, which produces throat-clearing and no argument. Jamal and Robinson do the third thing: they arrange the traditions so that a reader can see what each is for, and leave the choosing to the reader. The three-part structure is that arrangement made physical. Part One, "Approaches to Tourism Studies", is disciplinary. Each chapter reports what a parent discipline brings to tourism: its questions, its concepts, its characteristic evidence, its blind spots. Naomi Leite and Nelson Graburn on anthropological interventions, Sanjay Nepal on tourism geographies, Linda Richter on power and political science, David Telfer on development studies, Nigel Evans on strategic business perspectives — these are not chapters about topics. They are chapters about ways of knowing. Part Two, "Key Topics in Tourism", is phenomenal: it tells you what is currently known about a thing. Religion and spirituality, volunteer tourism, heritage conservation, rural tourism, transport, destination marketing organisations, safety and security. Part Three, "Critical Issues and Emerging Perspectives", is where the arguments are live — post-colonialism, thanatourism, performance, gender, mobilities, ethics — along with Gaye Jennings's chapter on methodologies and methods, which sits in Part Three but functions as a hinge for the whole volume. The student's characteristic error is to enter through Part Two. It is an entirely understandable error, because that is where their topic is. They are writing about volunteer tourism, so they turn to Stephen Wearing and Jess Ponting; about heritage, so they turn to Aylin Orbasli and Simon Woodward; about rural tourism, so they turn to Bernard Lane; about events, so they turn to Bernadette Quinn. They read the chapter, extract a definition and a debate, and proceed — having acquired a topic but no position. A topic chapter cannot supply a disciplinary position, because it is written across disciplines. Entering through Part One and then descending to the topic is the move this companion recommends throughout, and it costs one extra afternoon at the start of a project that will take six months. The table below sets out what each part of the book is actually for, what a student should extract from it, and how each ages. Table 1. What each part of the Handbook is for, and how it should be used. Part What it contains What to take from it How it dates Introduction and Conclusion The editors on the field's formation, tensions and omissions The case for organised plurality; the vocabulary for positioning your study Ages slowly; the diagnosis still holds Part One: Approaches Twelve disciplinary accounts, one per parent tradition Your disciplinary home; questions, concepts, evidentiary standards Ages very slowly; paradigms move over decades Part Two: Key Topics Thirteen phenomenon-based reviews A baseline of what was known; a curated bibliography Ages fastest; in places a historical document Part Three: Critical Issues and Emerging Perspectives Live debates and newer paradigms Where arguments stood; theoretical vocabulary Mixed; theory holds, "emerging" has partly arrived Jennings on methodologies and methods Paradigms, design logics, method families The link between worldview and technique Ages slowly; the underlying logic is stable Reading a review, and reading a book published in 2009 A handbook chapter is a review, and a review is a map of an argument, not a source of findings. Students misuse it constantly, and the misuse shows up in marked work as a distinctive citation pattern. The value of a good review chapter is threefold. It names the positions in a debate: it tells you that there are, say, three broad ways of understanding the relationship between volunteer tourism and commodification, and it tells you what distinguishes them. It names the people who hold those positions, which converts a vague sense that "the literature is divided" into an actual argumentative landscape with actors in it. And its reference list is a curated bibliography, assembled by somebody who read the field carefully so that you do not have to read it blindly — thirty or fifty items selected by an expert who knew which ones mattered. That reference list is frequently the single most valuable thing on the page. The correct procedure follows from this. Read the chapter for the structure of the debate. Identify the positions and who holds them. Then go to the primary sources the chapter points you towards, read them, and cite those. What you must not do is cite the handbook chapter for a finding that belongs to a study it summarises. That is a second-hand citation, and examiners notice it, because it has a signature: a reference list dominated by reviews, textbooks and edited collections, with very few of the empirical papers where the claims were actually made. It signals that the student has read about the literature rather than reading it, and it invites the examiner to test whether the summarised claim survives contact with its original — which, often enough, it does not, because compression loses conditions. The date should be handled honestly rather than nervously. The Handbook was published in 2009, which is a long time ago in some respects and no time at all in others. Its treatment of information technology, in Ulrike Gretzel and Daniel Fesenmaier's chapter, predates the platform economy at anything like its current scale — it predates peer-to-peer accommodation as a normal option, the smartphone as the default interface for travel, and the algorithmic curation of destinations through social media. Misela Mavric and John Urry's chapter on the new mobilities paradigm was written before a global pandemic stopped international mobility outright and then restarted it in an altered form. Several Part Two chapters are, in places, historical documents: accurate accounts of what was known at the time, now describing a landscape that has shifted. The disciplinary and methodological chapters have aged far better, and for a reason that is worth stating explicitly: paradigms move slowly. What anthropology brings to tourism, what geography asks, what the difference is between an interpretive and a post-positivist orientation, what makes a research design coherent — these were not substantially different in 2009 and they will not be substantially different in 2035. Franklin's account of sociological questions about tourism, and Jennings's treatment of the relationship between paradigm, methodology and method, are as usable now as on publication. The working rule follows directly. Use Part One and the methodological material as current — as live intellectual equipment, not as a historical record. Use Part Two as a baseline: a statement of what was established at a known date, against which you measure what has changed. That is genuinely valuable, because a baseline lets you say something precise about movement instead of something vague about novelty. And always update a topical claim against literature from the last five years before you commit to it in a dissertation, because the examiner will know the recent literature in their own area even if they know nothing about yours. None of this is a reason to distrust the book. It is a reason to use it as what it is. The Handbook's deepest service to a student is not any fact it contains but the structural lesson its own architecture teaches: that in a field without a centre, the researcher has to supply the centre. Nobody else will. The question does not arrive with a discipline attached, the method does not follow automatically from the topic, and there is no default standard of adequacy waiting to catch a study that has not chosen one. Choosing is the work. The rest of this companion is about how to choose well, and how to borrow across the lines afterwards without losing the thread. Questions for analysis 1. Tribe's characterisation of tourism as an "indiscipline" is presented here as a permanent structural condition rather than a stage of immaturity. Construct the strongest case for the opposing view — that the field is consolidating — and then explain what evidence would be needed to settle the disagreement. 2. Explain, using a concrete example of your own devising, how a sample of twelve interviews could be simultaneously adequate and inadequate depending on the tradition assessing it. What does this imply about how you should justify sample size in your own dissertation? 3. Jamal and Robinson describe a tension between a management-school home that demands usefulness and a social-science home that demands explanation. Identify which of these pressures dominates your own institutional context, and assess what that means for the kinds of questions likely to be rewarded there. 4. The chapter argues that entering the Handbook through Part Two rather than Part One is the student's characteristic error. Take a topic you might research and describe what you would gain, specifically, by reading two Part One chapters before the relevant Part Two chapter. 5. Distinguish between a claim from the Handbook that can be used as current and one that must be treated as a 2009 baseline. Give an example of each from the book's contents, and state how you would go about updating the second. Chapter 2: Epistemology Before Method Somewhere in the opening pages of most tourism methodology chapters there is a paragraph that begins: This study adopts an interpretivist philosophy. It is normally the second or third paragraph, it runs to about 120 words, and it cites two textbooks. Turn the page and the study is an online questionnaire with twenty-four five-point items, distributed to a few hundred respondents recruited through a Facebook group, analysed by multiple regression to test whether perceived value predicts intention to revisit. Nothing in that design is interpretivist. No meaning is reconstructed, no account is produced, no participant is treated as an author of their own situation. The philosophy paragraph and the study have no contact with one another at any point. Examiners are not confused by this. They read the philosophy paragraph looking for one thing, and one thing only: whether the student can say what difference the commitment makes to what they actually did. If the commitment made no difference — if the study would have been designed identically, sampled identically, analysed identically under the opposite philosophy — then the paragraph is decoration and is marked as decoration. In a double-anonymous panel, that judgement is made in under a minute and it colours everything that follows, because a student who has written a paragraph they do not mean has told the panel that the rest of the chapter may also be recitation. The paragraph is there because a template demanded it. Undergraduate methods teaching in tourism and hospitality tends to arrive as a set of concentric layers, philosophy on the outside and data collection at the centre, and students learn to fill the layers in from the outside inwards, selecting a plausible-sounding word at each ring. This is exactly backwards from how the thing works, and it is also the reason the philosophy is never mentioned again after page 41. G.R. Jennings's chapter on methodologies and methods in the SAGE Handbook of Tourism Studies presupposes an apparatus that most students have never been taught as an apparatus — only as a vocabulary list. The purpose of what follows is to supply it in a form you can deploy, which means a form in which each commitment has a consequence you can point to. The Chain, and the Direction It Runs Four terms, in order, and the order matters. Ontology is a claim about what kinds of things exist. For research purposes the operative question is narrower and sharper than it sounds: does the phenomenon you are studying exist independently of how it is perceived? Take authenticity, a concept tourism studies has argued about since Dean MacCannell's The Tourist (1976). One ontology says authenticity is a property that a site, an object or a performance either has or lacks — a provenance, a continuity of practice, a documented lineage — and that visitors perceive this property accurately or inaccurately. A different ontology says authenticity is not in the object at all; it is a judgement made by people, produced in particular circumstances, contested between groups, and capable of being negotiated. These are not two emphases within one study. They are incompatible claims about what is there. The first licenses an instrument that measures perceived authenticity against expert-assessed authenticity and treats the gap as error. The second makes that gap the phenomenon. Epistemology is a claim about what can be known of those things, and about the relationship in which the knower stands to them. If reality is mind-independent, the researcher's task is to observe it without contaminating it, and every design decision is a bias-control decision: randomisation, blinding, standardised instruments, pre-registered hypotheses. If the phenomenon is constituted in the meanings people give it, the researcher cannot stand outside it, because the interview in which the meaning is articulated is itself an occasion of meaning-making. The researcher becomes part of the apparatus rather than a threat to it. That is not a softer position; it is a different one, and it carries obligations of its own. Methodology is the logic by which a study of that kind can produce warranted conclusions. It is not a list of procedures, and the most common structural failure in a tourism dissertation is a chapter headed "Methodology" that contains only methods. Methodology answers the question: given what I have claimed exists and what I have claimed can be known about it, why would anyone accept the conclusion I reach? Sampling logic belongs here. So does the criterion of adequacy — the standard the study asks to be judged against, whether that is statistical inference beyond the sample, or credibility of an account, or the exposure of a mechanism. Methods are the techniques: the survey, the semi-structured interview, the participant observation, the content analysis of destination marketing material, the secondary arrivals dataset, the experiment. The chain is one of entailment, and it runs in one direction only. Your ontology constrains your methods. Your methods do not license an ontology. A semi-structured interview is not interpretivist; it is a technique for getting people to talk. Interviews are used positivistically all the time — to elicit reports about facts held to exist independently of the telling, coded into categories, counted, and compared across groups for association. Surveys can in principle be used to reconstruct meaning, though it is rarely done well. The method is not a badge. Writing "I used interviews, therefore my study is qualitative and interpretivist" is a non-sequitur that panels spot instantly, because it reasons up the chain instead of down it. The commonest error follows directly. A student settles on a method first, usually for good practical reasons — a survey is deliverable in eight weeks, interviews require access the student does not have — and then reverse-engineers a philosophy to justify it, finding the method listed under a paradigm in a textbook table and copying the paradigm across. The tell is a contradiction between the philosophy paragraph and the sampling paragraph. The second tell is that the philosophy, once declared, never does any work again. The remedy is not to declare a paradigm more carefully. It is to notice that a research question already has an ontology built into it, whether or not the student put it there. What factors influence repeat visitation to the Lake District? presupposes factors that exist, act with some stability, and can be separated from one another. How do residents of a heritage town understand the presence of visitors in their streets? presupposes meanings that are held, articulated and contested. You do not choose a paradigm the way you choose a title. You establish which one your question already belongs to, and then decide whether you are willing to live with the obligations — or change the question. Four Paradigms and What Each Treats as an Answer The scheme below follows the framework associated with Egon Guba and Yvonna Lincoln, whose Naturalistic Inquiry (1985) and subsequent paradigm work remain the standard reference point for it. Their move was to interrogate each position with the same three questions — what is the nature of reality, what is the relationship of knower to known, how is knowledge produced — so that the positions could be compared rather than merely listed. Table 2 sets out the four in that form, with the column that students most often omit: what each tradition would accept as a good finding. Table 2. Four research paradigms and what each treats as a good finding. Paradigm View of reality Relationship of researcher to subject What counts as a good finding Typical tourism study Positivism / post-positivism Single reality, mind-independent; knowable imperfectly Detached; bias to be controlled A relationship that holds beyond the sample International demand model; satisfaction–loyalty testing Interpretivism / constructivism Realities constituted by actors' meanings; multiple Co-producer of the account A defensible account of how participants understand their situation Residents' construction of visitors in a heritage town Critical theory Reality shaped by sedimented structures of power Positioned; research is intervention Exposure of a domination the standard account naturalises Post-colonial reading of host–guest relations; gendered hospitality labour Pragmatism Reality as encountered in consequences for action Instrumental; guided by the purpose An answer adequate to the stated question Mixed-design destination evaluation for a policy client Positivism and post-positivism hold that there is a reality out there that does not depend on the observer, and that it can be approached by hypothesis, measurement and the accumulation of tested relationships. Post-positivism is the more defensible modern version: it concedes that observation is theory-laden and that knowledge is fallible, so that a finding is never proved, only corroborated and held provisionally against attempts to falsify it. What makes a finding good here is that the relationship holds beyond the cases you happened to observe. Everything in the design follows from that: probability sampling, adequate statistical power, effect sizes, control variables, replication. Tourism does this seriously in economics — the demand modelling territory of John Fletcher's Handbook chapter, where arrivals are estimated against income, price and exchange rates — and in consumer-behaviour work on satisfaction, perceived value and loyalty. Such studies are rarely marked down for their paradigm. They are marked down for failing their own standard: a convenience sample of a hundred or so fellow students, no power calculation, and a discussion section that generalises to "tourists" without qualification. Interpretivism and constructivism hold that social reality is constituted by the meanings actors give it, and that those meanings are plural, situated and produced in interaction — including interaction with the researcher. A good finding is a defensible account of how participants understand their situation. It is not a generalisation, and claiming one is the fastest way to fail an otherwise decent qualitative study. Guba and Lincoln's alternative criteria — credibility, transferability, dependability, confirmability — exist precisely because validity and reliability are the wrong instruments for this kind of claim. Consider a study of how residents of a small heritage town construct their relationship to visitors. A strong interpretive finding might be that residents hold two incompatible positions at once — visitors as economic lifeline, visitors as intrusion into a place that used to be theirs — and move between them depending on who is asking and in whose hearing. Under positivism that pattern is measurement error to be minimised by a better-worded item. Under interpretivism it is the result. Critical theory holds that what presents itself as natural is in fact the sediment of history and power: capital, colonial relations, gender, race, class. Knowledge is never neutral; research either reproduces the arrangement or unsettles it. A good finding exposes a relation of domination that the conventional account makes invisible by treating it as the way things are. Post-colonial readings of host–guest relations, in the vein of Hazel Tucker and John Akama's Handbook chapter, do this to the vocabulary itself: "hospitality" implies a welcome freely extended, which obscures a relation structured by vast asymmetries of wealth, mobility and the power to represent — asymmetries whose representational machinery Edward Said's Orientalism (1978) traced. Cara Aitchison's work on gender and tourism discourses turns the same instrument on hospitality labour, where "service" names emotional work disproportionately extracted from women and from migrant staff, and where the industry's own language of warmth and care performs the concealment. The examiner's objection to weak critical work is always the same: the student asserts domination rather than demonstrating it. The structure has to be shown operating in the material you collected. Pragmatism holds that the value of a knowledge claim lies in its consequences for a stated purpose, that the question is prior to the paradigm, and that a design combining numbers and accounts needs no philosophical reconciliation because the question licenses it. Two honest observations follow. First, pragmatism is the position most students should probably declare, because most dissertations genuinely ask a question with two halves — how widespread is this, and how do the people involved account for it — and because most are written for a purpose that can be stated: to inform a destination management organisation, to evaluate a scheme, to establish whether a problem exists before theorising it. Second, it is the position students are most often discouraged from declaring, and the discouragement is not unreasonable. Supervisors read "pragmatism" as a way of not choosing, because that is very often what it is. The declaration only works if it is argued: you must state the purpose specifically enough that it can adjudicate a design decision. "To understand tourism in Bath" cannot settle anything. "To establish whether the residents' parking scheme has reduced complaints, and to identify what complainants believe it has failed to address, for a council deciding whether to extend it" can settle a great deal — it tells you the sample frame, the timeframe, and what would count as enough evidence. If you cannot write that sentence, pragmatism is not available to you. How Far Incommensurability Goes There is a strong claim and a weak claim, and the difference matters for what you are allowed to write. The strong claim is that paradigms cannot be combined at all, because their criteria of adequacy contradict one another. If a good finding under post-positivism is one that holds beyond the sample, and under constructivism generalisation is not an aim at all, then there is no neutral vantage point from which to judge a study that tries to do both. Arguments of this kind were pressed hard during the paradigm wars of the 1980s and 1990s, and they are not silly. The weak claim is that paradigms can be combined at the level of method, provided the study is explicit about which question each component answers and does not import the criteria of one component to judge the other. This is the workable position for a dissertation, and it is defensible — but only if you write the three things that defend it, and almost nobody does. First, state what each component contributes, in terms of a question rather than a virtue. "Triangulation" is not a contribution; it is a word students use to avoid specifying one. Write instead: the survey establishes how attitudes to the scheme are distributed across the resident population; the interviews establish the terms in which opponents account for their opposition, which the survey cannot recover because the categories were written by me. Second, state which component is prior. One frames the study and the other serves it. If the interviews generate the constructs the survey then measures, say so and design accordingly; if the survey identifies the divergent group the interviews then explore, say that instead. A study in which both components are simply present, with neither subordinate, has no logic — only two datasets in the same binding. Third — and this is the mark of a serious student — state in advance how a conflict between the components would be resolved. Suppose the survey shows resident attitudes to visitors are on balance favourable, and the interviews are dominated by resentment. You cannot average them. You cannot quietly report whichever result is more interesting. What you can do, and should have written before collecting anything, is specify what you would take a divergence to mean: that the instrument reaches a public register in which residents give the economically responsible answer, while the interview reaches a private one; or that the interview sample over-represents the aggrieved because the aggrieved volunteer. Either reading turns the divergence into a finding rather than an embarrassment. Two sentences, written early, convert the most dangerous outcome in a mixed design into its most interesting one. The sin is never mixing as such. The sin is mixing and then applying the wrong criterion — judging six interviews by whether they are representative, or complaining that a survey lacks richness. Reflexivity as an Argument About Evidence In interpretive and critical work the researcher is an instrument, and this is where tourism dissertations are weakest. If you are the instrument, then the properties of the instrument are evidence about the data, and an examiner is entitled to a specification: who you are in relation to the field, what access you had and how you obtained it, what you were structurally unable to see, and how your presence shaped what participants said. This has to be distinguished sharply from confession. A reflexivity section that opens "As a passionate traveller I have always been fascinated by other cultures" is autobiography; it has no evidentiary consequence and it wastes 300 words the examiner will not credit. The test for every sentence is whether it changes how the reader should weigh a piece of data. Compare. A student conducts interviews in a village where the first language is not English, in English, because that is the language she has. The residents willing to be interviewed are disproportionately those with tourism-facing jobs, since those are the residents whose work has required them to learn English. Her sample therefore over-represents people with a direct economic stake in visitor numbers, and the two shopkeepers who declined told her they had nothing good to say — which means the refusals are systematic rather than random, and the absence tilts the findings in a known direction. Every clause there is a claim about evidence. Or: a student obtains access to hotel staff because his uncle manages the property. The staff know this. Complaints about management are therefore unlikely to be voiced, and the striking uniformity of positive comments about supervision should be read as an artefact of access rather than as a finding about morale. Saying so is not an admission of weakness; it is the analysis. Quantitative work does not require reflexivity in this sense, since the instrument is not the person. It requires the same discipline in a different register: who the sampling frame excluded, who chose not to respond and whether their non-response is likely correlated with the outcome, what the instrument's categories made it impossible for a respondent to say. What all of this buys is a methodology chapter in which every subsequent choice has a stated reason — where the sample size is justified by the criterion of adequacy rather than by what was achievable, where the coding scheme follows from the kind of claim being made, where the decision to quote a participant at length is defensible rather than decorative. That is not a presentational refinement. It is the difference between a competent dissertation and a distinguished one, and it is also the point at which the paradigm question rejoins the question of disciplinary home, because the traditions that claim tourism do not merely prefer different methods. An anthropologist and an economist disagree about what tourism is before they disagree about how to study it. Choosing where your question lives is choosing an ontology, whether or not you notice the choice being made. Questions for analysis 1. Take a research question you are considering and write out the ontological commitment it already contains — what it presupposes exists and whether that thing is independent of how it is perceived. Would you defend that commitment, or does the question need rewriting? 2. The chapter argues that entailment runs from ontology to methods and never the reverse. Construct a case in which the same technique — the semi-structured interview — serves a post-positivist study and an interpretivist one, and specify exactly where the two designs diverge. 3. Using Table 2, explain why a pattern of contradictory resident attitudes would be treated as measurement error under one paradigm and as the central finding under another. Which treatment would your own project require? 4. Pragmatism is described as the paradigm most students should declare and are most often discouraged from declaring. Write the one-sentence statement of purpose that would make a pragmatist declaration defensible in your study, and assess whether it is specific enough to settle a real design decision. 5. Draft three sentences of reflexivity for a project of your own, applying the chapter's test: each sentence must change how a reader should weigh a particular piece of your evidence. Then identify what you removed as autobiography. Chapter 3: The Anthropological and Sociological Claim At nine in the morning in an airport departure lounge, people who would not dream of drinking before lunch on a Tuesday order a beer, and nobody at the table finds it strange. On the second evening of a package holiday, strangers who would not have exchanged a word on their own street exchange life histories and then never speak again. A man who has never taken a photograph of his own high street photographs a fishmonger in another country at close range without asking. None of this is unusual and none of it is explicable by the framework that dominated the first serious writing about tourism, which asked whether the industry brought more money than damage to the places it touched. That question is answerable — in principle, with enough data — but it cannot account for the beer, the confidences or the photograph, because it treats the tourist as an economic input and the destination as a site of impact. The founding achievement of the anthropology and sociology of tourism was to stop asking whether tourism was good for host societies and to start asking what kind of social form it is. That change of question is the origin of almost every theoretical tool the field now uses, and a student who understands why the change was productive is in a far better position than one who has simply memorised the names attached to it. The founding move Two books published within a year of each other set the terms. Valene Smith's edited collection Hosts and Guests (1977) did the more obvious work: it put the encounter between visitor and visited at the centre of analysis and gave the field a unit it could actually study. Not the sector, not the flow, not the balance of payments, but the meeting — what happens between a person who has come to look and a person who lives there, and what each makes of the other. Naming the parties as hosts and guests was not a decorative choice. It imported a whole vocabulary of obligation, welcome, intrusion and reciprocity from the anthropology of exchange, and it implied that the tourist encounter belongs to a family of relationships that anthropologists already knew how to describe. The collection's enduring effect was to make the ethnography of a single destination a legitimate contribution to knowledge rather than a case study awaiting aggregation. Nelson Graburn's "Tourism: The Sacred Journey" (1977) made the stronger and stranger claim. Tourism, on this account, is structurally a ritual. It is a temporary passage out of ordinary time, marked at both ends by thresholds that participants recognise — the packing, the airport, the arrival, the return — and governed internally by inversion. What is forbidden or merely unusual at home becomes expected away: idleness for the industrious, extravagance for the careful, sociability for the reserved, sun-worship for the office-bound, and in some settings sexual licence for the otherwise respectable. Graburn was drawing on Victor Turner's work on liminality, the middle phase of a rite of passage in which ordinary status distinctions are suspended and participants exist briefly outside the structures that usually govern them. The annual holiday, in this reading, is not leisure appended to a working life but the sacred alternating with the profane, the modern secular society's remaining mechanism for marking time and renewing the self. The reframing was productive for two reasons worth separating. The first is that it converted a policy question into a theoretical one. "Is tourism good for this village?" is a question whose answer depends entirely on who is asked and over what period, and which produces a literature of cases that do not accumulate. "What kind of social form is this, and what does it do for the people who participate in it?" is a question that generates propositions testable against other cases, in other places, in other periods — and which can be wrong. The second reason is simply that the ritual framing explained behaviour the policy framing could not. If tourism is liminal, then the beer at nine in the morning is not a lapse of judgement but a correct reading of the situation by a competent social actor: the ordinary rule has been suspended and everyone present knows it. The confidences between strangers are the communitas Turner described, an intense and temporary levelling that dissolves on re-entry. This is what a good theory does. It takes behaviour that looked like noise — trivial, embarrassing, the stuff of holiday anecdote — and shows it to be patterned, rule-governed and evidence of something. What the anthropology demands in return Naomi Leite and Nelson Graburn's chapter in the Handbook makes an argument about disciplinary contribution that a student should read carefully, because it is not the argument one expects. Anthropology's gift to tourism studies has been less a body of findings than a set of interventions — persistent, awkward corrections to the way the field frames its objects. Three of these matter most. The first is the insistence on long-term fieldwork. Anthropology's claim to authority rests on duration: on having been present long enough that people stop performing for the researcher, that the seasonal rhythm becomes visible, that the difference between what is said in an interview and what is done in the street can be observed rather than inferred. The second is the insistence on the host's account. Tourism generates an enormous literature about tourists, produced largely by researchers who resemble tourists, sampling people who are conveniently available because they have come to a place voluntarily and have time. The people who live there are harder to reach, less inclined to be interviewed, and more likely to have views that complicate the study. Anthropology's repeated intervention has been to point out that half the encounter is routinely missing. The third is the refusal of the tourist/traveller distinction as an analytic category. Every tourist believes themselves to be a traveller and other tourists to be tourists; this is a fact about how people position themselves socially, and as such it is excellent data. It is not, however, a classification the analyst may adopt, because to adopt it is to take one participant's status claim and quietly convert it into a scholarly finding. The methodological implication is the part a student actually needs, and it is uncomfortable. The anthropological contribution comes with a method attached. Liminality, communitas, the ritual reading of the holiday — these concepts were produced by long immersion and they presuppose the kind of evidence that only immersion generates. A dissertation that announces a liminality framework and then rests on eight semi-structured interviews conducted over a fortnight has borrowed the vocabulary without the epistemology. It will typically produce the concept as a label rather than a finding: respondents said they felt free, therefore liminality. The concept was designed to explain a structure that participants cannot fully articulate, which is precisely why asking them does not establish it. This is not an argument against small interview-based studies, which can be excellent. It is an argument for knowing which claims your evidence licenses, and for not reaching for a concept whose warrant you have not earned. The other founding text belongs to sociology but the argument it started has been fought largely on anthropological ground. Dean MacCannell's The Tourist (1976) proposed that the tourist is a modern pilgrim, travelling in search of an authenticity and a wholeness absent from a fragmented modern life, and that the tourism industry's core operation is the management of that search. What tourists are shown is arranged for showing: a front region dressed to look like a back region, a kitchen with a viewing window, a ceremony performed at the hour the coaches arrive. MacCannell called this staged authenticity, and the sharp edge of the argument is that the staging is not a betrayal of the tourist but a structural necessity, because the genuine back region ceases to be one the moment it is entered. The tourist's quest is therefore both sincere and systematically frustrated, and the industry exists to manage the frustration. Erik Cohen's typologies (1979) did the essential next thing: they broke the singular "tourist" apart. If MacCannell's tourist is a figure — a single modern subject with a single existential predicament — Cohen's contribution was to distinguish modes of touristic experience, from the recreational visitor who wants restoration and is entirely satisfied by a comfortable fiction, through the diversionary and the experiential, to the experimental and existential traveller for whom the encounter with another way of living carries the weight MacCannell described. The point of the typology is not the labels. It is that the question of what tourists seek stopped being a philosophical claim about modernity and became an empirical question about which people, in which settings, seek what — a question a researcher can actually investigate and lose an argument about. The authenticity debate matters methodologically for a reason that trips up more undergraduate work than any other single confusion. Authenticity is a participant category and an analyst category at the same time. When a visitor says the village felt authentic, they are performing an evaluation that is itself the object of study: it tells you about their expectations, their reference points, their reading of cues, their need to have had a real experience rather than a packaged one. When a researcher writes that the village is authentic, they are making a claim of an entirely different kind, and usually one they have no basis for and no criteria to defend. The two uses look identical on the page. A study that slides between them ends up asserting, on the strength of interview data, that a heritage site is or is not genuine — which is not a finding about the site but an unexamined judgement dressed as one. The disciplined move is to bracket the question of what is really authentic and study instead how authenticity is claimed, conferred, doubted and sold: who gets to certify it, what evidence is offered, what is at stake for whom when the certification is granted or withheld. From the tourist to the ordering of modern life Adrian Franklin's chapter on the sociology of tourism reports a turn that ran in parallel and reached a different destination. Early sociology of tourism was a sociology of the tourist: motivations, typologies, satisfaction, the social psychology of the holiday. The turn Franklin describes is towards a sociology of tourism as an ordering of modern life — not a behaviour that some people perform in some weeks of the year, but a set of arrangements, expectations and infrastructures through which contemporary societies organise mobility, leisure, looking and the consumption of place. On this account tourism is not a minor sector to be explained by reference to society; it is one of the things through which the society is constituted. John Urry's The Tourist Gaze (1990) is the pivot. The argument is deceptively simple: what tourists see is not what happens to be in front of them but what they have been taught to see. The gaze is organised — by photographs circulated before the trip, by guidebooks that mark some views as worth the detour, by the positioning of viewing platforms and the framing of windows, by the professional labour of designers and marketers, and by the whole prior visual culture the visitor carries. It is taught, in that people learn what a beautiful coastline or an interesting street looks like. And it is reproduced, because visitors photograph what they were shown and their photographs become the material that teaches the next cohort. The consequence for research is substantial: looking is a social practice, not an individual act, and it can therefore be studied through the objects that organise it — the brochure, the sign, the itinerary, the viewing point — rather than only through what individuals report about their experience. Urry and Larsen's third edition, The Tourist Gaze 3.0 (2011), revises the argument in two directions that matter for anyone writing now. It brings in digital mediation, which has changed both the pre-formation of expectation and the afterlife of the image: the visitor arrives having already seen the view many times on screens, and departs to circulate their own version into the same flow. And it takes seriously the performance of looking — that tourists are not disembodied eyes but bodies doing things, posing, arranging each other in front of monuments, performing the act of having been somewhere for an audience that is often not present. The gaze becomes something people do together, with equipment, for others. David Crouch's chapter on cultural studies and David Bell's on hospitality are best read together, as two versions of the same expansion of the object. Cultural studies brought embodiment, practice and the everyday into a field that had been dominated by structure and encounter. Against a literature of gazes and hosts and guests, it insists on the mundane texture of being somewhere: the feel of unfamiliar ground underfoot, the improvisation of a day that was planned differently, the small creative work through which people make a place their own rather than simply receiving it as arranged. This is a corrective to a tendency in both founding traditions to make the tourist either a dupe of staging or a bearer of structure, and never someone doing something. Bell's hospitality chapter makes a different and, for research design, a sharper move. Hospitality is not a business category with a social flavour; it is a social relation with a long pre-commercial history, an ancient set of obligations governing what is owed to a stranger who arrives at the door. That relation was mutual and morally weighted: the host was bound to shelter and feed, the guest was bound to accept the terms of the house, and the obligation ran in both directions and into the future. Reading commercial hospitality against that history is analytically productive precisely because of what the comparison reveals to be missing. Obligation has become contract. Reciprocity has become transaction, discharged and closed at checkout. The host's duty to the stranger has become a service standard, enforceable as a rating rather than as a moral claim, and the stranger has become a customer whose entitlements end where the payment does. Nothing in that account requires nostalgia. It supplies something more useful: a baseline against which the commercial form can be described as a specific historical arrangement rather than as the natural shape of welcome. The methodological inheritance What this tradition actually hands a student is a toolkit with a temperament. Participant observation, in which the researcher is present in the setting over time and the record is the fieldnote. Ethnographic interviewing, which is not a scheduled encounter with a list of questions but a conversation embedded in a relationship, returned to repeatedly as understanding changes. The extended case method, which takes a single situation and works outwards from it to the structures and histories that shape it, rather than treating it as one observation among many. And the analysis of narrative and representation — what brochures, itineraries, signage, guiding scripts and visitors' own accounts do, and what they take for granted. All of this implies small samples, long engagement and thick description. A student writing in this tradition must be prepared to defend depth against an examiner trained in generalisation, and will almost certainly have to: the question "how can you generalise from six people?" arrives in most vivas. The defence that fails is the one most students give, which is to argue that the sample is larger or more representative than it looks. That concedes the criterion and then loses on it. The defence that works is that generalisation was never the objective. The objective is the identification of a mechanism or a meaning-structure — how staging is accomplished and by whom, how a claim to authenticity is made and contested, what obligations survive in a commercial welcome — which can then be looked for elsewhere. The claim is not that this village is typical. The claim is that this process exists and works in this way, and that the next researcher now knows what to look for. A mechanism identified in one setting and absent in the next is not a failed generalisation; it is a finding about the conditions under which the mechanism operates. There is a live weakness in this tradition that a good dissertation can exploit, and it is not hidden. The anthropology and sociology of tourism have been much stronger on the tourist and the encounter than on the industry, and much stronger on meaning than on money. There is a large ethnographic literature on what visitors experience and a small one on how the firms, agencies and public bodies that arrange those experiences actually work. The rooms where destinations are decided are under-observed: the marketing office where a place is reduced to three images and a strapline, the concession negotiation in which access to a site is priced and allocated, the licensing hearing at which a community's objections are heard and disposed of, the internal meeting where the authenticity that will later be sold is specified as a deliverable. These are settings that yield to exactly the methods this tradition has perfected — sustained presence, attention to the gap between the stated and the done, the documentary trail read as representation. A study that takes an ethnographic method to a commercial or institutional setting is doing something the field has under-done, and that is a genuine contribution claim rather than a decorative one. It is also, usefully, the point at which the two founding questions rejoin: to watch the industry make a destination is to watch the encounter being manufactured in advance, which is the one thing the literature on the encounter has mostly had to take as given. Questions for analysis 1. Graburn's ritual reading explains behaviour the impact literature could not. Identify a tourist behaviour in a setting you know well that the policy framing would treat as an anomaly, and show what the liminality framing makes of it. Where does the ritual explanation run out? 2. A dissertation proposes to use liminality as its theoretical framework and to collect data through ten online interviews with returned travellers. State the mismatch precisely, then redesign the study so that either the concept or the method changes to fit the other. 3. MacCannell treats staged authenticity as structurally necessary rather than as deception. What follows for the ethics of destination marketing if he is right, and what would have to be true for the deception reading to be the better one? 4. Distinguish authenticity as a participant category from authenticity as an analyst category, using an example. Write the research question you would actually investigate in each case, and explain why only one of them is answerable. 5. Bell reads commercial hospitality against its pre-commercial history and finds obligation, reciprocity and duty to the stranger removed. Choose a contemporary hospitality setting and test the claim: what traces of the older relation survive there, and what work do they do for the business? Hashtags: #TheResearchCompass #TourismStudies #SAGEHandbookOfTourismStudies #TourismResearch #ResearchDesign #DisciplinaryPlurality #TourismIndiscipline #ResearchParadigms #Ontology #Epistemology #Methodology #ResearchMethods #StandardsOfAdequacy #Positivism #Interpretivism #CriticalTheory #Pragmatism #MixedMethodsResearch #ResearchAlignment #QualitativeResearch #QuantitativeResearch #TourismEthnography #Reflexivity #TheoreticalFrameworks #FutureOfTourismResearch

Download the Book (PDF): Introduction In the autumn of 1936 the Literary Digest, then one of the most widely read magazines in the United States, mailed roughly ten million straw-poll ballots to Americans whose names it had gathered from its own subscriber lists, telephone directories, and automobile registrations. Something over two million came back. On the strength of that enormous return the magazine predicted that Alf Landon would defeat Franklin Roosevelt comfortably. Roosevelt won forty-six of the forty-eight states and about sixty-one percent of the popular vote. The Digest never recovered its reputation and ceased publication within two years. The story is usually told as a lesson about sampling frames: in the depths of the Depression, people who owned telephones and cars were richer than the electorate as a whole, and richer voters leaned Republican. That explanation is part of the truth. But when the political scientist Peverill Squire re-examined the episode using a Gallup survey conducted in 1937, he found that the frame alone would not have produced so large an error. The larger problem was who chose to send the ballot back. Landon supporters, motivated by opposition to the incumbent, returned their ballots at higher rates than Roosevelt supporters on the same lists. The Digest suffered at least two distinct failures at once — a frame that did not cover the population and a response process that selected on the very thing being measured — and more than two million returned ballots could not compensate for either. That same year a young market researcher named George Gallup predicted Roosevelt's victory with a sample that was a small fraction of the size of the Digest's. His method, quota sampling, was not a probability design, and it would fail in its turn in 1948 when every major poll called the presidential race for Thomas Dewey. The pattern that runs through these episodes — large numbers failing where smaller, better-designed efforts succeed, and methods that work for a while and then break without warning — is the subject of this book. The argument The controlling idea of what follows can be put in one sentence. A survey estimate is the end of a long chain of decisions, from defining the population to adjusting the final weights, and its accuracy is governed by the sum of the errors introduced at every link, not by the size of the sample or the sophistication of any single step. The discipline that organises this idea is called Total Survey Error, and it is the frame for everything that follows. Three consequences follow from taking that idea seriously, and together they form the spine of the book. The first is that errors come in two families that must be managed together. Some errors concern who is measured: whether the list from which people are drawn includes everyone it should, whether chance in the selection process produces an unlucky sample, whether the people who respond differ from those who do not, and whether the adjustments made afterwards correct or compound those differences. Others concern what is measured: whether a question captures the concept the researcher had in mind, whether respondents understand it, recall the relevant facts, and report them honestly, and whether the answers are recorded and coded without distortion. A survey can have a flawless sample and useless questions, or perfect questions asked of the wrong people. Neither half compensates for the other. The second is that probability sampling remains the anchor of the field, not out of tradition but because it is the only design in which the relationship between the sample and the population is established by the researcher rather than assumed. When every member of the population has a known, non-zero chance of selection, the uncertainty in the resulting estimates can be calculated from the design itself. Every other approach — quota samples, opt-in online panels, river samples, social media data — must replace that design-based guarantee with a model of how the people who ended up in the data relate to those who did not. Such models can work well. They can also fail silently, and the failure is invisible from inside the data. Knowing which situation one is in is a matter of methodology, not statistics alone. The third is that the tools used to repair a survey after the fact, above all weighting, are only as good as the assumptions they rest on. Post-stratification, raking, and calibration can remove bias that is explained by the variables used in the adjustment. They cannot remove bias that is not, and they always cost precision. In an era of single-digit response rates, almost every published survey estimate is a heavily weighted one, which makes an understanding of what weighting does and does not do essential for anyone who produces or relies on survey data. What the book covers and what it leaves out The chapters move roughly in the order in which a survey is designed and carried out, though the argument doubles back where it must. Chapter 1 sets out the Total Survey Error framework and the vocabulary of bias, variance, and mean squared error that the rest of the book uses. Chapter 2 concerns populations and sampling frames: what it means to define the group one wants to describe, and how the lists and maps used to reach that group systematically fall short. Chapter 3 explains probability sampling — stratification, clustering, unequal probabilities, and the design effect — at the level needed to read a methods report critically and to plan a sample sensibly. Chapter 4 turns to non-probability sampling, the reasons for its rapid growth, the evidence on its accuracy, and the conditions under which its inferences can and cannot be trusted. The next three chapters move from representation to measurement. Chapter 5 describes what psychologists have learned about how respondents actually answer questions: the stages of comprehension, retrieval, judgement, and reporting, and the shortcuts people take when a questionnaire asks more of them than they are willing to give. Chapter 6 applies that understanding to the writing of questions and response scales. Chapter 7 covers pretesting, with particular attention to cognitive interviewing, the technique that transformed questionnaire design from a craft practised on intuition into one that can be tested. The last two chapters return to representation after the data have been collected. Chapter 8 deals with nonresponse — why response rates have collapsed, why low response rates do not automatically mean biased estimates, and what the evidence says about when they do. Chapter 9 explains weighting in detail, from base weights through nonresponse adjustments to post-stratification, raking, and calibration, and it is honest about the limits of each. The conclusion draws these threads together into a way of thinking about survey quality as a budget that must be spent deliberately across all sources of error rather than concentrated on the most visible one. The book concentrates on surveys of households and individuals intended to describe a defined population: government statistical surveys, social and health surveys, and the better class of opinion polls. It says less about establishment surveys of businesses and institutions, which share the same logic but face distinctive problems of their own, and it does not attempt to teach the full mathematics of complex sample variance estimation, for which excellent textbooks exist. Nor does it pretend to settle the arguments over non-probability data that are still very much alive; it tries instead to give the reader the means to judge a particular claim on its merits. Who this is for The intended reader is someone who needs to design, commission, evaluate, or use survey data and wants to understand why the field's practices are what they are. That includes researchers in the social and health sciences, analysts in government and industry who inherit survey data from others, journalists who report polls, and students who have learned the formulas of sampling theory without seeing how they connect to the practical decisions of fieldwork. The mathematics is kept to the level of simple algebra and is always explained in words. Where a formula appears, it is because it makes a practical point more clearly than prose could, and the point is always stated in plain language alongside it. A survey is, at bottom, a promise: that the numbers it produces say something true about people who were never asked. The rest of this book is about the conditions under which that promise can be kept. Chapter 1: The Total Survey Error Framework Every survey report contains a number that purports to describe its uncertainty. It usually appears as a margin of error — "plus or minus three percentage points" — and it is usually the only statement of quality the reader receives. That number is almost always the smallest part of the truth. It describes one source of error, the variability that arises because a random sample was drawn rather than the whole population, and it assumes that everything else in the survey went perfectly. In practice nothing else goes perfectly. The frame misses people, many of those sampled never respond, questions are misunderstood, answers are shaded toward what seems acceptable, and the weights applied at the end fix some problems while introducing others. The Total Survey Error framework exists to make all of that visible. It is less a single theory than an organising discipline: a way of listing every mechanism by which a survey estimate can depart from the true value it is meant to capture, and of thinking about how those mechanisms trade off against one another and against cost. This chapter sets out the framework and the handful of statistical ideas it rests on. A short history of an idea The recognition that sampling error is only part of the story is almost as old as modern sampling itself. In 1944 W. Edwards Deming, then working at the US Bureau of the Census, published a paper in the American Sociological Review titled "On Errors in Surveys." It listed thirteen factors affecting the usefulness of a survey, among them variability in response, bias arising from the interviewer, differences between the survey's definitions and the concept the user actually cared about, errors in processing, and the bias of the auxiliary data used in estimation. Sampling error was one item on the list. Over the following decades the statisticians who built the great government surveys — Morris Hansen, William Hurwitz, and their colleagues at the Census Bureau, and Leslie Kish at the University of Michigan — developed formal models for some of these errors, particularly for the variability introduced by interviewers and by respondents who would give different answers on different occasions. Kish's 1965 textbook Survey Sampling, still in print and still cited, distinguished carefully between variable errors and biases and between errors of observation and errors of non-observation. The phrase "total survey error" and its modern shape owe most to Robert Groves, whose 1989 book Survey Errors and Survey Costs brought the statistical tradition of the samplers together with the psychological and sociological traditions of the question designers, and argued that every design decision is a trade between error and cost. The version most widely taught today appears in the textbook Survey Methodology by Groves and five co-authors, first published in 2004 and revised in 2009. In 2010 a special issue of Public Opinion Quarterly marked the framework's maturity, with a historical review by Groves and Lars Lyberg and an account of its practical application by Paul Biemer. Two families of error The framework's central device is a diagram of the survey lifecycle, usually drawn as two parallel columns that converge on a single estimate. This book describes it in words. One column follows the path from a construct — the abstract thing the researcher wishes to know about, such as household food insecurity, trust in government, or the frequency of doctor visits — to a measurement, the specific question or set of questions used to capture it; then to a response, the answer a particular person gives; then to an edited response, the value that survives coding, cleaning, and consistency checks. At each step something can be lost. The gap between construct and measurement is an error of validity: the questions measure something, but not quite the thing intended. The gap between measurement and response is measurement error: the respondent misunderstands, forgets, estimates badly, or misreports. The gap between response and edited response is processing error: a keying mistake, a miscoded occupation, an editing rule that overrides a true but unusual answer. The other column follows the path from the target population — the people the researcher wishes to describe — to the sampling frame, the list or procedure through which they can be reached; then to the sample actually drawn from that frame; then to the respondents, the subset of the sample who provide data; and finally to the post-survey adjustments, the weights and imputations that attempt to repair the differences that have crept in. The gap between target population and frame is coverage error. The gap between frame and sample is sampling error. The gap between sample and respondents is nonresponse error. And the adjustments themselves can introduce adjustment error if they rest on the wrong assumptions. The first column is about measurement; the second is about representation. The survey statistic is produced where they meet: edited responses from the set of adjusted respondents are combined into a mean, a proportion, a total, or a regression coefficient. Table 1 summarises the seven components and the questions each raises. Table 1. Components of Total Survey Error. Component Family Gap it describes Typical question Validity Measurement Construct to question Does the question measure the concept intended? Measurement error Measurement Question to answer Do respondents understand, recall, and report accurately? Processing error Measurement Answer to data Are answers coded, keyed, and edited correctly? Coverage error Representation Population to frame Who cannot be reached through the frame at all? Sampling error Representation Frame to sample How much could results vary across possible samples? Nonresponse error Representation Sample to respondents Do those who respond differ from those who do not? Adjustment error Representation Respondents to weighted estimate Do weights correct the differences or add new ones? Two features of the list deserve emphasis. First, it is ordered in time, and errors propagate forward: a coverage gap cannot be fixed by drawing a larger sample from the same deficient frame, and a badly worded question cannot be rescued by excellent response rates. Second, the components interact. Nonresponse is often concentrated among the same groups who are poorly covered by the frame. Mode of data collection — face to face, telephone, web, paper — affects both who responds and how they answer. Interviewers who work hard to persuade reluctant respondents may also, through their manner, influence the answers they get. A design decision made to reduce one component almost always affects another. Bias and variance The framework uses a vocabulary borrowed from statistical estimation, and it is worth being precise about it. Imagine that a survey could be repeated many times under identical essential conditions: the same design, the same frame, the same questions, the same field procedures, but a new random sample each time, new draws of which interviewer is assigned to which case, and new realisations of each respondent's momentary state of mind. Each repetition would produce a slightly different estimate. The spread of those estimates around their own average is the variance of the survey procedure. The distance between that average and the true population value is its bias. Sampling error is the textbook example of variance: different random samples give different answers, but on average they are right. Interviewer effects are another source of variance: if one interviewer tends to elicit more reports of symptoms than another, and interviewers are assigned at random, the estimate will wobble depending on which interviewers happened to handle which cases. Response variability — the fact that a person asked the same question twice may give two different answers — is a third. Bias, by contrast, does not average away. If the frame systematically excludes people without fixed addresses, and those people are more likely to be food insecure, every repetition of the survey will underestimate food insecurity by roughly the same amount. If respondents systematically under-report alcohol consumption, a larger sample simply produces a more precise estimate of the wrong number. If people who agree to take part in a survey about civic life are more civically engaged than those who refuse, estimates of volunteering will be too high no matter how the sample is drawn. The two are combined in a single measure of overall accuracy, the mean squared error, which is the variance plus the square of the bias. The squared term matters: it means that bias grows in importance relative to variance as samples get larger, because variance shrinks with sample size while bias does not. With a sample of a few hundred, sampling variance may swamp a modest bias. With a sample of tens of thousands, the same bias dominates everything. This is the arithmetic behind the Literary Digest disaster and behind many subsequent failures of very large but poorly designed data collections. Why the published margin of error understates uncertainty The margin of error reported with a poll is conventionally about twice the standard error of the estimate, calculated as though the sample were a simple random sample from a perfect frame with full response. For a proportion near fifty percent and a sample of 1,000, this gives the familiar figure of about three percentage points. The calculation is correct for what it measures. It says nothing about bias, and in most modern surveys it also understates the variance, because the complex sample designs and heavy weighting discussed in later chapters inflate variance beyond the simple-random-sample benchmark. There is direct evidence of the gap. In a 2018 paper in the Journal of the American Statistical Association, Houshmand Shirani-Mehr, David Rothschild, Sharad Goel, and Andrew Gelman compared thousands of US state-level election polls with the eventual results. They found that the average absolute difference between poll and outcome was roughly twice what the reported margins of error implied, and that a substantial share of the excess came from what they called election-level bias — errors shared by all the polls in a given contest, such as a common misjudgement of who would turn out. The reported margin of error described a real source of uncertainty, but a minority of the total. None of this means margins of error should be abandoned. It means they should be read as a floor, not an estimate, of the uncertainty surrounding a survey number, and that a serious assessment of survey quality requires thinking about every other component in Table 1. Fitness for use A survey is not accurate or inaccurate in the abstract; it is accurate enough, or not, for a particular purpose. Statistical agencies have increasingly framed quality in these terms. The European Statistical System, Statistics Canada, and the US Federal Committee on Statistical Methodology all publish quality frameworks that treat accuracy as one dimension alongside relevance, timeliness, accessibility, interpretability, and coherence with other sources. A labour-force estimate that is extremely accurate but published eighteen months late may be less useful for monetary policy than a slightly noisier one published next week. The same survey can be fit for one use and not for another. A health survey whose small nonresponse bias shifts the national prevalence of smoking by half a percentage point may be perfectly adequate for tracking the national trend — if the bias is stable, it largely cancels out of year-to-year comparisons — while being quite inadequate for estimating smoking among young adults, a group whose response rates may be low and whose bias may be larger and less stable. Trend estimates, subgroup comparisons, and levels are all affected differently by the same error sources. Part of the discipline of Total Survey Error is asking which of these the user actually needs. Error and cost The final element of the framework is the one Groves placed in his book's title: every reduction in error costs something, and the budget is always finite. A face-to-face survey with a high response rate, carefully trained interviewers, and extensive pretesting may cost hundreds of dollars per completed interview; a web survey of an opt-in panel may cost a few dollars. The question is never whether the expensive design is better in some absolute sense, but whether the reduction in total error it buys is worth its cost for the purpose at hand, and whether that money would reduce total error more if spent elsewhere. This framing has practical consequences. It explains why a survey organisation might rationally accept a lower response rate in exchange for a larger sample, or a cheaper mode in exchange for more pretesting. It warns against optimising the most visible quality indicator — historically, the response rate — at the expense of less visible ones. A survey that spends heavily on refusal conversion to push its response rate from sixty to sixty-five percent may achieve little reduction in bias if the converted refusers resemble those who responded readily, while the same money spent on cognitive testing of a key question might have removed a measurement bias many times larger. The framework does not supply formulas for these trade-offs in most real situations, because the magnitudes of many error components are unknown for any particular survey. What it supplies is a checklist of the places to look and a vocabulary for arguing about priorities. The chapters that follow take each component in turn, with the aim of making clear how large it tends to be, how it can be detected, and what can be done about it. Measurability and the limits of the framework A frequent criticism of Total Survey Error is that it is easier to draw than to use. Of the seven components in Table 1, only sampling variance is routinely estimated from the survey data themselves. Coverage bias requires an external benchmark or a frame evaluation study. Nonresponse bias requires information on non-respondents, which by definition is scarce. Measurement bias requires a validation source — administrative records, biomarkers, a gold-standard interview — that is often unavailable. The framework can therefore become a list of worries rather than a quantitative tool. The criticism is fair, and the field has responded in several ways. One is the development of error models for specific components: interviewer variance can be estimated if interviewers are assigned to random subsamples of cases; response variance can be estimated from reinterviews; nonresponse bias can be bounded using frame variables, paradata about the fieldwork process, or follow-up studies of non-respondents. Another is the quality profile, a document that assembles everything known about the error properties of a major survey, as the US Census Bureau and others have done for surveys such as the Current Population Survey and the American Community Survey. A third is Biemer's proposal for regular, structured evaluation of each error source in continuing surveys, so that knowledge accumulates across rounds even when it cannot be complete in any single one. The more fundamental response is that a framework can be valuable even when it cannot be fully quantified. The alternative — attending only to the error that can be computed, and treating the margin of error as though it were the whole of the uncertainty — has repeatedly led survey producers and users into overconfidence. The best reason to think in terms of total error is that it forces the question every survey user ought to ask of every estimate: what else could have gone wrong, and how would I know? What this means for the rest of the book The chapters that follow are organised around the two columns of the lifecycle. Chapters 2 through 4 and 8 through 9 concern representation: frames, probability samples, non-probability samples, nonresponse, and weighting. Chapters 5 through 7 concern measurement: how respondents answer, how to write questions, and how to test them. The order is roughly that of survey design, but the argument of the framework runs through every chapter. No component can be judged in isolation, because the practical question is always which errors are large enough to matter for the intended use, and which of the available remedies reduces total error most for the money and effort they require. Chapter 2: Populations and Sampling Frames A survey begins with a decision that is often made too quickly: whom, exactly, it is meant to describe. The answer seems obvious until it has to be written down. "Adults in the United Kingdom" invites a string of questions. Does it include people living in care homes, prisons, military barracks, and student halls of residence? People who are temporarily abroad? Recent arrivals who have not yet registered anywhere? People who sleep rough? Residents of the Channel Islands, which are Crown Dependencies rather than parts of the United Kingdom? Each answer changes the population, and each has consequences for the estimates, because the excluded groups are rarely a random slice of everyone else. This chapter is about the distance between the population a survey wishes to describe and the population it can actually reach. That distance is coverage error, and it is the first place where representation can fail. Target population and survey population Survey methodologists distinguish several populations. The target population is the set of units — usually people, sometimes households, businesses, schools, or hospital episodes — about which the researcher wants to draw conclusions. It must be defined in terms of content (who counts), units (persons or households), geography, and time (on what date, or during what period, membership is determined). A precise definition might read: all persons aged sixteen and over who were usually resident in private households in Great Britain on the survey reference date. Almost every survey then quietly narrows the target to a survey population that is practical to reach. Large government household surveys typically exclude people living in institutions, sometimes those in remote or sparsely populated areas where fieldwork costs are prohibitive, and sometimes those who cannot be interviewed in any of the languages in which the survey is fielded. These exclusions are generally documented in the technical report and rarely mentioned in the headlines. They matter most when the excluded groups differ sharply on the survey's topic. A survey of disability that omits residents of care homes, or a survey of drug use that omits prisoners, is describing a population systematically healthier or more law-abiding than the one its title implies. What a sampling frame is To draw a probability sample, the researcher needs some way of giving every member of the survey population a known chance of selection. The device that makes this possible is the sampling frame. The simplest frame is a list: a population register, a list of patients registered with a health system, a membership roster. But frames need not be lists of people. An area frame is a map of the country divided into small geographic units that together cover the whole territory; the sample selects areas, then dwellings within areas, then people within dwellings. A random-digit-dial telephone frame is not a list of anyone in particular but a set of rules for generating telephone numbers in which working residential numbers are known to be concentrated. What these have in common is a mechanism by which each unit in the population is linked to a known, selectable element of the frame. Kish's classic treatment identified four ways in which a frame can depart from the ideal of a one-to-one correspondence with the target population. The first is undercoverage or missing elements: people in the population who have no corresponding entry in the frame. The second is overcoverage or foreign elements: frame entries that correspond to no member of the population, such as business telephone numbers in a residential telephone frame or demolished dwellings on an address list. The third is duplication: population members linked to more than one frame element, such as a person with both a landline and a mobile phone, or with two residential addresses. The fourth is clustering: frame elements linked to more than one population member, such as a household address behind which several adults live. Overcoverage, duplication, and clustering are nuisances that can be managed if the survey collects the right information. Foreign elements can be screened out at first contact. Duplicates can be handled by asking respondents how many ways they could have been selected and adjusting their weights accordingly — a person reachable through two telephone numbers had twice the chance of selection and receives half the weight. Clustering is handled by selecting one or more persons within the cluster with known probability, again with a corresponding weight. Undercoverage is different. Units that are not on the frame cannot be selected, cannot be screened, and cannot answer questions about how they might have been selected. Nothing in the survey data reveals their absence. The arithmetic of coverage bias A simple formula captures when undercoverage matters. Suppose a fraction of the target population is missing from the frame. The bias in a sample mean that is otherwise unbiased for the covered population equals that missing fraction multiplied by the difference between the covered and non-covered groups' means on the variable being measured. The formula has two factors, and both must be large for bias to be large. A frame that misses ten percent of the population produces little bias for a variable on which the missing ten percent resemble everyone else; a frame that misses two percent can produce meaningful bias for a variable on which the missing two percent are extreme. It follows that coverage error is not a property of a frame but of a frame in relation to a particular estimate. The same telephone frame may be adequate for estimating television viewing habits and seriously deficient for estimating residential instability or the prevalence of poverty. It also follows that the growth of any coverage gap is dangerous only insofar as the uncovered group is distinctive. When landline telephones first spread through the United States, those without them were disproportionately poor and rural, and early telephone surveys were justly suspected of bias. By the 1970s, household telephone coverage in the United States exceeded ninety percent and the remaining non-covered group, though still distinctive, was small enough that telephone surveying became respectable. The history of survey frames since then has been a series of such cycles, as new technologies and social changes open new gaps. The principal household frames For surveys of the general household population, four families of frame dominate. Each has a characteristic pattern of coverage strengths and weaknesses, set out in Table 2. Table 2. Principal frames for general population household surveys. Frame How units are reached Main coverage strengths Main coverage weaknesses Population register Named individuals from an official register Near-complete coverage of legal residents; auxiliary data on every unit Exists in few countries; misses unregistered and recently moved people Area probability Maps and field listing of dwellings in sampled areas Can in principle reach every dwelling Costly listing; misses hidden or irregular dwellings; requires in-person work Address-based Postal delivery address files High coverage of residential addresses; cheap to sample Weaker in rural areas and for non-standard addresses; no named persons Telephone (RDD) Randomly generated landline and mobile numbers Fast, cheap to sample, national reach Very low response; complex overlaps between landline and mobile users Population registers In the Nordic countries, the Netherlands, and a number of other European states, a continuously updated population register records every legal resident with a personal identification number, a date of birth, a sex, and an address. Sampling individuals directly from such a register is close to the textbook ideal. Every person has a known probability of selection, the frame supplies auxiliary information about non-respondents as well as respondents, and linkage to other administrative registers can supply data that the survey need not collect at all. Statistics Norway, Statistics Sweden, and Statistics Denmark have built much of their social statistics on this foundation. Registers are not perfect. They lag behind moves and emigration, they may omit undocumented residents entirely, and their address information can be out of date for young adults and others who change residence often. But in the countries that have them, they have made coverage error a secondary concern and freed methodologists to concentrate on nonresponse and measurement. Area probability frames Where no register exists, the traditional solution is to build a frame from geography. The country is divided into primary sampling units — counties, groups of counties, or census enumeration areas — which are sampled with probabilities proportional to their population. Within each sampled unit, smaller areas are selected. Field staff then walk the selected areas and list every dwelling they find, and a sample of dwellings is drawn from these listings. Finally, the interviewer enumerates the residents of each sampled dwelling and selects one or more of them. Area probability sampling has long been the gold standard for face-to-face surveys in the United States and elsewhere; the General Social Survey, the National Health Interview Survey, and the Current Population Survey have all relied on it. Its coverage is in principle complete, since every dwelling occupies some piece of ground. In practice, listers miss dwellings: basement flats, units above shops, informal structures, and multiple households concealed behind a single front door. Coverage of persons within dwellings is a further problem, because household rosters tend to omit people with a loose attachment to the household — often young men — who may be the very people the survey most needs. Coverage studies comparing survey totals with demographic benchmarks have long found that household surveys reach smaller shares of young adult men than of other groups, even before nonresponse is considered. Address-based sampling In the 2000s, survey researchers in the United States discovered that commercially available versions of the US Postal Service's Computerized Delivery Sequence file could serve as a frame of residential addresses with coverage approaching that of field listing in many areas, at a tiny fraction of the cost. Address-based sampling, as it came to be called, has since become the dominant frame for high-quality general population surveys in the United States, often combined with mail invitations to complete a questionnaire online or on paper. The Royal Mail's Postcode Address File plays a similar role in the United Kingdom and has long been the standard frame for major British surveys. Address frames have characteristic weaknesses. Coverage is poorer in rural areas where mail is delivered to post office boxes or rural routes, in areas of new construction, and for dwellings without a standard postal address. And an address frame identifies a place, not a person, so the survey must still select a respondent within the household, usually by asking whoever opens the envelope to hand the questionnaire to the adult with the next birthday or by some similar rule. Such self-administered within-household selection is imperfectly followed, which introduces its own errors. Telephone frames For roughly three decades from the 1970s, random-digit dialling was the workhorse of opinion polling and much academic survey research in the United States. Because telephone numbers were assigned in blocks, and residential numbers clustered within certain blocks, a sample of randomly generated numbers within active blocks gave every household with a landline a known probability of selection, including households with unlisted numbers. Two developments eroded the method. The first was the spread of mobile telephones and the consequent abandonment of landlines. The National Center for Health Statistics has tracked this since 2003 through the National Health Interview Survey, which asks respondents about the telephones in their household; the share of adults living in households with only mobile phones rose from a few percent in the early 2000s to a majority by the late 2010s and continued to rise into the 2020s. The wireless-only population is younger, more likely to rent, and more likely to be Hispanic than the landline population, so landline-only surveys developed serious coverage bias. Survey organisations responded with dual-frame designs that sample both landline and mobile numbers and combine the two samples with weights that account for people reachable through both. The second development, discussed in Chapter 8, was the collapse of telephone response rates, which by the late 2010s had fallen to single digits for many polls. Coverage of special and hidden populations Some target populations have no frame at all. There is no list of people who inject drugs, undocumented migrants, sex workers, or people with a rare disease. For such groups survey researchers use a range of workarounds. Screening draws a large general-population sample and asks eligibility questions, retaining only those who qualify; it preserves probability sampling but becomes prohibitively expensive when the group is rare. Disproportionate stratification concentrates sampling effort in areas where the group is known to cluster, at the cost of unequal weights. Multiple-frame designs combine a general frame with a partial but efficient list, such as a membership roster, and weight to account for overlap. When none of these is feasible, researchers turn to network-based methods. Respondent-driven sampling, developed by the sociologist Douglas Heckathorn in the 1990s, begins with a set of seed respondents who recruit peers, who recruit further peers, through successive waves, with estimators that attempt to correct for the unequal probability that different people are recruited. It has been widely used in HIV surveillance. Its statistical assumptions — that recruitment is random within each person's network, that people report their network size accurately, and that the chain runs long enough to forget its starting point — are rarely fully met, and methodological evaluations have found that its estimates can be highly variable. It is best regarded as a disciplined non-probability design rather than a probability sample. Selecting people within households Most household frames select dwellings, not people, and so every such survey must decide how to choose among the eligible residents it finds. The choice looks like an administrative detail and is in fact a coverage decision. The most rigorous approach, introduced by Kish in 1949, has the interviewer list every eligible adult in the household by sex and age and then use a pre-assigned selection table to pick one. It produces a known probability of selection for every adult, but it requires the person answering the door to disclose the composition of the household to a stranger before the interview has begun, and that request itself provokes refusals. Cheaper alternatives ask for the adult with the most recent or next birthday, on the reasoning that birthdays are close to randomly distributed. These methods are less intrusive and widely used, particularly in telephone and mail surveys. Their weakness is that they depend on the household to apply them honestly and correctly, and studies that have checked the selected respondent against a full household roster have repeatedly found that a substantial minority of households select the wrong person — usually the one who happens to be available, interested, or accustomed to dealing with official correspondence. Such errors are not random. They tend to over-represent women, older adults, and the more educated members of the household, which are precisely the groups that are already over-represented through nonresponse. Whatever method is used, a person selected from a household of four adults had one quarter of the chance of selection of a person living alone, and must carry four times the weight. Forgetting this step, as some analyses of secondary data do, biases estimates toward the characteristics of people in larger households — who are, among other things, more likely to be married and to have children. The web has no frame The rise of online data collection has produced an asymmetry that is easy to overlook. Collecting data over the internet is cheap and fast, but there is no general frame of internet users from which to draw a probability sample. Email addresses are not listed in any comprehensive directory, are not tied to one person each, and cannot be generated at random the way telephone numbers can. A survey that wishes to collect data online from a probability sample must therefore make first contact through some other frame — usually addresses or telephone numbers — and then invite the sampled people to go online. This is the design of the probability-based online panels that emerged from the late 1990s onward: panels such as the Dutch LISS panel, the German Internet Panel, the Pew Research Center's American Trends Panel, and NORC's AmeriSpeak. Each recruits members through a probability frame, typically addresses, and in some cases supplies internet access or devices to people who lack them so that the offline population is not excluded. Once recruited, panel members can be surveyed repeatedly online at low cost. The coverage properties of such panels are inherited from the recruitment frame; their weaknesses lie elsewhere, in the cumulative nonresponse that occurs at recruitment, at joining, and in each subsequent wave, and in the possibility that long-serving members come to answer differently from fresh respondents. Surveys that recruit online without any probability frame — through advertisements, website banners, email lists of volunteers, or commercial panels of people who have signed up to take surveys for rewards — are in a different position altogether. They have not merely a coverage problem but no defined selection probabilities at all. That is the subject of Chapter 4. Frames change, and so must surveys The main lesson of the history of sampling frames is that no frame stays good forever. Telephone frames went from inadequate to excellent to inadequate again within two generations. Address frames rose to prominence in a decade. Registers are threatened by migration and by public reluctance to share data. Each change alters not only the coverage of the frame but the mode of contact it implies — an address invites a letter, a telephone number invites a call, a register invites whichever mode the agency chooses — and therefore the pattern of nonresponse and measurement error that follows. The frame decision is where the two columns of the Total Survey Error lifecycle first meet. For the survey user, the practical questions are three. What was the frame, and whom does it exclude? How large is the excluded group relative to the population of interest? And is there reason to think that group differs on the variables being estimated? A technical report that answers these clearly is a sign of a survey whose producers understand what they are doing. A report that says only that the sample is "nationally representative" answers none of them. Chapter 3: Probability Sampling and Design In 1934 the Polish statistician Jerzy Neyman read a paper to the Royal Statistical Society in London that settled a long-running dispute. The question was how to choose a part of a population so that it could stand for the whole. One school, influential in official statistics, favoured purposive selection: choosing districts or units deliberately so that the sample matched the population on known characteristics. The other favoured random selection. Neyman showed, using an Italian census study that had chosen districts purposively to match national averages and had nonetheless produced poor estimates of other characteristics, that purposive selection offered no general protection against error and no way of measuring the error it produced. Random selection, particularly when combined with stratification, did both. The paper, "On the Two Different Aspects of the Representative Method," is generally regarded as the foundation of modern survey sampling. This chapter explains the logic Neyman established and the designs that grew from it, at the level needed to plan a sample, read a methods report, and understand why the precision of a real survey is almost never what a simple formula would suggest. What makes a sample a probability sample A probability sample is one in which every unit in the frame has a known, non-zero probability of being selected, and in which selection is carried out by a random mechanism under the researcher's control. The probabilities need not be equal. They need only be known. This is the whole of the definition, and each part does work. The requirement that probabilities be known is what allows the sample to be linked back to the population. If a person had a one-in-a-thousand chance of selection, then in a sense that person stands for a thousand people, and weighting each observation by the inverse of its selection probability produces unbiased estimates of population totals. This result, formalised by Daniel Horvitz and Donovan Thompson in 1952, is the basis of design-based inference: the randomness that justifies the estimate is the randomness the researcher introduced, not an assumption about how the population behaves. The requirement that probabilities be non-zero is what rules out coverage exclusion within the frame. A unit with zero chance of selection can never be represented, and no weighting can bring it in. The requirement that selection be random is what distinguishes probability sampling from haphazard or convenience selection. An interviewer instructed to "choose a typical household on each street" is not sampling randomly, however conscientious, because the interviewer's judgement about typicality enters the selection and introduces biases that cannot be measured. The payoff from meeting these requirements is that the sampling distribution of an estimate — the distribution of values it would take across all possible samples that could have been drawn under the design — can be derived from the design itself. That is what allows a probability survey to state its sampling error without assuming anything about the population beyond what the frame contains. Simple random sampling as a benchmark The simplest probability design is the simple random sample, in which every possible subset of a given size has the same chance of selection. Few real surveys use it, because it is usually inefficient or impractical, but it serves as the benchmark against which other designs are compared. Under simple random sampling, the variance of a sample mean equals the population variance of the variable divided by the sample size, multiplied by a finite population correction equal to one minus the sampling fraction. When the sample is a small part of the population, as in most national surveys, the correction is close to one and can be ignored. This has a counterintuitive but important consequence: the precision of an estimate depends on the absolute size of the sample, not on the fraction of the population sampled. A simple random sample of 1,000 people gives about the same precision whether it is drawn from a city of 100,000 or a nation of 300 million. Sample sizes for national polls are not small because pollsters are careless; they are adequate because population size barely matters. For a proportion, the population variance is the proportion multiplied by its complement, which is largest at fifty percent. This is why the standard margin of error for a sample of 1,000 is about plus or minus three percentage points, and why quadrupling the sample to 4,000 only halves it to about one and a half. Precision improves with the square root of the sample size, so each additional increment of accuracy costs more than the last. Stratification Stratification divides the population into mutually exclusive groups, or strata, and draws a separate probability sample within each. Typical strata in household surveys are regions, urban and rural areas, or small areas grouped by socioeconomic indicators. In list samples, strata may be formed from any variable on the frame: age groups on a population register, size classes on a business register. Stratification serves two purposes. The first is precision. Because each stratum is sampled separately, the variation between strata contributes nothing to the sampling variance; only variation within strata does. If strata are formed so that units within each are similar on the survey variables, the gain can be substantial. With proportionate allocation, in which each stratum's share of the sample equals its share of the population, stratification can never do worse than simple random sampling of the same size, and usually does somewhat better. The second purpose is control over subgroup sample sizes. A survey that needs reliable estimates for each of several regions, including small ones, can sample the small regions at higher rates than the large ones. This disproportionate allocation guarantees enough cases in each region for separate analysis, at the cost of unequal weights in national estimates, which generally reduces national precision. Neyman's 1934 paper derived the allocation that minimises the variance of an overall estimate for a fixed sample size: sample each stratum in proportion to the product of its population size and its within-stratum standard deviation. Strata that are larger or more variable receive more of the sample. When costs per interview differ between strata, the optimal allocation also takes account of cost, sampling more heavily where interviews are cheap. In practice, optimal allocation for one variable is rarely optimal for others, and surveys that measure hundreds of variables typically settle for a compromise: roughly proportionate allocation with oversampling of subgroups that are analytically important. Clustering If stratification is the design feature that usually improves precision, clustering is the one that usually worsens it, and it is used anyway because it cuts costs dramatically. A face-to-face survey that selected 3,000 households at random across a large country would send interviewers to 3,000 widely scattered locations, many of them hours apart. The travel alone would consume most of the budget. Cluster sampling solves this by selecting geographic units first — say, 150 small areas — and then selecting about twenty households within each. Interviewers can then work efficiently in a limited number of places. Area frames, described in Chapter 2, are almost always used in this multistage clustered form. The cost of clustering is statistical. People who live near one another tend to resemble one another: in income, ethnicity, housing, political views, exposure to local health risks. Twenty households drawn from one neighbourhood therefore carry less independent information than twenty households drawn from twenty neighbourhoods. The degree of resemblance is measured by the intraclass correlation, usually written with the Greek letter rho, which is zero if people within clusters are no more alike than people in general and one if they are identical. The effect of clustering on variance is summarised by a formula that every survey designer should know. The design effect due to clustering is approximately one plus the product of the intraclass correlation and one less than the average number of interviews per cluster. The design effect is the ratio of the actual variance of an estimate to the variance a simple random sample of the same size would have produced. The formula shows why even small intraclass correlations matter. Suppose rho is 0.05, a typical value for many socioeconomic variables, and each cluster contributes twenty interviews. The design effect is one plus 0.05 times nineteen, or 1.95. The variance is nearly double that of a simple random sample, and the effective sample size — the size of a simple random sample that would have given the same precision — is the actual sample divided by the design effect. A clustered sample of 3,000 behaves like a simple random sample of about 1,540. For variables with higher intraclass correlations, such as access to piped water in a developing country or ethnicity in a segregated city, rho may exceed 0.2 and the design effect may be five or more. The design lesson is that the number of clusters matters more than the number of interviews per cluster. Taking fewer interviews in more clusters reduces the design effect, at the price of more travel. The optimal cluster size balances the cost of reaching a new cluster against the cost of an additional interview within one, and the answer depends on rho; for variables with high intraclass correlation, small clusters are worth paying for. Unequal probabilities and multistage selection Real household surveys usually select areas with probability proportional to size — that is, a larger area has a proportionally larger chance of selection. Then, within each selected area, a fixed number of dwellings is chosen. The two stages cancel: a dwelling in a large area had a high chance of its area being chosen and a low chance of being chosen within it, and a dwelling in a small area the reverse. If the size measures are accurate, every dwelling ends up with the same overall probability of selection, a so-called self-weighting design, while every interviewer has the same workload. When the size measures are out of date — because an area has seen new construction since the last census, for example — probabilities become unequal and weights must compensate. Other sources of unequal probability are deliberate: oversampling of strata, selection of one adult from households of different sizes, and dual-frame designs in which some people can be reached through two routes. All of them require weights, and all weights, as Chapter 9 explains, carry a price in variance. Kish proposed a simple approximation for this price: when weights vary for reasons unrelated to the survey variables, the design effect due to weighting is about one plus the square of the coefficient of variation of the weights. A set of weights whose standard deviation equals half their mean produces a design effect of about 1.25, a loss of a fifth of the effective sample. The clustering and weighting effects compound, so a survey with both can easily have an overall design effect of two or three. Systematic sampling A common practical method of selecting units from a list is systematic sampling: choose a random starting point, then take every kth unit thereafter, where k is the population size divided by the desired sample size. It is simple to carry out, especially in the field or from printed lists, and if the list is sorted by a variable related to the survey topic — for example, addresses sorted by postcode, which groups them geographically — systematic selection produces a sample that is implicitly stratified by that variable and usually gains precision as a result. The risk is periodicity. If the list has a regular pattern that coincides with the sampling interval — a housing estate in which every tenth dwelling is a corner unit, or a payroll list in which every twentieth entry is a supervisor — systematic selection can produce a badly unrepresentative sample. Such patterns are rare in practice but should be checked for. Estimating variance from complex samples Because complex designs change the variance of estimates, the software that analyses the data must know about the design. Analysing a clustered, stratified, weighted sample as though it were a simple random sample almost always understates standard errors, sometimes grossly, and leads to confidence intervals that are too narrow and significance tests that are too liberal. This remains one of the most common errors in published secondary analysis of survey data. Two families of method are used to estimate variance correctly. Taylor series linearisation approximates nonlinear estimators such as ratios and regression coefficients by linear functions and applies the standard formulas for stratified cluster samples to the linearised values. It requires the data set to identify each case's stratum and primary sampling unit. Replication methods — the jackknife, balanced repeated replication, and the bootstrap — form many subsamples or reweighted versions of the full sample, compute the estimate on each, and use the variation among them to estimate the variance. Replication is convenient because it can be packaged as a set of replicate weights that accompany the public data, allowing users to compute correct standard errors without seeing confidential design information. The US Census Bureau distributes the American Community Survey with eighty replicate weights for this reason. Major statistical packages, including the survey package in R and the survey commands in Stata and SAS, implement both approaches. A worked example of design planning Suppose a health agency wishes to estimate the prevalence of a condition believed to affect about twenty percent of adults, with a margin of error of plus or minus two percentage points at ninety-five percent confidence, using a clustered face-to-face design. For a simple random sample, the required size is found by setting 1.96 times the standard error equal to 0.02. The standard error of a proportion of 0.2 is the square root of 0.2 times 0.8 divided by the sample size. Solving gives a sample of about 1,540. Now suppose previous surveys suggest an intraclass correlation of 0.03 for this condition, and the agency plans twenty-five interviews per cluster. The design effect for clustering is one plus 0.03 times twenty-four, or 1.72. Suppose further that the planned oversampling of rural areas and within-household selection will produce weights with a coefficient of variation of about 0.4, adding a weighting design effect of about 1.16. The overall design effect is roughly the product, 2.0. The required number of completed interviews doubles to about 3,080. Finally, the agency expects a response rate of about sixty percent and an eligibility rate of ninety percent among sampled addresses. It must therefore select about 3,080 divided by 0.54, or roughly 5,700 addresses, in about 125 clusters. Every step of this calculation rests on an assumption that could be wrong, and a careful planner would test how sensitive the answer is to each. But the exercise shows why a survey that would need 1,540 interviews on the simple textbook formula may need to issue nearly four times as many addresses in practice. What probability sampling does and does not guarantee The strength of probability sampling is that it converts the question of representativeness from a matter of judgement into a matter of design. Given a complete frame and full response, the estimates are unbiased and their variance can be calculated. No other method offers that guarantee. But the guarantee is conditional. It assumes the frame covers the population, and Chapter 2 showed that frames rarely do. It assumes that everyone selected responds, and Chapter 8 will show that in contemporary surveys most do not. When coverage and response are incomplete, the realised sample is no longer a probability sample of the target population in the strict sense; it is a probability sample of a frame, filtered through a response process whose probabilities are unknown. The estimates then depend, like those of any non-probability sample, on assumptions about the people who are missing. This has led some commentators to argue that the distinction between probability and non-probability surveys has become meaningless when response rates are low. That conclusion goes too far. A probability sample with a low response rate still begins from a known selection mechanism, still offers information about the non-respondents from the frame and the fieldwork, and still allows the effects of nonresponse to be studied and bounded. A sample assembled from volunteers begins with none of those things. The difference is a matter of degree rather than kind, but the degree is large. The next chapter examines what happens when that starting point is abandoned altogether. Hashtags: #SurveyMethodology #TotalSurveyError #SamplingFrames #CoverageError #ProbabilitySampling #ComplexSurveyDesign #StratifiedSampling #ClusterSampling #DesignEffect #SamplingError #NonresponseError #MeasurementError #ProcessingError #AdjustmentError #QuestionDesign #SurveyQuestionnaireDesign #CognitiveInterviewing #RespondentComprehension #ResponseProcess #NonProbabilitySampling #SurveyWeighting #PostStratification #Raking #CalibrationWeighting #FutureOfSurveyMethodology