By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that integrity is the foundation of trust in empowered product teams, and that trust rests on both competence and character. He acknowledges that integrity is hard to maintain, since product managers constantly face pressure from executives, customers, stakeholders, and partners. He contrasts the messenger role of a feature-team product manager with the greater expectation on empowered PMs to find solutions that serve both customers and the business. Cagan frames integrity around three behaviors he coaches: dependability, acting in the company's best interests, and accountability. He notes that integrity does not require perfection, only consistent dependability and responsibility for mistakes.
01Key takeaways
- Only make commitments after enough discovery to understand value, usability, feasibility, and viability risks, leaning on designers and engineers.
- Deliver commitments in a way that solves the customer or business problem, not just ships on time.
- Look for chances to act for the whole company, such as helping another team hit its objective or backing a better decision for the business.
- Share the overall purpose of the work rather than relying on imposed deadlines to keep an empowered team engaged.
- When things fail, ask what you could have managed better, such as feasibility or legal risks, before attributing fault to others.
- Integrity allows for mistakes; a reputation survives if you are dependable overall and take responsibility when you err.
02Key sections
- Why integrity is hard
- Product managers face recurring conflicts between urgent executive demands, team constraints, frustrated customers, and stakeholder or partner expectations. Cagan says integrity is the foundation for good decisions in empowered teams.
- Feature team versus empowered team
- A feature-team PM mainly relays requirements and status, while an empowered PM must find workable solutions balancing customer and business needs.
- Dependability
- Commitments should only be made after adequate discovery of value, usability, feasibility, and viability, and then delivered in a way that actually solves the problem.
- Company's best interests
- PMs should be seen as serving the whole company rather than their own team or career, even when this means choosing a decision that is less optimal for their team.
- Accountability
- Empowerment brings responsibility for results, so PMs should ask what they could have done differently, including managing risks during discovery, rather than only blaming others.
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.