DEV Community

Discussion on: How to prioritize too many feature requests to your team

Collapse
 
murrayvarey profile image
MurrayVarey

Great post. Prioritizing work is so important ... and so difficult. I might try some of the approaches you've described here. Do you have a favourite?

High value / Low complexity are your quick wins

I love quick wins. They're easy to underestimate -- after all, they seem so simple -- but the value they provide is awesome. Noticing quick wins is a skill, because they're hidden among other small (but less valuable) changes.

Collapse
 
darraghor profile image
Darragh O'Riordan

Hey! thanks for the kind words. I usually use the quadrants method for prioritizing stuff myself or for a small team. The matrix mapping one is my go to when trying to prioritize across a bunch of very different teams/people.

You can keep adding columns as people talk about what's important to them. If you get to 8-10 columns there is probably some strategic miss-alignment somewhere. That's where you need to get a bit more focus on what's really important for your org. So it's good for highlighting if that's an issue.

All of them are good for getting discussions started and that's the most important thing!