Template PPT

1. Now, choose your prioritization method
Value/
Effort Scale
Kano Model
MoSCoW
Feasibility,
Desirability,
Viability
Rice Scoring
Model

2. MoSCoW Method
Prioritization Guidelines
1. Define your business
values
2. Define your risks
3. Edit your priority
categories as needed
Must have
Absolutely vital
components
You genuinely cannot launch without this due to legal reasons, safety
concerns, or business needs. Perhaps you’ve created based your marketing
campaign off a specific new feature—it would be a terrible idea to launch
without this!
Should have
High-priority features
It would be best to include these, but your product won’t be an absolute
failure without them.
Could have
Possible optional
features
Nice-to-haves if you have the resources and time. But not necessary for
success. Think of how each requirement (or lack thereof) will affect customer
experience. The lesser the impact, the further down the list it goes!
Won’t have
Will not be
implemented
To include in V2, or to collect dust in the backlog for all of eternity. Either
way, you’ve made an active decision that it’s not coming out with this launch.
MoSCoW: Must have, Should have, Could have, Won’t have

3. Example: MoSCoW Method
Book Review Website: Beta Launch
M
● Create account
function
● Login function
● Leave text review
function
● Giving review stars
● Book search
function
● Fix redirect bug
S
● Mobile
compatibility
● Fast page load
time
● Ask for help
feature
● Personal library of
old reviews
● Personal timeline
of books read
● Follow other users
function
C
● Automatically
remember old help
session when re-
entering site
● Nav bar freeze in
scroll
● “More books like
this” feature
W
● Reading speed
tracker
● In-depth sub-
genre evaluation /
profile
categorization
● Chat with other
users

4. Kano Model
Need
not met
User
dissatisfaction
Need fully
met
User
satisfaction
Need not
met
User
dissatisfaction
Need
fully met
User
satisfaction
Must have
Performance
(more is better)
Delighter
(wow)
Needs & features
migrate over time

5. Kano Model
Prioritization Guidelines
1. Define your Delighters,
performance features,
and basic features
2. Delighters are highest
priority if all of the
essential infrastructure
(basic and performance
features) are built
3. Performance feature
priority depends on
customer demand
4. If you’re improving a
basic feature (instead of
creating it), it’s not a high
priority
5. Based on this input, make
an ordered list to show
what order you will build
the features in.
Delighters
The features that customers will perceive as going ‘above and beyond’ their
expectations. These are the things that will differentiate you from your
competition.
Pay attention! Over time, features that used to be Delighters can move to
Basic features as users come to expect them.
Performance
features
Customers respond well to high investments in performance features.
Basic features
Basic features. The minimum expected by customers to solve their problem.
Without these, the product is useless to them.
Indifferent Features your users could take or leave.
From Dan Olsen’s “The Lean Product Playbook”

6. Example: Kano Model
Book Review Website: Beta Launch
Basic
Improve signup questionnaire
Improve login function
Leave text review function
Giving review stars
Book search function
Personal library of old reviews
Personal timeline of books
read
Delighters
Creative book tagging
capability
“For you” list - in depth profile
with preferences (genre, types
of characters/plot liked and
disliked)
“On my shelf” - To be read
“More books like this” feature
Follow other users function
Reading speed tracker
Performance
Fix redirect bug
Mobile compatibility
Fast page load time
Ask for help feature
Simple and open frontend
design - lots of white space
Indifferent
Chat with other users
Nav bar freeze in scroll

7. Kano Model
Ordered list of features
1. Fix redirect bug
2. Fast page load time
3. Book search function
4. Giving review stars
5. Creative book tagging capability
6. Mobile compatibility
7. Leave text review function
8. Personal library of old reviews
9. Improve sign-up questionnaire
10. “For you” list - in depth profile with preferences (genre,
types of characters/plot liked and disliked)
11. “On my shelf” - To be read
12. “More books like this” feature
Ordered list of features, cont.
13. Personal timeline of books read
14. Ask for help feature
15. Reading speed tracker
16. Simple and open frontend design - lots of white
space
17. Improve login function
18. Follow other users function
19. Nav bar freeze in scroll
20. Chat with other users

8. Feasibility, Desirability, and Viability
Prioritization Guidelines
1. Align with technical team
2. Get customer validation
3. Check business and
market viability
4. Sort by highest score to
lowest score so you
know what to build first
Feasibility
How technically possible or practical is the feature given the set of resources
and tools that you currently have? Avoiding impossible or highly improbable
features by aligning your feature with your back-end engineers, UI designers,
and front-end developers.
Desirability
Is the feature wanted by users? Discuss the feature with researchers, UX
designers, marketers, and support, and go through any already existing user
tests and validation.
Viability
Alignment with overall business strategy and market reality. Talk to
executives and other PMs to understand how this feature works in the bigger
ecosystem of your company and the market.
Talk with your team, customers, and stakeholders

