By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that many teams disband the people who built and launched a product right after release, wasting the period when learning and correction are most valuable. He proposes a dedicated "Rapid Response" phase lasting at least two weeks after launch, focused on quickly reacting to what live usage reveals. He notes this applies beyond consumer internet to platform, infrastructure, and enterprise products. Success depends on knowing what to measure, spotting problems fast, and responding fast, since issues are inevitable even after thorough pre-launch validation. The phase offers high return on investment and is an easy case to make to management.
01Key takeaways
- Keep the core product team engaged for at least two weeks after launch instead of reassigning them immediately.
- Define in advance which business metrics matter and what results count as success or as a problem.
- Instrument your product so you can see user behavior in near real time after release.
- Meet at least daily after launch to prioritize issues and decide on hot fixes or explanatory content.
- For enterprise products, have team members work alongside the customer through installation until the deployment is live and referenceable.
- Assume issues will surface only after launch, and optimize for how fast you respond rather than hoping for none.
02Key sections
- Launch is not the finish line
- Teams often reassign their resources right after launch, which wastes the most valuable learning window. Cagan treats this as a process failure that can be fixed by extending the project.
- Introducing the Rapid Response phase
- He recommends scheduling a phase starting at launch and lasting at least two weeks, applicable to consumer, platform, infrastructure, and enterprise products alike.
- Expect issues and measure how fast you respond
- Even well-validated, reliable products surface problems only in production, so the real question is how quickly the team addresses them. Waiting for complaints and then slowly shipping point releases is too slow and costly.
- Three keys: metrics, detection, and response
- Success requires a prioritized set of business metrics with defined thresholds for success and problems, fast insight into user behavior, and a team that meets at least daily to prioritize and act.
- Analytics and embedded teams
- Consumer teams can instrument usage easily, while enterprise teams benefit from sending members to customer sites through go-live. Analytics and surveys together give near real-time signals that Cagan checks almost daily.
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.