Preface: Structures Don't Need Villains
📖 Who's Collecting at the Door ｜ 📖 Full Edition
Preface: Structures Don't Need Villains
1. Four Headlines
Imagine that one day in October 2026 you pick up your phone and see four headlines.
One says AI will replace a large share of white-collar work, and anyone who doesn't learn it will be left behind. One says a long-established restaurant group and the partner it has worked with for more than fifty years have parted ways amicably, each taking what it needs. One says the myth of young people's micro-entrepreneurship has collapsed, and going back to a salaried job is the safe choice. And one is about an entertainer who was told by a show's host that she got the short end of things because she didn't have enough backbone.
Four headlines, four explanations: technological progress, an amicable split, naive founders, a flaw in someone's character. Each explanation is partly true. But they have one thing in common: none of them tells you where the money went.
Four of this book's nine chapters start from these four headlines (see Chapters 1, 2, 7 and 9).
2. Seeing How Money Flows
I have come to believe that life is, to a large degree, a game of strategy. The game itself is not what should frighten you. What should frighten you is not knowing who else is at the table, who wrote the rules, and who takes a cut of every hand.
And the story follows the money. The side collecting the money always has a reason to tell a pleasant story: transformation, upgrading, professionalization, win-win. The side paying hears a different story most often: you didn't try hard enough, you aren't tough enough, you can't keep up with the times. Nobody necessarily invents either story on purpose. Wherever the money flows, someone there is willing to tell the story a little more smoothly.
So this book uses a single method. Each time you hear an explanation, don't ask first whether it is right. Ask: where is the money flowing from, and to where? Whichever exit you take, who is standing at the door collecting?
That doesn't mean every explanation is false. AI really is useful, just as computers and the internet really were useful. The technology is real and the story is real; they happen at the same time, but they are not the same thing (see Chapter 1). Seeing how money flows is how you tell the two apart.
3. Where I Stand
I have worked in R&D, written embedded systems, solved customers' problems in the field, and later worked in corporate strategy. Some of the companies I worked for were expanding, some were buying up others, and some were slowly shrinking. As a child I grew up next to my family's small trading business; I watched it expand, and I watched it fall into infighting because it could not collect what it was owed. Many of the examples in this book were seen from those positions.
But I have to be clear about something. I spent most of my career in companies that were growing, and I ran into real backstabbing only once. Part Two will argue that where a person stands decides what they see (see Chapter 4). I am a position too, a single sample.
So you need not take everything I saw on trust. A better way to read this book is to take its questions and check them against what you have seen yourself.
4. What This Book Is Not
It does not teach you how to win. There are already plenty of books and courses that do, and most of them assume you are standing on a fair stage. This book is about the places where that assumption fails.
It is not against technology, and it is not against making money. Someone else doing well has not necessarily taken anything from you; the world is not zero-sum everywhere (see Chapter 4).
Nor does it hunt for villains. This is the point I most want to make up front. Very few of the companies, platforms, hosts and HR departments in this book set out to do harm. Each of their steps is a rational response to the step before; but once the loop is complete, the result lands on someone who did nothing wrong. Structures don't need villains. Precisely because they don't need villains, they are hard to see, and easy to describe as your own problem.
5. How to Read This Book
The book has three parts, and each asks one question.
Part One (Chapters 1 to 3) asks: what shape is this structure? From an R&D department quietly replaced inside a company, to chicken that no longer tastes like chicken, to the entry fee charged at every exit.
Part Two (Chapters 4 to 6) asks: why can you see it when others can't? And the reverse: why can others see it when you can't?
Part Three (Chapters 7 to 9) asks: once the cost of a structure lands on one person, how does it get described as that person's flaw?
The conclusion tries to answer: knowing all this, what can you do?
Almost every example in the book carries a date, most of them in 2026. This is deliberate. Ten years from now, the companies in this book may have gone public or been sold, the shops may have closed, the platforms may have been renamed, and AI may have been replaced by the next round's name. By then these examples will have become a record: the world as one person saw it in 2026.
What you should take away is not the examples but the method. Many chapters end with a few questions that can be asked without any inside information, and that will not stop working because a platform or a technology changes its name. It doesn't matter if you don't know the people in this book or never heard of the controversies. The examples are a record; the method is a tool. Records age; tools don't.
Each chapter can be read on its own; chapters point to one another with "(see Chapter X)". Sources and my other articles are cited by numbered notes; in this web edition they appear at the end of each chapter.
The title comes from a question in Chapter 9: whichever exit you take, who is standing at the door collecting? The subtitle is the conclusion's answer. The nine chapters in between are the road from the question to the answer.
| 📖 Back to Contents | Chapter 1: What Financialization Cuts Is Not R&D, but the Word "No" → |
|---|