Menschgeist

Most organizations that “go agile” start with teams. They rename projects, install new tools, introduce sprints, and send a few people to Scrum or SAFe training. For a while, things look better. Then a familiar pattern appears: teams move faster, but the rest of the organization remains slow, opaque, and over‑controlled. Work gets stuck in HR processes, finance routines, legacy IT, or compliance procedures that were never designed for continuous change.

In the AO model, this is not a side issue. It is a structural problem. Agility is understood as a system dynamic, not a local method. If we want agility to propagate across the whole company, we must design the “hidden infrastructure.” This infrastructure makes adaptation possible. It is the social and technical platform on which ventures, programs, projects, and swarms live and evolve.

When I say platform in AO, I do not mean a software product alone, nor a classic “shared services” department. Platform consists of a cluster of people, capabilities, and routines. These offer reusable services to the rest of the organization. They include HR and learning, finance and controlling, IT and data, facilities, legal and compliance, and other enabling functions. In a traditional design, these functions are organized as silos, optimized for internal efficiency, budgets, or risk avoidance. In an AO design, they create a unified platform. Its main goal is to liberate as much energy as possible. This energy is directed towards value creation at the edge.

This book is about that platform. It is about how to design and run it so that:

• ventures and swarms can move fast without creating chaos or hidden risk
• people experience support, clarity, and fair rules instead of bureaucratic noise
• the enterprise can meet its obligations to owners, regulators, and society while still learning and adapting continuously
• system partners and customers experience a coherent organization, not an internal maze.

You will not find a universal blueprint here. There is no single ideal AO platform structure that you can copy‑paste into any company. Instead, you will find a set of principles, patterns, and examples. These are drawn from more than a decade of experimentation with AO in different contexts. Some examples come from full AO implementations. Other examples come from partial “platform moves” inside more traditional organizations. In these cases, a single function started to operate as a platform. This occurred long before the rest of the company caught up.

The book is written for two kinds of readers. The first is the COO, platform leader, or head of an enabling function. This person needs to keep the organization compliant and reliable. At the same time, they must remove friction for ventures and swarms. The second is the AO coach or organizational designer. They help leaders reshape structures, decisions, and interfaces. Their goal is to embed agility throughout the entire system. It should not be just an island in IT or product development. You might recognize yourself in both roles.

The structure of the book reflects this dual audience. Part I introduces the role of Platform in the AO model. It links the role to AO’s core principles. These include five experiences: enterprise, organization, people, customers, and system partners. Part II presents a small number of platform principles, each with practical design questions, patterns, and signals to watch. Part III tells short case‑based stories. These stories show how real organizations used these principles to change a piece of their platform. They highlight what went wrong and what they learned.

You can read the book linearly, or jump straight to a principle or example that resonates with your current situation. If you lead a function today, start by mapping your existing services. Compare them against the AO platform principles. Notice where your work behaves like a silo. Also, observe where it already behaves like an enabling platform. If you are an AO coach, you might use the questions as lenses in your next diagnosis. You can also use the patterns in your next workshop.

Throughout, I will invite you to treat the AO platform not as a finished design, but as a living product. It has users: ventures, swarms, leaders, and partners. It offers a value proposition for what it makes easier and safer. There are constraints such as regulation, risk, and cost. It includes a Roadmap detailing how it will evolve as the organization grows and the environment shifts. Thinking this way can be uncomfortable for functions that are used to fixed mandates and annual plans. Yet it is precisely this shift—from static support departments to an evolving enabling platform—that makes systemic agility possible.

If you are reading this, you probably already feel that your current platform is both essential and under‑designed. My hope is that the pages that follow will provide you with enough structure to act. They will also give you enough freedom to adapt. This way, you can build a platform that quietly powers an organization. Such an organization is capable of learning and regenerating itself over time.