Field Guides teach the domain; playbooks cover the job. Each one walks through a situation product leaders face on complex B2B platforms, phase by phase, with the decisions, trade-offs and checklists I would want in hand.
For a product leader asked to make a regulated platform team AI native: measure first, then change how code ships, how internal work is reviewed and what customers see, in that order, with outcome metrics, real oversight and partner sign-off.
Last updated October 2026
Name the job your AI app does, pick the least autonomous building block that does it, give it the right context and tools, define good with real cases, set autonomy per action, and run each new job on shared layers at a known cost per task.
Last updated October 2026
What to do with the products after you buy a platform company: sort every product and component into kill, keep independent, migrate or shared services, sequence the work, keep customers and revenue, and clear the licences, banks and registrations that slow regulated deals.
Last updated October 2026
In about 90 days of owning an AI agent: read its traces until you know how it fails, turn those failures into a test set and release gate, ship model and prompt changes safely, make it ask, undo and hand off well, and set a weekly quality review.
Last updated October 2026
For a senior product person with no product or team of their own: get the mandate and the sponsor clear, map the journey with its owners and their metrics, get the owning teams to fix one handoff customers feel, and put the outcome into the planning cycle by day 60.
Last updated October 2026
For a new head of product on a payments, telco, security, identity or AI platform: learn the domain, diagnose the team and the product, act at once only where you must, and commit to a plan by day 60 without breaking what works.
Last updated October 2026