When a major oil company tries to extract oil, it usually takes the following steps:

1. First, it carries out an investigation of the area, it analyzes the legal issues, the environmental impact, the possibilities of the area being rich in organic matter. Let’s just say, it prepares the ground for the first surveys by analyzing the context.
2. Secondly the company begins an experiment: it sends ships to propel compressed air bubbles up to 7,000 meters deep. Through sonar, it is able to create a map of the rocky surface and the shape of the sea floor.
3. Once the signals create the expected map (verification of the initial hypothesis), the drilling phase (second experiment), where kilometers are drilled until the first gases appear, takes place. The first hydrocarbons would certify that there is actually oil .

Finally everything is prepared to properly extract the oil and give way to its commercial exploitation.
Let’s say that an oil exploration goes through five well differentiated steps:

1. Establishment of the initial hypothesis.
2. Documentation and analysis of the context in which the action is to be developed (product).
3. Performing a first experiment (Research through air and sound).
4. Second experiment. Initial prospecting
5. Implementation of the final model

I have given the example of oil prospecting because in the world of creating digital products (meaning start-up) the steps could be the same:

1. We establish a product hypothesis.
2. We document the problem and analyze similar business ideas.
3. We performed the first experiments with the idea of ​​verifying the hypothesis.
4. If the experiments are positive, we go to the development phase.
5. We develop the product and we scale up to grow and maintain the product in the market.

1. Hypothesis.

Starting a project is always trying to give an answer to a business hypothesis. If we create such and such product (or application) we can position ourselves in such and such market. We will meet this segment. In this case we start our project with a business hypothesis, which implies a product hypothesis. The relationship is complex and there are too many answers to find. In design terms we speak of diffuse goals.
How can we verify that our business hypothesis is correct if our product is not well defined or our product hypothesis has not been verified? We can only arrive at a possible result by responding to the two hypotheses in order.

The user experience as a product hypothesis verification system.

Experienced designers add value to a product as they are able to define a product that, in addition to being well designed, achieves business hypotheses. An interaction designer defines a product based on the analysis of the user (understood as consumer of the product) Therefore, the design is already thinking about the final consumer and success in the market. Now, does the user experience guarantee the success of the business? If so … Which UX methods are able to bring us closer to success? Is creating a well designed product enough to achieve business success?

2. Read, UX and other issues.

The methodology followed by the oil companies, as we saw at the beginning, follows a process of verification of hypotheses through experiments that are closer to reality before drilling the soil. It is a process of investigation by phases, in which each phase brings us closer to or away from the objective.

This in business methodology is called LEAN. The Lean Startup process proposed by Eric Ries and the UX version (Lean UX) proposed by Jeff Gothelf is a method that proposes to prospect with the intention to verify the hypothesis BEFORE developing the definitive proposal. That is, before developing a single line of the final product code. An example might be this:

• First prospect (first design sprint)
  Hypothesis> Product experiment> Data / knowledge (Check hypothesis?) If not verify ….
• Second prospect (second design sprint)
  Changing hypotheses> Product experiment> Data / knowledge (Do we get positive data?) Then we must continue to perform product experiments until the results come closer to the verification of our hypothesis.

As is seen, the LEAN UX proposal does not talk about developing products. It talks about performing experiments (creating mini-products) that serve to verify the initial hypotheses. This process, through repetition and use of economic models, uncovers the true nature of the product. A product in the sense that it helps us CREATE THE RIGHT HYPOTHESIS or verify the hypothesis raised using the minimum possible expenditure.

In this phase the development is minimal, the research work is maximal.
In a process of verification of hypotheses, it is necessary to work with design thinking techniques, to be well documented, to take into account the stakeholders’ vision – but only through analysis of the market can the hypothesis be verified.

Conclusion

Many companies anchored in the product development cascade system do not just understand that product innovation requires different processes when it comes to tackling the problem of creating a successful new product.

In order to develop products that reach the market it is necessary to repeat processes at two levels:
1. On the one hand creating products that necessarily start from a design based on adequate experience.
2. Research / verification of business hypothesis that can be repeated until it reaches an optimum result that guarantees commercial success of the product.

All this must be done using processes of great initial collaboration, processes based on data and having designers able to test and discover the true nature of the product before it is developed.

Documentation and references

The lean startp methodology

A simple introduction to Lean UX