Product Discovery

Our skills at your disposal:

How we work with you in a software development discovery phase to truly understand what needs to be built

Throughout our 11 years in the software development industry, we’ve listened to countless app ideas from different clients and industries. Some of these bring up several uncertainties about the users. Others mention the product’s functionalities, and others, its monetization strategy. We believe it’s essential to manage these factors correctly from the project’s kickstart; if not, these concerns can escalate and compromise your project’s timeline and budget.


Our goal is to create ways to start off a product development on the right foot and minimize risks. Some years ago we started bringing together different roles to better establish the product idea before embarking on a whole project, which included stakeholders from the business side, product experts, developers, and designers.


The Discovery Phase, as we call it, is a process that brings the client and dev team together prior to the development process in order to reach a broader understanding of the software and how it can serve its users the best possible way.

It has three main goals: understand, analyze, and propose.

  • Understand

    The team gets a complete understanding of your business model and its context, your company's goals and your consumers.


  • Analyze

    The team documents and aligns expectations of what needs to be done, in order to mitigate risks, define processes, create story maps, and so on.


  • Propose

    Collaboratively, they propose an initial backlog, a team, and a ballpark for the software development project.

Benefits of a Software Development Discovery Phase:

business-icon

Understand the app’s business model so every team member is on the same page.

expectations-icon

Foster an alignment of expectations, needs, and risks about the project between you and our nearshore team.

prioritize-icon

Identify your main users and prioritize the most important features accordingly.

roadmap-icon

Collaboratively build a roadmap among developers, designers, and the business experts.

estimate-icon

Get a rough estimate of time and costs.

documentation-icon

Generate high level documentation of the project scope, such as a list of requirements, timesheets, wireframes, mockups, and more.

How we do it

The Discovery phase is highly adaptable process, customized to accomplish the client’s goals. It’s based completely on your context and the maturity of your product idea. The preliminary step is internal, where we establish an agenda of Discovery activities that usually lasts one week. This is tailored to your needs, and it is co-defined with your team. Although the specific Discovery activities can change, the general goals of each step are:
01

Uncovering the purpose

  • The team kicks off the Discovery phase by working together to understand why they are there and what is the product they want to build.

02

Taking a business overview

  • At this phase, the objective is to understand the app’s business model and your company’s current context.

03

Identifying metrics, constraints and risks

  • Moving forward, the team will decide which metrics they should use to measure the project’s success. They will also consider risks or constraints to take into account.

04

Understanding the users

  • At this stage, we work closely with our UX team to build a profile of the app’s users, understand their needs, and, when applicable, their current experience--which will give the direction of the app’s development.

05

Assembling a roadmap

  • Based on a story map, the team identifies the journey of the app and generate a prioritized backlog to get the development started.

06

Final details

  • At this last step, we focus on estimating the project’s cost and duration, recommending the right team for the job, and documenting the Discovery output.

Case studies

This is how some of our clients have teamed up with us to live successful software development discovery phases:

Our preferred tools / frameworks:

User Definition

User Definition

User Persona

User Persona

User Journey

User Journey

Features Prioritization

Features Prioritization

Story Mapping

Story Mapping

User Definition

User Definition

User Persona

User Persona

User Journey

User Journey

Features Prioritization

Features Prioritization

Story Mapping

Story Mapping

User Definition

User Definition

User Persona

User Persona

User Journey

User Journey

Features Prioritization

Features Prioritization

Story Mapping

Story Mapping

User Definition

User Definition

User Persona

User Persona

User Journey

User Journey

Features Prioritization

Features Prioritization

Story Mapping

Story Mapping

Want to discuss your project?

We'd love to hear about your project, feel free to reach out to us.

Explore other skills: