What determines the correct choice of process are the objectives and timeframes that are defined in the first place. Projects have their starting point, some from data or other by people.
I'm talking to
When I dive into a new project, be it personal or commissioned, I want to understand immediately who is the user I want to communicate with. By analysing the user, a lot of interesting information can be gleaned for the usefulness of the project, one can understand what the user's needs and concerns are. Once this information is clear, one can proceed with solutions that meet the needs of the end user.
Never speak alone
n order to understand whether the proposed solutions are feasible or whether they can be made even more accurate, I get help from the knowledge of programmers or business analysts. Personally, I have no problem getting my hands on the code or understanding the ABCs of business models, but I believe that solid collaboration between partners helps to improve the solution in the form of a product.
More and more dialogue with users
Well, now that we have more or less the basics of the solution, we need to quickly design the product and test it with the user, I am of the opinion that a quickly built product helps more to clarify the ideas about the product itself, and get feedback from the user quickly. Feedback is very important, the user broadens the vision of the product, points out problems unknown to us, or chooses alternative paths proposed to him.
Communication is the key
So user feedback has to be integrated, consulting partners to see if solutions are feasible or not. We go back to re-designing the product and testing it again with the user, this takes us through a cycle until it is interrupted by the goal or timeline I mentioned earlier.