Skip to content
AI-Native PM

Frameworks & execution models

A model never gives you the same answer twice, and a framework is what makes the decision come out right anyway.

A framework does for product judgment what a good recipe does for cooking: a result you can count on even as the inputs keep changing. So on every AI decision we run one cycle, Shape · Ship · Track, then run it again until it holds.

  • Shape. Decide how the system behaves, and make it real.
  • Ship. Put it in front of a human, behind guardrails, at a workable cost and speed.
  • Track. Find out whether it is behaving, and catch what users never report.
  • Continuous Operations. The umbrella across every turn of the cycle.

The Frameworks

Product management frameworks created for the full AI product lifecycle.

The Discipline: what changed about the workA before-and-after wipe. A bright divider sweeps left to right. As it passes each row, the muted old way crossfades into the vivid new way and an accent underline draws in. A spec of features becomes a spec of behavior. Owned across functions becomes PM accountable for behavior. A known menu becomes new problems and new solutions. Acceleration is tablestakes. Owning this work is the job.WHAT CHANGEDBEFOREAFTERA spec of featuresA spec of behaviorOwned across functionsPM accountable for behaviorA known menuNew problems and new solutionsAcceleration is tablestakes. Owning this work is the job.

Using AI to move faster is becoming table stakes. Building with AI is a separate craft, and the work itself changes. What you ship becomes a spec of behavior rather than a set of features. You own how the model behaves when no other function does. And the menu of what is worth building is new, so the only way to know is to build it.

  • A spec of behavior
  • Owning the behavior
  • New problems to solve
Go deeper12 min read

The Human FactorsConcentric rings like a radar of the mind, from the outer ring Perception inward through Working Memory and Mental Models to the innermost Metacognition, with a human mind mark at the center. A pulse ripples inward through the layers; each faculty lights up in turn with its design recommendation.DESIGNING FOR THE HUMANPERCEPTIONWORKING MEMORYMENTAL MODELSMETACOGNITIONTHE HUMAN MINDPERCEPTION"Make the warning impossible to miss."

The part of the system the model has no access to, and the part the PM is there to protect.

The products that win will be the ones designed for the mind that has to use them, with its real and well-documented limits, not for an idealized user who has none. That mind is on the other side of every model. It is the part of the system the model cannot see, and the part the PM is there to protect.

  • Perception
  • Working memory
  • Mental models
  • Metacognition
Go deeper16 min read

Shape · Ship · TrackA continuous cycle of Shape, Ship, and Track, then Shape again, because a probabilistic system is never finished.A probabilistic modelmade reliable1ShapeDecide how it behaves2ShipPut it behind guardrails3TrackCatch what users won't report

The whole practice. You shape how a model behaves, you ship it to a human behind guardrails, and you track whether it holds. Then you do it again, because a probabilistic system is never finished.

  • Shape
  • Ship
  • Track
Go deeper7 min read

The Operating Manual: Shape · Ship · Track, operationalizedA blueprint of columns headed Shape, Ship and Track, under one umbrella band labelled Continuous Operations, the umbrella across every turn of the cycle. Shape opens into Frame the problem, Write the behavior, Choose the model, and Prototype it. Ship opens into Build the guardrails, Build the eval suite, Earn trust when unsure, and Set the cost and speed budget. Track opens into Watch in production, Catch the drift, and Feed back into Shape. The rows draw in column by column, then a dotted feedback path runs from Feed back into Shape back up to the Shape column. The cycle opens into its activities. Continuous Operations runs across every turn.THE CYCLE, OPERATIONALIZEDCONTINUOUS OPERATIONSthe umbrella across every turn of the cycleShapeFrame the problemWrite the behaviorChoose the modelPrototype itShipBuild the guardrailsBuild the eval suiteEarn trust when unsureSet the cost & speed budgetTrackWatch in productionCatch the driftFeed back into ShapeThe cycle opens into its activities. ContinuousOperations runs across every turn.

The cycle, made operational. Each move opens into the activities you actually do, with Continuous Operations running across all of them, and every activity produces something real you can hand off.

  • Shape
  • Ship
  • Track
  • Continuous Operations
Go deeper14 min read

How to use them

Two ways to put the frameworks to work.

Reading the four frameworks is the thinking. These two are how you run them: one to read, one to click through.

Read it

The Operating Manual

A plain, step-by-step guide to running the cycle. It breaks Shape, Ship, and Track into the specific things you do, and each step leaves you with something real to hand off: a written spec, a release checklist, a report on what to watch. Read it start to finish, or jump to the move you are on.

Open the Operating Manual

Run it

The Console

The same manual, made interactive. Instead of reading the steps, you click through them: pick a move, open any activity to see what it produces, and fork the whole cycle into a checklist you can run against your own product.

Open the Console

Go hands-on

Read the frameworks, then build it.

The Builder's Stack is the hands-on course where you take everything on this page and turn it into a product that behaves. Three levels carry you from the fundamentals to the frontier.

Open the Builder's Stack
Level 1The FundamentalsMaster the core software skills needed to build confidently with AI.Level 2The PracticeMake a working build safe, tested, and ready for real users.Level 3The FrontierTake on the newest AI problems, from agent fleets to agent users.