9. Example: Feasibility, Desirability, and Viability (on a scale of 10)
Feature Feasibility Desirability Viability Total (sum)
Sign up function 10 10 10 30
Login function 10 10 10 30
Search feature 8 10 10 28
Review feature 7 9 10 26
“More books like this”
feature
6 8 8 22
Ask for help feature 8 7 6 21
Chat with other users 6 4 7 17
Book Review Website: Beta Launch

10. Value/Effort Scale
Prioritization Guidelines
1. Rate each feature by
a) effort to build the
feature and b) potential
impact on business value
2. Create a 2x2 grid
3. Map out features on grid
4. The objective is to
identify features that will
have the highest impact
with the lowest effort.
Build these first. Next,
build high impact, high
effort features.
5. Deprioritize low impact,
low effort features, and
do NOT build low
impact, high effort
features!
Identify high impact, low effort tasks
High
Complexity/effort
Low
Business
value
High
1 2
X
?

11. 1 2
X
Value
Effort
Map out your each feature idea
on a sticky note and draw your
matrix on a board.
Value/Effort Scale
TIP
If you’re in-person with your team or
using a virtual whiteboard, you can
range and map out your sticky notes live
with your team!
Feature #1
?
Feature #2
Feature #3 Feature #4
Feature #5 Feature #6

12. Example: Value/Effort Scale
Feature Effort to build (/10) Business value (/10)
Login function 3 10
Search feature 5 10
Review feature 8 10
Sign up function 3 10
“More books like this”
feature
8 9
Ask for help feature 4 6
Chat with other users 5 7
Book Review Website: Beta Launch

13. X
Value
Effort
Map out your each feature idea
on a sticky note and draw your
matrix on a board.
Example: Value/Effort Scale
TIP
If you’re in-person with your team or
using a virtual whiteboard, you can
range and map out your sticky notes live
with your team!
Book Review Website: Beta Launch
Search
feature
Review
feature
“More
books like
this” feature
?
Chat with
other users
0 10
10
Sign up
function
Login
function
Ask for help
feature
1 2
4
3
5
6

14. Customer Journey Map
[Insert Title Here]
Template validated by Rachael Larsen, Senior Director of Product at Product School

15. Give context
Project name
Start thinking about…
1. Touchpoints
2. Actions
3. Thought
4. Feelings
5. Paint points
6. Opportunities
Define
Stage
Are you mapping a currently existing journey, or potential future one?
Customer
persona
Every user will have a different journey. Choose one persona to focus on and dive
deep into their specific experience of your product.
Scope &
Timeframe
What aspect of your product are you focusing on? You can go big or get granular.
On one hand, you can map out the customer lifecycle journey. On the other, you
can map out the use of a specific feature or moment within the overall product use.

16. Definitions
Touchpoints
All of the moments a customer directly interacts with your company or product.
Actions
What actions does the customer take in these interactions?
Thoughts
What thoughts does the customer have before, during, after?
Feelings
Use a scale or use one word to describe the user’s emotional state.
Pain points
What are problems and annoyances the user experiences?
Opportunities / Gain point
How can you fix a user’s problem or find a new way to delight them? What about the experience is already delightful?

17. Action or Touchpoint Map
Add note
here
Add note
here
Phase 1
Phase 2
Gain point
Pain point
An outline of customer actions or interactions with your product (actions or touchpoints depending on scope of
the journey. Longer journeys can use touchpoints, shorter journeys will tend to use actions)

18. Give context
First time ride call in ridesharing app
Define
Stage
Currently existing journey
Customer
persona
A person calling a ride through your app for the first time to see how it compares
with a competitor’s
Scope &
Timeframe
Small scope. Just the few minutes, covering account setup and first call
Start thinking about…
1. Touchpoints
2. Actions
3. Thought
4. Feelings
5. Paint points
6. Opportunities

