How to define digital products requirements

The definition of requirements is the initial part of our discovery process to develop a digital product. This is divided into 4 steps:

1. Client milestones (Research, What happens in the market or context and with the specific customer) What are the needs, and what has to be achieved to meet them?
Requirement and research.

The milestones of the success of the product with respect to the customer involved in its management (from whom the requirement is born), are measurable events structured specifically from the particular metrics to the project in question. That is, thanks to the research in the Discovery process, we set measurable objectives in terms of product attributes, which, as a consequence of a good research, allows us to create a structure based on success metrics regarding the first approach of the product. In this sense, we propose the milestones to be reached for the product to determine whether it is successful or not in its development, and on this depends the way in which we approach the user to build the path towards the product's objectives.

In the first stage, with respect to the initial hypothesis, we will find the necessary metrics for the future construction of the M.V.P (Minimum Viable Product), to be able to evaluate the success regarding the fulfillment of the requirement and how the product relates in a measurable way with its final users. This is vital to determine if the users see value in the proposal and if it is that product that could interest them to fulfill their study dynamics (What the user wants, needs, feels and ends up doing).

2. Conceptual map of the solutions

Solution map: It is a tool that allows within the methodology to organize the team in favor of making decisions focused in the most objective way, inside and outside the discovery process. In the exchange of information and proposals is filtered in a coherent manner and represented in a process map which in turn could exemplify the first hypothesis towards the problem in question.

Following the thread of the Discovery process in the definition process, we will analyze the most favorable scenario where the first hypothesis comes to life, thus approaching the solution to the problem is nothing more than finding the perfect opportunity to innovate or apply the product strategy. In other words, the prototype (the first hypothesis) constitutes the conglomerate of the analysis of the opportunity and the user.

It should be clarified that it is thanks to this process that determining a solution (hypothesis) can be represented in a graph by way of a conclusion on the synthesis of the information discovered, which in other words brings us closer to having "mapped" one or more paths to the solution of the problem. Let's remember that user-centered methodologies, and even more the Auxo Method itself, have the end user and his behavior as the central axis to determine the structure of the product (and its strategy), which concretely establishes the user as the main flow point where any of the concise ideas become solutions to the problem, from different angles. 

3. Business requirement analysis / Product analytics or visualization, perspective. 

Within the product strategy, there is a fundamental aspect for the life and subsequent management of the product, the viability of the business. Thus the analysis of the requirements, from the business, the creation process and the management recreate the primary scenario of the requirement and establish basic information for all involved, priorities, needs, consistency in the information and objectives, scalability and verification processes are defined, these last two are the central axis within the idea of the M.V.P (Backlog). Ergo, in order to build a solution that can be scaled over time, measured and adapted, it is essential to establish the viability of the business and how it is consolidated with respect to the user and the relationship between the product and the company. Ergo the analysis of the requirement must be done exhaustively to translate the needs of those involved and from them find the opportunity for innovation from the business plan, those involved, the competition, operating models and service among others.

4. Business needs prioritization and M.V.P definition

Siguiendo con el punto anterior y retomando el modelo de construcción sugerido (el proceso de discovery), identificamos las necesidades del usuario y dentro de la dinámica del análisis del mapa de soluciones y el pensamiento de diseño centraremos los esfuerzos en hilar la construcción a partir de la jerarquización de los objetivos del usuario y sus respectivas necesidades. Es vital organizar los objetivos (en analogía al proceso de UX) para entender de qué forma el usuario se comporta y genera necesidades con respecto a una problemática. Esto contribuye de manera local a la definición del M.V.P como la suma de los atributos esenciales para cumplir con las necesidades primarias del usuario. Ergo al generar una estructura de prioridades, atacamos en orden con lo mínimo necesario que nos permita medir el comportamiento del usuario y la efectividad del producto, con un único fin: aprender y adaptarse. Nos construimos con y para el usuario y el M.V.P entra a consolidar el concepto de iteración dentro del proceso de construcción de producto.

Having explained each of the above processes, it is worth noting that the corresponding deliverables for each point in the discovery extension and the first process, whose conclusive is the prototype as an emulation of the first hypothesis, are the following:

  1. Client milestones: The milestones on the first proposal, this will be intervened from the first stage of research and definition, so that when approaching the first hypothesis we will determine and record what will be each of the milestones and how it is planned to measure them when the product is in production. To pose a problem.
  2. Map of solutions: Map that shows part of the process that covers the development of one or several solutions, this document synthesizes the analysis and within the ideation process constitutes a relationship map of the possible paths to take to create the value hypothesis, where the team and those involved play a fundamental role (We determine a solution).
  3. Business requirement analysis: Business viability and analysis of the requirement in favor of the relationship of the user with the product and the product with the business. The life of the product determines the essence of the business and its correct operation over time.
  4. Business needs prioritization and M.V.P definition: Definition of main objectives as a result of the way we build the M.V.P. with the team involved in order to adapt the product to the user's behavior towards their needs. We define the M.V.P. based on what the process entails and those involved in analyzing the user and his situation. 

Recent articles