Q&A2025-09-26
CTO SyncDiscover the power of user research techniques that can dramatically shift your product's trajectory. This article delves into seven key methods, each offering unique insights that have the potential to revolutionize your approach to product development. Drawing from expert knowledge and real-world applications, these techniques provide a roadmap for creating more user-centric and successful products.
Contributors · 7
Siddharth Vij<CEO & Design Lead, Bricx Labs>One of our SaaS clients approached us, requesting a redesign that could potentially double their conversions. They had a decent number of sign-ups, but hardly anyone was progressing beyond the first day. One of the simplest user research techniques we employed was to conduct user interviews with their power users and understand their problems.
Instead of only talking to engaged users, we also conducted interviews with churned users - unlocking a goldmine of value. We then used these insights to rebuild the onboarding process, adding questions to the onboarding flow and adapting the user journey from there.
The results were immediate: Activation rates doubled, retention improved, and free-to-paid conversions jumped from a mere 6% to 13%.
For SaaS teams that really want to understand how to approach a redesign, the simplest technique would be to talk to their users (especially those who leave on Day 1). They often point out issues you'd never see otherwise.
Nikita Sherbina<Co-Founder & CEO, AIScreen Digital Signage Software>One user research technique that completely changed the direction of our product was conducting in-depth contextual interviews with actual users in their own work environments. I spent several days observing how our target audience interacted with existing tools and noting pain points they didn't always articulate in surveys. One insight stood out: users were struggling with navigating complex dashboards, which slowed down their workflow and caused frustration. Based on this, we redesigned the interface to prioritize simplicity, with a more intuitive navigation structure and customizable shortcuts for the most-used features. The impact was immediate—during beta testing, task completion times dropped by 30%, and users reported feeling more confident and satisfied with the product. This experience taught me the value of seeing how people truly engage with a product in context rather than relying solely on assumptions or high-level feedback. It shifted our focus from feature-heavy design to user-centered simplicity.
Dhari Alabdulhadi<CTO and Founder, Ubuy Peru>Usability testing has completely changed the way things work for me. You spend most of the time brainstorming, conducting regular check-ups on how intuitive your design can be. But in reality, the moment you show these designs to your users, the illusion crumbles.
It is something hard to digest. Watching someone struggle with your work, which you thought would be fine, is a mix of humbling and horrifying. Once, I thought a feature would be the centerpiece of the product. But when it was time to test, it was actually ignored by the user. They really valued a simpler workflow, and this led us to scrap some brilliant ideas. We redesigned the interface and prioritized what the user wanted. The final product was leaner, clearer, and actually an effective solution to all the problems. Seems shocking, right? But it is reality.
Valentin Radu<CEO & Founder, Blogger, Speaker, Podcaster, Omniconvert>One user research technique that completely changed the direction of our SaaS product was conducting in-depth customer interviews early in development. Through these conversations, we discovered that many users prioritized integration capabilities over standalone features, which was not originally our primary focus.
This insight led us to pivot our design toward building robust API functionalities and seamless third-party integrations. As a result, our product not only attracted a wider audience but also significantly improved retention rates by solving a critical need in our target market.
Nick Gabriele<Director, Noterro>At Noterro, we transformed our user research approach by shifting from generic testimonial requests to targeted, workflow-specific questions. Instead of asking "Tell us what you think," we began asking questions like "What part of your workflow feels easier now?" This simple change yielded substantially more honest and actionable feedback from users. The resulting insights allowed us to refine our product design around actual user workflows rather than our assumptions about what was important.
Elmo Taddeo<CEO, Parachute>I've seen firsthand how ethnographic research can turn a project upside down—in a good way. My team once set out to design a time-management tool that we thought needed advanced scheduling features. After spending time with real office workers in their own environments, we discovered something surprising. People weren't struggling with scheduling; they were drowning in constant interruptions and relying on sticky notes more than calendars.
That insight forced us to rethink everything. Instead of chasing complex calendar functions, we built features around focus management. We introduced a "Do Not Disturb" mode that connected with Slack and email, so users could silence distractions when needed. We also created a digital "focus board" that acted like quick sticky notes, making it easy to jot something down and return to the task at hand without losing momentum.
If you're building a product, get out of the conference room and into your users' daily world. Observing real behavior shows you pain points that scripted interviews miss. Ask yourself: Are you solving the problem your users say they have, or the one they actually face? That's the difference between building a tool that's ignored and one that truly changes how people work.
Vincent Carrié<CEO, Purple Media>The biggest change we implemented came through our observation of real customers using the SaaS tool without guidance. The users stopped using the onboarding process after five minutes, becoming completely stuck because they failed to make any clicks. The users interpreted the dashboard as a completed report instead of an interactive platform.
This discovery prompted us to create a new onboarding sequence with dashboard-based contextual assistance. The new design achieved both visual appeal and practical benefits: it reduced support requests by 40% while increasing activation rates by 100% during the first month.
