You are on page 1of 20

PRIORITIZATION

FRAMEWORK

Part 6 of Strategy Series, a 10-part series

Content: Shyvee Shi


Infographic: VisualPortfolios.com
What are some great prioritization
frameworks and factors to consider to
ensure you’re tackling the needle-moving
work and not just “snacking” on the
marginal work?

At the simplest, you could do a cost/benefit


analysis.
BENEFITS
Importance vs.
Satisfaction

Focus on the needs that are important


to the users but are not yet well
satisfied by the current solutions
available.

Content: Shyvee Shi Infographic: VisualPortfolios.com


Size of
User Benefit

Can you quantify the value ($ saved,


time saved) for the user?

Content: Shyvee Shi Infographic: VisualPortfolios.com


Reach
(# Users Benefited)

What % of the user base will be


benefited? Do a quick
back-of-the-envelope calculation based
on the estimated traffic to the new
feature to verify impact.

Content: Shyvee Shi Infographic: VisualPortfolios.com


Type of Users
Who Benefit

Who will benefit primarily from this


feature?
The core users or the non-target
users?
How important are the users who
benefit?

Content: Shyvee Shi Infographic: VisualPortfolios.com


Completeness of
Use Case

Satisfying a use case completely is


significantly more valuable than doing
just okay for many use cases.

Content: Shyvee Shi Infographic: VisualPortfolios.com


Size of
Business Benefit

How much money is it estimated to


bring in?
Will it cut down on support costs?
Does it help complete a marketing
story?

Content: Shyvee Shi Infographic: VisualPortfolios.com


Size of
Internal Benefit

Will it reduce future dev cost?


Will it improve team morale?
Will it help the team learn something
important and help with other
initiatives?

Content: Shyvee Shi Infographic: VisualPortfolios.com


Vision
Alignment

Will this lay the groundwork and drive


progress towards long-term vision?

Content: Shyvee Shi Infographic: VisualPortfolios.com


Risk /
Certainty of Success

Is this a venture bet?


Have the hypotheses been well
validated?
What is our confidence to deliver the
expected impact?

Content: Shyvee Shi Infographic: VisualPortfolios.com


COST & CONSTRAINTS
Level
of Effort

How much effort across


eng/design/product/research (in terms
of estimated number days or weeks)
will it take to complete?

Content: Shyvee Shi Infographic: VisualPortfolios.com


Team Capacity
and Skills

Do we have the right people with the


right skills to do this work well? Or
some ramp up time needs to be
factored in?

Content: Shyvee Shi Infographic: VisualPortfolios.com


Cross-team
Dependency

Are there other work that need to be


done first?
What can be done at the same time?

Content: Shyvee Shi Infographic: VisualPortfolios.com


Confidence
in Estimates

How likely is it that this work could be


much more costly than planned?
Are there significant unknowns and/or
dependencies?

Content: Shyvee Shi Infographic: VisualPortfolios.com


Perishable
Opportunities

Is this a time-restricted opportunity


that if you don’t launch it before a
certain date, the impact will be
significantly less?

Content: Shyvee Shi Infographic: VisualPortfolios.com


Other
Risks

Could this work introduce security,


scalability, performance, or brand risk?
For very complex projects, it may be
worthwhile to conduct a pre-mortem to
outline the various areas where things
could go wrong.

Content: Shyvee Shi Infographic: VisualPortfolios.com

You might also like