Product Management is still about telling stories
Summary
Josh Elman argues that product management has shifted from writing technical specs to telling stories, as AI collapses the cost of building prototypes while increasing the necessity of human judgment.
Stories replace technical specs.
Specs describe systems and requirements, but stories communicate why a product matters to people and must be repeatable without the manager present.
The spec describes a system, what it must do, and what boxes must be checked off before it is done.
AI inverts the development loop.
The old sequence of idea-spec-build is replaced by build-and-play, where AI allows teams to prototype and feel a product before designing it.
It completely inverts: from spec-and-scope, to build-and-play.
Judgment is the scarcest resource.
As the cost of making things collapses, the difficulty shifts to curation and deciding which ideas provide actual impact rather than just filling schedules.
But the cost of judgment hasn’t changed at all.
Core actions define product success.
True usage is measured by purpose, core actions, and cycle frequency, rather than vanity metrics like signups or total tokens processed.
A vision is the end-to-end reason for the product to exist for users.
Onboarding must teach capabilities.
To convert curious users, products must avoid blank prompt boxes and instead use discrete, simple steps to demonstrate specific value concepts.
You have to teach capabilities concept by concept.
Highlights
We taught them Twitter, one concept at a time, as a story.
But the cost of judgment hasn’t changed at all. Figuring out what to build is more important now than ever.
First, take the idea and you build it quickly with AI, just to see how it works and how it feels.
The spec describes a system, what it must do, and what boxes must be checked off before it is done. That is not the art
Read the original ↗Save to your Sponge
Summarized with Sponge. Quotes are the author’s own words.