LeadingAgile

In this video, Stacy Gordon sits down with John Greisner, a management consultant at LiminalArc, to explore why AI doesn’t remove your software delivery bottleneck so much as move it. Drawing on Goldratt’s theory of constraints from The Goal, John walks through what happens once engineering gets fast and cheap: the real slow point shifts...

My last six posts made an argument: AI fails on conditions, not models; capabilities are the unit; AI has three jobs and one it can’t take; transform by slices, never all at once. The most common response I get is some version of: okay, I buy it. What do we actually do on Monday?

Fair question. Here’s what it looks like on the ground:...

The argument so far, in one breath: your pilots work and don’t pay because they simulate conditions your enterprise doesn’t have; the conditions are four, and testable; the place you create them is a capability, not an application; and once created, AI has three real jobs and one it can never take. That leaves the question every executive actually ge...

This series has been about conditions: why pilots die in production, what the four conditions are, why capabilities and not applications are the unit you create them around. Now the question underneath everything: once you’ve done that work, once a capability is genuinely free, encapsulated, with clean data and one team that owns it, what is AI actua...

The last post ended with a question: which slice? If the way out of the pilot graveyard is creating the four conditions in one real place at a time, one boundary with production inside it, then everything depends ...