This document provides guidance on how to prioritize features and plan a product roadmap. It recommends defining objectives and key results (OKRs) to establish goals. Features should help achieve the key results. An example lists OKRs for increasing usage and decreasing dissatisfaction. The document also advises gathering requirements from various sources, prioritizing features, and communicating the roadmap regularly. The overall message is that defining goals through OKRs helps focus development efforts and prioritize the right features.

1. How to Drive Prioritization and Planning by
Microsoft PM
www.productschool.com

2. FREE INVITE
Join 23,000+ Product Managers on

3. COURSES
Product Management
Learn the skills you need to land a product manager job

4. COURSES
Coding for Managers
Build a website and gain the technical knowledge to lead software engineers

5. COURSES
Data Analytics for Managers
Learn the skills to understand web analytics, SQL and machine learning concepts

6. COURSES
Blockchain and Cryptocurrencies
Learn how to trade cryptocurrencies and build products using the blockchain

7. Salah Ahmed
TONIGHT’S SPEAKERS

8. Roadmap Prioritization &
Planning
Salah Ahmed

9. Roadmap prioritization and planning
• The Problem: What to build?
• Gathering requirements
• Defining your goals using OKR methodology
• Advantages of using OKRs
• Prioritizing the features
• Communicating your roadmap

10. Your customers are screaming at you to build new features.
Your dev team wants to pay off engineering debt.
Your manager has his own agenda.
Your partner teams also have requests.
So what should you build?

12. Unprioritized list of features
• Talk to customers
• Feedback from official channels
• Social media: Twitter, LinkedIn, Reddit
• Talk to sales
• Telemetry
• How’s your usage?
• How’s your quality?
• What are you missing?
• How do you fit into your org’s strategy?
• What are your competitors doing?

13. “If you don’t know where you are
going, you might not get there.”
Yogi Berra

14. Objectives and Key Results (OKRs)
methodology
Objectives should be
• Long term. Shouldn’t change month to month
• Up to 3 objectives for each PM. Up to 5 objectives for a PM team
Key Results should be
• SMART: Specific, Measurable, Attainable, Relevant, Timely
• 3- 5 Key Results per Objective
• Flexible and updatable
“We will deliver a certain OBJECTIVE as measured by
the following KEY RESULTS: ….”

15. Advantages of using OKRs
• Requires regular planning
• Commitment from all stakeholders
• Transparency
• Provides focus
• Accountability tracking
• Makes it easier to say no
• Stretch goals boost morale

16. Sample OKRs
We will increase usage as
measured by the following key
results:
• Increase monthly active
enterprise customers by 3X in
the next 3 months
• Increase monthly active users
by 2X in the next 3 months
• Increasing new app sign-ups
by 2X in the next 3 months
We will decrease customer
dissatisfaction as measured by
the following key results:
• Reduce app crashes by 2X in
the next 3 months
• Reduce support tickets by 3X
in the next 3 months
• Improving availability to 99% in
next 3 months

18. Create prioritized list of features
• Should help you achieve your Key Results
• List should ideally be stack-ranked
• Accurate list for next 3 months
• Less accurate for next 6 months
• Everything else goes into >6 months bucket

19. Communicate!
• Communicate your features to your team and partners
• Send regular status updates
• Tweak Key Results if required. Prioritize on an ongoing basis

21. Recommended reading

22. Key takeaways
• Define your objectives and key
results (OKRs)
• Prioritize a list of features and plan
your roadmap with your OKRs in
mind
• Communicate the roadmap to
partners and customers
• Close the loop by tracking success

23. Part-time Product Management Courses in
San Francisco, Silicon Valley, Los Angeles, New York, Austin,
Boston, Seattle, Chicago, Denver, London, Toronto
www.productschool.com