Discovery
Synthesis of insights and solutions
How to synthesize research results: coding observations, patterns, opportunities, contradictions, and team decisions.
Synthesis is the transition from disparate notes to an explanation that withstands the test of the original data. Don’t vote for the brightest quotes: group observations, note the frequency and strength of the signal, look for exceptions, and keep each output related to specific episodes.
What is the synthesis of insights
Definition and principle
Insight synthesis is the process of analyzing information from users, teams, and markets to identify real problems and hidden needs. The main difference from simple collection is not just to hear a complaint, but to understand what is behind it and how it affects user behavior or business.
Example: Users complain that they are confused in the settings of the application. Synthesizing insights, you find out that the problem is not in the location of the buttons, but in too complex customization scenarios for beginners.
Why you can’t do it without fusion
If you ignore the synthesis stage, the product will be built on individual pieces of feedback and discussion of ideas in the chat. You get a set of random improvements that don’t solve the real problem.
How to identify and formulate problems
Problem-finding techniques
A good practice is to use multiple data sources: interviews, questionnaires, analytics, support. Write down all observations – not just what users say, but what they do.
Example: The SaaS platform team noticed that customers often leave the onboarding on step three. After the synthesis of insights found the reason: the requirements for data at this stage were not prepared in advance by the user.
Mistakes and anti-patterns
Don’t start formulating a solution until the problem is formulated. A common mistake is to try to guess the user or discuss only obvious improvements.
The dangerous way is to substitute your hypothesis for insights or project your own experience onto all users. Maintain a strict position: Formulate the problem so that the client and the team can recognize it.
How to test ideas: Fast cycles
Verification through customer development
When a problem is found, formulate a solution hypothesis. Don’t waste resources on complex features—look for quick ways to make sure your solution actually reduces pain.
Example: If users are confused onboarding, check the simplified script prototype on 8-10 users and compare the completion metrics. This will give you a quick answer – did your approach help?
Tracking success criteria
Set clear metrics: percentage of users who have overcome a bottleneck, time on a task, level of satisfaction with CSAT. After a quick check, remember to analyze the feedback – why it worked or why it didn’t.
Practical tips for synthesis
Take notes and visualize
Process the results of the research visually: use an affinity map or a user journey. It’s easier to highlight patterns and quickly show the team where the root of the problem is.
Example: After user interviews using the digital affinity board, the SaaS product team grouped the problems: learning, integration, and key pains at the start. So it became clear where to focus resources on the next sprint.
Convert Your Insights to Hypothesis Statement
Formulate your insight and hypothesis with a standard template: If the cause of the problem is a problem, then the cause of the problem is a problem. And if we do, we will see that we will be able to do it.
This approach helps not to confuse the problem with the solution and not to spray.
Where to look for benchmarks and best practices
For each metric, look for industry reports or public discussions. The best sources are backup from product and UX researchers:
- Product Talk - Good guides for formulating and checking insights
- Mind the Product - synthesis and discovery techniques
- SVPG Series - Approaches to Problem Search and Validation
The exact numbers suitable for a particular product depend on the market, the customer and the maturity of the team. The key metrics are retention, conversion, NPS, and CSAT, which are the values of open research in your industry.
FAQ
**How to distinguish an insight from a simple user complaint? Insight is not what the user says, but why they say or do it. Complaining about speed - perhaps the real problem is the non-obviousness of the next step, not the performance.
**Is it possible to miss the synthesis of insights, if everything is clear? Nope. First impressions are often deceptive, especially if the team has been working with the product for a long time. A fresh look reveals the hidden patterns.
When do you start thinking about a solution? Only after the problem is formulated and its importance for the client and business is confirmed.
What tools do you use for synthesis? Affinity mapping, user journey maps, familiar boards in Miro or FigJam. The main thing is to quickly collect and structure data.
*How do you know if the problem is important? The problem is important if the customer is willing to spend time, money or looking for workarounds. It is better when it is confirmed in numbers (outflows, returns, decrease in adoption).