Phileas Fogg Invented What Is Now Killing Modern Corporations

What this chapter is about. A provocative analysis of how a fictional nineteenth-century character intuitively applied the principles that today's Agile industry has commercialized and distorted. How the common sense of one literary gentleman lays bare the derangement of an industry worth tens of billions of dollars.

Amiens, January 1872

Jules Verne sits in his study, surrounded by geographical maps and stacks of correspondence from his publisher, Pierre-Jules Hetzel. Spread across the desk: sailing schedules of the Peninsular and Oriental Steam Navigation Company, railway maps of British India, and clippings from Le Temps about the reported completion of the Indian rail line.

Verne is forty-three. He has already had commercial success with the novels about Captain Nemo and the trip to the moon, but Hetzel is demanding still more of an adventure, something that will make readers buy the next issue of the paper without waiting for the run to end. Hetzel pays a flat fee per manuscript, no royalties: modest money even by the standards of 1872, but steady. Steadier, at least, than sea expeditions or theatrical speculations.

Verne spreads a map of the world in front of him and does the arithmetic quickly: London to Suez to Bombay to Calcutta to Hong Kong to Yokohama to San Francisco to New York to Liverpool. Given a steamer at the right hour and a working railway timetable, the thing is, in theory, possible. Provided the Indian rail line has actually been finished, as the papers claim.

What Verne does not yet know is that alongside an entertainment novel he is writing the formula for project management for the next 150 years.

He picks up his pen and writes: "The Reform Club, Wednesday, 2 October 1872."⁹

The story begins.

The fireplace in the salon of the Reform Club on Pall Mall burns evenly, giving off a steady heat. Four gentlemen are gathered around the whist table: the engineer Andrew Stuart, the banker John Sullivan, Gauthier Ralph (one of the directors of the Bank of England), and Phileas Fogg, a gentleman of unknown occupation but known punctuality.

Three of them are treating the morning's news as one more newspaper curiosity, amusing and no more. The fourth, Fogg, pronounces a sentence that will change his life and anticipate the management revolution of the next century:

"I wager twenty thousand pounds sterling [...] that I shall go around the earth in no more than eighty days, that is to say, in one thousand nine hundred and twenty hours, or one hundred and fifteen thousand two hundred minutes."¹

Twenty thousand pounds sterling of 1872, adjusted for inflation, comes to roughly £2.9 million (about $3.5 million) in today's purchasing power.² You do not back out of a bet like that, and you do not forget it.

What makes the scene remarkable is not the sum but the way Fogg frames the challenge. He does not say, "I shall draw up a detailed itinerary." He does not say he will need an expert commission, logistics consultants, and half a year of preparation. He simply picks up the paper, assembles his route out of the available transport schedules, and walks out of the club that same evening.

His companions are stunned, not by the recklessness of the bet, but by the recklessness of the method. No reasonable man of the nineteenth century begins a trip around the world with a few lines torn hastily from the morning paper.

Fogg answers them, and the whole future industry of project management, with a single line: "The unforeseen does not exist."¹

He is, of course, wrong. The unforeseen will chase him for all eighty days without letup. The railway will break off in the middle of the Indian jungle at exactly the wrong place. The steamer will leave Calcutta without him, refusing to wait for a passenger who is running late, and Fogg will have to find any other vessel headed the right way. The transatlantic liner will refuse to change course. A Scotland Yard detective will follow him doggedly across three continents, convinced beyond argument that Fogg is the man wanted for robbing the Bank of England.

And here is what is really remarkable: Fogg does not just survive the chaos. He systematically prospers in it. Not because he is a genius, and not because his luck is stubbornly good. Because his method of working, knowingly or not, is a perfect implementation of the principles that 129 years later will be called a revolution and put down on a single page as the Manifesto for Agile Software Development.

Fogg did not know the word "Agile." He did not know that a repeating cycle, an iteration, is a thing that can be handsomely certified and sold. He did not know that common sense could be packaged into a framework and moved for two million dollars to a corporate client shopping for transformation.

He simply did what worked, without thinking about the terminology. Therein lies the problem.

This book is about a paradox.

The paradox is this: the project-management principles that actually work were known to literature long before management became a science with its own faculties and journals. Jules Verne described iterative delivery in 1872, forty years ahead of Taylor and his scientific management.

