Pledge To Customers

Marty Cagan argues that as companies shift from sales-driven feature teams to empowered product teams, the way product teams engage customers changes, and customers need to understand why. He frames a set of pledges that product teams can make to customers, covering promises, product discovery, and delivery. The core idea is that commitments should only be made after real discovery with direct user access, and that solutions must be valuable, usable, feasible, and viable. The pledges matter because customers are willing to accept the change only if they believe their needs will be met more reliably than before.

01Key takeaways

• Explain to customers why commitments will now come from the team that will build the solution, so they understand the change.
• Only commit to a date or deliverable after discovery work has shown what is truly required and that the solution will work.
• Engage directly with actual users rather than relying on account managers or other proxies to understand their needs.
• Design solutions that generalize across customers; if a request only works for one customer, consider alternatives or a custom-solution provider.
• Judge every solution against value, usability, technical feasibility, and business viability, including compliance.
• Minimize adoption cost for customers and treat fast, transparent correction of mistakes as a core responsibility.

02Key sections

Why explain the change to customers

Customers are used to dictating features to sales and expecting dated roadmap commitments, and they may already doubt delivery. Explaining the shift helps them accept a new dynamic that they expect will serve them better.

Promises and high-integrity commitments

Only the product team that will deliver should make promises, and only after enough discovery to know what is required. Proxies such as account managers cannot substitute for direct access to users.

Commercial products versus custom solutions

A commercial product must work for many customers, not just one. When a request is too narrow, the team explores alternatives or refers the customer to a custom-solution provider.

Product discovery standards

Solutions must solve the customer's problem, be technically feasible, and be viable for the business, including funding, monetization, and regulatory compliance. Cross-functional product, design, and engineering staff interview users and test prototypes.

Delivery obligations

The team commits to testing for both new functionality and regressions, minimizing disruption to users' workflows, and quickly correcting and learning from mistakes.

Referenceable customers

The highest goal is that customers use the product daily for meaningful work and love it enough to recommend it to 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.