Table of content
It’s tempting to take that brilliant idea of yours and turn it into an app. However, skipping the initial research often leads to the same mistakes as many other companies did.
Peeple, an app where you could rate and review people, was called off as there’s a lack of interest from the market. Meanwhile, Washboard failed to validate the pain point of users and create a product that users use. Big brands such as Google are also in the list, just remember the case with Google Glasses.
At Uptech we’ve come across many startup owners who are left disappointed when their ‘promising apps’ failed to impress the users. Yet, those that are sticking to conducting initial project research have a significantly increased success rate.
What Is Project Discovery?
Project discovery or initial research is a process that takes place before kicking off project development. It is focused on identifying your target audience, their problems, and needs. In the discovery phase, you test your idea against the reality of solving problems and meeting expectations of the users.
The main goal of the discovery stage is to dispel doubts and prove your assumptions on the app, one way or another. Based on the feedback and collected data, you can then fine tune your idea to create a product that matches the expectations and needs of the users.
In other words, project discovery is a data-driven approach to model your app.
Why Discovery Is Crucial For Your Project?
Executing the project discovery phase allows you to validate project idea with users instead of going ahead with mere assumptions. It puts you on the right track by defining your target audience, modeling vision and business goals.
The discovery stage is also an excellent approach to define problems that you’re going to solve with the app. By talking to users, you get to know their pain points and turn them into value-added features on the app.
Naturally, heeding the voice of your users allows you to create a product focused on great user experience. But that’s not all.
With a clear direction for the app, the app development could take off with clear milestones and possibly lower cost.
How Does Uptech Conduct Project Discovery?
At Uptech, we involve the project manager, business analyst, and UX designer in the discovery phase of a project. Research usually takes around 4 weeks to carry out the data gathering and analysis.
Here are what we do in a project discovery stage.
Step 1 - Collect Product Information For a Holistic Perspective
The first step involves gathering existing information on the respective project from the stakeholders. We look into the business model, project roadmap, research results, wireframes, and other sources to build an initial understanding of the project.
We conduct an interview with stakeholders in order to stay aligned with business needs, goals, and priorities. It’s crucial to capture the visions and motivations that drive the idea behind the product.
Once the information is gathered, we work on a business model canvas. It provides an overview of the entire project and allows us to study it from a different perspective.
Step 2 - Step Into the User’s Shoe With Product Studio Session
It’s important to put yourself into the customer’s shoes, and that’s what the next step is all about. The product studio session is where we work on assumptions of how our users might interact with the product.
During the session, we create a proto persona of the target users. Proto persona is akin to building a virtual portrait for the users. We envision the user's appearance, his/her likes and dislikes, occupations, hobbies, and more. It’s also important to cover user problems that our product might solve.
We create a customer journey map (CJM). It’s a schema that reflects how the user will interact with the product, so to say what steps he will make within the app. A CJM is also helpful during prototype testing as it allows comparison of actual user behaviors with our assumptions.
A hypothesis table is also created at this point based on preliminary assumptions of the app. For example, we assumed that features A, B, C will sufficiently address the user needs of X, Y, Z. These assumptions are turned into a list, which is then validated during the user interviews.
Step 3 - Conduct User Interviews to Validate Persona
So far, the proto persona is created based on assumptions. We ought to validate the persona by holding interviews with the users. During the interviews, we could test out the hypothesis and finetune the persona based on real users' needs, preferences, and problems faced.
We update the persona accordingly, as it will become the foundation of further product modeling.
Step 4 - Brainstorm Solutions With the Design Studio Session
It’s now time to put our best minds to work. Our team came together to explore a wide set of ideas, share thoughts, and offer solutions in the design studio session. It’s an intense session of brainstorming, critique, and prioritization.
Based on the users’ needs and feedback, we raced towards probable solutions and ultimately shortlist the best ones. They are then used as a reference when we move on to work on a prototype.
Step 5 - Iterate Prototype With User Interviews
Before moving forward, we hold another round of user interviews to test the prototype that we’ve created. The intention is to validate the hypothesis which the prototype is based on. We prepare tasks, cases, and lists of questions to ensure that the interview is focused and carried out in a structured manner.
The collected feedback is a valuable input to make enhancements and improve the prototype.
Project Discovery Deliverables
After going through the steps of project discovery, we’ll produce the following items:
- Software requirements specification (SRS) - a document describing the functionality of the software and how it fulfills the user needs.
- Clickable prototype - a prototype designed to mimic how the final app would look like.
- Technical design document - a blueprint that highlights the features and solutions to be implemented by the development team.
- Timeline estimate - estimated efforts and timeline with milestones breakdown which are expected to complete the project.
- Cost estimate - a breakdown of the expenses involved in developing the app.
The deliverables are the result of the conducted research and analyzed data, which are adapted into the solution. They serve as a source of truth for the product development team.
Tips for Conducting Discovery Stage
A thoroughly planned and executed project discovery leads to model the right product for the right users. Here are some valuable tips.
Tip 1: It’s important to build a united and trustful team with the stakeholders and get the latter highly involved in the different activities to create the best product.
Tip 2: Test the hypothesis against real customers. You may have a set of hypotheses about the product. Until you get feedback from potential customers, they remain assumptions which could be proven false.
Tip 3: Avoid interrupting the flow of ideas. You never know if a seemingly crazy idea may turn out to be the winner in a highly competitive market.
Why Our Discovery Approach Works?
We’ve applied the project discovery steps in many of our projects. One of them is PNKYSWR app.
PNKYSWR is a unique mobile product aimed at solving trust issues between individuals, including parents and their children. It does so by allowing both parties to create simple binding agreements and spelled out terms transparently and unambiguously.
The app attempts to solve parents-children problems of lack of clarity in agreements. Before the development of the app started, our team conducted the discovery phase.
You can check more details on our project on our Behance case.
Project discovery is pivotal in determining the success rate of a product or an app. We’ve shown that it can be done systematically in a 5 steps approach. The main goals are to remove doubts and allow development to be carried out in a clear direction.
Talk to our dedicated development team to avoid building the next ‘Washboard’ that is doomed to fail.