# Planning a study Build a study plan around a goal, scenarios, questions, and hypotheses. For research to be useful, you need a plan — a research design. It shows in advance which answers you will get and how they will help you make a decision. - [the business problem](https://wynde.evgeniichekov.com/en/guide/gotovimsya-k-issledovaniyu#biznes-zadacha) - [the main research goal](https://wynde.evgeniichekov.com/en/guide/gotovimsya-k-issledovaniyu#glavnaya-tsel-issledovaniya) - [research questions and hypotheses](https://wynde.evgeniichekov.com/en/guide/gotovimsya-k-issledovaniyu#gipotezy-i-issledovatelskie-voprosy) - [methods](https://wynde.evgeniichekov.com/en/guide/metody-kak-vybrat-i-zapustit) - [audience: how to choose it and calculate the right number of participants](https://wynde.evgeniichekov.com/en/guide/auditoriya-kak-vybrat-i-poschitat-nuzhnoe-kolichestvo) - [prototypes: what types exist and how to prepare them for testing](https://wynde.evgeniichekov.com/en/guide/prototipy-kakie-byvayut-i-kak-podgotovit-k-testirovaniyu) - [timeline](https://wynde.evgeniichekov.com/en/guide/chek-list-o-chem-esche-podumat-pered-zapuskom#sroki) - [how the results will be used](https://wynde.evgeniichekov.com/en/guide/kak-rabotat-s-rezultatami) - [who can be responsible for what: product managers, designers, editors, analysts, and marketers](https://wynde.evgeniichekov.com/en/guide/chek-list-o-chem-esche-podumat-pered-zapuskom#kto-za-chto-mozhet-otvechat-prodakty-dizaynery-redaktory-analitiki-marketologi) This document connects all parts of the study and makes it meaningful: you spend time not for the sake of “process,” but for clear numbers, insights, and business value. [Open the research brief template](https://wynde.evgeniichekov.com/guide/templates/research-brief.en.md) ## Business problem The first step in any study is to understand the business problem. Why is the study needed? What problem does it solve? Which product priorities is it connected to? Focusing on the business problem helps you: - set priorities correctly - choose the right research method - focus only on what truly moves the team forward Talk to the stakeholder, or ask yourself, and try to formulate the business problem as best you can. The main thing is to keep the business interests in focus, even if the wording is not perfect yet. **Example questions for clarifying the business problem** - Why is this study needed now? What changed? - What business problem can the study help solve? - How does the problem affect the business and its metrics today? - How will we know the problem is solved, and what will change in the metrics? - What will happen if we leave the problem unresolved? - How does solving it relate to OKRs and quarterly or annual goals? **Example tasks** - Increase conversion from free to paid users - Reduce the percentage of abandoned orders - Reduce support load - Increase sign-up conversion Dasha Lupakhina, Head of Product Research at Profi.ru, explained in the Pathway blog how to make research a lever for business decisions [Dasha Lupakhina on research and business decisions](https://pthwy.design/blog/ne-prosto-insayty-kak-sdelat-issledovanie-rychagom-dlya-biznes-resheniy) ## Main research goal When the business problem is clear, move to the next step: define the main research goal. **Example questions for clarifying the main research goal** - What exactly do we want to understand about users or their experience? - What aspect of user behaviour or perception is unclear? - What uncertainty do we want to resolve? - At what point in the user journey or scenario does the question arise? - What mechanisms, motives, barriers, or behaviours do we want to understand? - Is there something we observe without understanding why it happens? - What exactly should be clearer after the study? - Which focus matters most: motivation, perception, context, decision-making, or behaviour? These answers can suggest dozens of hypotheses and research questions. Choose the main one. As an example, let’s take business problems and add the main research goal to each of them. Business problem: increase conversion from free users to paid users. Main research goal: understand how users perceive the interface and the scenarios for moving to the paid version, and identify barriers that prevent them from completing payment. Business problem: reduce the percentage of abandoned orders. Main research goal: understand which usability factors prevent users from completing the process. Business problem: reduce support load. Main research goal: understand how easy it is to find the needed information in the FAQ. Business problem: increase registration conversion. Main research goal: understand whether the authorization process is fast and error-free for users, and identify barriers that make them abandon it halfway. Before moving on, discuss with the team what actions they see for different research outcomes. Sometimes it turns out that colleagues expect confirmation of their assumptions and are not ready for another result. Discussing this in advance helps you: - understand whether there is a plan B - decide whether the research is really needed - prepare for the next steps ## Scenarios If you are testing a prototype or a real website, start with product-use scenarios — larger user actions that people perform to solve their task. This will help you: - identify the key tasks that are most important to test first - not forget secondary scenarios that also affect the experience - formulate hypotheses more precisely — they will be based on real user actions You can document a scenario in different ways: - as plain text, - as a flowchart, - or as a chain of Figma screens you want to test. The main thing is to understand and document the scenarios in advance. Make sure they are connected to the main research goal and the business problem, and that testing them will actually help solve it. **Scenario example** Your product is a tutor-search service, and the target audience is parents of schoolchildren who have little time and usually search in the evening after work. Business problem: increase conversion from search to booking the first lesson. Main research goal: identify the scenario steps that prevent parents from quickly finding and choosing a tutor, and understand how to remove them. Parent scenarios: - Filter math tutors on the platform. - Share options with the child. - Return to saved profiles. - Book the first lesson. ## Hypotheses and research questions A hypothesis is a reasoned assumption that needs to be tested. It is formulated as a statement about people, a product, or an interface. **Example hypotheses** - Users will understand that to apply for a tax deduction, they need to click “Deductions” on the home screen and then “Apply for tax deduction.” - Users will understand that the home-page banner invites them to subscribe for discounts. - New users most often come through friends’ recommendations, rather than through ads. - Users abandon their carts at the delivery step because they cannot find a suitable option. A research question is needed when there is no hypothesis and you want to find a new solution or better understand behavior. **Example research questions** - Which delivery method do most people prefer? - How will users understand the button label? - Which offer variant looks more trustworthy? It is better to formulate a hypothesis or research question when you are just beginning to think about the study. This helps you decide: - whether you really need user research rather than, for example, an A/B test - which research method can test the hypothesis or answer the research question - how to formulate the test task - how to structure and analyze the results after the test. ### How to understand whether a hypothesis or question is formulated correctly Check your version against these five rules: - Behavior is more precise than emotions - New knowledge - Formulated specifically - One hypothesis — one statement - The results will be used If at least one rule is not met, it is better to reformulate the hypothesis or question. Behavior is more precise than emotions. Ratings such as “liked it” do not provide reliable data — look at what people do and how they do it. Hypothesis: The user likes button A more than button B. Users clicked button A faster than button B. Question: Which button does the user like more? Which button do users click faster and more often: A or B? New knowledge. If the answer is already known from analytics or experience, testing it is pointless. A good hypothesis clarifies something the team does not yet understand. Hypothesis: Users understand that the magnifying-glass icon means search. Users understood that the text “Let’s go” in search means submitting a request. Question: Do people like doing sports? What prevents users from starting to exercise? Formulated specifically. You need to clarify exactly what you are testing. Users will understand the text on the button. Users understood that delivery was postponed by one day after seeing the text on the button. Or: The design of the authorization page is fine. Users found the “Log in” button without hints. Users completed authorization on the first attempt. One hypothesis — one statement. There should not be two ideas inside one hypothesis at the same time. Users understood the new name and consider it more convenient than the old one. Users understood what the new name means. And: Users consider the new name more convenient than the old one. The results will be used. If nothing will change even after you learn the answer, the study is not worth launching. Find out which icon is clearer if developers will not change it. Find out which icon is clearer if improvements are possible. If the hypothesis or research question passes all five checks, it is ready to use.