An abandoned creation that avenges itself upon its creator. The art of telling a relevant trail from noise. A map in one-to-one scale that buried the empire beneath it. All these plots — Shelley, Doyle, Borges — will unfold in this book as separate chapters, and each one predated its managerial "innovation" by decades. The authors were neither cleverer nor better educated than today's consultants. Literature simply writes living people — and project management, at bottom, is precisely people. Not processes and not statuses. Not frameworks and not methodologies. People under pressure, making real decisions under uncertainty.

The paradox is compounded by what happened after the Manifesto was published. In 2001, seventeen practitioners formalized these literary intuitions into four values and twelve principles. They called the document the Manifesto for Agile Software Development, and the whole text fit on a single page. The idea was banally simple: people over processes, working product over documentation, collaboration over contracts, adaptation over the original plan.

Then that single page was turned into a full-scale industry with its own vocabulary and hierarchy. The market for Agile implementation is valued in the tens of billions of dollars and grows every year without stumbling.³ Certifications, coaches, frameworks, conferences, training courses, multi-stage transformation programs with their own jargon: all of it sells reliably to corporate clients. A whole army of intermediaries has grown up between common sense and its direct application at work.

Fogg went around the world with one servant and a newspaper timetable. The average corporation's Agile transformation now requires consultants, Scrum Masters, Agile coaches, Release Trains, PI Planning sessions, portfolio managers, and transformation-steering committees to teach teams to do what Fogg did on instinct.

And that is the central argument of this book: the Agile industry sells corporations common sense wrapped in a complexity that kills the common sense.

Phileas Fogg is a fictional character. Jules Verne invented him for an adventure novel that appeared in installments in Le Temps from November to December 1872.⁴ It is precisely because Fogg is fictional that he is ideal for our purpose. A fictional character is a clean model: undistorted by career interest, unclouded by corporate politics, unedited by the PR department. Fogg shows the principles in laboratory purity, and, in doing so, exposes an industry that has complicated those principles past recognition.

That is what the book will do over the following chapters. Literary works, management archetypes, close analyses of the corporate pathologies that literature diagnosed before the business schools gave them official names.

First, though, back to the Reform Club. Fogg has a great deal to teach.

The Agile-Industrial Complex

Here is a sentence worth saying out loud, without euphemism: the Agile industry has become the largest sale of the obvious in commercial history, and it is not the consultants' fault. It is the consequence of a systemic paradox: the more intuitive the principle, the more expensive its formalization.

Consider the economics of this industry more closely. Allied Market Research values the global Agile implementation market at $27.6–49 billion in 2024–2025, with a projected rise to $140+ billion by 2032–2034.³ For scale: that is comparable to the GDP of Paraguay.⁵ A whole economy built on selling principles that Dickens applied for free in 1836, and Verne in 1872, without ever taking a consulting fee.

The Scrum Alliance, the largest Agile-certification body in the world, reports about a million and a half professionals in its community; the count of certifications issued has crossed two million.⁶ Two million certificates for the right to do what Fogg did without a single course: to respond to change rather than follow the plan. The average price of a two-day Certified ScrumMaster course runs from $1,000 to $2,500, depending on the region. The arithmetic is merciless: the certification business built on Scrum alone is a billion-dollar operation with a steady revenue stream.

SAFe (Scaled Agile Framework) went further still. A full corporate SAFe license, covering trainings, certifications, and tooling, runs a large company several hundred thousand dollars a year.⁷ SAFe offers four levels of configuration, twelve types of certification, and more than seventy-five practices. To describe how people ought to work together. Jules Verne and Pierre-Jules Hetzel solved the same problem over coffee on the rue Jacob.

One qualification of principle is in order here. The problem is not that these are bad or wrong principles. Scrum works; Kanban works; iterations work too, and they worked for Dickens, for the Japanese rakugo masters, and for Verne himself. The problem is that we have turned an engineering practice into a religion. With its own catechism (the Scrum Guide), its own hierarchy (the configurations of the scaled Agile methodologies, or SAFe configurations), its own indulgences (certifications), and its own tithe (licensing fees).

McKinsey, an outfit not readily suspected of anti-corporate radicalism, published a 2021 study titled "Losing from day one." Seventy percent of corporate transformations, it reported, fail to hit their stated targets.⁸ Seventy percent failure, at budgets in the millions and tens of millions of dollars.

Corporations bring in whole armies of certified professionals and seasoned coaches. With frameworks calibrated separately for every level of the organizational hierarchy and for every department.

