# Research Ops Assess your team’s maturity and build a sustainable research practice. Research creates value only when decisions are made based on its results. For this to become normal, two things are needed: trust in the results and a system that reinforces success. Next, we will look at steps for integrating research. Their order is not universal. Choose what seems most suitable for your situation and context. ## Assess what situation you are in UX Research Maturity shows how deeply research is embedded in business processes, which methods are suitable at the current stage, and which steps will help you move forward. There are different maturity models, for example from NN/g or KEIKENDO, which is good for getting started. It shows what place research occupies in a company: [NN/g UX maturity model](https://www.nngroup.com/articles/ux-maturity-model/) [KEIKENDO UX maturity model](https://uxmag.com/articles/how-mature-is-your-organization-when-it-comes-to-ux) - Low maturity: research is conducted occasionally and depends on enthusiasts, or it is not conducted at all. Today, many companies already have research in one form or another. Yes, you will need to invest time in training and show new approaches in practice. But the most important thing is that interest in the topic already exists, and that is an excellent foundation. From there, everything depends on time and leaders’ readiness to move toward greater customer centricity. - Medium maturity: research is embedded in team processes, but its influence on strategy is limited. - High maturity: research systematically manages risks and shapes business decisions. ![KEIKENDO’s five UX maturity levels show common barriers and ways to advance.](https://wynde.evgeniichekov.com/guide/illustrations/f0d24849-e55f-4b2f-997c-380fa34601d5.png) **KEIKENDO maturity matrix** | | Unintentional | Self-Referential | Expert | Centralized | Distributed | | --- | --- | --- | --- | --- | --- | | What it looks like | UX | UX + discourse | UX + discourse + methods | UX + discourse + methods + processes | UX culture + discourse + methods + processes + business | | Key barriers | Lack of awareness, rejection | Time, budget, and resource constraints | Formalization, deepening, expansion | Scaling | | | Tools for advancement | Training | Usability testing | Quantitative methods | Linking UX metrics to KPIs | | **How to read the maturity model** | | | | | | | --- | --- | --- | --- | --- | | UX is not considered a separate practice. It emerges incidentally — as a by-product of business or IT tasks. | The product is designed “for ourselves”: users are idealized, and real data is barely used. UX appears in external communications but remains a slogan. | A dedicated UX specialist or small UX team emerges within the company. Tests are rare and not always methodologically rigorous. | There is a full UX team (information architecture, interaction design, usability). UX techniques are systematic and embedded in the process. | UX has the same organizational standing as marketing and finance. It is embedded in the culture and involved at every stage: discovery → design → development. | Nasdaq’s maturity model is more detailed. It works well for planning the next steps to raise the maturity level. Usage example: Mark the intersections that are closest to your situation. The result may look like a chessboard. It is rare for a company to fit clearly into one column or row. ![The Nasdaq matrix compares stages of research maturity across several dimensions.](https://wynde.evgeniichekov.com/guide/illustrations/84e15e57-4a4f-4ef3-b6ac-2853e585d55d.png) ## Step 1. Earn trust through practice At the beginning, you do not need to convince everyone with presentations and theory. It is better to show the effect through concrete examples. ### Start with small studies that are visible to the business, and expand the scale step by step They are easier to run and quickly show results. If after a test users contact support less often, conversion grows, or the task is completed faster, stakeholders themselves start saying “yes” to new research. Example: Try to find one clear insight that could potentially improve one of the business’s focus metrics. For example, choose an important release and run an unmoderated usability test or a survey to evaluate the design. Then act according to the situation: either show the impact immediately by identifying weak points and redesigning them, or wait for the release and, if the metrics do not meet expectations, explain to the business why that happened and how research helps predict it. Bonus: And if many point studies have already been run before you, try to look at the bigger picture. Ask yourself: Which key business questions are still unanswered? Which stages of the user journey have we not researched yet or researched only superficially? Are there audience segments we know least about? Which methods have we used, and which could complement them — for example, only surveys without observation, or only qualitative methods without quantitative ones? Which hypotheses have already been confirmed, and which remain untested? How have our past studies affected product decisions, and where was the connection between insights and actions weak or absent? Where are the biggest risks and uncertainties in the product or business right now, and are they covered by research? ### Find allies Look for people who are ready to support research: from partners-in-crime, people who believe in research as much as you do, to those who at least do not reject it. These may be product managers, marketing, sales, support, development, and other people in the company. The main thing is that together you can demonstrate value in practice. Example: Launch a pilot study and talk about it at a meetup. One successful case with a clear, vivid insight can turn skeptics first into people who are unsure, and then into supporters. ### Involve stakeholders as observers This lets them see for themselves where users run into difficulties, and they will support improvements faster. The main thing is not to overload them with details. Examples: Share recordings of unmoderated tests — some people like watching them in full. For key stakeholders, make short highlight reels with moments that show difficulties, successes, thoughts, and emotions of users. This format is more visual and helps insights stick more strongly. ### Show ROI through real cases ROI (Return on Investment) is a measure of return on investment in research. It shows how much value, savings, or additional revenue the resources invested in research generated. Research can surface risks before launch, while the team can still change course. To show its contribution, record which decision changed after testing, which metric the team tracked, and what happened after launch. If you calculate ROI, state the time period, costs, evidenced financial benefit, and the assumptions behind attributing that benefit to research. Market case studies Work & Co reports that mobile conversion in the Virgin America app tripled and web-related support calls fell by 20% following the digital redesign. The project included research, design, and development. HubSpot redesigned its CRM record page to make it easier for sales and support teams to scan activity and find relevant actions. The team also reported faster page loading. [Virgin America case study](https://work.co/clients/virgin-america/) [HubSpot case study](https://product.hubspot.com/blog/rethinking-hubspots-record-design-with-usability-in-mind) ## Step 2. Embed yourself in business processes Once trust has been earned, it is important to turn research from one-off work into part of the system. ### Consider the business context What matters most at the moment: release speed, release quality, finding product-market fit, maintaining market position, or something else? This will help you understand how to embed research so that it brings value, does not slow the team down, and keeps the right balance between speed, quality, and money. ![A diagram illustrates trade-offs among research speed, quality, and cost.](https://wynde.evgeniichekov.com/guide/illustrations/dd7585e3-2528-4bf0-9d55-7712320a40b9.png) Examples: Get involved in planning, especially if you work with several teams. At the start, it is worth attending their meetings more often so you become established as part of the team. Get involved in planning. Especially if you work with several teams, at the start it is worth attending their meetings more often so you become established as part of the team and build context. Try to evaluate the project realistically. Especially at the beginning, give teams a positive experience with research. Plan studies independently in advance around project milestones. This shows your foresight. At the beginning of developing a research practice, do not block team work and releases because research is absent. Mandatory usability tests before releases are more appropriate for teams with high UX maturity. For example, in a large bank, this may be justified and necessary. In a small startup trying to reach the market faster and outpace competitors, this approach will only slow growth. What should you do if you are the first researcher and there are many teams? There is no single correct answer. But there is a plan that can help you orient yourself: - understand the business context and find the balance between speed, quality, and resources - clarify expectations with your manager and key stakeholders - look at the company’s strategic and tactical plans - define what exactly you consider important. This point is key: you are the one who sets the research standard. But form your opinion based on everything listed above Examples: The company expects strategic influence. Teams already run tactical research and want to continue. It is important to align expectations: focus on strategic projects, and offer teams consulting, methodological support, and help with recruiting. Common sense matters more, and one burned-out researcher will not help anyone. The company wants to improve product quality. Prioritization and the need for features are decided differently. Then it makes sense to focus on tactical projects and processes for different teams: research sign-up, recruiting external and internal users, speed and quality of results, evaluating user experience in production, and so on. ### Build relationships and trust with stakeholders This is not a bonus, but a working tool that increases the value of research. Relationships provide understanding of business priorities, access to data and users, help align the focus, and make it easier to implement insights in work. Examples: Regularly share research progress updates with stakeholders. For example, agree that every Monday morning a short status update will appear in the work chat. This reduces uncertainty, saves time on clarification, and shows that you have the process under control. Do not wait until the end of the study to share important findings. If something can influence a business decision right now, report it immediately. The main thing is to separate signal from noise: share only what truly leads to action. Value time — yours and stakeholders’. If an issue can be discussed in 10 minutes instead of half an hour, shorten the meeting. If the key point can be communicated in 15 minutes, do it at the beginning of an hour-long presentation, then let the CPO leave and devote the remaining time to details for those who need them. ### Teach the value of UX research The more clearly stakeholders see how research helps their goals, the more willingly they support it. The NN Group guide describes 5 workshop formats for effective research and team involvement: - Discovery workshops. Help capture the current state of the product and agree on plans and key milestones. - Empathy workshops. Help the team and stakeholders better understand users and prioritize their needs before design begins. - Design workshops. Help generate and discuss many ideas quickly in a diverse group of participants. - Prioritization workshops. Help the team agree on which features matter most to users or stakeholders and set priorities. - Critique workshops. Check how well design decisions actually meet user needs. [Five types of UX workshops by NN/g](https://www.nngroup.com/articles/5-ux-workshops/) ## Step 3. Strengthen the foundation When the team has already seen the value of research, the next step is to make it not one-off, but embedded in product life. This means defining the rules of the game, building a system, and enabling knowledge to accumulate. A researcher is not a “support service” for the product, but a partner in decision-making. To make that work: Connect research at the stage of ideas and hypothesis formulation; align with stakeholders before launch: what do we want to achieve, and how will we use the results; create a single knowledge repository, such as YouTrack, Notion, Dovetail, or Confluence — all studies should go there in a convenient format. This saves hours of work, helps avoid repeated tests, and turns scattered findings into a system. Fix a report template: 1–2 slides with the task, method, findings, and product decision. Then any team member can quickly skim the most important parts of the results. Organize cross-functional interaction. A good practice is to make research not only for researchers: Create a shared research calendar so everyone knows what is already in progress and where they can join; invite product managers, designers, and marketers to observe interviews or tests, so insights are perceived firsthand; after each study, formulate action items: what exactly the team should try, change, or test; build a feedback loop — come back in a month and check whether the metric or user behavior changed after the insights were implemented. This will reinforce the value of research: it will stop being a “collection of interesting facts” and become a working tool that influences the product. ## Step 4. Set up democratization Research democratization is useful only where there are clear boundaries. Giving people a tool does not mean they know how to use it, and a one-day workshop does not turn a stakeholder into a researcher. If the system is not built, instead of value you get “research theater”: insights stop being taken seriously, and research becomes imitation. What works in practice: Define which studies can be delegated and which cannot. It is safe to delegate simple usability tests, short surveys, or hallway tests. But strategic discovery, segmentation, or in-depth interviews remain in researchers’ area. Create a “living document” listing tasks that can and cannot be delegated. Define access levels. For example: Observer (watches interviews), Assistant (runs simple tests using a template), Lead (can assemble a project with mentorship). Each level should have clear expectations and boundaries. Build training as a system, not a one-off workshop. Design stages: “basics” → “intermediate level” → “partnership.” Pair every newcomer with a mentor and give them shadow sessions with feedback. Focus on outcomes, not activity. Count not “how many people tried to run a test,” but “which decisions were made based on their results.” This helps you see value and adjust the system in time. Use democratization metrics for hiring. If suddenly more and more research goes to non-researchers, it is not a signal to “reduce the load,” but a signal that it is time to hire a researcher. If democratization replaces hiring researchers, the system is built incorrectly.