Afterword. Eleven Questions

What this afterword is about. Twelve chapters, distilled into eleven questions (the pilot chapter offers not a question but a frame). Each question helps a team see what usually goes unnoticed because it stands too close. The book does not prescribe; it restores the right to ask questions from outside a framework.

The book has ended. What do you hold in your hands after twelve chapters?

Not a methodology: a methodology fits on one page and is sold in an industry valued in the tens of billions of dollars. Not a set of examples: examples grow stale before the next edition appears. Not a theory: a theory tested by literature and untested by practice remains fiction.

You hold eleven questions. Each question helps you see what usually goes unnoticed because it stands too close.

The Eleven Questions

Twelve chapters yield eleven archetypes, and eleven questions. A question does not prescribe an action. It calibrates the vision. The pilot chapter stands apart: it offers not a question but a frame.

The Frame. Fogg. Map and Territory

In the pilot chapter, Fogg learns at Kholby Station that the railway announced by the newspapers as complete breaks off in the middle of the jungle, and within minutes he purchases an elephant. He neither complains nor demands compensation: the map has diverged from the territory, and one discards the map. Boeing kept driving down the nonexistent rails of formal certification; Fogg switched domains and drove down reality. The question: when the plan diverges from reality, do we redraw the map — or do we buy an elephant?

1. Verne. Iteration

The cycles of Dickens, Verne, and rakugo are described in the first chapter as convergent evolution across three cultures: create an increment, deliver it to an audience, receive feedback, correct. One and the same pattern arises in London in 1836, in Paris in 1872, and in Tokyo of the same decade, independently. The question: does our work cycle deliver an intermediate result to an audience — or are we firing the final version into the dark?

2. Frankenstein. Operational Model

Victor works in isolation for two years, launches the result, is horrified, and flees the laboratory. Mary Shelley in 1818 described what contemporary development calls "flight from the laboratory": the creator does not think through what will happen to the product after release. The question: am I creating a product — or am I creating a product plus the operational model of its life?

3. Holmes. Observation

"I never guess," says Holmes in The Sign of Four. "It is a shocking habit — destructive to the logical faculty." Data are gathered on site, not in the office; in observation of behavior, not in a report of it. The question: am I observing what people do — or what they say?

4. Borges. Measurement

The Lottery in Babylon: every free act gradually enters its sphere. Story points, velocity, OKRs — tools that become institutions and then become the only reality in which a team knows how to describe itself. The question: does this metric measure something that matters — or the thing we have learned to measure?

5. Nemo. Bootstrap Team

In the fifth chapter, the positive archetype is not Nemo with his solitary Nautilus but Cyrus Smith with the team of The Mysterious Island: recruitment by competence, isolation as strategy, a leader who knows the subject, crisis as the normal operating mode. Nemo is the counter-example: a monoculture of one genius, sealed in a submarine without succession. The question: is this a bootstrap team of specialists — or a cruise ship of process?

6. Mina Harker. Distributed Knowledge

Stoker's Team Light would have had no chance against Dracula without Mina's typewritten report. Six people, six fragments of the truth, plus one document in which the fragments are assembled and redistributed back to the team. Before the transcription — six separate truths; after it — a shared context. The question: where is the single source of truth stored — and who is responsible for the assembly of the fragments?

7. Jekyll. Declared and Practiced

