August 7, 2026
—
3 minutes

Everyone Says They're User-Centric. So Why Do Most Products Still Suck?

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.

Share this article
Author
Optimal
Workshop

Related articles

View all blog articles
Learn more
1 min read

7 Ways UX and Product Designers Can Use MCP to Back Up Design Decisions

Great design decisions are grounded in evidence. But finding the right evidence isn't always easy when it's spread across multiple teams, usability tests, interviews, and surveys.

‍

Instead of searching through reports or asking teammates if research already exists, Model Context Protocol (MCP) lets you ask questions about your research repository in natural language from AI tools like ChatGPT, Claude, Gemini, and Cursor.

‍

Whether you're designing a new feature, iterating on a prototype, or preparing for a design review, MCP helps you quickly bring user evidence into your workflow.

‍

Here are seven ways UX, product, and experience designers can use MCP throughout the design process.

‍

‍

1. Start every design project with what users already told you

‍

Before opening Figma, understand what users are trying to accomplish, where they're struggling, and what your team has already learned.

‍

Try asking:

  • What have we already learned about onboarding?
  • What usability issues have we identified in checkout?
  • What are users trying to achieve when managing their account settings?
  • What research should I review before redesigning navigation?

‍

Designer workflow

Before kicking off a redesign, ask MCP to summarize existing research. Use the findings to define design goals, identify constraints, and prioritize the problems worth solving before creating your first wireframe.

‍

‍

2. Validate design concepts before investing time in high-fidelity designs

‍

As ideas begin to take shape, use previous research to pressure-test your thinking. MCP can surface similar studies, recurring usability issues, and participant feedback that helps you refine concepts earlier.

‍

Try asking:

  • Have we tested a similar design before?
  • What patterns have users struggled with in previous prototypes?
  • What should we avoid repeating?
  • Which usability findings should influence this design?

‍

Designer workflow

While exploring concepts in Figma, keep an AI assistant open alongside your design files. Ask questions as you work so previous research continuously informs design decisions instead of becoming something you review once at the beginning.

‍

‍

3. Write stronger design rationale

‍

Design reviews often involve explaining why a particular solution was chosen. Use MCP to find supporting evidence from previous studies.

‍

Try asking:

  • Find participant quotes supporting a simplified navigation.
  • What evidence suggests users prefer this workflow?
  • Which usability studies identified this problem?
  • Show examples of participants struggling with this interaction.

‍

Designer workflow

Use participant quotes, findings, and usability observations directly in design specs, PRDs, or design review presentations to help stakeholders understand the reasoning behind your decisions.

‍

‍

4. Spot UX patterns across products and releases

‍

Looking across multiple studies can reveal broader experience patterns. MCP can identify recurring pain points, emerging behaviours, and themes that may influence future design priorities.

‍

Try asking:

  • What usability issues appear across multiple product areas?
  • Compare findings from our last five prototype tests.
  • Which friction points have become more common over time?
  • What navigation issues keep appearing across studies?

‍

Designer workflow

Before planning a larger redesign, review patterns across multiple past studies. These recurring themes often highlight systemic UX issues that individual projects miss.

‍

‍

5. Prepare for design critiques and stakeholder reviews

‍

Strong design presentations combine visual solutions with user evidence. Use MCP to generate summaries tailored to your audience.

‍

Try asking:

  • Summarize the research supporting this redesign.
  • What are the three biggest user pain points?
  • Create an executive summary for stakeholders.
  • What customer evidence supports prioritizing this work?

‍

Designer workflow

Generate concise summaries before design critiques, roadmap discussions, or leadership reviews, then pair them with your prototypes to show both the solution and the evidence behind it.

‍

‍

6. Plan better usability tests

‍

Designers frequently need to validate prototypes, but not every question requires a brand new study. MCP helps identify what has already been answered and where genuine knowledge gaps remain.

‍

Try asking:

  • What questions about this flow are still unanswered?
  • What assumptions should we validate?
  • Which participant groups haven't been represented?
  • What tasks should we include in our next prototype test?

‍

Designer workflow

Review previous findings before writing test tasks. Build studies that extend existing knowledge instead of repeating research your team has already completed.

‍

‍

7. Bring research into the tools you already use

‍

Research is most valuable when it appears alongside the work you're already doing. With MCP, your repository becomes accessible from AI tools that support everyday design work.

‍

