Key Takeaways

  • Execution alone no longer makes a product manager valuable because generative tools and agents make shipping code cheap and fast.
  • Robby Stein, who led product teams for Instagram Stories, Reels, and Google AI search, argues that the central craft of product management is now judgment.
  • PMs must evolve from project coordinators into students of decision-making under uncertainty.
  • Building beloved products requires pairing Jobs to Be Done with pain elimination and emotional delight rather than tracking sprint tickets.

When Shipping Gets Cheap, Taste Becomes the Bottleneck

For years, tech companies measured product managers by execution momentum. A good PM organized standups, unblocked engineers, wrote Jira tickets, and kept launches on schedule.

Stein points out that this equation broke when software creation accelerated: “We used to be, I think as PMs, a big part of our value was around getting stuff done.”

When generative tools can produce working prototypes in minutes, raw execution speed stops being a competitive advantage. Anyone can build a feature. The difficult challenge is knowing whether anyone should. As Stein explains: “If in the world of today, almost anything you can think of can get built, it's more clear to me than ever that the actual true value of PM is actually around judging. It's around taste. It's around doing something extremely well.”

Taste is not mystical intuition. In Stein's playbook across Instagram Stories, Reels, and Google AI search, taste comes from diagnosing the exact human need. It requires understanding the specific Job to Be Done, finding where current tools cause friction, and obsessing over craft until the product eliminates pain.

The Only Skill That Survives Automation Is Decision-Making

When engineering velocity explodes, team backlogs fill up with low-conviction ideas. Teams drown in features because building is easy.

Stein argues that PMs must stop acting like project trackers and start treating decision-making as their primary discipline: “I think above all else actually the craft of PM is one simple thing that you should be the absolute best at. And that is decision making.”

Making high-quality decisions requires ruthless root-cause diagnosis. When a product or feature fails to get traction, weak teams tweak surface elements like button colors or onboarding copy. Strong teams investigate the deeper failure mode: did the product solve the wrong problem, or did it fail to spark delight?

As Stein puts it: “It's about making decisions and you should be students of what it takes to make great decisions.”

If you spend your week writing status updates, an automated script can replace your job today. If you spend your week filtering ten plausible product directions down to the single one that solves an urgent human problem, you remain irreplaceable.

What to Do With This

Audit your calendar from last week. Calculate the hours you spent coordinating tasks (status meetings, ticket updates, schedule nudges) versus making product judgment calls (user pain analysis, feature cut decisions, root-cause teardowns). If coordination took more than 50% of your time, hand off ticket tracking to engineering leads this sprint and spend Friday writing a one-page decision log on your three highest-risk feature bets.