The PM playbook was built on an assumption that the technology underneath your product is roughly stable
With the current pace of model progress, this is no longer true. Here's how we've evolved the PM role:
1/ Plan in short sprints
Long roadmaps can't compete with a high velocity of small experiments. Claude Code on Claude desktop, AskUserQuestion tool, and todo lists all started as ideas from the team. We built a prototype, internal users liked it, we shipped it.
2/ Encourage demos and evals over docs.
Claude Code with Opus 4.6 has lowered the barrier to build a working prototype to showcase an idea. It's faster and higher fidelity than trying to convey the idea in a doc.
3/ Revisit features with new models
Every model release, go back through your list of features that were too hard for the previous model and test the ideas again. Also, remove the extra scaffolding that is no longer needed.
4/ Do the simple thing
With agentic systems, failures compound with system complexity. Find the simplest thing that works.
Bihan Jiang (Director of Product, Decagon) and Kai Xin Tai (Senior Product Manager, Datadog) also shared how their teams get a prototype in front of a customer way faster than they used to.
Read more: claude.com/blog/product-m…
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.