Reuleaux is the triangle formed at the centre of Venn diagrams. The three intersecting circles of desirability, feasibility and viability that forms Design Thinking. Which often refers to Reuleaux triangle as innovation in many models and describes an idea or solution, where value-based design focuses on the value created for organisations and people. It increase your confidence in making the right product decisions, through testing and optimising the return on investment of a vision. So before you write any code or decide on any a feature we need to understand the potential value.
Today we are all too often feature factories, with little regard for whether the features actually solve the underlying business problems.
A value-based design process can deliver real value to clients. This will help to establish yourself as a trustworthy digital partner. Value-design keeps us focused on outcomes, and forces us to check as we build how our product works and what it accomplishes.
The inconvenient truth about product design, Marty Cagan states that at least half of the ideas are just not going to work. Even when we do find the ideas that are valuable, usable and feasible. It takes many iterations to get the implementation of this idea to the point where it actually delivers the expected customer and business value.
There are many reasons for an idea to not work out. The most common is that the customers aren't as excited about this idea as we are, so they choose not to use it. When they do want to use it, if it's so complicated that it's simply more trouble than it's worth, this yields the same result. Even when we validate that customers will love it, it can become much more involved to build than we thought. We simply can't afford the time and money to deliver.
Value-based design is to fundamentally change focus from outputs to outcomes. Many of our beliefs about users, their problems, and possible solutions are assumptions that need to be tested. We can do this by building in small, iterative pieces with the goal of learning whether our assumptions are well-founded - and ultimately whether our ideas or features will have the outcomes we want, both for the business and for our end users.