The Three "I"s of B2B Roadmapping
•Download as PPTX, PDF•
0 likes•314 views
My talk at Product Management Festival 2018. Try Ruum: www.ruumapp.com #PMF18
Recommended
Recommended
More Related Content
Similar to The Three "I"s of B2B Roadmapping
Similar to The Three "I"s of B2B Roadmapping (20)
Recently uploaded
Recently uploaded (20)
The Three "I"s of B2B Roadmapping
- 1. The Three “I”s of B2B Roadmapping
- 2. The Three “I”s of B2B Roadmapping Infrastructure, Interface, Intelligence
- 3. I <3 SaaS
- 5. 200 Things We Could Do
- 6. 200 Things We Could Do
- 7. Effort
- 8. Revenue
- 11. Competition
- 12. Time
- 14. Infrastructure
- 15. Infrastructure Applied Review SLA in every planning and mid-sprint review to prioritize infra work.
- 16. Interface
- 17. Interface Applied Review your North Star metric every day during stand up.
- 18. Interface Applied Review your North Star metric every day during stand up + projections.
- 19. Intelligence
- 21. Intelligence Applied Everyone in the team has access to Jupyterhub - connected to live & anonymized usage data for their investigations.
- 22. Putting it all together
- 23. Putting it all together Infrastructure: monitor SLA to re-prioritize Interface: build for buyers and end-users, based on your north star Intelligence: build AI-first and make everyone in the team a data analyst
- 24. Closing thoughts We’re hiring in Berlin: @stefanritter
- 25. Closing thoughts We’re hiring in Berlin: @stefanritter
Editor's Notes
- I’d like to share with you something, that at least for me, changed my life as a PM. And simplified Atmosphere Thom yesterday morning said good PMs need to be able to break every problem into three points.
- But before I go into the details of each, let me take a step back and show you how I got here.
- I love working in SaaS - especially at SAP every day a new industry a new customer with their specific problems. Working on something people use every day.
- 3am - you get the call you’re all dreading The app is down - isn’t this awesome
- Try with revenue, let’s prioritize all the tasks we believe have the most impact on the bottom line. ARR, ARM
- Kano
- 3am story, but another good one 3 years ago, supply chain solution, 10% savings in raw material, put so much load on the DB that it tripled the time it takes to process a truck at the warehouse. >> learning, when building customer requests, never forget the infra
- If we would have had end 2 end tests in our SLA, we would have noticed
- B2B - the buyer is often not the user. This is an SAP event, many C levels. Swarovski story, takes out his phone to show everyone what he can do know with this shiny new SAP
- You need a metric that normalizes all stories and features built. North star, revenue is a lagging indicator. Ideally you want a leading indicator - more weekly active users, will lead to more revenue.
- I’m sure most of you have heard about AI and ML
- Everyone in the team has access to GA, Amplitude, etc. but most importantly everyone knows a bit of data analysis, Udacity
- The components of my roadmap, it exists in github, airtable, community page, excel Interface are end user features, plus growth hacks Infra includes API work, scale work, integration work Intelligence is everything around ML and AI, data collecting, notifications Customer specific needs are marked on the post it.