As product developers, we all have limited resources in terms of people and time. On the other hand, we have a lot of features to build, and we should find a good balance so that we can use our resources the best way possible.
When we are in that situation (almost always) the importance of prioritization appears in our mind and we suddenly start thinking in the best way to decide what to do next. We have some tips, based on our experience, to deal with this question.
Features that give value go first
The first thing that we have to understand is that the most important voice that we have to listen to is “our customers”. The features that they ask for, commonly, are those that will give more value and are more desirable for the clients.
Simple before complex
Once you have identified that most desired features, it’s time to consider your own needs. The general advice is to develop simple tasks first. At the end of the day, it’s like any other tasks in your life: if you get stuck in an infinitely complex task, you won’t make room for others tasks that provide good results and are easier to complete.
We understand how “sexy” can be to release that “great and disruptive” feature before everything else. But if you don’t move fast enough, it can be too late when it’s ready to be published.
The faster the better
Even in a list of simple tasks, there are some of them that can be developed faster than others. Keep in mind that the goal is to give value to the users as soon as possible, so we recommend to put on the top those tasks that can be done in less time.
These tips are basic ones, but we are sure that will be very helpful for a lot of people who are starting in the world of prioritization and user value proposition.
. . .
Regos Dev Studio is a product development company that builds add-ons for Jira and Confluence, combined with the development of custom solutions in a variety of languages.