The Most Important Thing

Marty Cagan argues that if he could change only one thing about how a product organization works, it would be empowering engineers. Engineers work with enabling technology daily, so they are best placed to spot what is newly possible and are often the best source of innovation. Empowerment means giving engineers the problem, the strategic context, and the freedom to find the best technical solution, not merely letting them code what they are handed. Cagan notes that treating engineers as first-class product team members, rather than outsourced coders, is what separates missionary teams from mercenary ones. For product leaders, this reframes engineering from an execution resource into a primary source of product insight.

01Key takeaways

• Give engineers the problem, the strategic context, and the outcomes to pursue, then let them find the solution.
• If engineers first see product ideas at sprint planning, your team is a feature team and engineers are underused.
• Treat engineers as first-class members of product teams, not as outsourced coders.
• Use dual-track career ladders so top engineers can grow and be recognized without moving into management.
• Engineers are often the best source of innovation because they see daily what the technology now makes possible.

02Key sections

Choosing one change

Cagan reflects on a listener question about the single most important change for a feature team. He settles on empowering engineers over his usual answer of user research, which assumes the team is already empowered.

What empowerment means

Empowerment is not just letting engineers choose implementation or architecture. It means giving them the problem, the strategic context, and room to apply technology creatively.

How the product system supports engineers

Vision, strategy, objectives, product and design constraints, and research and data each play a role in equipping engineers to solve the right problems well.

Signs of empowerment

A simple test is whether engineers first see a product idea only at sprint planning, which would indicate they are not empowered. Strong tech companies use dual-track career ladders and treat top engineers as senior leaders.

Engineering-driven companies

A company described as engineering-driven often already has the most important piece in place, which makes the move to a strong product company easier.

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.