By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that as teams move to frequent or continuous delivery, releases can surprise customers and internal stakeholders such as sales, service, and product marketing. Most incremental releases are invisible to users, but visible changes need deliberate management. He describes a 'Customer Impact Assessment' performed just before going live, in which the product manager and product marketing decide how to handle changes, including delaying them or shipping them dark. He also notes that good UX design can prevent customer impact rather than only managing it. The piece matters because frequent releases make coordination harder, since product managers own priorities but not exact delivery timing.
01Key takeaways
- Release at least every two weeks; infrequent big-bang releases make surprises more likely and hurt competitiveness.
- Flag customer-visible backlog items early and give product marketing a heads-up before they ship.
- Run a short impact check before each push, sorting changes into invisible, visible-harmless, and visible-with-impact buckets.
- If stakeholders are not prepared for a visible change, delay it or ship it dark until they are.
- Design visible changes to minimize disruption and make new capabilities easy to discover, preventing issues rather than only managing them.
02Key sections
- Why frequent releases create surprises
- Rapid releases can change customer workflows, sales demos, or service workarounds without warning. Cagan notes that surprises cannot be fully prevented but can be reduced.
- Most releases are invisible
- Typical incremental releases touch internals or minor fixes that customers and frontline teams never notice, so only a subset needs coordination.
- Coordination gap between PM and delivery
- The product manager owns the backlog and priorities but does not control build and test timing, making it hard to know exactly when visible changes will ship.
- The Customer Impact Assessment
- A pre-release check sorts changes into not visible, visible but harmless, and visible with potential impact, with product marketing leading preparation for the last group.
- Designing to avoid impact
- Designing changes to minimize disruption and ease discovery of new capabilities can prevent many customer impact issues in the first place.
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.