The Product Playbook

This is the system I use to build product, product teams, and the cultures that make good product work repeatable. I started building this playbook over a decade ago and carried it into every job since, sharpening it each time. For most of its life it was mine, a private system I leaned on to help every team I joined do their best work. I'm sharing it now in case it helps you wherever you are in your own product journey.

Nobody is born into product. People find their way in from everywhere. Engineering, design, project management, business analysis, straight out of a school that never taught the job at all. Each one picks up the craft a little differently, shaped by wherever they came from. That mix is a strength, not a flaw. The best teams I've built had the widest range of instincts in the room.

But range comes with drift. An engineer leans on an engineer's instincts. A project manager reaches for a plan and a date. Left to sort it out alone, people fall back on an old habit or lose an afternoon hunting for how the good teams handle it. That doesn't scale. The bigger the team, the more that can go wrong.

That's the gap this closes. Not with a rigid process to run start to finish, but with the best ways I've found to do the work and the judgment for when to reach for each one. It breaks product down into its real parts, teaches them one at a time, and tells you the stories underneath. So a method connects to your actual week instead of sitting in your notes as theory.

That's the difference between this and a quick search or an AI that spins you up a process on demand. Those hand you steps. This hands you the whole picture. The situation you're in, the move that fits it, and the point of all of it, which is to stay close to your customer and solve real problems.

Line everyone up behind that same picture and the range finally pays off. The instincts still differ, but they point at one goal, and the product comes out built well instead of built around whoever argued hardest in the room.

I've used this playbook to build systems across AgTech, compliance, insurance, and CPG, on teams as small as two and as large as twenty-six.

The industries change. The work doesn't.

You shape the method to the room you're standing in. AgTech is a clean example. You don't have millions of users, you have hundreds, and the calendar runs the business. Build a brilliant app for planting, miss the planting window, and you haven't shipped a week late, you've shipped a year late.