19. Customer Journey Map Part 1
First time ride call in ridesharing app
Account setup Account setup Account setup Account setup
Steps First app open Accept permissions Begin account setup
Enter phone and email
information
Touchpoints Interaction with app
Actions Click to open
Have to make a selection
between allowing location
services “only one” “only
when the app is open” and
“always”
Click “start” Click into
Thoughts “Ooh I like their logo”
“I don’t like sharing my
data”
Feelings (1-5)
4 (unsure if they will like
your app but open-minded
2 (annoyed but accept this
as part of the process)
3 (things are moving
along)
Pain points Long loading time Have to make a choice
Lots of asks one after
another
Opportunities/
Gain point
Set permissions ask later in
journey
Consolidate the asks into
one (i.e. ask for gmail
account and autofill)

20. Customer Journey Map Part 2
First time ride call through ridesharing app
Account setup Account setup Account setup Call ride Call ride
Steps Confirm information
Accept terms and
service
Enter payment
information
Enter destination
address
Confirm ride
Touchpoints
Interaction through,
text, email and app
Actions
Leave app to check
messages and
manually enter. Leave
app to open email and
click confirmation link
Scroll quickly to
the bottom and
click “Accept”
Stand up, grab credit
card, enter card
information manually
Leave app, opens
chat app to confirm
address. Enters home
and destination
address
Clicks button to
confirm and waits to
see the driver
confirmed and how
many minutes away
Thoughts “Not reading this”
“When will I be able
to order my ride??”
“Finally!”
Thinking about how
long before pickup, if
they’ll make it on
time to the event
Feelings (1-5) 2 2 1 3 4
Pain points Have to leave app Long load time
Opportunities
/Gain point
Can automatically fill
out info for a seamless
experience
Message that this is
the final step
Offer discount to
make them excited
about first ride

21. First app open Begin account
setup
Accept
permissions
Enter personal
information
Confirm
information
Enter destination
address
Confirm Ride
Persona: Customer familiar with rideshare apps, trying
yours for the first time. Opportunity to win them over.
Set this
ask to
later in
journey
First time ride call in ridesharing app
Account setup
Ride calling
Gain point
Pain point
Accept Terms &
Service
Enter payment
information
Long load
time
Choice
early on
Multiple
asks in a
row
Have to
leave app
Autofill
this info
for user
Encouraging
message
Long load
time
Discount
off of first
ride

22. Product Roadmap
Template validated by Amin Bashi, VP of Product, and Rachael Larsen, Senior Director of Product at Product School
[Insert Title Here]

23. THE TECHNICAL:
Agile Roadmap
Good for:
Highly technical projects
To communicate with:
Engineers + Product Dev
Sprint-based
Details small chunks of work
linked to the epics and
features that will be released
with sprints.
THE GO-TO:
Feature Roadmap
Good for:
Detailed solutions and the
steps to get there
To communicate with:
Product Team
Time or progress-based
List of features to be
developed and released for
a product. Shows the
solution, not the problem
space.
THE MODERN: Outcome-
Based Roadmap
Good for:
Aligning Product Vision + Action
To communicate with:
Product Team, influential stakeholders
Now-next-later framework
Uses Product Vision and business
goals as a starting point and solves
user problems that will lead to those
desired outcomes.
THE NO-FRILLS:
Visual Roadmap
Good for:
An easily digestible overview
To communicate with:
Influential stakeholders; non-
Product team members
A high-level view of the
roadmap that is simple and
easy to understand.

24. To explore later: The different types of roadmaps
Timeline
Technology
Agile
Feature based
Short and long
term
Outcome based
Visual
Business
OKR
Experiment based
Product launch
Ready to double click into these roadmaps right now? Then you need The Ultimate Guide to Roadmapping

25. Feature Roadmap
The baseline Product Roadmap that every PM has in their toolbelt.
You’ve identified your solution and need detailed steps on how to get
there. What to include:
1. Features, by category or theme
2. Simple titles
3. An indication of progress or time

26. Example: Feature roadmap
Q1 Q2 Q3 Q4 Q1
Profile
Notifications
Community
Gamification
New Preference Settings
Login with LinkedIn
Omni Channel Notifications
Vendor Update
Integrate Reputation
Translations
New Badging System
New Graphics
Today

27. Strategy → Discovery
Business Impacts Product Vision Principles / Values
Goal/Objective Goal/Objective
Outcome/
Key result
Outcome/
Key result
Outcome/
Key result
Outcome/
Key result
Opportunity Opportunity Opportunity Opportunity
Opportunity Opportunity Opportunity Opportunity

28. Discovery → Delivery
Opportunity Opportunity
Opportunity Opportunity
Idea Idea
Idea Idea
Solution Solution
Solution Solution
Feature or
Experiment
Feature or
Experiment
Feature or
Experiment
Feature or
Experiment
Idea Idea
Idea Idea

29. Goal
Double DAU within the next 6
months
Go big in Europe with 35%
usage
Example: Outcome-based Product Roadmap
Later (6+ months)
Daily use
At least 80% of all app users
manage at least 5 work orders
weekly
Increase native language use
35% of all application usage is
in Portuguese, French, or
Spanish by end of 2023
Now (1-2 months)
EU Daily Usage = 34% of users
Total downloads = 120k
Work in your language
Customers create a work order
in their language within 5 min
of app download by Dec 31
2022
Next (3 - 6 months)
EU Usage
Mobile worker DAU
increased 30% in EU by Feb
28, 2023
Total downloads
Daily app downloads up by 80%
by end of 1H2023
Expand deeper in EU
Enter Easter European EU
Market by 1Q2023
Compliance needs
Full GDPR compliance by
1Q2020

30. Example: Agile Roadmap
Sprint 1.1 1.2 1.3 2.1 2.2
Development
Product
QA
UX
Front-end prototype
Repository deployment
Environment setup
Back-end engine
Feature A scope
Store review
Demo staging
Feature B scope
Environment setup
Integrated prototype
Analytics engine
Unit testing
Back-end analytics
Engineering review
MVP Requirements Roadmap brief
Feature requirements
Pilot
Feedback
Launch
Customer Testing
Backlog sweep
Feature release A-B
Wireframe UX Design Templates Feature-level design UX Audit High level design
Metrics QA Variance testing UAT PM Testing

31. Example: Visual Roadmap
Q1 - transfer main web
architecture to new
CMS
Website launch
Q2-Q3 - identify and
debug high priority
issues with transfer
Debugging
Q4 - create workflows
and architecture for
adding new content types
New content flow
Q1-Q2 2023 - Finalize old,
low priority content
transfer
Transfer old content

32. User Flow
[Insert Title Here]
Template validated by Andrew Nguyen, VP of Product at Loop

33. Before mapping, identify…
Project name
Users
Users are anybody interacting with your system. A user can be a customer, person, system, or
organization.
Objective
Outline 1) your happy path, and 2) your unhappy path. When you test the happy path, you test
actions you want the user to take. The unhappy path, you test actions you do not want the user to
take. This is not where you want your users to be, but they end up there because they're not
qualified to follow the happy path, or they explicitly chose a different path (rejected
product/feature/upsell).
Traffic source
How do users find your product? Is it organic or paid traffic? Referral sites, email? Different entry
points highlight how customers are using your product and how you can cater it to their needs.
More importantly, these points can be the entryway for your diagram.
The what and when
To get conversion you need to give the right information, at the right time. What information does
your user need? What actions they should take to move towards the target objective?

