As a rule, Discovery activities imply multiple diverse operations that serve to reach a consensus on the issues which shall be resolved and achieve expected results at the end. The definition of the “discovery” term states that this notion refers to the initial stage of software development and performs the following key tasks:

• research of the original problem;
• clear identification of the issue (or even issues) which shall be tackled;
• collection of relevant evidence;
• determination of further actions.

The given phase is essential to figure out the right direction and start the project effectively since the most topical problems are defined, which allows you to create successful digital solutions. SDLC discovery phase is sometimes mistakenly seen as a process of discovering future software requirements. In fact, we’re talking about something much more complicated and comprehensive.

When it comes to UX activities, one would distinguish the below goals to be achieved:

• get familiar with the raw data you originally have;
• clearly figure out who the target audience is, including the problems, needs, and expectations of the future users;
• establish reliable communication between all the stakeholders and departments involved to ensure proper work across the company;
• make sure everyone is on the same page and ready to proceed with the following steps.

Everything depends on the objectives of each startup, so the overall process and the actions to be taken have to be based on those objectives to choose the most optimal tools and methodology. Take a look at the list below. In fact, the Discovery team can implement only several activities mentioned, or go for those which are not on the list, in case this is what a specific project needs.

• Initial meeting. It’s vital to thoroughly discuss project objectives and their priorities with the stakeholders.
• Interviews. The idea is to learn about business goals and challenges as much as possible, thus, the more people you talk to, the better.
• Brainstorming. When some original information is collected, it makes sense to define what you have and what issues still require further research. It’s important to determine what facts you have and if there are any assumptions among them.
• Field studies. The mentioned activity is carried out to gather the insights of future users. Moreover, the audience interviews could also provide valuable details.
• Diary research. In addition to the current situation, you shall figure out longer-term experiences and users’ behaviors. This is what this study is all about.
• Competitive analysis. Your task is to understand how the audience prefers to use the products your rivals offer.
• User journey mapping. You shall visualize the path users take and demonstrate the connection between various elements of the platform. All opportunities and issues shall be identified.
• Regular meetings. It’s critical to hold workshops on a regular basis to establish,  manage and adjust requirements as soon as there’s such a need.

In some cases, it’d also be useful to interview such departments, as customer support and sales. Moreover, certain agencies keep an eye on incoming calls for tech support.

Discovery research methodology

# Stakeholder meetings

Whether we’re talking about software development from scratch, or it’s about implementing  new features into already-made solutions, interviewing stakeholders shall help you figure out such aspects, as:

• main goals of a given company;
• the scope of work to be carried out to launch the project;
• possible risks and issues, including, business, financial, technical, and others;
• niche specifics;
• main market competitors;
• other vital points related to a startup in question.

# Research of competitors

The objective here is to gather as much data on your competitors as you can. Such an analysis serves to determine and evaluate the solutions rivals offer, their weak and strong aspects. This is for you to establish an effective strategy for your project. Discovery activities shall include competitive analysis to draw the most appropriate conclusions.

# Field survey

The given methodology allows us to watch the behavior of people when they’re home, at work, at the coffee house, and elsewhere, to learn something that couldn’t be just expected. The fieldwork helps figure out how specific software is applied in the real world, and what people do in day-to-day situations, for instance, when they’re irritated, distracted, happy, working, spending time with their family, and the like.

# Diary research

According to startup needs and the number of people involved in the study, diary research could be quantitative or qualitative. It doesn’t make sense to carry out the research having less than 10 participants. When dealing with a sufficient number of individuals, you’ll manage to understand how users will act in the long run. After having analyzed the data received during the study, you come up with reliable and valuable information on users’ habits, motivations, behavior scenarios, as well as the customer journey.

# Competitive testing

In fact, this activity could be well-conducted during various stages of development. While conducting it as part of the Discovery process, you shall test solutions of competitors since your own software design isn’t available yet. In case you do competitive testing during the exploration (or even testing) period, you can test your design and compare it with what competitors provide.

Summing up, Discovery could be implemented to solve multiple problems, engaging teams of different sizes and carrying out diverse activities. No matter what project it’s about, the Discovery phase is designed to reveal insights on a problem and to reach a consensus on the outcomes intended.