Phileas Fogg went around the world with a 100 percent success rate. Budget: one bet and a newspaper timetable. Team: one man and one servant. Methodology: common sense, not documented in any project-management manual of any kind.

The analogy is, of course, unfair, and I am prepared to admit it up front. Fogg is fictional; corporations are real enough. A real corporation has thousands of people, legacy systems, regulatory requirements, and its own complicated internal politics. Fogg did not have to clear a change of route through a risk-management committee.

That is precisely the whole point. The complexity of real organizations is exactly the reason simple principles are needed. Not complex frameworks for managing complexity, but simple principles for finding a way through it. Fogg had no adaptivity certificate, and that is exactly why he adapted better than any of today's certified professionals. He had no approved process to observe scrupulously. He had a compass. A goal, a deadline, and the willingness to change route at any moment.

In 2001, seventeen programmers at Snowbird wrote down exactly that: four values, twelve principles on a single page, without commentary. Then the industry took that modest page and turned it into a multivolume encyclopedia. A fair question follows. If the principles are so intuitive that a fictional gentleman applied them 129 years before the Manifesto, what is the encyclopedia of thousands of pages for?

The answer is in the following chapters. For now, take a close look at how Fogg actually did it. Method, not mystique.

Textual Analysis of Around the World in Eighty Days

The Machine and the Man — Fogg as System

The first thing the reader learns about Phileas Fogg, on the very first page, is neither his name nor his fortune nor his habits. It is an extended metaphor. Verne writes: "He lived alone in his house on Savile Row [...]. Was he rich? Without question. But how he came by his fortune, not even the best-informed knew."⁹ Fogg is presented as a living riddle, wrapped in the strict regularity of his rituals. Verne does not tell the reader: this man is clever, well-read, or unusually educated. He tells us: this man is exact.

Precision is the key to understanding Fogg-as-system. Verne describes his morning with surgical detail: "That day, as every day, Phileas Fogg left his house at half-past eleven and made for the Reform Club, taking exactly five hundred and seventy-five steps with his right foot and five hundred and seventy-six with his left."⁹ Five hundred and seventy-five with the right, not one more, not one less. Verne is not simply drawing the typical pedant of his day. He is deliberately building a model. A man who measures the world around him with such pedantic precision is constructing a durable system for himself well before the actual need for one arises.

Passepartout, Fogg's new servant, reads this system as a long-awaited promise of stability. At their first meeting he thinks to himself: "At last I have found what I need. A quiet, measured gentleman. A real machine."⁹ Verne's irony works on two levels at once. For Passepartout, "machine" is a compliment: a predictable master, a quiet regular life. For the reader it is already an omen. The "machine," within a few hours, will set off around the world and demolish every expectation of a quiet life. Verne threads into the fabric of the novel the paradox that will define its whole plot: the most predictable man in London is about to become the least predictable traveler on earth.

It is here that Verne's literary model becomes a genuinely managerial one, applicable to corporations. Fogg is not a chaotic innovator, and he is not a prophet of change. He is not Steve Jobs, blowing up the industry with intuitive flashes on the Apple stage. He is not the "disruptive leader" of the Silicon Valley lexicon. Fogg is a disciplined adapter: a man whose baseline system is so stable that it can absorb chaos without falling apart.

This pattern is closer to the Toyota management philosophy than to the mythology of Silicon Valley.

In the 1950s, Taiichi Ohno built the Toyota Production System on a principle that sounds thoroughly Fogg-like: eliminate waste, standardize the process, and only then adapt to change.¹⁰ Ohno did not call for revolution, and he did not promise a magical transformation in one quarter. He called for the daily discipline of every worker on the line, the kind of discipline that alone makes real adaptation possible. In his view, the standard is not the opposite of flexibility. It is its foundation.

General Motors in the 1980s, by contrast, was an organization that tried to manage complexity through more complexity: bureaucratic layers, sign-off committees, approval procedures for every decision. The result was predictable. The MIT IMVP study (1990) found that the GM plant in Framingham built a car in 40 labor-hours, while Toyota built a comparable car in half that time.¹⁰ Not because Toyota worked faster in the sense of hand-speed. Because Toyota worked more systemically in its very structure. Less waste, fewer buffers, and fewer "correct procedures" that protect habit rather than quality.