Stevenson in 1886 described what Argyris and Schön in 1978 would formalize as the gap between espoused theory and theory-in-use. The declaration lives on the front stage (the mission statement, the poster in the conference room); the behavior lives on the back stage (the Slack channel #vent, the conversation in the parking lot). The gap grows through defensive routines and rests against undiscussables — topics that are not formally forbidden but that no one discusses. The question: does what we declare about ourselves match what we do — or does an undiscussable gap exist?

8. Don Quixote. Team Mythology

Cervantes formulated the four laws of team mythology four centuries before Karl Weick described sensemaking: the founding myth, the duet of visionary and pragmatist, the adventure as narrative, the collision of the myth with reality. Teams hold together not on regulations but on interpretive frames that permit joint action. A myth that cannot be rewritten under collision with reality kills the team; a myth that renounces itself under every collision kills it too. The question: on what founding myth does the team rest — and does that myth allow for local rewriting on collision with reality?

9. The Time Machine. Labor Horizons

Wells, Autor, Acemoglu-Johnson, Polanyi: the four laws of labor horizons. The technology of the "assistant" reorganizes the structure of work around itself; the polarization of tasks into routine and nonroutine unfolds by mechanism, not by choice; the distribution of the fruits is a political process, not an economic one; society responds to market pressure with a counter-movement. The question: which of our tasks are routine and which are not — and where is the balance of work-distribution and its fruits shifting?

10. NIICHAVO. Selection

The Strugatsky brothers described a team that cannot be assembled through recruitment — such a team is assembled through meaning. Monday begins on Saturday not because the labor code requires it, but because for a NIICHAVO employee the distinction between work and life does not exist. Command-and-control becomes mechanically impossible: one cannot command a person who does not work for an order. The question: do we have selection by meaning — or by hiring?

11. The Plague. The Sustained Crisis

Camus described a team that forms not through calling, but through the refusal to leave. Doctor Rieux, Tarrou, Castel, Rambert, Grand, Paneloux: common decency instead of heroism, parallel obligations without hierarchy, convergence without architecture, the discipline of continuation instead of the horizon of victory. A sustained crisis has no finale in which victory becomes obvious; it has only two modes of ending — disqualification or continuation until the pressure lifts by itself. The question: what do we do when optimization stops working, and the crisis continues?

The Question You Reach for First

These eleven questions are not a table of "if situation X, apply question Y." The book begins with a protest against such tables — against an industry that packaged common sense in complexity and thereby destroyed common sense itself.¹

Questions work differently. What you see through a question is determined in part by what you were already looking for. The team that first reaches for Holmes's question is searching for a diagnosis: what is broken here. The team that first reaches for Camus's question is searching for discipline: how to continue. The team that first reaches for Borges's question is defending itself: measurement has drowned us. The question you reach for first says more about your team than the situation itself does.

And one more thing. The very choice of question is a diagnostic act. Borges in "The Lottery in Babylon" showed that the attempt to measure chance through an institution turns the institution into a new form of chance. The meta-measurement of which question to use has the same logic: the attempt to systematize the choice of question turns the choice into a new set of rules, requiring a new question to verify.

The book's diagnostics, therefore, cannot be algorithmized. They are applied by hand, and under the responsibility of the person who applies them.

What This Book Is Not

This book does not deny agile methodologies. Standups, retros, demos, sprints — these are normal working practices invented long before they were given names. What the book denies is the transformation of practices into institutions, of rituals into fetishes, of language into an industry.

This book does not propose "be like Holmes," "be like Rieux," or "be like Smith." Literature does not offer role models — it offers mirrors. Holmes is effective because he is Holmes. A team that tries to become Holmes stops being itself and does not become Holmes.

This book does not feel nostalgic for a "real" management of some previous era. The nineteenth century was not an age of common sense — it was the age of factory children, coal mines, and colonial enterprises. The literature we read was written against the management that surrounded it, and it remains relevant precisely because its authors saw what their contemporaries preferred not to notice.

Where Does the Elevator Go

In Intermezzo III, the elevator of digital transformation rises one floor per iteration, with a strategic retrospective between floors. Alice asks: "May I press directly to the one-hundred-and-twenty-seventh?" The cat explains that this would violate the methodology.

The elevator is not going anywhere. It is not a functional elevator — it is the methodology theater in the form of an elevator. The teams that are doing the work stepped out of the cabin long ago and are climbing the stairs on foot. Those who remained in the elevator are discussing how to improve the process of ascent.

This is not a cynical conclusion, but a diagnostic one. The elevator is a normal tool in the right building; the theater of the elevator is a pathology that emerges when the tool becomes an end in itself. The questions collected in this book help distinguish one from the other.

Literary Analysis of Business

The approach we applied to twelve literary texts is named in the preface: Literary Analysis of Business. It is not a theory and not a school. It is a reading skill: the ability to see in a literary text, written long before the emergence of contemporary management, a diagnosis of the phenomena that management would later describe and often formalize worse than literature had done intuitively.

The method does not claim to exhaust the phenomena. Eleven questions are not all possible questions; they are the ones that emerge convincingly from the texts we read. Dostoevsky, Chekhov, Kafka, Platonov (who works for us in the ninth chapter as the Russian voice of The Foundation Pit, not as a separate question), Beckett could give another ten. Perhaps in the next book. Perhaps the reader will do this work themselves, opening a favorite novel not as entertainment but as a diagnostic instrument.

A Quiet Finale

Literature does not offer instructions — it offers a language. Not algorithms, but ethical supports. Not technologies of management, but a vocabulary for describing those layers of work that lie deeper than procedures.²

The team that has read to this page has not received solutions. It has received eleven questions and the right to choose which one to ask today. The longer a team works together, the more often it will change questions, and the more precisely those questions will show it what cannot be seen from within a single frame.

The book has ended. The team has not.

¹ Chapter 0, central thesis: "the industry of agile methods sells corporations common sense packaged in a complexity that destroys common sense itself."

² Paraphrase of the closing of Chapter 10: "literature preserves what management does not preserve — a language for describing those layers of work that lie deeper than procedures."

Comandante FolkUp Co-author: Alice (PM, FolkUp ecosystem) · Editor: Iskra Translator (English edition): Lolik (S1LOLIK) 2026