Slide Discovery . Our process
< Stages_of>
Our process
1. Business understanding

We carry out key business context activities that help uncover business and users’ motivations. We use Business Model Canvas® and Value Proposition Canvas® as a preliminary common ground for teams to start collaborating and sharing the same business jargon.

Business Model Canvas
We use the Business Model Canvas® as a strategic guide for the analysis, creation, and documentation of competent business models with clear goals.
Value proposition canvas
We use the Value Proposition Canvas® as a tool that allows us to create or improve products and services around the user’s real needs.
Competitve analysis
At this stage, a plan and estimation for the MVP is relatively feasible. We provide a breakdown of engineering and design hours needed to reach every milestone of your product roadmap, so that you can put a dollar number to your vision.
2. User experience desing

Your products should always usable, enjoyable, and accessible for humans. During this phase we will bridge the gap between the user, the development team, and key business stakeholders.

User personas
We create the main user personas profiles to understand the motivations and goals that they may have within your application and provide solutions focused on relevant business outcomes.
Feature map
It allows us to generate a global view of the characteristics of your application. It is used to understand in detail the interaction of the views, as well as being a tool for continuous use throughout the life of the Project.
User flow
It is a fundamental tool within the user experience, since it helps to understand the routes that a user takes within the application to complete a certain task.
Wireframes
Through the creation of wireframes, we will graphically capture the functionalities and user interaction schemes within the application to ensure a solid structure during the following stages. It allows us to generate a connection and understanding between the feature map and the user flows.
3. User interface design

Your products should always usable, enjoyable, and accessible for humans. During this phase we will bridge the gap between the user, the development team, and key business stakeholders.

Style concepts
An important part of the application is the design concept, since it defines the type of communication established with the user and their feelings within the application. It also To do this, we usually iterate over 3 different style proposals.
Style Guide
An important part of the application is the design concept, since it defines the type of communication established with the user and their feelings within the application. It also To do this, we usually iterate over 3 different style proposals.
Hight fidelity interactive prototypes
A high-fidelity interactive prototype will help bring your ideas to life and get a detailed vision of appearance of the application.
4. Product Plan

Your product plan is an agile yet comprehensive representation of your vision and how you plan to prioritize your product offering and its functionalities over time.

Initial product backlog
Your product backlog is a tactical tool delivered from your product roadmap, made up of user stories and epics, which describe the functionality of your product.
Architecture design
After the vision and roadmap are complete, information architecture and patterns are laid out, followed by a selection of the right set of tools and the technology stack needed to build the product.
Team configuration
Your project will probably need more than one coder. The value of hiring a team resides in their collective wisdom, and this is where we assemble the team needed to deliver the vision such as: designer, full stack developer, QA, etc.
Development estimation
At this stage, a plan and estimation for the MVP is relatively feasible. We provide a breakdown of engineering and design hours needed to reach every milestone of your product roadmap, so that you can put a dollar number to your vision.