The Product OS Handbook · 62 chapters

One handbook. Five seats.

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. Start with the core, then read your seat.

Everyone · 6 chapters

The core

What every seat shares. Read these first.

  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.8 min read
  2. 02The AI Product Operating ModelWhat worked before AI, what's breaking now, and how I'm rewiring my practice.13 min read
  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.5 min read
  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.7 min read
  5. 05Kill the RoadmapThe roadmap is the most expensive lie in product management. Retire it and run a live bet portfolio instead.7 min read
  6. 06The Impact LoopThe daily loop the AI-era product org runs: customer, spec, build, story, adoption. One measure per stage, one owner for the whole loop.7 min read

Seat · 12 chapters

CPO

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

Go to the CPO seat →
  1. 07The CPO 30/60/90The operational week-by-week plan for a new CPO: four audits, a trust ledger, a coalition map, and a day-90 readout the board will quote. With templates.10 min read
  2. 08Strategy From Signals, Not SlidesThe annual strategy deck is a memorial to a meeting. Run a one-page living strategy doc, updated weekly with the signals that could change your beliefs.8 min read
  3. 09Dual Transformation: Running Two ClocksTwo cadences, three talent categories, six CEO scoreboard numbers, three rituals. The operating model that runs legacy and successor cleanly.8 min read
  4. 10Gross Margin Is Your Job NowCost per successful action is the new primary PM metric. If you don't own it, your CFO will kill your product before your customers do.7 min read
  5. 11The Investor and Board Narrative for AI-Era SaaSGross margin compression, NRR redefinition, the new rule of 40, the right comp set, and the four CFO sub-agreements that make the trough boring.4 min read
  6. 12The Cannibalization Decision FrameworkFour diagnostic questions, three operating modes (sunset, refresh, split), the political map, and the seven-decision sequence for the AI inflection.9 min read
  7. 13Trust, Safety, and the Guardrail as a Product DecisionEvery guardrail is a product decision. The PM who outsources it to legal gets a product they didn't design and a customer experience they wouldn't approve.8 min read
  8. 14Incident Response Is a PM RitualAn incident is a customer telling you the truth about your product, loudly, all at once. Stop letting engineering listen alone.7 min read
  9. 15Kill the Status MeetingThe status meeting exists because nobody trusts the dashboard. Fix the dashboard once. Stop paying the tax weekly.7 min read
  10. 16Your Weekly PlaybookWhat a week looks like when you run the full handbook. The week is the rhythm, the loop is same-day, and you run it as often as hot signals land.11 min read
  11. 17Hiring the Builder PMMost PM hiring loops test skills the role no longer needs. Hire by what they can ship, not by how they talk about shipping.8 min read
  12. 18The Skill Stack: What PMs and CPOs Must Learn NowThe 12 skills that decide PM and CPO careers now, organized in five layers from judgment to storytelling, with a self-test and learning path for each.10 min read

Seat · 20 chapters

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.

Go to the product seat →
  1. 19Product Builder OSThe working standard for the Product Builder: six skills, the career ladder, the principles, and the errata.
  2. 20Old PM vs Product Builder, The LedgerThe line-by-line ledger of what changes when product management gets rewritten by AI: output, cycle time, unit of work, deliverable, accountability.9 min read
  3. 21Continuous DiscoveryAI ingests every call, ticket, and email, extracts the signal, and hands you a prototype the same day. Continuous discovery is no longer a weekly ritual.18 min read
  4. 22The Interview Guide That Actually WorksCustomer interviews matter more than ever. Show up with full signal context, a working prototype, and AI that synthesizes the conversation in minutes.13 min read
  5. 23The Assumption Testing PlaybookStop debating what to build. Prototype it in hours, test with customers, and let their reaction decide. Assumption testing just went from weeks to 3-5 days.14 min read
  6. 24Continuous Listening: Every Customer, Every DayWeekly customer calls are the floor, not the ceiling. Pipe every support ticket, call, and churn survey into a daily digest and stop scheduling discovery.8 min read
  7. 25Build Your First Opportunity Solution TreeBuild your first Opportunity Solution Tree. AI populates the opportunity layer from 500+ signals. Prototype and test a solution in one week instead of eight.13 min read
  8. 26Prototype Before You SpecWhy the fastest way to get alignment, test ideas, and advance your career is to build something people can touch - and exactly how to do it in 2 hours.16 min read
  9. 27Building Evals: Error Analysis, Eval Types, the Loop, the GateTeresa Torres's three steps as a weekly routine, plus the fourth step that turns an eval from a scoreboard into what decides what an agent may do alone.7 min read
  10. 28Ship With Observability or Don't ShipNo feature leaves staging without the traces, metrics, and evals that will tell you whether it's working. Before your first customer hits it.7 min read
  11. 29Direction Metrics for AI-Native VelocityOutcomes lag by weeks. Direction moves with each iteration. The seven leading indicators that predict outcomes 4-8 weeks ahead, and the dual-cadence system.3 min read
  12. 30PM-as-Editor: Managing a Fleet of AgentsThe 39-agent chapter told you what to deploy. This is the skill you need once they're running: great editing at volume.8 min read
  13. 31PM AI Agent Fleet, Mapped to the 7-Stage Operating SystemA live index of every AI agent for product managers, mapped to the 7 stages of the PM Operating System: Sense, Discover, Decide, Build, Ship, Measure, Amplify.8 min read
  14. 32The PM Agent Stack: Open-Source Tools Mapped to PM WorkBuild a personal PM agent stack from open-source Claude repos. 18 tool categories mapped to the 7-stage PM operating system, with install order and how-tos.14 min read
  15. 33Agent-to-Agent DispatchThe listening agent does not file a ticket. It hands the outcome to a prototyping agent, and a working prototype is waiting before standup.6 min read
  16. 34Prompt OpsYour prompts are production code. Version, review, eval, stage, and roll back, or your product is one Notion edit away from breaking.7 min read
  17. 35When Not to Use AIThe senior PM move in 2026 isn't using AI everywhere. It's knowing when a regex, a query, or a form beats a model.7 min read
  18. 36The Anti-BacklogThe backlog is a graveyard pretending to be an inventory. Burn it. Replace with a live queue, signal-fed, capped at two weeks.7 min read
  19. 37The PM 30/60/90A week-by-week 90-day plan for PMs starting a new job: decision archaeology, a signal map, a manager contract, and one compounding artifact by day 60.8 min read
  20. 38The Builder PM 30/60/90The 90-day plan for making the shift from traditional PM to product builder. Done in order. In 90 days, you have a different job.8 min read

