# Launch checklist Check the timeline and agree who owns each part of the study before launch. - [ ] You know what you want to learn and why the business needs it. - [ ] You understand what you want to learn. In other words, the main research goal has been formulated. - [ ] There is a decision path based on the results. You know what you or the team will do in any outcome. - [ ] You are sure that research is what you need, not an A/B test or analytics. - [ ] The method matches the goal: scenario test, first click, preference test, scale, matrix, and others. - [ ] Questions and tasks have been checked against the checklist. - [ ] Show the study to colleagues on your team. They may have valuable comments. Enable pilot testing to get feedback. It is recommended to plan a pilot usability test — a rehearsal with an employee from your organization. Make sure the pilot participant was not involved in preparing the usability test; otherwise, you risk false consensus. You need a person with roughly the same knowledge level as an external participant, otherwise the pilot will be inaccurate. A pilot test helps improve the process, refine tasks and questions, and identify any problems in the current testing setup. What seems simple to you may be difficult for participants because they have relatively little information to work with, so a pilot session is essential. [Business problem](https://wynde.evgeniichekov.com/en/guide/gotovimsya-k-issledovaniyu#biznes-zadacha) [Main research goal](https://wynde.evgeniichekov.com/en/guide/gotovimsya-k-issledovaniyu#glavnaya-tsel-issledovaniya) [Research methods](https://wynde.evgeniichekov.com/en/guide/metody-kak-vybrat-i-zapustit) [Reviewing tasks and questions](https://wynde.evgeniichekov.com/en/guide/metody-kak-vybrat-i-zapustit#chek-list-dlya-proverki-zadaniy-i-voprosov-v-nemoderiruemyh-issledovaniyah) [False consensus effect](https://maze.co/guides/ux-cognitive-biases/types/#false-consensus) ## Timeline You need to understand when the data is needed and why that timing matters. This affects method choice, makes it possible to plan research, and helps you stay in the business rhythm. Or, if there is no rush, it helps you plan properly and work comfortably. User data is needed at the right time and place. Research results usually have a “window of opportunity” when they can bring maximum benefit and there is enough time to implement them. For example, discovery interviews will bring important knowledge for product-strategy planning, while testing a prototype of a new feature is needed before it goes to production. Consider these timeframes and think through deadlines. ## Who can be responsible for what: product managers, designers, editors, analysts, and marketers Think about who you will do the study with, who will be responsible for what, and what your own responsibility is. Research is always teamwork. It is important to involve people: if someone participates in business decisions but is not connected to the research, that becomes a problem rather than an advantage. And if resources are limited, think about whom you can ask for support. Basic areas of responsibility are usually distributed like this: - The product manager owns the task and then makes the business decision based on the research. They immerse you in the context, explain the business problem and their expectations, share questions and hypotheses, study the data and report, and discuss thoughts after the study. - The designer owns the design and makes decisions about it. They formulate questions and hypotheses for the test, define expectations, prepare prototypes and monitor their quality, participate in the research, and make design changes based on the results. Their involvement in the study may vary. When it comes to usability tests, designers increasingly run them themselves. This is convenient: the researcher does not need to be immersed in the details of the solution, the launch is faster, and the designer can make changes immediately without reports and retellings. The researcher’s role in this process is to provide tools, train the team, and help with conclusions if needed. But responsibility for the brief, launch, analysis, and decisions remains with the designer. “I am always happy when designers or product managers run tests on Pathway themselves. It reduces the time needed to transfer context and usually greatly increases motivation because the team sees feedback on their work. The researcher’s task is to provide the tool in advance and describe a clear process and guides so it is clear which methodologies to use in which cases and for which tasks. During the test, the researcher answers questions, helps with methodology and complex moments, and reviews the test and result analysis. Research democratization enables the research team to work more effectively, and design and product teams to interact more with user feedback.” Marina Suslova, Head of Research, Zvuk. - The editor owns the text and makes decisions about it. They formulate questions and hypotheses, define expectations, write copy, and make sure that when variants are compared, only the tested attribute changes. After the study, they make edits. Like designers, editors can research their own texts themselves. - The analyst owns work with data and helps strengthen research conclusions. They can be a source of hypotheses and questions, and motivate the product manager to check behavior visible in product analytics. After the study, they evaluate release results, enrich insights with analytics data, and help ground conclusions at larger volumes, which makes prioritization easier. - The marketer owns product communication and can be a source of research tasks. For example, NPS results may show that the app’s inconvenience reduces people’s willingness to share it with friends. This insight becomes a reason to run research together with the product manager. Another common case is a drop in landing-page registration conversion. Marketing usually tracks this metric and may request a check of whether users really understand who the product is for and whether they find everything they need on the page to register. The composition of research participants can vary greatly. In some companies, it is important to involve Sales; in others, developers or AI/ML specialists participate more actively. It all depends on context: roles may differ, but the main thing is that the team helps each other and moves the research forward together. The company’s maturity level and available resources determine how actively the researcher, or the person who has taken on the study, can be involved in research, and what role the rest of the team takes. ![Four ways to divide the work between the team and a researcher.](https://wynde.evgeniichekov.com/guide/illustrations/007bfb9a-c8f9-429a-b7a3-963542193bf0.png) For example, if one researcher works with five teams at once and a product manager wants to talk to users every week and get new insights, the researcher physically cannot take this task fully on. In that case, the product manager can act as the interviewer, while the researcher provides methodological support and develops quality.