Empowered Engineers FAQ

Marty Cagan answers the most common objections people raise against the idea of empowered engineers, the engineers who take part in product discovery rather than only building what they are handed. He argues that the objections, such as engineers only wanting to code or product managers wanting to stay in a narrow role, often mask problems with the product manager's approach or the company's hiring and process choices. He suggests these attitudes help explain why strong product companies value technology backgrounds in product managers. The piece matters because it reframes engineer involvement as a core product-team responsibility rather than an optional extra.

01Key takeaways

• Speak directly with engineers before accepting that they are uninterested in discovery work.
• Bring engineers face to face with customers so they see both the good and the painful parts.
• Ensure each product team has at least one true tech lead who shares discovery responsibility.
• Recognize that many hard technical problems are fundamentally business and customer problems worth engineer involvement.
• If engineers lack customer understanding, treat it as a product manager responsibility to fix immediately.
• Empowering engineers does not reduce the need for strong product managers and product designers on the team.

02Key sections

Engineers who only want to code

The most common objection is that engineers are uninterested in discovery. Cagan finds that when he speaks to engineers directly, they usually say they were brought in too late, and the blame often lies with a product manager who avoids including them.

Over-engineering and hard technical problems

Some worry empowered engineers will over-engineer or chase new technology. Cagan responds that engineers who understand customer pain are motivated by it, and that many hard technical problems are really business and customer problems.

Engineers clueless about customers and PM roles

When engineers lack customer understanding, Cagan places responsibility on the product manager. Many product managers of feature teams struggle to see their own role, which he argues is a project-manager role in disguise.

Process and structure objections

Cagan dismisses the idea that a product manager can simply define problems and step aside, noting this presumes a product strategy exists. He also argues frameworks like SAFe are incompatible with empowered engineers at innovation-driven companies.

Product management still matters

Cagan clarifies that empowering engineers does not diminish the importance of product managers and product designers, since extraordinary products come from complete product teams.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.