AI + Product Management, part 1
Your company is about to stop buying SaaS. That's a PM problem.
AI made software cheap to write. It has not made it cheap to own. That distinction, not the license fee, is what should decide build vs. buy now.
Writing
Organized by theme rather than by date. If you only read one section, make it the one closest to the decision you are currently arguing about.
Build vs. Buy
Why the buy decision keeps getting made badly, and what it actually costs after the contract is signed.
AI and the PM Role
What moving the bottleneck from execution to judgment changes about the job, and what it leaves untouched.
AI + Product Management, part 2
I wrote a one-paragraph feature. The estimate came back at a month.
Three architectural facts decided what a feature cost. None were in my PRD. What AI catches before a spec ships, and the gap it structurally cannot close.
Defining the Product
The layers between a vision and a line of code, and why most prioritization arguments are really a missing layer in disguise.
Product Abstraction, part 3
The layer where product management stops being an opinion
A goal needs a unit, not a target. Use cases split into ones that drive value and ones that only unblock it, and conflating them wrecks a roadmap.
Product Abstraction, part 2
A vision you can reach is not a vision
Five people, five answers, one product. How to write a vision that rules something out, and a mission that is a destination rather than a metric.
Product Abstraction, part 1
Software has abstraction layers. Your spec should have them too.
Prioritization feels like guessing until there's something above it to derive from. The seven-layer chain between a vision and a line of code.