structure for the “why” behind a developing roadmap Develops expertise in eyes of org, especially important if PMM role is historically outbound-driven Product Common language as you talk about a nebulous problem
Where is the market today and where do we expect it to go? How can we differentiate vs. competitors? Product What do we need to build and for whom do we build? What is the total opportunity and what can we expect to capture based on our product and customers?
product teams… They’ll be incentivized to ship (every Q or every half) They’ll need “product vision” for the next 12-24 months They may be stacked against adoption or revenue goals Product YOUR INBOUND INSIGHTS = MORE LIKELY TO REACH THEIR GOALS
of a “team sport” The other cross functions – data science, engineering, design, content strategy, UX, will all have a role in influencing the roadmap Get them on your side
N S PROCESS - New/improved production or delivery - Enabled by changes in technique, software - Costs / profit NOT QUITE AS SEXY, CAN BE JUST AS IMPACTFUL