Communicating Product Learnings

Marty Cagan argues that as a company scales, the natural sharing of product learnings that happens in a small startup breaks down, so it must be done deliberately. He recommends a recurring, brief update, run by the VP of Product every week or two, that highlights the big learnings from product discovery across teams. The update is meant to stay high-level, covering what worked, what didn't, and what teams plan to try next, rather than detailed sprint-style reporting. Beyond the tactical value of spreading insights, the practice reinforces a culture of continuous experimentation and transparency. It signals that product exists to solve customer problems in ways that work for the business, not merely to serve the business.

01Key takeaways

• As companies grow, deliberately share product learnings, because they no longer spread naturally.
• Hold a short update every week or two that covers only the big discovery learnings.
• Have the VP of Product deliver the update so it stays fast and high-level.
• Share failed experiments openly, since others may offer insight into why results fell short.
• Use the forum to keep teams focused on learnings that affect customers or the business, not minor experiments.
• Be transparent about learning to show the organization that product solves customer problems in ways that work for the business.

02Key sections

The problem of scale

In a startup, learnings flow naturally because the product team and the company are essentially the same. As organizations grow, that sharing becomes harder and more important.

The recurring learnings update

The head of product gives a short, regular briefing to the whole company on the bigger discovery learnings across product teams. It focuses on significant results rather than minor experiments.

Why the VP of Product leads it

The update must move quickly and stay at a high level, so it is best delivered by one leader rather than by every product manager presenting detailed work.

Tactical benefits

Sharing big learnings, especially failures, lets others offer insights, helps teams stay aware of each other's findings, and ensures useful lessons reach leadership.

Cultural benefits

The practice builds an understanding that innovation means running rapid experiments, and that product is transparent and generous with learning in service of customers and the business.

03From the post

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

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