Potential workflows

  • Generate a design brief from previous research before starting a new feature.
  • Draft usability findings directly into Confluence or Notion.
  • Format ideas into sticky notes and prep for a design sprint with Miro or Mural.
  • Create presentation-ready summaries for design reviews.
  • Turn research findings into product requirements for engineering.
  • Compare proposed designs against historical usability findings.
  • Ask follow-up research questions while designing in Figma with an AI assistant open alongside your work.

‍

Instead of switching between repositories, documents, and reports, research becomes part of your design process.

‍

‍

Designing with confidence

‍

The best design decisions aren't based on intuition alone; they're informed by a deep understanding of user behavior.

‍

MCP makes it easier to bring research into everyday design work, helping you move from evidence to action faster. Whether you're exploring concepts, validating ideas, preparing stakeholder reviews, or planning usability tests, you can use MCP to help your research repository become an active design partner. 

‍

Book a demo or log into your account to get set up with MCP. 

Learn more
1 min read

When to use MCP vs. AI Chat

Optimal gives you two ways to use AI to ask questions about your research and explore your findings: AI Chat in Optimal Interviews and Optimal MCP.

‍

Both let you ask questions in natural language, but they’re designed for different types of research exploration.

‍

The simple difference: Use AI Chat to explore interview data in depth. Use MCP to explore individual studies, connect research from different studies, connect to other tools, automate existing or new workflows

‍

‍

AI Chat vs. MCP: Which should I use?

‍

Use AI Chat when you want to:

  • Explore a specific interview topic
  • Find supporting evidence in interview sessions
  • Find new video clips
  • Generate new highlight reels
  • Investigate participant reactions in more detail
  • Follow evidence back to timestamped interview sessions

‍

Use MCP when you want to:

  • Search across multiple studies
  • Compare findings across studies or time periods
  • Identify recurring themes and trends
  • Combine research from different methods
  • Explore individual studies using participant results, study setup and metadata
  • Analyse transcripts, task results, user paths and other available research data
  • Connect Optimal research to ChatGPT, Claude, Gemini, Cursor or other MCP-compatible tools
  • Bring research into broader AI-powered workflows and automate research tasks

‍

In short

‍

Go deeper into interviews → AI Chat

Use AI Chat when your question is focused on what participants said, how they reacted, or finding evidence within interview sessions.

‍

Go broader across research → MCP

Use MCP when your question spans multiple studies, research methods, time periods or data sources, or when you want to bring Optimal research into another AI workflow.

‍

‍

What is AI Chat in Optimal?

‍

AI Chat is an AI-powered research assistant built into Optimal Interviews. It helps you explore interview data using natural-language questions.

‍

Use AI Chat to find what participants said, investigate specific topics, discover supporting evidence and explore interview findings in more depth.

‍

For example, you can ask:

  • “What frustrations did participants mention about checkout?”
  • “Show me quotes about trust in the product.”
  • “What did participants find confusing about onboarding?”
  • “Find examples of participants struggling with the navigation.”

‍

You can ask follow-up questions to refine your search or investigate a finding further. AI Chat can also surface participant quotes, video clips and highlight reels, with citations that take you back to the supporting evidence in your interviews. Learn more about AI Chat.
‍

‍

What is Optimal MCP?

‍

Optimal MCP connects your Optimal research to MCP-compatible AI assistants and tools, including ChatGPT, Claude, Gemini and Cursor.

‍

MCP is designed for broader research exploration. It lets you work with research data across individual studies or your wider Workspace, making it useful for research synthesis, cross-study analysis and AI-powered research workflows.

‍

For example, you can ask:

  • “What usability issues have appeared across our research this year?”
  • “Compare our findings from March and June.”
  • “What themes are recurring across our recent studies?”
  • “Which studies included feedback about onboarding?”
  • “Create a Notion page outline summarising these research findings.”

‍

Depending on the data available to you, MCP can help you explore study information, participant results, supported survey results, transcripts, task results, user paths, study metadata and AI-generated insights. Learn more about Optimal MCP.

‍

‍

AI Chat vs. MCP example

‍

Imagine you want to understand problems with onboarding.

‍

Use AI Chat

Ask: “What did participants say was confusing about onboarding? Show me examples.”

‍

Use MCP

Ask: “What onboarding issues have appeared across our research over the past six months?”

‍

‍

What research data can AI Chat and MCP access?

