How to Read This Book

This book is written to be read from start to end. Each part also stands on its own, so if you prefer to jump in from the side, pick the one that matches where you are right now.

Part One: System

The System is the operational model at the heart of AME3. It defines how your enterprise leads, governs, and evolves.

The Strategy answers what to evolve and where to invest. Three strategic doctrines guide this. Empirical Control structures your learning through Anticipate-Advance-Assess cycles at multiple timescales. Overall Optimization ensures that local improvements benefit the entire enterprise, not just the unit making them. Evolution Focus maps your products along their evolution path, from genesis to commodity, so you invest where it matters most.

The Leadership System introduces three balanced leadership functions: the Owner, the System Lead, and the Team. Together they form a triangle of forces that keeps the organization stable yet adaptive. You will learn why leadership is a system design challenge, not a question of individual traits. Each function carries clear responsibilities: Owners set direction and balance opportunity against risk. System Leads develop people and improve the work system. Teams manage and execute work while driving quality and customer satisfaction.

The Rules establish a minimal yet sufficient framework for enterprise-wide collaboration. They operate on two levels: the Arena, where Teams create products and services, and the Enterprise, where strategic decisions shape the portfolio. You will find leadership functions, artifacts, and constraints at both levels, just enough structure to enable integration with proven methods like Scrum, LeSS, and Kanban, without prescribing how to do the work.

Part Two: Playbook

The Playbook is your step-by-step guide for getting started. It turns the System into action without requiring a large-scale transformation.

It begins with Slicing the Organization and Slicing the Product, which explain how to design Teams and product architecture as a single, evolving system. They provide the foundations for every structural decision that follows.

The first entry point is the enterprise. You start the game at the enterprise level by defining the Leadership functions: the Enterprise Owner, Accountable Representatives, and Enterprise System Lead. You adopt the Rules as your shared operating agreement, analyze your product portfolio for innovation potential, and build an Enterprise Backlog that orders all strategic Goals. Then you launch the first Tournament, the enterprise-level cycle where strategy meets reality and adjusts based on evidence. Finally, you define your first Arena and its Ambition.

The second entry point is the Arena. You start the game in an Arena from one of three starting situations: a brand-new product independent from existing processes, an existing work system that already uses agile and lean practices, or an established product that has not yet adopted them. Each path provides detailed steps, from setting up a Leadership System with Arena Owner, System Lead, and Teams to creating a single Backlog and starting the first Match.

You do not need to reorganize everything at once. Employees move to Arenas as they are needed. The rest of the organization continues operating as before. Improve the Play of the Old Game provides a gradual improvement path for these parts: retrospectives in the Match rhythm, value stream analysis, Kanban systems, and team formation, until they are ready to become Arenas themselves. The enterprise evolves one Arena at a time, guided by strategic Goals and governed by the Tournament cycle.

Part Three: Interplay

Interplay connects the System to the real world. It shows how organizations apply AME3 to the challenges they face today.

The AI section explores how generative AI reshapes products, teams, and business models. You will learn why AI will not fix your bureaucracy, how to assess your strategic terrain using Wardley Mapping, how to develop a strategy for the GenAI era, and how Teams are evolving from component teams to full-stack teams to AI-enhanced Teams that own end-to-end business outcomes.

The Methods section curates practical guides for selecting, adapting, and combining proven frameworks. You will find a detailed analysis of what makes framework adoption succeed or fail, and why AME3 works as a meta-framework that composes rather than prescribes.

You will learn how to use methods like Scrum, LeSS, Wardley Mapping, and Estuarine Mapping within AME3 for the benefit of your enterprise, your products, and your services. Other chapters cover the transition from project to product thinking, enterprise Goal visualization, and practical tips for planning and estimation at every level of the organization.

Each chapter and method stands alone. Together they show how the System comes alive in practice.