The Product OS

One loop. One owner.
Five seats that run it.

When building is cheap, the outcome is decided by the loop from customer to adoption. One loop needs one owner. The CPO owns the whole product outcome, and product, design, product marketing, and forward deployed engineering run it together.

seats
5
OS chapters
61
series parts
27

The loop

Customer to adoption, and back.

  1. 01 →CustomerField signal from deployments, support, and usage, read daily.FDE
  2. 02 →SpecThe problem, the behavior, and the eval that says it works.PRODUCTDESIGN
  3. 03 →BuildAgents and Product Builders take the spec to working software.PRODUCTDESIGN
  4. 04 →StoryPositioning and proof that buyers, sellers, and AI assistants read.PMM
  5. 05 ↺AdoptionThe outcome number moves, or the loop runs again.PMMFDE

The CPO owns every stage. The other four seats lead the stages marked on each card.

The core

Start here, whatever your seat.

The chapters every seat runs on. Read them in order.

Every handbook chapter
  1. 01Why This ExistsThe backstory: why I started documenting how I work, what I've learned so far, and what I'm still figuring out.
  2. 02The AI Product Operating ModelWhat worked before AI, what's breaking now, and how I'm rewiring my practice.
  3. 03Engineering Builds the Substrate, Not FeaturesIn an AI-native org, engineering's highest-leverage work is the substrate that lets PMs and designers ship safely: guardrails, evals, isolated deploys.
  4. 04The Eval Is The SpecKill the PRD. Ship against a test set. The eval is the contract, the changelog, and the definition of done.
  5. 05Kill the RoadmapThe roadmap is the most expensive lie in product management. Retire it and run a live bet portfolio instead.
  6. 06The Impact LoopThe daily rhythm that replaces sprints, stand-ups, and roadmap reviews. Sense what's happening, build a response, measure the impact, amplify what works.

The seats

Each seat has a playbook, a running series, and its chapters.

CPO

CPO

The whole product outcome, from the customer problem to adoption, and the org, the margin, and the board story that go with it.

The CPO seat The CPO Transition, 5 parts Latest: Anthropic's S-1 Has No Gross Margin Line. Your AI Product Needs One.
PRODUCT

Product

The spec and the build: Product Builders take an outcome to a working product in a day and run the agents that build it.

The Product seat The PM Transition, 1 part Latest: Salesforce Hires PMs to Say What Good Looks Like. The PM Is the Product Builder Now.
DESIGN

Design

Behavior and the quality bar: the rubric agents build against, and interfaces that hold up when output cannot be predicted.

The Design seat The Design Transition, 5 parts Latest: 84,000 Chats Show When Users Re-Ask the AI. Design Should Own the Repair Rate.
PMM

Product marketing

The story and adoption: positioning as a living spec that buyers, sales agents, and AI assistants read, pricing as a product decision, and adoption as the deliverable.

The Product marketing seat The Product Marketing Transition, 1 part Latest: Your Buyer's Agent Reads One File. Product Marketing Reports to the CPO Now.
FDE

Forward deployed engineering

The customer edge: deployments that land, and field signal back into the product in hours, not quarters.

The FDE seat The FDE Transition, 15 parts Latest: NICE Moved Its FDEs Into Go-to-Market. The FDE Org Belongs Under the CPO.

The rhythm

One new part a day. One OS update a week.

Every part is written against what changed that week. On Sundays the OS itself gets revised: chapters updated, gaps filled, and the change logged here.

The changelog

What changed in the OS.

  1. The five seats became one operating system. CPO, Product, Design, Product Marketing, and FDE now share one hub, one loop, and one publishing rhythm.