HANDBOOK
AI didn't add a chapter. It rewrote the book.
The companion to Product Builder OS. The rituals you were trained on now run slower than the people you're competing with. This handbook is the operating system that replaced them — 35 chapters across 5sections, every practice I'm running with my team this quarter.
Deceased · what this handbook replaces
- The PRD
- The quarterly roadmap
- The status meeting
- The six-week sprint
- Opinion-as-default
Pick your reading path.
Resume where you left off, take the 60-minute Espresso shortcut, or jump to the section that matches what you're fighting through this week.
The Thesis.
Why the PM role was rewritten
The old playbook is dead. These four chapters explain why, lay out the new operating model, and burn the two rituals that hold teams back the most. Start here.
- 01§01.017 min readUpdated
Why This Exists
The backstory: why I started documenting how I work, what I've learned so far, and what I'm still figuring out.
- 02§01.0212 min readUpdated
The AI Product Operating Model
What worked before AI, what's breaking now, and how I'm rewiring my practice.
- 03§01.036 min readNew
Kill the Roadmap
The roadmap is the most expensive lie in product management. Retire it and run a live bet portfolio instead.
- 04§01.046 min readNew
Kill the Status Meeting
The status meeting exists because nobody trusts the dashboard. Fix the dashboard once. Stop paying the tax weekly.
Discover.
Find the right problem before you build
Signal-driven discovery that runs every day, not once a quarter. Auto-ingest every customer signal, build opportunity trees from data, run interviews that test prototypes, and validate assumptions in a week.
- 01§02.0117 min readUpdated
Continuous Discovery
Discovery used to mean scheduling interviews and hoping for insights. Now AI ingests every call, email, and ticket your company generates, extracts the signal, and hands you a prototype before you finish your coffee.
- 02§02.0212 min readUpdated
Build Your First Opportunity Solution Tree
The OST used to take weeks of interviews and synthesis. Now AI extracts opportunities from every customer signal, prototypes solutions in hours, and tests assumptions before lunch. Here's how to build one that actually moves.
- 03§02.0312 min readUpdated
The Interview Guide That Actually Works
Customer interviews still matter more than ever. But now you show up with full signal context, a working prototype in hand, and AI that synthesizes the conversation before you close your notebook.
- 04§02.0413 min readUpdated
The Assumption Testing Playbook
Stop debating what to build. Prototype it in hours, put it in front of customers, and let their reaction be the test. Assumption testing just went from weeks to days.
- 05§02.057 min readNew
Continuous Listening: Every Customer, Every Day
Weekly customer conversations are the floor, not the ceiling. Pipe every support ticket, call, and churn survey into a daily digest and stop scheduling discovery.
Build & Ship.
Prototypes, not specs. Evals, not reviews.
From working prototype to production in days. The eval replaces the PRD. Observability is a launch gate. Deprecation runs on signal. Incident response is a PM ritual, not an engineering one.
- 01§03.0115 min readUpdated
Prototype Before You Spec
Why 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.
- 02§03.0218 min readUpdated
The Impact Loop
The daily rhythm that replaces sprints, stand-ups, and roadmap reviews. Sense what's happening, build a response, measure the impact, amplify what works.
- 03§03.036 min readNew
The Eval Is The Spec
Kill the PRD. Ship against a test set. The eval is the contract, the changelog, and the definition of done.
- 04§03.046 min readNew
Ship With Observability or Don't Ship
No feature leaves staging without the traces, metrics, and evals that will tell you whether it's working. Before your first customer hits it.
- 05§03.057 min readNew
The Deprecation Playbook
Feature 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.
- 06§03.066 min readNew
Incident Response Is a PM Ritual
An incident is a customer telling you the truth about your product, loudly, all at once. Stop letting engineering listen alone.
AI Craft.
The technical discipline the role now demands
Seven chapters on the craft underneath AI products: your agent fleet, when not to use AI, unit economics, pricing, prompt ops, model drift, and guardrails. The reference for building AI products the way they deserve to be built.
- 01§04.018 min readUpdated
The PM AI Agent Fleet: 39 Agents Mapped to the 7-Stage Operating System
A 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.
- 02§04.026 min readNew
When Not to Use AI
The senior PM move in 2026 isn't using AI everywhere. It's knowing when a regex, a query, or a form beats a model.
- 03§04.036 min readNew
Gross Margin Is Your Job Now
Cost 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.
- 04§04.046 min readNew
Pricing for AI Products
Per-seat is dead for AI. Price the work the seat is no longer doing: outcomes, usage, value units.
- 05§04.056 min readNew
Prompt Ops
Your prompts are production code. Version, review, eval, stage, and roll back, or your product is one Notion edit away from breaking.
- 06§04.067 min readNew
The Living Changelog
Your 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.
- 07§04.077 min readNew
Trust, Safety, and the Guardrail as a Product Decision
Every 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.
- 08§04.0814 min readNew
The PM Agent Stack: Open-Source Tools Mapped to PM Work
Build 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.
- 09§04.092 min readNew
Direction Metrics for AI-Native Velocity
Outcomes lag by weeks. Direction moves with each iteration. The seven leading indicators that predict outcomes 4-8 weeks ahead, and the dual-cadence system.
Lead the Shift.
Scale yourself, your team, and your practice
The weekly operating rhythm. Strategy from signals instead of slides. Killing the backlog. A 90-day plan for becoming a Builder PM. How to hire for it. How to manage an agent fleet at scale.
- 01§05.0115 min readUpdated
Your Weekly Playbook
What a week actually looks like when you're running the full handbook - discovery, prototyping, outcomes, and AI agents working together.
- 02§05.027 min readNew
Strategy From Signals, Not Slides
The 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.
- 03§05.036 min readNew
The Anti-Backlog
The backlog is a graveyard pretending to be an inventory. Burn it. Replace with a live queue, signal-fed, capped at two weeks.
- 04§05.048 min readNew
The Builder PM 30/60/90
The 90-day plan for making the shift from traditional PM to product builder. Done in order. In 90 days, you have a different job.
- 05§05.057 min readNew
Hiring the Builder PM
Most PM hiring loops test skills the role no longer needs. Hire by what they can ship, not by how they talk about shipping.
- 06§05.067 min readNew
PM-as-Editor: Managing a Fleet of Agents
The 39-agent chapter told you what to deploy. This is the skill you need once they're running: great editing at volume.
- 07§05.078 min readNew
The Cannibalization Decision Framework
Four diagnostic questions, three operating modes (sunset, refresh, split), the political map, and the seven-decision sequence for the AI inflection.
- 08§05.087 min readNew
Dual Transformation: Running Two Clocks
Two cadences, three talent categories, six CEO scoreboard numbers, three rituals. The operating model that runs legacy and successor cleanly.
- 09§05.098 min readNew
Pricing Migration: The 18-Month Quarterly Playbook
Six quarters, four mandatory CFO/CRO/Board/Lead-customer conversations, the gross-margin recovery curve, and the contract terms that defend outcome billing.
- 10§05.103 min readNew
The Investor and Board Narrative for AI-Era SaaS
Gross margin compression, NRR redefinition, the new rule of 40, the right comp set, and the four CFO sub-agreements that make the trough boring.
- 11§05.112 min readNew
The Pricing-Tier Sunset Playbook
How to end-of-life a revenue line: announcement timing, three-wave customer migration, comp plan rewrite, dispute mechanism at scale, post-sunset reorg.
Quotable, screenshottable, defensible.
Six practices a Product Builder can paste into a team channel without losing the source. One line per Product Builder OS skill — the skill taxonomy from /pm-standard, not the handbook's five sections.
- P01·§1 · Rapid Prototyping
If you cannot build it in hours, your stack is the bottleneck. Prototypes kill arguments specs prolong.
falkster · /handbookProduct Builder OS · P01 / 06 - P02·§2 · Customer Proximity
AI generates code in seconds. It cannot replace deep human understanding. Stay close to customers, support, churn, onboarding — daily.
falkster · /handbookProduct Builder OS · P02 / 06 - P03·§3 · AI Fluency
You don't design RAG. You decide whether you need it. Pick the cheapest primitive that works; defend it in five minutes.
falkster · /handbookProduct Builder OS · P03 / 06 - P04·§4 · Outcomes Thinking
Did the spec ship? Wrong question. Did the customer behavior change? Outputs are vanity; outcomes are job security.
falkster · /handbookProduct Builder OS · P04 / 06 - P05·§5 · Storytelling & Distribution
Great products lose to mediocre products with better stories. Write the launch tweet before you write the spec.
falkster · /handbookProduct Builder OS · P05 / 06 - P06·§6 · End-to-End Ownership
Own the full arc. Insight to prototype to launch to gross margin. The builder/PM/founder/GTM line is collapsing — close the loop yourself.
falkster · /handbookProduct Builder OS · P06 / 06
The Handbook, in plain English.
The questions I get asked most often after someone reads their first chapter.
What is The PM Handbook?+
The PM Handbook is a 35-chapter operating system for product managers in the AI era, organized into five sections — The Thesis, Discover, Build & Ship, AI Craft, and Lead the Shift. Each chapter is a practice Falk Gottlob is actively running, not a retrospective written years after the fact. Companion to Product Builder OS at /pm-standard.
How is the handbook different from Product Builder OS?+
Product Builder OS (at /pm-standard) defines what the AI-era PM role IS: the six skills that separate Product Builders from old-school Product Managers. The Handbook (here) is HOW to live that role day to day: 35 specific practices, frameworks, and playbooks, organized into five sections you can read in order or skim by topic.
How is the handbook organized?+
Five sections: §1 The Thesis (why the role got rewritten — the operating model and what dies in the old playbook), §2 Discover (signal-driven discovery on autopilot, interviews, assumption tests), §3 Build & Ship (prototypes, evals, observability, deprecation), §4 AI Craft (the technical discipline — agents, pricing, prompt ops, drift, guardrails), §5 Lead the Shift (strategy from signals, hiring, the weekly playbook, the 30-60-90).
Who is the handbook for?+
Working product managers, CPOs, and founders who want to operate the new way: shipping prototypes in hours, running evals as specs, treating agents as teammates, and replacing roadmaps with real-time signal. Both ICs and leaders. Not a beginner intro to PM, but accessible to mid-level PMs with at least one shipping cycle under their belt.
How is the handbook structured?+
Five sections, each containing 4–10 chapters. Read in order or jump straight to the section you're fighting through this week. Each chapter is self-contained — open one without reading the others. The handbook organizes chapters by section; Product Builder OS at /pm-standard organizes the same chapters by which skill they teach.
Is The PM Handbook free?+
Yes. Every chapter is free to read on falkster.com, no signup required. There's an optional once-a-month dispatch (The Dispatch) for new chapters and field notes, but nothing is gated.
Stop reading. Start practicing.
Pick one chapter from the skill section above. Run the practice with your team this week. That's how the handbook stops being a handbook and starts being how you ship.