When you know a project is a good idea, or your extended team keeps asking you to tackle a new project, but you just can’t get it done in the current cycle of workーadd it to your backlog! To help communicate why you might take on one project over several others, think about doing a quick “t-shirt sizing” of Priority and Lift to stack rank your back log. Expand the heading below for more details.
🎯 Need more help prioritizing requests? The Product Marketing Alliance is here to help with
Determine Project Priority
We can’t do it all! But we want to!
Here’s a table of items to consider in future planning cycles, or as bandwidth allows.
Note - for planned inbound activities, please see
🚦 Tips for gauging priority
How closely does this align to company OKRs (DAU growth & ARR)?
How many users will this impact (all of them? some of them? none of them?)
How many internal team members will this impact? What is the net ROI in FTEs?
🏋🏻♀️ Tips for gauging lift
How many “sub-tasks” are there to this (including internal reviews, message testing, etc.)
How big is the cross-functional team required to make this happen?
Are you borrowing from other teams’ time?
How long would it take you do on your own?
Sorted by Priority divided by Lift