Fogg went around the world in eighty days not because he improvised better than his contemporaries. He did it because his baseline system — discipline, precision, economy of motion — left him the surplus resources to improvise when improvisation was necessary. Taiichi Ohno would have approved. A GM transformation committee, probably not.

The Elephant Instead of the Train — Context Determines Method

In the novel's eleventh chapter, Verne constructs a scene that, read correctly, contains everything you need to know about project management under uncertainty.

Fogg and his party arrive at Kholby station, in India, at noon. The conductor calls out: "All passengers off!"⁹ Passepartout is surprised: "But the railway is not finished, is it?"⁹ The on-duty reply: "No, but the papers announced the line was open."⁹ The rails have in fact been laid from Rothal to Allahabad, but between Kholby and Allahabad there remain fifty miles of unlaid track through the jungle. The papers wrote that the road was ready. The road is not ready.

In 1872, Verne described precisely the thing that, a century and a half later, would kill 346 people.

First, though, back to Fogg.

He has three options: wait for the next train (no telling when), walk (fifty miles, impossible on time), or find alternative transport. Fogg chooses the third. For two thousand pounds sterling (roughly £294,000 in today's purchasing power²) he buys an elephant from a local. No haggling, no discussion, no convening of a risk-assessment committee on the safety of mounted elephant travel.

Two elements of the scene deserve close attention.

First: the speed of decision, based on sufficiency rather than optimality. Fogg does not analyze the optimality of the route. He immediately assesses the sufficiency of the transport. Will the elephant get us there in a reasonable time? Yes. Is the elephant expensive, and how much exactly? Yes, two thousand pounds. More expensive than being late and losing the bet? Obviously not. The decision is made in a few minutes. Verne shows the difference between the "correct" decision, waiting for the system (the railway) to work as promised, and the "effective" one: go around the system, using what is physically available here and now. Fogg optimizes for the result, not for the process.

Second: the response to false information from a source people are used to trusting. The papers announced the road was ready. The road is not ready. Fogg does not complain, does not demand compensation, does not accuse anyone publicly. He accepts reality as it is, on the spot, and acts from within it. This is not stoicism. It is operational pragmatism in its pure form. The map disagrees with the territory. Throw out the map.

In 2000, Dave Snowden formalized this intuition as the Cynefin framework: a model that divides decision-making contexts into four domains.¹¹ The simple domain: causes and effects are obvious, the answer is standard and needs no debate. The complicated domain: causes and effects can be established by analysis, and an expert with accumulated experience is required. The complex domain: causes and effects are visible only in retrospect, and an experiment in real conditions is required. The chaotic domain: there are no discernible causes and effects at all, and immediate action is required to create some structure for later analysis.

The railway belongs to Snowden's complicated system; it yields to expert analysis. Schedule, rails, stations: study them with an experienced eye and you get a predictable result. But a railway that exists in the newspaper and does not exist on the ground is already a complex system of a different order. There is no schedule to trust; there is no expert who will say when the rails will appear; there is only reality, fifty miles, an elephant, and two days in hand.

Fogg switches between domains instantly, without a management pause and without convening a committee. Train: complicated domain, standard industry solution, known algorithm. No train: complex domain, experimental solution, local improvisation on the spot. Elephant. That is what genuine managerial flexibility looks like: not adherence to a single method, but the ability to select the method calmly to fit the context.

Turn now to the Boeing 737 MAX, a disaster that unfolded almost a century and a half after the elephant scene and demonstrated with alarming clarity what happens when an organization has forgotten how to switch between domains.

In the five months between October 2018 and March 2019, two Boeing 737 MAX aircraft went down: Lion Air Flight 610 (29 October 2018) and Ethiopian Airlines Flight 302 (10 March 2019). Three hundred and forty-six people died. In both cases the cause was the MCAS (Maneuvering Characteristics Augmentation System), software that automatically corrected the aircraft's pitch.¹²

The Joint Authorities Technical Review (JATR), commissioned by the FAA in 2019, established the following: MCAS was designed as a solution for the complicated domain, an algorithmic correction of a predictable aerodynamic problem. Reality, however, turned out to be complex. The interaction of automation with pilots, with their training, with their cognitive reactions under stress, none of it fit the complicated model. The system depended on one angle-of-attack sensor. One. No redundancy, no cross-check.¹²

The final report of the U.S. House Committee on Transportation and Infrastructure (September 2020) delivered the verdict: a series of faulty technical assumptions by Boeing's engineers, a lack of management transparency, and grossly insufficient FAA oversight.¹³ Not a fluke. Not bad luck. A systemic failure of an organization that had applied a solution from one domain in another. The "correct" engineering process, formal certification, delegated oversight, documentary compliance, worked flawlessly on paper. And killed 346 people in reality, on two different continents, five months apart.

The papers wrote that the Indian railway was ready. MCAS was formally FAA-certified as safe for commercial operation. In both cases the formal system diverged from the actual territory. The difference: Fogg threw out the map and bought an elephant. Boeing kept driving stubbornly along nonexistent rails until two aircraft fell out of the sky.

The Rescue of Aouda — People Over Plan

In the twelfth chapter, Verne does something unexpected: he breaks his own character.

Fogg, the human machine, the man of 576 steps, the man whose daily route is calibrated to the minute, makes a decision that cannot be explained by the logic of the schedule. Somewhere between Kholby and Allahabad, on the back of an elephant bought for a fortune, his party runs into a procession. A young woman, Aouda, is being led to a funeral pyre. Sati: the Hindu rite in which a widow ascends her husband's pyre. Aouda does not want to die on a stranger's pyre, and tears run down her face. She has no choice.

Fogg does. That is the whole fork of the scene. Continue and the schedule holds. Stop and the schedule is immediately at risk of collapse. Twenty thousand pounds sterling, £2,935,637 in today's purchasing power, is a considerable sum even by modern standards. Eighty days, and every hour is counted by the watchmaker of his own schedules.

Fogg stops.

"I still have twelve hours in hand; I can devote them to this matter."¹⁴

Here Verne executes a shift of narrative that readers of an adventure novel rarely notice, but that defines the whole managerial philosophy of Around the World in Eighty Days. Fogg stops being a machine. For the first time in the novel his decision is driven not by the schedule, not by route optimization, not by calculation, but by a value that cannot be expressed in pounds and minutes. The project scope changes. Not because external conditions changed, but because Fogg changed the definition of success.

Passepartout, the loyal practical servant, proposes a Plan B that deserves its own place in literary history. He disguises himself as the dead rajah, lies down on the funeral pyre beside Aouda, and at the moment the flames should have swallowed them both he rises, a living "corpse," and carries Aouda off into the night. The guards are in shock. Passepartout is in soot. Fogg is unruffled.

The maddest Plan B in the history of literature. And it works.

The literary analysis here is transparent, but the managerial point is worth stating out loud. Verne shows the moment when a project ceases to be the mechanical execution of a plan and becomes something more. A scope change: not as deviation, not as a planning error, but as a conscious choice. Fogg does not lose control. He widens the definition of what "control" means. The project is no longer "go around the world in 80 days." The project is "go around the world in 80 days and not stop being human."

The Agile Manifesto would formulate this in 2001: "Individuals and interactions over processes and tools." The first of four values, and by the sense of the whole Manifesto the most important. And, in bitter irony, the most ignored in actual corporate practice under the banner of "Agile transformation." It is easy to print a handsome formula on a poster in the meeting room. It is harder to stop a project worth millions simply because the people inside it are frankly miserable.

Satya Nadella did exactly that. Taking the CEO post at Microsoft in 2014, he inherited an organization that a decade of Steve Ballmer had turned into a machine, though not in the Fogg sense. Ballmer's Microsoft was a machine of metrics: forced stack ranking of employees, internal competition between departments, KPI as religion.¹⁵ Result: a company that missed the mobile revolution, lost the search market, and was losing its best engineers.

Nadella did not optimize the metrics. He changed the definition of success. From a know-it-all culture to a learn-it-all culture. From interdepartmental competition to collaboration. From forced stack ranking to a growth mindset for every employee. A scope change at the level of the whole organization, not a single team. Microsoft's market capitalization from 2014 to 2024 grew more than tenfold and reached three trillion dollars.¹⁵

Fogg saved Aouda and won the bet. Nadella stopped the metrics machine and built one of the most valuable companies in history. Coincidence? No. Pattern. Projects in which people matter more than the plan are not merely more humane. They deliver better results. Not because kindness is good strategy. Because a system in which people are a resource to optimize loses its main asset: the capacity of people to solve problems the system did not foresee. Passepartout on the funeral pyre is not a "resource." He is a man who dreamed up the impossible, not because he was asked to by the procedure, but because it needed doing.

"The Extra Day" — Uncertainty as Resource

The novel's ending is one of the most elegant denouements in world literature. It is also one of the most instructive for anyone who runs a project.

Fogg arrives in London late in the evening. He is certain he is hopelessly late. By his own calculation, the gap is exactly five minutes, five minutes that cannot be made up under any circumstances. Eighty days, three continents, steamers, trains, an elephant, a funeral pyre, a hurricane in the Atlantic, and, in the finale, five minutes. The project has failed.

Fogg accepts this with the same unruffled calm with which he accepted every prior catastrophe and setback. He does not blame circumstances, he does not look for culprits, he does not demand renegotiation of the terms. The project has failed. Failed, then.

Then Passepartout notices the obvious. What had been obvious from the start, but which no one, not Fogg, not his opponents, not Detective Fix, had taken into account. Traveling east, they had crossed the international date line. They had gained a full day. Today is not Sunday but Saturday. Fogg is not five minutes short. He is twenty-three hours and fifty-five minutes ahead.

Verne pulls off a perfect plot twist without any deus ex machina. The international date line is no invention. No accident. No miracle. It is a constraint that existed from the first page of the novel. Fogg knew the route. Fogg knew perfectly well he was traveling east around the earth. Fogg could, in theory, have calculated the gained day in advance with a simple almanac at his elbow. He simply did not. His model of the world, precise, pedantic, 576-steps-with-the-right-foot, did not include what he did not know he did not know.

This is not Fogg's mistake and not a gap in his method. It is a fundamental property of reality, and there is nothing to be done about it.

In 2002, U.S. Secretary of Defense Donald Rumsfeld offered a formulation that became famous: "There are known knowns... There are known unknowns... But there are also unknown unknowns: the things we don't know we don't know."¹⁶ The formulation was laughed at. It should not have been. Rumsfeld described an exact taxonomy of uncertainty, the same one Verne had staged 129 years before the Pentagon press briefing.

The international date line: an unknown unknown. Fogg could not have planned for it because he did not know it was relevant. Here is the central paradox. It was that very "unknown unknown" that saved the project. Not control. Not the plan. Not foresight. A fact that was not in the model.

Modern project management is afraid of uncertainty. Risk registers, contingency buffers, Monte Carlo simulations: all of it is tooling for converting the unknown unknown into a known unknown. A noble goal. It also misses the point. Uncertainty is not only a threat. Uncertainty is a resource. The international date line was not in Fogg's risk register. It was better than any register. It was in reality itself.

SpaceX illustrated the same principle with engineering directness and without extra lyricism. Between 2006 and 2008, three consecutive launches of the Falcon 1 ended in failure.¹⁷ The first: an engine fire twenty-five seconds after liftoff. The second: instability in the second stage and loss of thrust already on an orbital trajectory. The third: a stage-separation collision in the upper atmosphere. Each failure cost the company dearly, and the company was already balanced on the edge of bankruptcy.

The fourth launch, on 28 September 2008, was at last a success. Falcon 1 reached orbit. Not because SpaceX had finally "gotten it all right" on the third try. Because each previous failure was not a catastrophe but information for the next iteration. Not loss, precisely valuable information. Unknown unknowns were becoming known knowns with every new explosion on the launch pad. Elon Musk would say later: "Failure is an option. If things are not failing, you are not innovating enough."¹⁷ Rhetorically the phrasing is pure Silicon Valley, but the principle behind it is Vernian to the core. Fogg did not plan for the international date line as part of his strategy. SpaceX did not plan for a stage-separation collision. Both, Fogg and SpaceX alike, were working within a system that allowed uncertainty to become a resource rather than a catastrophe.

Most failed projects do not fail from a shortage of control. They fail from its excess. An organization obsessed with eliminating uncertainty eliminates, along with it, the possibility of discovering what it was not looking for. A risk register that catalogs every known risk creates the illusion of completeness, and it is precisely that illusion that blinds. Boeing accounted for every known aerodynamic factor of MCAS and missed the unknown one: the reaction of live pilots under stress. Fogg did not account for the international date line and gained a full day. The difference: Fogg did not consider his model complete. Boeing did.

From Literature to Practice

Phileas Fogg won the bet for a reason no project manager would ever put in the plan: he did not know it was impossible.

Not in the romantic sense in which motivational speakers call from the stage to "dream big." In the literal, operational sense. Fogg did not know that the international date line would hand him exactly one day. He did not assume that Passepartout would dream up an insane plan involving a funeral pyre, and he would not have dared it himself. He did not suspect that the elephant would prove faster than the train. Every one of these facts was outside his model, and every one of them, in the end, saved the project.

Today's executives, by contrast, lose winnable projects precisely because they know too much about what cannot be done. Their models are complete, and that is the problem. Their risk registers are exhaustive, written out to the line. Their frameworks are ISO-certified. Their processes are approved by committee. Their plans are signed off at three levels. And all this knowledge, of risks, of complications, of impossibilities, paralyzes. Not because information is harmful. Because the completeness of the model creates the illusion that the model is reality.

Verne wrote a novel about this in 1872. Not a business case. Not a white paper. A novel. And the novel turned out to be more accurate, because literature is not afraid of paradox. Literature is not obliged to prove return on investment. Literature can say: the most exact man in London is the one who is prepared to throw out the schedule and buy an elephant.

This book is a deliberate continuation of the same method. Literary works and management archetypes, arranged into a single arc. Not because literature is "also useful for business," as corporate trainers like to say. Because literature saw the patterns first and formulated them before management did.

Mary Shelley in 1818 described what happens when the creator abandons the creation, and the creation takes revenge. That was 175 years before the first corporate "transformation project" was abandoned halfway. Arthur Conan Doyle in 1887 described diagnostics: the art of separating the relevant from the noise. That was a century before data science became an industry. Borges in 1941 described a civilization that made a map on a one-to-one scale and died under its weight. Half a century before Goodhart's Law became a management meme.

Every one of these writers worked purely by intuition, without a management school behind him. Every one, more accurate than a certified consultant with an MBA. Not because they were smarter than today's consultants, or better educated. Because literature describes living people, and project management, at its root, is nothing but people. Not processes, not statuses. Not frameworks, not methodologies. Not certifications, not standards. People under pressure, making real decisions under uncertainty.

The following chapters are about the rest of what literature knew about management, and what management still does not.

To be continued. In the next chapter: Paris, 1872 — Verne and Hetzel invent iterative delivery 129 years before the Manifesto, and Le Temps prints the chapters of the trip around the world like releases: one a day, no right to delay.

Footnotes

¹ Jules Verne. Around the World in Eighty Days (1872/1873). Hetzel, Paris. Public domain. Quotations are given in the author's translation. Original publication: Le Temps, November–December 1872 (daily serialization), followed by a standalone edition from Hetzel in January 1873. The wager scene: Chapter III of the original.

² Purchasing power calculated using the Bank of England inflation calculator: £20,000 in 1872 is equivalent to £2,935,637 in 2026 at an average inflation rate of 3.30 percent per year. Sources: Bank of England Historical Exchange Rates; UK Inflation Calculator (officialdata.org).

³ Allied Market Research and Verified Market Research estimate the global enterprise agile transformation services market at USD 27.6–49.0 billion in 2024–2025, with projections to reach USD 140+ billion by 2032–2034. T2 market research data, 2024–2025.

⁴ Around the World in Eighty Days was published daily in the Paris newspaper Le Temps from 6 November to 22 December 1872. The standalone edition appeared from Hetzel on 30 January 1873. The novel became one of Verne's greatest commercial successes; its print runs exceeded all his previous publications. See Dumas, Olivier. "Correspondance inédite de Jules Verne et de Pierre-Jules Hetzel" (1999–2002).

⁵ World Bank GDP data 2024: Paraguay GDP USD 44.46 billion (2024 official data). Comparison illustrative — the Agile transformation market size rivals the entire economic output of a mid-sized nation.

⁶ Scrum Alliance. "About Scrum Alliance" and annual membership data, 2026. Global community of approximately 1.5 million professionals; 2 million credentials issued milestone (GlobeNewswire, June 2026). CSM course pricing: USD 1,000–2,500 (varies by region and trainer). T2 source: organizational self-reporting.

⁷ Scaled Agile, Inc. SAFe licensing and certification pricing, 2024–2025. Individual certification costs range from $1,000 to $3,000 (varies significantly by certification type and organization size); enterprise licensing costs vary substantially by organization size. Certification paths include 12+ role-based certifications. Pricing data from public course listings and partner program documentation.

⁸ McKinsey & Company. "Losing from day one: Why even successful transformations fall short." McKinsey Quarterly, December 2021. Survey of 1,000+ organizations: approximately 70 percent of transformation programs fail to meet stated objectives. T2 source: consulting research with disclosed methodology.

⁹ Jules Verne. Around the World in Eighty Days (1872/1873). Hetzel, Paris. Public domain. All quotations from the novel are given in the author's translation. Chapter I (description of Fogg, daily route: 575 steps with his right foot and 576 with his left, per the Verne original), Chapter II (Passepartout, "a real machine"), Chapter XI (Kholby station, the newspaper announcement of the railway's completion, the purchase of the elephant). Translator's note: the compound shorthand — «the man of 576 steps», «576-steps-with-the-right-foot» — deliberately mirrors the metonymic figure of the Russian original.