34. Qualifying
factor
End result #1
Task #2
Possible end
result
Variation A: One User
Task #1

35. User 1
Action #2
Action #1 Action #3
User 2
User 3
Variation B: Multiple users

36. Example A: Document management software
End result: Create a new doc
Identify users actors
Single user. Someone logging onto the platform and creating a doc as their first option (first time or
returning user).
Outline the Objective
Log-in phase: User wants access to platform. Document creation phase: User wants to create a
visually pleasing and organized document in as little time as possible.
Identify discovery source
Paid traffic (e.g. Facebook; Google Ads), organic discovery through pre-made templates, and word of
mouth.
What and when of the need
Clear direction at every step of the login process. Once in the platform, the most obvious and
attention-grabbing CTA needs to be “Add new document.” When user click this, they need
choice/options, presented in an understandable and not overwhelming way. Next possible steps
always need to be clear.

37. Already
signed up
Enter email
address
Set up free
account
Enter
name
Enter
password
Add New
Doc
Blank
document
All
templates
Add icon
Type title
Icon choices
Pre-made
template: Tasks
Your templates
Pre-made
template:
Project hub
Task list
Product
roadmap
OKR planner
Project brief
template
Log In/Sign up Create a document
Add cover
Reposition
Upload image
Remove
Choose from
Unsplash
Log In or Sign Up

38. Example B: Food delivery app (from customer perspective)
End result: food delivery and confirmation
Identify users Restaurant owner/workers; delivery person; customer
Outline the Objective Successfully order and deliver food from restaurant to delivery location
Identify discovery source Paid traffic
What and when of the need
Ongoing direction and information for all users, especially for customers and delivery person.
Assuming customer has already selected restaurant. Restaurant will have previously updated their
offerings. Within restaurant page, customers need to understand what they are ordering (dish
names, prices, images). They need to be able to edit cart, review before confirmation, and pay
seamlessly.
Upon confirmation, they need to know delivery time, which is dependent on restaurant capacity and
delivery person. Restaurant needs to confirm it has handed off food to delivery person. Delivery
person needs to know final address. Once food is delivered, delivery person has to confirm order;
customer has option to rate experience.

39. Restaurant Owner
Review Menu
Edit Menu
Add Item to
Cart
Delivery Driver
Review Order
Customer
Confirm
Delivery
Enter Address
Remove Item
from Cart
Make Order
Payment
Confirm Food
Order
Food order user flow