Enterprise Capability Framework

Successful technology organizations get slower as they grow. Each new technology arrives with the promise that it will fix that, and each time the enterprises that pull ahead are not the ones that adopt it first. They are the ones that already know how to turn any new technology into something the whole organization can reuse.

Enterprise Capability Framework makes one argument and follows it through every discipline a technology leader is responsible for: enterprises build lasting advantage not by accumulating technologies, but by converting specialized expertise into organizational capability that outlives the person, project, or platform that created it. Architecture, platform engineering, cloud, security, data, AI, delivery, and governance are treated as instances of that same move, parts of one operating model rather than separate fields.

Written for CIOs, CTOs, chief digital officers, and the directors and architects who report to them, the book is organized in five parts: how enterprises evolve, and how they design, deliver, govern, and steward their capability. Each of its 27 chapters follows the same structure:

• A real, named case that shows the idea at work
• A contrasting case that shows what the idea depends on when it fails
• A mechanism you can use: the decision it governs, the steps for making it, and the measures that tell you whether it is working
• A path for organizations that are starting late
• A section called Where This Breaks Down, marking the conditions under which the argument stops applying

The cases include Amazon's API mandate, Spotify's Backstage and Golden Paths, ING's reorganization into squads and tribes, Google's error budgets, the Equifax breach, Zillow Offers, CrowdStrike's Channel File 291, and Air Canada's chatbot ruling. Sources are cited chapter by chapter.

Artificial intelligence runs through every part. AI can now draft documents, analyze information, and write working software for anyone who asks, including competitors. The book asks what that changes and what it leaves standing: software that merely looks finished is now cheap, while software an enterprise can rely on, secure, connect to its other systems, and answer for is not. The final part asks what the technology organization is for when almost anyone can build, and what it means to lead it as a long-term steward rather than a short-term operator.