¹⁰ Womack, James P., Daniel T. Jones, Daniel Roos. The Machine That Changed the World: The Story of Lean Production. Free Press, 1990. The MIT International Motor Vehicle Program (IMVP) study found that Japanese manufacturers (including Toyota) produced comparable cars in half the labor hours of their American counterparts (the GM Framingham plant: 40 labor hours per car in the 1980s). T1 source: five-year MIT academic study costing $5 million. See also: Ohno, Taiichi. Toyota Production System: Beyond Large-Scale Production. Productivity Press, 1988.

¹¹ Snowden, David J., Mary E. Boone. "A Leader's Framework for Decision Making." Harvard Business Review, November 2007. Cynefin framework: simple (obvious), complicated, complex, chaotic domains. T1 source: peer-reviewed management research.

¹² Joint Authorities Technical Review (JATR). "Boeing 737 MAX Flight Control System: Observations, Findings, and Recommendations." October 2019. Commissioned by the FAA Administrator. Findings: MCAS design relied on single angle-of-attack sensor input without redundancy; assumptions about pilot response time proved inadequate in operational context. T1 source: multi-national regulatory review body. See also: Federal Aviation Administration. "Summary of the FAA's Review of the Boeing 737 MAX." January 2020.

¹³ U.S. House Committee on Transportation and Infrastructure. "Final Committee Report: The Design, Development & Certification of the Boeing 737 MAX." September 2020. 238 pages. Conclusion: "The crashes of Lion Air Flight 610 and Ethiopian Airlines Flight 302 were the horrific culmination of a series of faulty technical assumptions by Boeing's engineers, a lack of transparency on the part of Boeing's management, and grossly insufficient oversight by the FAA." T1 source: congressional investigation with subpoena authority. See also: National Transportation Safety Board (NTSB) accident investigation reports for Lion Air Flight 610 (2019) and Ethiopian Airlines Flight 302 (2019).

