# When the Business Case Becomes the Warning ## A Menu-Innovation Reading of Jonathan Swift’s “A Modest Proposal” ### Executive Summary Jonathan Swift’s “A Modest Proposal” is constructed as a business case for an atrocity. Its speaker presents the sale and consumption of poor Irish infants as an inexpensive, scalable answer to poverty, population pressure, unemployment, landlord losses, and national economic stagnation. He supplies demand assumptions, supply estimates, operating mechanics, customer segments, by-product opportunities, seasonal considerations, and a list of alleged stakeholders who would benefit. The proposal is not a serious menu concept. Its value for menu and business leaders lies in the diagnostic method it exposes. Swift shows how a proposal becomes dangerous when financial logic is allowed to replace human judgment: people become units of supply; suffering becomes a cost burden; precision becomes a substitute for evidence; and a broad list of beneficiaries is used to obscure who bears the harm. For a menu innovation organization, the practical lesson is direct. A concept should not be judged only by food cost, throughput, supplier economics, or projected demand. Those measures matter, but they must remain subordinate to the customer promise, the dignity of affected people, operational reality, and the consequences of public interpretation. A business case that is internally efficient can still be strategically defective if its value proposition depends on exploitation, concealment, or the assumption that affected stakeholders have no meaningful alternative. The text also offers a disciplined way to test proposals before they reach development. Ask whether the idea is solving the stated problem or merely monetizing a vulnerable group; whether its numerical precision reflects evidence or theatrical certainty; whether rejected alternatives were genuinely evaluated; and whether the proposal remains defensible when described plainly to customers, employees, suppliers, and the public. ## 1. The Proposal’s Apparent Business Logic The speaker begins with a visible social problem: poor mothers and children crowd streets, roads, and cabin doors, with mothers forced to beg. He describes children growing up without support as potential thieves, emigrants, or people driven into servitude. The issue is framed as a large and urgent public-policy burden, extending beyond professional beggars to the wider population of parents unable to support their children. That opening resembles the first section of a conventional business case: define the problem, establish its scale, and show the cost of inaction. The speaker then claims years of study and criticizes earlier schemes for faulty calculations. This creates the impression of expertise before the proposal is disclosed. The proposed solution is deliberately presented in operational terms. Of 120,000 children born annually to poor parents, 20,000 would be retained for breeding and 100,000 sold at one year old. The product is described as a healthy, well-nursed child, with assigned weights and supposed nutritional value. The speaker identifies wealthy buyers, household use cases, taverns, public entertainments, landlords, mothers, and manufacturers of gloves and boots as participants in the resulting economy. The structure is familiar: - A defined problem and target population. - A quantified supply base. - A product specification. - A segmentation of buyers. - A proposed operating model. - Claimed savings and new revenue. - Secondary uses for residual materials. - An answer to objections. - A list of alternatives dismissed as impractical. The horror comes not from a lack of business logic, but from business logic functioning smoothly after the moral premise has been corrupted. ## 2. The Central Failure: Treating People as Inventory Swift’s central satirical move is to show poor people being treated as economic burdens and commodities. Children who were initially described as costs to parents, parishes, and the state are transformed into food, clothing, rent payments, and national wealth. The proposal’s language makes the reversal explicit: children cease to be dependents and become productive assets for others. This is the point at which a commercially attractive idea can become strategically unsound. A menu concept may have an appealing margin, an available supply, and a workable preparation method. Yet if the concept’s appeal depends on reducing people to objects, extracting value from vulnerability, or hiding the burden imposed on a stakeholder, the economics are not the whole case. They are evidence of the problem. Swift’s proposal repeatedly asks the reader to accept a narrow definition of value. A poor mother receives a supposed profit and is released from the cost of raising a child. A landlord gains another asset to seize when rent is unpaid. Wealthy diners receive an unusual food. Taverns gain custom. The nation supposedly reduces maintenance costs and creates a domestic industry. The list is comprehensive but not balanced. It counts transactions while excluding the moral and human cost of the transaction itself. That is the warning for innovation leaders: a stakeholder map can appear complete while omitting the people who bear the deepest consequences. A useful review question is therefore not simply, “Who benefits?” It is: > Who is converted into the source of that benefit, and what happens to that person’s ability to refuse, negotiate, or remain unharmed? ## 3. Precision Is Not Proof The speaker uses numbers to make the proposal sound tested. He estimates annual births, subtracts financially secure families, miscarriages, and infant deaths, assigns weights to newborns and one-year-olds, calculates portions, and forecasts consumption in Dublin and elsewhere. He even states an annual increase in national wealth. The numerical detail creates a surface impression of rigor. But the calculations do not validate the premise. They simply make an indefensible premise look administratively manageable. This distinction matters in menu development. Forecasts, food-cost models, supplier quotes, yield assumptions, and labor estimates are indispensable. They are also vulnerable to false confidence when the underlying assumptions have not been challenged. A precise number can conceal a weak definition of demand, an untested customer response, an unavailable supply, or a cost transferred to another party. Swift’s pseudo-analysis suggests four questions for commercial review: 1. **What is being measured?** A number may describe volume while ignoring dignity, trust, or reputational exposure. 2. **Which assumptions create the result?** The arithmetic may be sound only because the speaker has defined human beings as inventory. 3. **Who supplied the evidence?** The speaker invokes merchants, calculations, and years of study, but the authority is part of the satire rather than independent validation. 4. **What would disconfirm the case?** A proposal that cannot survive a plain-language challenge is not robust because it is numerically detailed. The practical standard is not less quantitative discipline. It is better sequencing: first test the premise and affected stakeholders, then test the economics. ## 4. Operational Completeness Can Intensify the Risk The proposal does not stop at a product description. It imagines how mothers would be encouraged to nourish children for maximum value, how buyers would use the product, where slaughterhouses could be established, how supply would vary by season, and how skins would become luxury goods. It turns an abstract outrage into a complete operating system. That level of operational detail is one reason the satire remains powerful. Executional feasibility does not redeem a bad proposition; it can make the bad proposition more disturbing by showing how institutions might normalize it. For a restaurant chain operating across hundreds of locations, operational simplicity is rightly valuable. A concept that requires unusual ingredients, complicated preparation, fragile supply, or extensive training carries downside risk. But executional feasibility should not be treated as a moral clearance. A smoothly executable idea can still create: - A customer-positioning problem if the promise is difficult to explain plainly. - A supplier-economics problem if the model depends on a vulnerable or coercive source. - A kitchen-execution problem if the concept invites inconsistent interpretation or preparation. - A consumer-appeal problem if curiosity does not translate into repeat demand. - A public-relations problem if the most memorable description is worse than the intended brand story. Swift’s imagined shambles make infrastructure visible. That is useful because infrastructure often reveals the true nature of a proposal more clearly than its headline benefit. Review the purchasing process, labor implications, preparation environment, waste stream, and customer-facing language. If the operating model makes the ethical weakness more visible rather than less, the concept should not advance simply because it can be executed. ## 5. The False Comfort of Broad Benefits The speaker claims that nearly everyone gains: poor mothers receive money, landlords recover value, taverns gain custom, cooks gain work, wealthy households receive food, and the nation reduces costs. He also claims the scheme will encourage marriage, improve husbands’ treatment of pregnant wives, advance trade, relieve the poor, and entertain the rich. This is a classic broad-benefit argument. It is persuasive because it gives each audience a reason to approve the proposal. It is also misleading because the alleged benefits are built on the same underlying harm. A menu innovation review should distinguish between: - **Direct value:** What does the customer receive? - **Operational value:** What improves in purchasing, preparation, throughput, or waste? - **Strategic value:** How does the concept differentiate the brand? - **Transferred cost:** Who absorbs the downside that the financial model does not show? - **Interpretive risk:** What will customers and the public believe the concept says about the company? The last two categories are where Swift’s proposal collapses. Its benefits exist only because poor families are denied meaningful alternatives and because wealthy consumers are invited to convert suffering into pleasure. The proposal’s apparent inclusiveness is therefore a form of concealment. A strong business case should make the distribution of benefits and burdens explicit. If a concept needs euphemism, selective disclosure, or an exhaustive list of secondary winners to remain attractive, that is not persuasive stakeholder management. It is a warning signal. ## 6. Alternatives Are Part of the Case, Not a Footnote Near the end, Swift’s speaker rejects a catalogue of ordinary reforms: taxing absentees, buying domestic goods, reducing luxury, improving thrift, ending faction, dealing honestly, and showing mercy to tenants. He does not argue that these ideas are meaningless in themselves. He argues that they are useless without sincere commitment to put them into practice. This is the text’s most important strategic turn. The grotesque proposal is not offered because no humane alternatives exist. It is offered because the ruling system refuses to implement them. For menu strategy, this creates a useful discipline. A new product should not be evaluated against an imaginary “do nothing” baseline. It should be compared with credible alternatives, including simpler changes to the current menu, supplier terms, portioning, preparation, promotion, or product architecture. Before approving a high-risk concept, decision-makers should ask: - What lower-complexity options address the same customer or commercial need? - Has the team tested a less novel version with better supply resilience? - Is the proposed differentiation genuinely valuable, or merely shocking? - Are savings coming from better design or from shifting costs elsewhere? - What known reforms or process changes have been deferred because they are less exciting? Swift’s catalogue also exposes a common organizational failure: leaders may describe alternatives as impractical when the real obstacle is unwillingness to act. A proposal should therefore separate “cannot be done” from “has not been prioritized.” ## 7. A Practical Review Framework for Menu Innovation The following framework translates the text’s warning into a decision screen for new-product development. ### 7.1 Premise test State the customer problem, business problem, or differentiation opportunity in plain language. Then identify whose circumstances make the solution possible. If the concept depends on a group being powerless, unseen, or unable to object, stop and reassess the premise. ### 7.2 Value-and-burden map List every beneficiary and every party carrying cost, risk, labor, or reputational exposure. Do not limit the map to the paying customer, restaurant unit, and supplier. A proposal is incomplete if its most affected stakeholders are absent from the analysis. ### 7.3 Evidence test Separate observed evidence from assumptions, rhetorical precision, and borrowed authority. Quantification should clarify uncertainty, not disguise it. A forecast with many decimal places is not stronger than the assumptions beneath it. ### 7.4 Alternatives test Document the humane, simpler, or less disruptive alternatives considered. Explain why they were rejected. If the answer is merely that they require commitment, coordination, or operational change, the organization may be avoiding the real solution. ### 7.5 Plain-language test Describe the concept without brand language, euphemism, or selective emphasis. Then consider how the description would sound to customers, employees, suppliers, and the public. If the plain version creates immediate reputational harm, that harm belongs in the business case before development begins. ### 7.6 Scale test A concept that seems tolerable in one location may become unacceptable when reproduced across hundreds of locations. Review supply availability, consistency, training requirements, waste, customer interpretation, and public visibility at chain scale—not only in a controlled pilot. ### 7.7 Stop-rule test Define the conditions that would end development: evidence of unacceptable customer rejection, unreliable supply, unmanageable execution, exploitative economics, or a public interpretation fundamentally at odds with the brand. A proposal without stop rules can turn sunk effort into false commitment. ## Conclusion: The Business Case Must Remain Human “A Modest Proposal” is memorable because it makes an immoral system sound efficient. Its speaker offers low cost, abundant supply, convenient execution, multiple revenue streams, broad stakeholder benefits, and apparent national advantage. The proposal fails not because it lacks a business case, but because the business case has become the instrument of dehumanization. For menu innovation leaders, the lesson is not to distrust economics or avoid distinctive food. It is to use commercial discipline more completely. Food cost, supplier economics, kitchen execution, customer appeal, and scale are necessary measures, but they are not sufficient measures. The proposal must also survive scrutiny of who is being valued, who is being used, what alternatives were ignored, and how the concept will be understood when its logic is stated plainly. A proposal can look cheap, scalable, and broadly beneficial while its very logic reveals that people have been reduced to inventory. The strongest innovation process catches that failure before it becomes a product, a press story, or a permanent expression of the brand.