Business Rewritten

Change is hard. Business Rewritten was created for intractable problems that are complex, interconnected, and resistant to straightforward solutions. Conventional tools such as strategic planning, Six Sigma, SWOT, process reengineering, and AI-assisted analysis repeatedly miss the patterns that matter in fast-moving settings. Change falters because the things that actually drive outcomes go undetected: human dynamics, path dependencies, and hidden themes.

Business Rewritten introduces the Business Rewrite Framework, a different way of thinking about a company and of organizing what you know about it. The framework uses story as an analytical discipline rather than just a way to communicate. Every organization is a character in its own story, with customers, employees, competitors, boards, and regulators all playing a part. The framework is not a replacement for process reengineering, financial modeling, or operational improvement methods; it is the overarching framework that sits above them and points them at the right problems for the right reasons. What it adds is the ability to:

1. Counter the natural tendency to attack symptoms rather than causes, dissecting complex problems to discover what really makes a business tick.
2. Surface unrealized opportunities, eliminate points of resistance, and clear the barriers that block change.
3. Drill down into the detail while keeping the high-level perspective in view, so nothing important gets lost.

Using the power of story, the Business Rewrite Framework achieves one of the hardest things in business: effecting change successfully.

How it works

The framework begins by clarifying the objective, and from whose vantage point. Six author personas - Creator, Change Agent, Problem Solver, Opportunist, Risk Mitigator, and Investigator - each apply the framework through their own perspective. The same method can serve a founder writing the first chapter of a new business, a company facing a technology revolution, or a CEO evaluating a potential acquisition.

From there it maps the backstory: the settings the company has operated in, the events that shaped it, and the cast of characters who passed through. Then comes the work of extracting the themes, the patterns that explain why some things worked and others did not. Only after that does the framework turn forward, creating scenarios and assessing risks and opportunities as the next chapters are drafted.

Themes are where the real work happens. Delving into them reveals the root causes of problems, the barriers to progress, and the opportunities and risks concealed beneath. It is common to find repeated patterns, connections, and problems emerging from complexity; treating each one as a theme gives you a way to navigate and understand the whole story rather than a pile of disconnected facts.

The framework works because narrative is how people process complexity. Engaging with a story lets you take in more information, and gives complex ideas a shape that is memorable, relatable, and meaningful. The same property explains a common failure the framework is built to avoid: most change initiatives fail not because the destination is wrong, but because the backstory creates barriers the change plan never accounted for.

The book was written with AI in mind. The framework structures the analysis; AI provides the speed. The combination is powerful as long as the analyst stays the author by choosing the persona, framing the call to action, demanding evidence, and deciding what the story actually is. The moment the analyst becomes a passive reader of the tool's output, it stops working.