How to make UX research actually useful for your team
In a nutshell
Sacha Kocovski sees UX teams called in when a product already has a problem. Research can help at that point, but it has more influence when it shapes the question before a solution is fixed. His test is practical: understand which decision the work should support, what the method can reveal and whether the team can act on the findings. AI makes that judgment more valuable, not less.
A stakeholder told Sacha Kocovski he could read Sacha’s research report on the train, even on his phone, and use it in a meeting the next day. Sacha remembers it as one of the best compliments he has received: the work had become useful in somebody else’s working day.
Sacha has spent more than 20 years in UX. At Proximus he worked across digital channels; at BNP Paribas Fortis he led research projects, worked with design teams and trained designers in research methods. That long view of how large organisations commission and use UX work gives weight to a frustration he says has barely changed: teams still call on UX when a product has already run into trouble.
Sacha Kocovski, UX Coach & Leadership Facilitator
When UX arrives to correct a decision already made
Sacha calls this corrective usability. A company has a difficult system merge, a flow that fails or a redesign to rescue, and UX is asked to improve what exists. That work can matter. But the team has much less room to question the original problem or direction than it would have had at the start. He believes UX has struggled to earn a place at the strategic table. Researchers may do valuable work while still being called in mainly to fix things. User evidence can shape a product earlier if decision makers invite it in before committing to a solution.
Instead of arriving with eye tracking or a usability test already prescribed, Sacha asks why the data is needed:
- What is at risk?
- What would success look like?
- How could a finding be implemented and checked?
A convincing research process can still lead nowhere
Sacha describes the danger as “UX theater”: visible research activity, impressive technology and a polished output, followed by little action. Nielsen Norman Group discusses the related idea of “design theater” in its State of UX in 2026, warning against going through the motions without results. Sacha’s own example is direct: a team might invest in eye tracking because the method looks persuasive, then do nothing with the result.
"Choose a method for a decision it can inform, explain its limits and prepare the people who will use the findings. Because if you don't do that, you will produce a tonne of interesting insights, but that nobody will use,” Sacha says.
His reports are built for that next step. A finding that a button confused users leaves a designer asking why and what to try. Examples and action points help the team work with the evidence. The train story shows the standard he cares about, although it does not prove a measured product outcome.
AI can produce more but the team still has to make the final choice
Sacha sees value in AI for summarising conversations, clustering information and suggesting approaches he might not have considered. He says the output should be checked before use. For design, faster generation creates another constraint: a team may produce more concepts than it can meaningfully test. Sacha says knowing why a design exists and which problem it addresses becomes more important when creating another option is easy. The team still has to choose what deserves attention.
This reinforces his earlier point. If research is already commissioned without a clear decision, faster analysis and more concepts can simply make the unused output pile larger. The question before the method becomes more useful as the methods become quicker.
Getting started with UX research in your team
You may know that research could help your product team without knowing which study to commission or whom to hire. Sacha’s advice offers a simpler starting point: describe the situation before choosing the solution.
Begin with the friction you can see:
- What are users struggling with?
- What has the team already tried, and what evidence does it have?
- Speak with the people who will use the findings, then name the decision that is waiting.
This gives a researcher a problem to investigate rather than a method to execute.
Next, consider what the team could do with an answer. Can it change the design, build and test an alternative, or check whether the change worked? If that route is unclear, more studies may add to the backlog of findings. Sacha cautions that the obstacle can be capacity, a missing skill or the way work moves through the team; it takes conversation to tell which.
If UX research is new to the organisation, an experienced external specialist can help establish the practice and work out which roles are needed. Sacha’s advice is to grow part of that capability internally afterward, so the team becomes more confident using research over time.
For Ariad, these are useful questions before turning an uncertain need into a vacancy. Start with the problem, the decision and the team that will act. Then choose the expertise that helps research become part of how the product improves.