Path 1 · 3 steps Draft
The job after AI
What product management became once building stopped being the expensive part, where the value went, and how to hire for the job as it is now.
From the channel
The essays, read aloud and drawn, for when you would rather watch.
Latest · Everything is repricing · 8 min · The 60-second version →
AI made every step of product research faster: recruiting, interviewing, synthesizing, even the users. It didn’t make it cheaper to know whether any of it is true. What the evidence says, and how to do research now.
How to keep judging well when the volume of plausible artifacts goes up tenfold: what the detection research actually says, and what to do about it.
New habits for product leaders in 2027: what to drop, what to build, and which part of the job each one fixes.
A 2027 risk map for B2B SaaS: what’s actually dangerous, what only looks dangerous, and an 18-month plan.
Where humans actually sit in product management after AI — and why “orchestrator” is the wrong answer.
You cannot write an acceptance criterion for a system that answers differently every time. What you can write is the standard you will judge it against.
Not complete yet. The Evals path is ready to follow; the other four are drafts, and more steps are coming.
Path 1 · 3 steps Draft
What product management became once building stopped being the expensive part, where the value went, and how to hire for the job as it is now.
Path 2 · 2 steps Draft
Why reading AI output is not a check, and the few habits that tell you, soon and plainly, whether you were right.
Path 3 · 5 steps
From “I tried it and it seemed fine” to a score you can rerun. By the end you will have real cases, a rubric you wrote, and a first run to compare against.
Path 4 · 2 steps Draft
The reading skills and the kit a product leader needs now: what to read in the code, and what to use, choose and test in each category.
Path 5 · 2 steps Draft
One mechanism behind the headlines about roles, pricing and valuations, and a way to place your own product on the risk map.
Reference
Every tool the job now runs on, what each one is actually for, and where it stops being worth the setup.
4 parts
What product management became once building stopped being the expensive part — one argument at a time.
Bring 50 real cases and a rubric written in plain English, and get a score you can rerun after any change. The screen that matters is the diff: which cases moved, and in which direction.
Write down what success looks like before you ship, and keep the verdict whichever way it lands. Unclear counts as an answer, and the ledger says how good your predictions have actually been.
Reads a set of transcripts and returns themes and contradictions, where every claim is built from quotes checked word for word against the transcript they came from. A quote it invents is caught on the page, not by you, later.