prioritization should be simple
Instead of a prioritization framework, look at the desired outcomes.
- Understand what the desired outcome is for your users.
- Understand what their problem is.
- Understand how many users are affected.
- Understand why this particular experiment/project is valuable given the two constraints above.
- Understand how you will measure success.
- Use Teresa Torres's opportunity solution tree how many users are affected.
Shreyas also told a story about when he was a product manager at Twitter, and his boss simply asked one question.
"How does [this acquisition] make our users love Twitter more?"
Thats it. No data, metrics, quantitative evaluations. This one simple question encompasses so much:
- Do you know who our users are?
- Do you know why they come to Twitter?
- Do you know why they love Twitter?
- How does [this acquisition] change the dynamic of the three points above?
Source: Shreyas Doshi on Lenny's Podcast
Back to map of content (product)