Building Productive PMM - I share practical advice, templates, and inspiration for founding product marketers.
What’s the difference between a #release and a #launch? Both are closely related, but not the same thing. 🔘 A Release = pushing code to production. This can be as small as a big fix to as big as a new game-changing product. 🚀 A Launch = a go-to-market event that brings value to your customers and your business. If you have an agile development process, there could be releases happening every week. Some are big news, but most are not. Which is totally fine. The word “launch” should be associated with something meaningful that brings notable value to your customers and your business. After all, if you treated every release like a launch, you would: 😵💫 Create too much noise → you would drown out the important stuff. Customers wouldn't be able to keep up. You'd see diminishing returns. 😓 Burn out → your go-to-market teams would just be running from one launch to the next. Sales would be changing their pitch every week. Marketing would only focus on launch campaigns. That’s why a launch tiering system is important. It gives you a framework for prioritizing your releases and determining what level of go-to-market effort is required. And remember — just because you release something today that goes undetected, doesn’t mean it can’t be launched later on. You can bundle multiple small, released features into a larger launch around a specific theme. Take Canva for example. I’ve been noticing new AI-powered image editing features over the last couple of months. Then last week, they launch “Magic Studio” where all of these small enhancements became part of a much bigger launch and story. -------------------------- Looking to up-level your product launches? Check out Ready for Launch - the PMM’s guide to product launches. Bit(dot)ly/ready-for-launch #productmarketing #productlaunch #launch
Agree! I have worked with clients on naming the various stages of a product lifestyle and advocate that we create an internal glossary of terms. Each of these means different things with different levels of effort and different teams involved. Sometimes you even give access to customers but you don't do a full marketing launch yet - there's a unique one;)
This needs to be talked about way more - not every release is a launch. And, when you over-sell every feature you release, you may actually lose attention and impact on the larger, key launch moments throughout the year (customer fatigue). Major stakeholder management needed with this though, particularly with product teams (and founders) 🙃
Fantastic visual - the art is that the delivery and product understand that they cannot do releases without PMM/growth/marketing team.
I like to look at it this way: Release: the product led introduction of new functionality into the market. Launch: the marketing led introduction of new functionality to the world. Aligning PM/PMM to get the most bang for your buck on new product functionality is critical.
Sound familiar Matt Mayhew? You and Jason Oakley should connect to share frameworks. Matt has a great PPT and launch plan framework which has really helped us here at Prophix.
Great explanation, Jason Oakley! 🚀 Indeed, distinguishing between a release and a launch is crucial. Releases keep the development cycle moving, but launches are the moments that truly matter for customers and the business. In the world of Agile, it's easy to have frequent releases. As a Technology Manager, I've seen the importance of strategically timing launches. It's about creating an impact without overwhelming your audience. Your point about tiering is spot on. Prioritisation and focused go-to-market efforts are key. It ensures that what truly adds value gets the spotlight. Canva's approach is a brilliant example. They transformed small releases into a compelling story. It's all about the narrative and how it resonates with the audience. Keep sharing these insights, Jason! They're invaluable for tech professionals. 🚀👨💻🌟
Super insightful, Jason. The GTM component of the launch is key difference. I sometimes look at a release that brings a ton of value to a customer but doesn’t affect our GTM motion, and WANT to call it a “launch.” But I think you’re right that if it doesn’t affect GTM, it’s not a launch.
This design aesthetic 🔥🔥🔥🔥🔥🔥
Yup—the features might have released, but maybe you're still working on the story before you officially launch. It's easy to freak out when you release important features without coupling them with a launch. But we're all wayyyyy closer to our products than users are—many might not even notice the feature in the first few weeks.
PMM Career and Leadership Coach | Startup Product Marketing Advisor | 3x Startup PMM Leader | Berkeley MBA | Learn more: 👉 courageous-careers.com
7moWell said! A launch is a strategy, a release is....well, just a release as you described. This is literally the first thing I share with my product counterparts and my team in the first month on the job, because confusing the two is way too common! As a PMM you have the power to launch a product WHEN you believe is best for the market environment, and most likely it is not when it is immediately released.