A
PUBLICATION
ABOUT
PMs
SHIPPING
THINGS.
Bias to Build is a publication, a podcast, and a small-cohort workshop for product managers reckoning with a strange new fact: the gap between an idea and a working prototype has collapsed to an afternoon. The job, then, is changing.
Why this exists
For most of the last fifteen years, the job of a product manager has been to coordinate — to write specs, run reviews, prioritise backlogs, and shepherd ideas through a sequence of specialists.
That worked. It worked because the cost of producing the actual artefact — a working interface, a deployable feature — was high enough that you needed specialists, and the coordination overhead was worth paying for.
Something has changed.
The cost of producing the artefact is collapsing. A PM with a clear brief, an AI assistant, and a free Friday afternoon can stand up a working prototype that two years ago would have needed a designer for a week and an engineer for a sprint.
That doesn't make designers and engineers obsolete. It changes the shape of the workflow — and it changes what makes a PM useful.
Bias to Build is for the PMs who want to be early to that shift. It's a place to share what's actually working, and to argue about what isn't.
How it's organised
There are three things, and they're all run by one person:
The Field Notes blog
Short, opinionated essays on shipping product with AI. Tools, workflows, patterns, the occasional honest failure. New ones go out roughly weekly via the newsletter.
The podcast
Mostly me at the camera, building real things and narrating the decisions. The occasional interview when I find someone with a story worth telling. New episode roughly weekly.
The workshops
A five-day, eight-person cohort for individuals, plus one-day intensives and embedded sprints for whole teams. You bring a real problem from your real job and leave with a working prototype your team can use on Monday. The first cohorts and team dates are on the calendar now — bring it to your team if you're buying for a group.