The Product Engineers Podcast · October 20, 2026

Marty Cagan on Empowered Engineers in the AI Era: Push Back, Then Prototype

Marty Cagan says engineers are the best single source of product innovation, because they work with new technology every day. He made the case on The Product Engineers Podcast, published 20 October 2026, as AI changes how teams build. If engineers first see an idea at sprint planning, he says, the team has failed.

Speaker
Marty Cagan
Where
The Product Engineers Podcast
Published
Length
53 min

Marty Cagan: Founder of Silicon Valley Product Group (SVPG), co-author of Empowered.

Recording: Why AI Makes Empowered Engineers More Important Than Ever | Marty Cagan (SVPG founder)

Key points

  1. 1

    Engineers are the best source of innovation

    Cagan says engineers are the best single source of innovation, ahead of customers, executives and product managers. He says this has been known for decades. Engineers work with the enabling technology every day, so they are first to see what just became possible. He points to the AI companies whose new products people love: engineers invented them. He admits a bias, since he worked as an engineer for the first 10 years of his career.

    “the best single source of innovation is not our customers, it's not our executives, it's not our product managers. It's the engineers.”
    Marty Cagan, The Product Engineers Podcast, 05:43
  2. 2

    Sprint planning is too late

    In a feature factory, the roadmap is set and engineers execute it. In a product company, Cagan says, the job is to work out what to build as well as to build it. An engineer at a consultancy builds what the client asks for. An empowered engineer cares as much about what gets built as about how it gets built.

    “If the first time the engineers are seeing the idea is at sprint planning, you have failed.”
    Marty Cagan, The Product Engineers Podcast, 06:28
  3. 3

    Engineers should push back

    Cagan gives two reasons for an engineer to say no to a feature. The feature may be a bad idea, such as copying a competitor without knowing whether anyone uses it. Or the product manager has not explained why it is a good one. An engineer who builds only because they were told to is a mercenary, he says. Pushback is how a product team corrects itself, and a tech lead has to be comfortable doing it.

    “we do not want the engineers to build it because they were told to. That's a mercenary. We want them to build it”
    Marty Cagan, The Product Engineers Podcast, 19:57
  4. 4

    Prototype the idea and show it

    Engineers in companies without real product managers can still act, Cagan says. Talk to the head of sales, then build a prototype of a better solution in Claude Code, Lovable or whatever tool you use. The prototype exists to illustrate the idea, and nobody ships it. Executives ignore slide decks and talk, he says, and respond to a prototype. Showing it to a customer is better still.

    “then the secret weapon that anybody can do today, not just engineers, is when you get an idea of a better solution, just prototype it.”
    Marty Cagan, The Product Engineers Podcast, 50:10

Where experts disagree

Jake Knapp holds the prototype back. In his five-day design sprint the team maps the problem, sketches options and picks one before it builds a prototype on day four. Cagan tells engineers to build one as soon as they have an idea for a better solution.

Jake Knapp on holding the prototype until day four

How it compares

How this recording lines up with what Marty said before and with other operators Gavel cites.

Agrees with

Tara Seshan prefers mocks to docs, since something people can try beats a written brief. Cagan says executives respond the same way.

Tara Seshan on prototypes over docs

Agrees with

Teresa Torres puts the engineer in the product trio. The product manager, the designer and the engineer decide together. That is Cagan's point about sprint planning: engineers belong in the room before the work is set.

Teresa Torres on the product trio

Related

Want the full playbook?

Get 128 product management frameworks.

34 frameworks 21 rules 65 heuristics & principles 49 operators

From Stewart Butterfield, Ami Vora, Codebase Guidelines, and 46 more. Drop one .md into Claude, Cursor, or ChatGPT. Your AI cites practitioners, not guesses.

See the pack

Instant .md download · One-time purchase · No subscription

New experts every week

Know when the next expert lands.

Gavel adds new operators to the database every week, each one with cited frameworks you can check and a note on where they disagree with the others. You found this page by searching. Get the next one by email instead.

65 experts 84 cited frameworks

Latest: Gary Klein on The Premortem

One email a week, only when new experts shipped. Unsubscribe with one click. We never sell or share email.

More talks

All talks