How to manage a PDE function that does not want to commit to any dates, ever, but also does not want to uncouple release from launch?
I'm establishing PMM at my org as a function, and trying to put in place a launch process. The PDE function are used to just shipping when ready, without giving thought to the need for a launch plan. We're missing opportunities to launch, but also annoying clients by not giving enough notice when we plan to roll out new features or functionality.
.png)
Top Product Marketing Mentors
Claudia Michon
Automation Anywhere Senior Vice President, Product & Solutions Marketing
Sarah Din
Quickbase VP of Product Marketing
Mary Sheehan
Adobe Head of Lightroom Product Marketing
Alex Lobert
Meta Product Marketing Lead, Facebook for Business & Commerce
Jenna Crane
Klaviyo Head of Product Marketing
Kevin Garcia
Anthropic Product Marketing Leader
Christine Sotelo-Dag
ThoughtSpot Senior Director of Product Marketing
Amanda Groves
Crossbeam Senior Director Product Marketing
Amanda Groves
Crossbeam Senior Director Product Marketing
Alissa Lydon
Dovetail Product Marketing Lead
Related Questions
What role should a product launch have with your existing customers?How do you and the PMM team communicate updates and progress on your product launch to the rest of the org? What is the format? What do you report back on? Etc.Do you have a framework or process for determining what tactics to use as part of your launch? What are the main components of your GTM strategy? How do those vary by product type?If your product team works in two-week sprints, how do you balance and prioritize each launch? In other words is a "release" always a "launch" and how do you differentiate and treat each? What’s your advice on how best to handle communicating tier 2 and 3 product releases? E.g., all of the updates that aren’t big, flashy new features?