If the team has an idea of the functions or services that the solution could provide at the end of the project, it is important to prioritize them in order to manage the pace and expected results of the development and testing phases of the solution.
The trap would be to want to immediately develop a solution or a service that already includes all of the imagined functionalities.
Instead, start by defining, based on your knowledge of the market’s behaviors, frustrations and practices, the main function to be highlighted in the solution.
Then, you can read what are the 2 or 3 secondary functions and then the possible accessory functions.
For example, in the realization of a phone, the size of the screen or the performance of the photo sensors can be functions to put forward when the customization of the interface is rather secondary and the number of applications to display at the same time is accessory.
The result of this work should be a value versus effort matrix where it becomes easier for the team to arbitrate which value functions should be prioritized.