Every technological revolution runs the same arc. A new capability arrives, capital floods toward it faster than the institutions that would govern it can adapt, and a frenzy inflates. We are inside one now.
In the stretch between installation and deployment, the capability curve goes vertical while the operating model, the governance, and the organizational form move at institutional speed. This is the pattern Carlota Perez traced across two centuries of surges. Inside a single company it shows up as a widening gap. The capability can already do the work, and the P&L stays flat, because the system around it takes far longer to change. A capability is a purchase. An operating model is structural work. The return sits in that gap until the structure catches up, and the organizations that pull ahead are the ones that close it first.
It starts from a plain question the old model never asked: which decisions should software own, which stay with a named person, and where do the two meet. That line is the operating model. Draw it right and the capability has a shape that lets it pay.
In the frenzy, capital rushes to acquire the capability. The harder question, how it operationalizes into P&L expansion, gets deferred to later, and later never comes. Advantage goes to the organizations that answer it. We work in all three practices that answer it. OOA is the one we are publishing in full, and the depth behind the other two is the same.

We will tell you where it does not pay, and we will tell you to walk away.
Request a briefingOr read the thinking behind the method, and the record behind it, on About.