.webp)
Walk into any product company and you'll hear the same language about being user-centric. So why does the average person still rage-quit apps weekly? If everyone's truly putting users at the center, something's not adding up. Most companies aren't lying when they say they're user-centric. They genuinely believe it. Leadership believes it. Product teams believe it. The values are probably painted on the office wall. But there's a massive gap between claiming to be user-centric and actually building products that work for users.
Where user insights go to die
Let's trace what actually happens to user research in most organizations. A researcher conducts a brilliant study. They talk to real users, identify genuine pain points, uncover surprising insights about how people actually use the product. The researcher creates a comprehensive report with clear recommendations. They present to stakeholders and then…nothing happens.
Product moves forward based on roadmap commitments made three months ago. Design tackles the projects already scoped. Engineering builds what's already been spec'd and by the time the next planning cycle rolls around, the research is old news. The context has shifted. New priorities have emerged. The research was great. It just never actually changed anything.
The issue here isn't that teams don't value research. It's that the systems aren't set up to close the gap between insight and implementation. Research lives in one place and product decisions happen somewhere else. There's a handoff required. Someone needs to take the insights from the research and translate them into the specific contexts where decisions get made. But who owns that handoff? Usually nobody explicitly. The researcher assumes product managers will incorporate the findings. Product managers assume researchers will flag critical issues. Designers are caught in the middle, trying to advocate for users while also hitting delivery dates. So insights leak at every transition point.
Even when research does make it into decision-making conversations, it's often in the wrong format for action. Researchers are trained to present thorough findings and all of that is valuable. But it's not always actionable. The gap between what users said and what should be done about it, is a lot bigger than most teams realize, but an even bigger problem is that product decisions can’t wait for perfect information. Product decisions need to happen fast, often in real-time, in contexts where pulling up a research report isn't practical. If research insights aren't immediately accessible in the moment decisions are being made, they effectively don't exist.
So…What actually works?
The companies that successfully put users at the center do something different. They build research into the decision-making flow rather than treating it as a separate activity that informs decisions. They make sure that research insights live where decisions happen, integrated into project management tools, design files, and product specs.
Increasingly, they're also using MCP (Model Context Protocol) to connect AI tools like Claude, ChatGPT, and Cursor directly to their research repository – here's how. Instead of searching through reports, teams can ask questions in natural language to surface relevant findings, user insights, and context exactly when they need them, or generate artifacts and workflows grounded in real user research. Insights are accessible in the moment someone needs them.
At Optimal, our design team embeds research findings directly in their Figma files. Not as links to external reports, but as context right next to the designs. When someone's reviewing navigation options, the tree test results are right there. When they're looking at prototype variations, the usability data is embedded in the file. Decisions and insights exist in the same place.
Another great step is to make sure that all research insights are framed as recommendations, not just observations. Instead of "Users struggled with the checkout flow," the insight could be "Simplify checkout to 3 steps instead of 5, based on usability testing where users abandoned at step 4." The researcher isn't just reporting what happened. They're translating it into clear next steps.
We also firmly believe that research should be continuous instead of episodic. Instead of big studies that take weeks and produce comprehensive reports, teams run smaller tests constantly. This doesn't replace deep foundational research. But it supplements it with rapid feedback loops that keep user input flowing into active work.
And lastly - research should be accessible to all. When only dedicated researchers can conduct studies, research becomes a bottleneck. When product managers and designers can run quick tests themselves, with appropriate guidance and quality standards, research becomes embedded in how the team works rather than something teams have to request and wait for.
Being genuinely user-centric requires infrastructure, not just values. You need tools that make it easy to share findings where people actually work. You need workflows that integrate research into product development rather than treating it as a separate track. You need the ability to run research at the speed decisions happen.
Most importantly, you need to make the gap between insight and action as small as possible. The best research in the world doesn't help users if it never influences what gets built.
.webp)
