The Constraint Capture Matrix

Finding a bottleneck is not the same thing as capturing it.

Every technology cycle creates the same illusion. Leaders locate the friction point in their industry, buy software to address it, and expect market share to follow. The historical pattern says otherwise. Some companies convert that diagnosis into a multi year moat while others just automate their existing limitations.

In The Strategy Isn’t Wrong. The Clock Is., I argued value migrates to whichever constraint is binding at a given moment. In The Scarce Thing, we saw what happens when that constraint becomes permission. Diagnosing a bottleneck tells you where value is trapped. It tells you nothing about whether your organization can actually claim it.

Two independent variables decide that. Does the organization control the constraint, and has it built the authority to act on that control? Advantage doesn’t come from finding the next constraint, your competitors will see it too eventually. It comes from controlling the constraint and redesigning the permission structure to act on it. The final scarce resource is authorized action.

Control vs. Authority

Constraint control is the control surface. A company rarely owns a bottleneck outright, regulators own rules, payers own reimbursement, markets own capital costs. What a company can build is the specific point where it can influence the outcome without controlling the entire system. High control means the deciding variables sit inside your software, your balance sheet, your data, your infrastructure. Low control means clearing the bottleneck requires independent third parties, regulators, licensing boards, platform monopolies, to move together.

Execution authority is the permission structure, an organizational choice to delegate action without a human calendar queue. It requires runtime verification, pre audited risk bounds, and clearing the liability traps that make managers hoard sign off. Most AI transformations don’t stall for lack of use cases. They build intelligence systems inside organizations still running on human speed permission.

Four positions follow from these two axes. Quadrant 1, Default Capture, high control and high authority. Quadrant 2, the Sunk Cost Engine, high control and low authority. Quadrant 3, the Fragile Velocity Trap, low control and high authority. Quadrant 4, the Dependency Trap, low control and low authority. Companies move between them along recognizable paths: control without new authority takes you from Quadrant 4 to 2, authority without control takes you from 4 to 3, securing a control surface over your dependencies moves you from 3 to 1, and replacing manual queues with real permission architecture moves you from 2 to 1.

This matters now because AI compresses the cost of insight faster than organizations can redesign around it. The bottleneck is moving from generating answers to authorizing actions. The companies that win won’t necessarily have the best models. They’ll have the shortest path between machine insight and business execution.

The Four Quadrants

Quadrant 1 is the target state. Amazon Logistics is canonical. Delivery reliability, not inventory selection, became the real promise to the customer, and third party carriers were a bottleneck Amazon couldn’t dictate. By building its own fulfillment centers and last mile fleet, Amazon built the control surface itself, and every routing improvement compounded into its moat. Credit unions like FORUM, Centris, and Del-One did the same thing in lending. Underwriting guidelines and software sat inside their own walls, so they controlled the constraint, and granting execution authority to pre audited, bounded transactions turned that into a 70% jump in processing capacity, the case covered in The Scarce Thing.

Quadrant 2 is where most enterprise technology budgets die. In corporate procurement, AI can ingest contracts and draft renegotiated terms in seconds, fully within the company’s control. CFOs still refuse to delegate execution, a rational response until machine agency liability is settled in court. The system drafts faster. A human still signs everything.

Quadrant 3 is speed without ownership. Marcus by Goldman Sachs built genuine machine speed underwriting, real authority by any definition, on top of an economic foundation it didn’t control. A new accounting rule, CECL, forced far more aggressive loss reserving just as rates made the loan book more expensive to carry. Worth repeating the honest caveat here rather than dropping it: some of the loss likely traces to underwriting quality itself, Goldman’s card loss rate ran above peer issuers, which is an execution problem, not a control problem. Both can be true. Quadrant 3 doesn’t require a company to be blameless, only that part of the outcome trace to a constraint it never controlled, and here it does.

Pear Therapeutics belongs here too. Its software tracked and adapted treatment for substance use disorder without clinician micromanagement, real authority over the clinical action itself. What it never had was control over the constraint that decided its fate, CMS and commercial payers never assigned a reimbursement code that made the product viable at scale. Pear cleared the hard regulatory hurdle and still had no leverage over the variable that actually mattered.

Quadrant 4 is the default posture of most regulated industries, because it takes no decision to end up there. Traditional prior authorization is the clearest case. AMA surveys consistently find the overwhelming majority of physicians say it delays necessary care, and most of the industry still runs on fax and phone holds on both sides. No one owns the reimbursement rules, and no one built software to act quickly within them either. It’s the quadrant every other example in this chapter started from.

Cohere Health vs. Olive AI

Both companies attacked prior authorization from Quadrant 2. Olive AI raised over $900 million to a $4 billion valuation using robotic process automation to fill out payer web forms faster. It automated the paperwork, not the authority, hospital staff still verified and submitted every request, because Olive had no integration into payer decision engines. It shut down in October 2023, selling its prior authorization unit to Humata Health. In fairness, overexpansion and a burn rate above $100 million a year played a real part too, not every dollar of that failure is a pure Quadrant 2 story. But the core pattern holds.

Cohere Health partnered directly with Humana in 2021 to embed the payer’s own coverage policies into its platform at the point of care. Median approval time on musculoskeletal requests dropped to zero minutes, with 89% approved for immediate scheduling. The partnership is now nationwide, and Cohere reports real time approval on up to 85% of documented submissions. Olive optimized Quadrant 2. Cohere built a new control surface and moved to Quadrant 1.

Beyond AI

This move predates artificial intelligence. Apple built the App Store’s review and payment architecture into an unassailable control surface over mobile distribution. NVIDIA built CUDA into a software layer that binds developers to its silicon. Tesla built the Supercharger network to remove a constraint utilities weren’t going to solve for it. Medtronic used FDA’s Predetermined Change Control Plan to pre negotiate future updates to its LINQ II monitor, turning a recurring regulatory toll into its own iteration schedule. Every one of these firms treated the binding constraint as something to be redesigned, not accepted.

The Guardrail and the Audit

Control and authority are necessary, not sufficient. A company can execute flawlessly inside a domain it fully controls and still fail if it misdiagnosed where scarcity actually lives. The matrix starts only after that diagnosis is right.

Before allocating capital, ask three things. Which quadrant does this initiative occupy now? Do you control the constraint, or are you building a Fragile Velocity Trap? And what organizational cover is keeping you in Quadrant 2, what would it take to authorize the bounded action instead of routing the whole system through a human queue?

Diagnosing the bottleneck tells you where value is migrating. The matrix tells you whether you’re actually equipped to capture it.