¹⁴ Jules Verne. Around the World in Eighty Days (1872/1873). Hetzel, Paris. Public domain. Chapters XII–XIII: the rescue of Aouda from the sati rite. Quotation — author's translation. Original French: "J'ai encore douze heures d'avance. Je puis les consacrer à cela." (Ch. XII, canonical Hetzel 1873 edition). Note: the RU master (v1.0.20 text baseline) faithfully renders "twelve hours in hand" and "devote them all"; EN preserves this reading. KN1-FAKTY-6 (Iskra Vier-Augen S284-03): earlier draft misquoted the French; corrected to canonical Verne — 12 hours committed, not partial.

¹⁵ Nadella, Satya. Hit Refresh: The Quest to Rediscover Microsoft's Soul and Imagine a Better Future for Everyone. Harper Business, 2017. Stack ranking elimination, culture shift from "know-it-all" to "learn-it-all." Microsoft market capitalization: ~$300 billion (January 2014) to $3+ trillion (2024). T2 source: CEO autobiography with verifiable market data.

¹⁶ U.S. Department of Defense. News briefing by Secretary Donald H. Rumsfeld. February 12, 2002. "Known knowns, known unknowns, unknown unknowns" taxonomy. Transcript available via DoD archives. T1 source: public government record.

¹⁷ SpaceX Falcon 1 launch history: Flight 1 (March 24, 2006): engine fire at T+25s; Flight 2 (March 21, 2007): second-stage instability; Flight 3 (August 3, 2008): stage-separation collision; Flight 4 (September 28, 2008): successful orbital insertion. Sources: NASA Commercial Orbital Transportation Services (COTS) program documentation; SpaceX mission updates (public). T1/T2: government program records + corporate disclosures.