Lean Inception promotes the identification of opportunities for agile enabling and integration of potential APIs and service drivers, ensuring a holistic view of our customers’ architecture (Business, Data, Application and Technology). And this comprehension allows enabling digital initiatives “linked” with strategic actions.
The Lean Inception model application is the combination of the pillars of design thinking (collaboration, experimentation and empathy), seeking to focus on learning about personas and journeys, and the pillars of lean startup (building, measuring and learning), with the purpose of helping the understanding, as well as building the MVP and architectural assessment, always considering the digital and technological context that the customer is in.
Lean Inception in practice is a workshop where collaboration is a fundamental point to align the understanding of the business and technology areas about a product and its key aspects. It is a great recommendation for organizations with projects that are still very embryonic, without a clear comprehension about persona, pain points, journey, features and scope.
Lean Inception in practice
The main problem with product creation in the traditional model is the time spent and the engagement of many resources of the organization, which often causes the loss of time-to-market. Lean Inception, on the other hand, reduces the time to create digital products, something fundamental for companies that need to have quick answers to remain competitive in the market and a direction for what actually needs to be done. It is not static, but evolutionary; new drivers may emerge precisely because of the market agility.
How it should be done, that is, the best viable way to solve the problem identified in the main cause.
To identify the solution, techniques such as: Model A3, 5 Whys, Brainstorming and Design Thinking. But we know that there are many other buzzwords in the business world: OKR, Scrum, assessments, canvas models, as well as reference frameworks. The choice and application will depend on the nature of the business, the type of project and the context of the organization.
The initial focus should be on working on actions that eliminate or minimize the problems/pains faced by personas. For this, it is essential to understand clearly how APIs can contribute to the problem’s solution. What opportunity do we want to leverage? What is the API purpose? And listen to your customers, partners and even developers to offer the best experience.
These are just some of the fundamental questions that the project must answer and they refer to the corporate vision of the business and the vision for the API, ensuring the alignment between the business strategy and the implementation of APIs as a digital enabler.