‍

AI Chat focuses on your Interviews data, helping you explore interview responses and supporting evidence such as quotes and highlight reels.

‍

MCP provides read-only access to research data available to you in Optimal, including study information, participant results, supported survey results, and AI insights.

‍

‍

Best practices for using AI Chat and MCP

‍

Whichever tool you use, you’ll get more useful results by giving the AI enough context.

  • Ask specific questions. Include the product, feature, audience, study or timeframe where relevant.
  • Start broad, then dig deeper. Use follow-up questions to explore interesting findings.
  • Ask for evidence. Request quotes, examples, citations or the studies supporting a finding.
  • Specify the format. Ask for a summary, presentation-ready bullets, or another format that suits your needs. With MCP, you further specify formats, such as charts, tables, or interactive deliverables. 
  • Check important findings. Use AI to accelerate analysis, but review the underlying research before making important decisions.

‍

Find out more in our AI Chat best practices.

‍

Already using AI Chat or MCP? We’d love to hear how you’re using AI to explore your research. Share your use case, workflow or favorite way to work with AI with our team.

‍

Not using Optimal yet? See how Optimal can help you bring AI into your research workflow.
Book a demo.

Optimal MCP + Figma Agent
Learn more
1 min read

Optimal MCP + Figma Agent: Turning User Research Into Better Designs

What if you could turn real user feedback into your next design iteration with a single prompt?

‍

With Optimal MCP and Figma Agent, you can turn user research to design updates in minutes. Pull insights from your Optimal studies into Figma, then let its AI design agent update multiple frames and screens based on real participant feedback. As you gather more feedback, you can keep refining your designs, testing updated prototypes with real users and using what you learn to shape the next iteration.

‍

Together, Optimal MCP and Figma Agent help close the loop between research and design, helping you turn real user feedback into better designs with every iteration.
‍
‍

How does the Optimal MCP & Figma Agent work? 


Optimal MCP and Figma Agent help you connect the dots between research and design. Connect Optimal to Figma and draw on findings from one or multiple studies, including participant feedback, usability insights, transcripts and prototype task results. Figma’s AI design agent can use these insights to update existing designs or generate new ones based on your prompts.
‍

Then, bring your updated prototypes back into Optimal to test them with real participants and see how your changes perform.
‍

So what does this look like in practice? Imagine you've run a usability study and discovered that participants are struggling to find an important action in your product. Here’s how to put this research design loop into action.

‍

Optimal MCP + Figma Agent in action

‍

‍

From research insight to your next breakthrough
‍

1. Turn user insights into new design possibilities

‍

Reference Optimal MCP and one or more Optimal studies in Figma’s agent chat. Ask the agent to explore solutions to the usability issues your research revealed and generate design changes to address them.

Example prompt: "Connect to Optimal Workshop MCP, look at study "Mobile banking app", read the feedback and update the prototype based on the participants' feedback. Add these updated prototype screens to a new page in this file, side-by-side with the original artboard."

‍
‍

2. Explore further. Iterate faster.

‍

Use AI to explore alternatives, challenge your first approach and move through design possibilities faster. Then bring your expertise to the process. Evaluate the trade-offs, review the prototype flows, refine the details and decide which ideas best serve your users.

‍

As more participant feedback to your Optimal studies comes through, ask the agent to pull feedback from those new participants to bring those fresh insights into your Figma iterations.

‍
‍

3. Put your changes to the test

‍

Here's where the loop gets even more exciting.

‍

Put your newly updated prototype to the test with a new Optimal study. Have you made that important action easier to find? Does the new design solve the original problem? What could be even better?

‍

You can test multiple prototypes or combine multiple methods in one study, whether you're working with a prototype, live website or web app, or AI prototype with Optimal’s Usability Testing tool or keep it focused on one prototype with Optimal’s Prototype Testing tool.

‍

Every round of testing gives you more to work with. Every new insight creates another opportunity to improve.
‍

Ready to bring user research into your next design iteration?

‍

AI is changing how quickly we can move from an idea to a design. Make the most of your research by connecting Optimal to Figma’s AI Design Agent with Optimal MCP to build experiences and products people love.

‍

Get started with the Optimal MCP setup guide or check out the interactive demo.

‍

‍

‍

Seeing is believing

Explore our tools and see how Optimal makes gathering insights simple, powerful, and impactful.