# Introduction 🎧 [Listen to the Introduction](https://thetwoproject.com/player.html?src=https%3A%2F%2Ftheowner-audio.s3.us-east-2.amazonaws.com%2FThe_Owner_Introduction.mp3\&chapter=intro\&type=gitbook) We wrote this book as teachers as much as practitioners. In classrooms, we kept asking what our students should become in an AI-rich world: faster prompt writers, or people who can evaluate, take responsibility, and redesign real work. That question pushed us beyond curriculum into a harder one: if work is changing, what should organizations look like so people can do accountable, high-quality work with AI? To find out, we talked with industry partners living these tensions every day. Leaders under pressure for speed. Operators carrying context no system captured. Teams stuck between compliance and growth. Their stories shared a pattern: the failures were rarely about the model. They were about who owned the process the model was part of, and what happened when nobody did. AI didn't create dysfunction in these organizations. It accelerated what was already there: unclear authority, misaligned incentives, workflows no single person owned. AI does not remove work. It moves work. The story follows a consulting firm trying to survive a market that rewards speed over responsibility, and the people who have to decide what they are willing to answer for. It begins with pilots and demos and the optimism that comes with a powerful new tool. It ends somewhere harder and more honest, with the question of what organizations must change about themselves before AI can change anything for them. The characters and companies are fictional. The patterns are not. We wrote it as a novel because the logic of organizational change lives in postmortems where no one raises their hand, in career moves that look like demotions, in the slow work of earning trust one workflow at a time. You might read as a leader deciding what to delegate, as a teacher deciding what kind of professional to form, or as a builder deciding whether your work will optimize a task or strengthen a whole system. The answer is not complicated. But it is hard. We have a story about people who stayed with the question long enough to learn why. ## Disclaimer We used large language models to craft a novel about what happens when organizations use AI without owning the process. The irony was not lost on us. AI agents drafted, polished, and revised this manuscript across hundreds of iterations, occasionally producing confident prose built on incomplete context, behaving, in other words, exactly like the systems in this book. We decided what stayed, what changed, and whose name went on the outcome. We caught what we caught. We missed what we missed. The gates were ours. All remaining errors are strictly carbon-based. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://thetwoproject.gitbook.io/the-owner-preview/introduction.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.