Seat · 12 chapters

Design

Behavior and the quality bar: the rubric agents build against, the states around output nobody can predict, and the repair rate that says which state failed.

Go to the design seat →

Part 2 · Designing Non-Deterministic Products

  1. 42You Cannot Mock a DistributionThere is no final state to draw when the output is assembled at runtime. What you specify instead is a band, and everything inside it ships without your review.7 min read
  2. 43The Shape of UncertaintyHow a product says it is not sure without looking broken. There are four moves, and the wrong one is why products read as falsely confident or hedged.7 min read
  3. 44Undo Is a Design PrimitiveUndo used to mean the last thing you did. It has to mean the thing the system did while you slept, which is three design problems instead of one.8 min read
  4. 45Disclosure Without OverwhelmShowing everything is not transparency. It is a way of making the user responsible for checking work they never asked to supervise.7 min read
  5. 46Latency Is InterfaceWaiting used to be a spinner problem. It is a relationship problem now: the user cannot tell if anything is happening or if they are still needed.7 min read
  6. 47Designing RefusalRefusal is the most under-designed surface in AI products and the one users judge fastest, because a bad refusal is indistinguishable from a broken product.7 min read
  7. 48Recovery and Trust RepairThe thirty seconds after your product is confidently wrong decide whether the person keeps using it. Almost nobody designs that moment.8 min read

Seat · 5 chapters

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.

Go to the product marketing seat →
  1. 51Pricing for AI ProductsPer-seat is dead for AI. Price the work the seat is no longer doing: outcomes, usage, value units.7 min read
  2. 52Pricing Migration: The 18-Month Quarterly PlaybookSix quarters, four mandatory CFO/CRO/Board/Lead-customer conversations, the gross-margin recovery curve, and the contract terms that defend outcome billing.9 min read
  3. 53The Pricing-Tier Sunset PlaybookHow to end-of-life a revenue line: announcement timing, three-wave customer migration, comp plan rewrite, dispute mechanism at scale, post-sunset reorg.3 min read
  4. 54The Living ChangelogYour model vendor changed the model on Tuesday and didn't tell you. Run a daily replay against production or your customers will catch it before you do.7 min read
  5. 55The Deprecation PlaybookFeature death is the most under-written topic in PM. Kill on signal, not politics, and your team ships faster than the team that hopes politely.8 min read

Seat · 7 chapters

Forward deployed engineering

The customer edge: deployments that land, and field findings back into the spec in hours, with fewer hops every quarter.

Go to the forward deployed engineering seat →
  1. 56The Forward Deployed Engineer Is a Product Builder in DisguisePalantir invented the FDE because software shipped without its engineer does not get adopted. It is the Product Builder, from the services side.7 min read
  2. 57FDE vs Sales Engineer: The Job Starts Where the Contract Is SignedA sales engineer's job ends when the customer says yes. An FDE's job begins there. Confusing the two is how companies get expensive demos and no adoption.7 min read
  3. 58What Has to Change in the Product Before FDEs Can WorkSending engineers into customers without changing the product turns them into a consulting firm. Five things the product must expose before the first FDE lands.8 min read
  4. 59The Deployment-to-Product Loop: How FDE Work Becomes RoadmapPalantir's ingestion, visualization, and app builder all started as one FDE's hack for one customer. The loop that generalized them is why the model made money.7 min read
  5. 60Building the FDE Team: Reporting Line, Bar, Pairing, and CompFDEs who report to sales become sales engineers within two quarters. Reporting line, hiring bar, pairing, and comp decide whether the team lasts a year.7 min read
  6. 61FDE Economics: Margins, Outcome Pricing, and When to StopForward deployment costs like services and has to earn like software. The math works only if the loop closes and the pricing puts revenue behind the result.7 min read
  7. 62Becoming an FDE: The Transition From PM, Engineer, or SEThree doors lead into the FDE role. Each one arrives with two of the three things the job needs and is missing the third. A 90-day plan for each.7 min read

About the handbook

What is The Product OS Handbook?
The handbook of The Product OS, one operating system for the AI-era product org. 62 chapters, grouped as the core every seat shares and then one section for each seat: CPO, Product, Design, Product marketing, and forward deployed engineering. Every chapter is free.
How is the handbook organized?
By the OS. The core comes first: the manifesto, the operating model, substrate-first engineering, the eval as the spec, killing the roadmap, and the impact loop. Then each seat's chapters, in reading order. A chapter belongs to exactly one section.
Where is Product Builder OS?
Product Builder OS, the six-skill standard for the Product Builder role, is the first chapter of the Product section. The Product seat page links it with the assessment, the course, and the career path.
Where are the Design chapters?
The 12 Design chapters are the Design section of this handbook. They keep their /design/<slug> addresses, and the Design seat page lists them in book order.

Read by seat

CPOOwn the whole outcome.PRODUCTBuild what matters.DESIGNDesign the behavior.PMMMake the product matter.FDEMake AI work in the real world.