IT projects are created based on requirements collected internally by the client and workshops detailing the scope of the project. The supplier prepares a quote, if there is an agreement on the budget and expectations then the project team proceeds to create the product. Then all that's left is the production launch. Further on, we have changes due to user needs. We recognize this as a normal state of affairs, but is this a good approach? Can we limit the number of post-implementation changes so as to maximize the budget for developing only the needed functionality, creating the perfect product? It turns out that yes - the answer is Design Thinking and User Centered Design.