It doesn’t matter how brilliant your research is, or how profound the insights are, if those findings never influence decisions. Every researcher has experienced it: you uncover game-changing user needs, document them beautifully, present them compellingly, and watch them disappear into a research blackhole.

‍

While most companies invest significantly in user research, the majority of insights never impact product decisions. Research becomes a check box activity, not a driver of action and the problem isn't usually the quality of the research. It's in understanding how to turn those insights into action.

‍

Why research sits unused: 

‍

• Research findings are presented in the wrong format. A 40-page research report requires dedicated reading time that product managers don't have. 

• If research takes too long, the research findings can arrive after decisions are made. The team has already committed to a direction, and contradictory research becomes an inconvenient truth easily ignored.

• Sometimes researchers struggle to translate their findings into actions product teams understand. Researchers say "Users struggle with task completion due to cognitive load." Product managers need "If we simplify this flow by removing these three steps, we'll increase conversion by X%."

• Research can often be problem focused, not solution oriented. Research identifies problems but doesn't propose solutions. Teams agree there's an issue but they have no clear path forward.

‍

Alternatively, when research findings are delivered in an  action-oriented way, it starts with the conclusion, not the methodology, it answers the question “So what?” at every stage, and it states the business impact before the user impact. 

‍

Instead of: "We conducted 12 user interviews to understand onboarding experiences..." research findings like this result in statements like: "We can increase trial conversion by 35% by removing two steps from onboarding."

‍

So, how can you make research findings more actionable? 

‍

• Ensure that your researchers are deeply aligned with your product teams. Make sure they understand what product is looking for and the best way to share and deliver research findings. Getting research actioned, requires a mutual understanding of the value of research. 

• Make it clear the priority level of your findings: indicate which findings need immediate action, distinguish between "must fix" from "nice to have" and connect the recommendations  to business metrics.

• Provide concrete next steps: provide specific recommendations, not general direction, speak product’s language by Including effort estimates and suggest quick wins alongside strategic changes.

• Don’t underestimate the power of storytelling. Data doesn’t persuade, but stories do. The most actionable research turns insights into a narrative around the user journey and business impact. One of the best ways to do this is using video and highlight reels (see how we help with this here) which can really bring users pain points to life. 

‍

We believe that the most actionable research is designed for action from the start and that can require a shift in mindset from some research teams. Teams that want to make this shift (and that should be all of them) need to understand up front what decisions their research needs to inform and to include stakeholders early so they’re invested in research outcomes. 

‍

Research that doesn't drive action isn't research, t's expensive documentation. The goal isn't creating perfect insights but creating change. The researchers making the biggest impact aren't those conducting the most rigorous studies. They're those creating insights so clear, so timely, and so actionable that not using them feels irresponsible.

Most product teams treat UX research as something that happens to them:  a necessary evil that slows things down or a luxury they can't afford. The best product teams flip this narrative completely. Their research doesn't interrupt their roadmap; it powers it.

‍

"We need insights by Friday."

‍

"Proper research takes at least three weeks."

‍

This conversation happens in product teams everywhere, creating an eternal tension between the need for speed and the demands of rigor. But what if this debate is based on a false choice?

‍

Research that Moves at the Speed of Product

‍

Product development has accelerated dramatically. Two-week sprints are standard. Daily deployment is common. Feature flags allow instant iterations. In this environment, a four-week research study feels like asking a Formula 1 race car to wait for a horse-drawn carriage.

‍

The pressure is real. Product teams make dozens of decisions per sprint, about features, designs, priorities, and trade-offs. Waiting weeks for research on each decision simply isn't viable. So teams face an impossible choice: make decisions without insights or slow down dramatically.

‍

As a result, most teams choose speed. They make educated guesses, rely on assumptions, and hope for the best. Then they wonder why features flop and users churn.

‍

The False Dichotomy

‍

The framing of "speed vs. rigor" assumes these are opposing forces. But the best research teams have learned they're not mutually exclusive, they require different approaches for different situations.

‍

We think about research in three buckets, each serving a different strategic purpose:

‍

Discovery: You're exploring a space, building foundational knowledge, understanding thelandscape before you commit to a direction. This is where you uncover the problems worth solving and identify opportunities that weren't obvious from inside your product bubble.

‍

Fine-Tuning: You have a direction but need to nail the specifics. What exactly should this feature do? How should it work? What's the minimum viable version that still delivers value? This research turns broad opportunities into concrete solutions.

‍

Delivery: You're close to shipping and need to iron out the final details: copy, flows, edge cases. This isn't about validating whether you should build it; it's about making sure you build it right.

‍

Every week, our product, design, research and engineering leads review the roadmap together. We look at what's coming and decide which type of research goes where. The principle is simple: If something's already well-shaped, move fast. If it's risky and hard to reverse, invest in deeper research.

‍

How Fast Can Good Research Be?

‍

The answer is: surprisingly fast, when structured correctly! 

‍

For our teams, how deep we go isn't about how much time we have: it's about how much it would hurt to get it wrong. This is a strategic choice that most teams get backwards.

‍

Go deep when the stakes are high, foundational decisions that affect your entire product architecture, things that would be expensive to reverse, moments where you need multiple stakeholders aligned around a shared understanding of the problem.

‍

Move fast when you can afford to be wrong,  incremental improvements to existing flows, things you can change easily based on user feedback, places where you want to ship-learn-adjust in tight loops.

‍

Think of it as portfolio management for your research investment. Save your "big research bets" for the decisions that could set you back months, not days. Use lightweight validation for everything else.

‍

And while good research can be fast, speed isn't always the answer. There are definitely situations where deep research needs to run and it takes time. Save those moments for high stakes investments like repositioning your entire product, entering new markets, or pivoting your business model. But be cautious of research perfectionism which is a risk with deep research. Perfection is the enemy of progress. Your research team shouldn’t be asking "Is this research perfect?" but instead "Is this insight sufficient for the decision at hand?"

‍

The research goal should always be appropriate confidence, not perfect certainty.

‍

The Real Trade-Off

‍

The choice shouldn’t be  speed vs. rigor, it's between:

‍

• Research that matters (timely, actionable, sufficient confidence)

• Research that doesn't (perfect methodology, late arrival, irrelevant to decisions)

‍

The best research teams have learned to be ruthlessly pragmatic. They match research effort to decision impact. They deliver "good enough" insights quickly for small decisions and comprehensive insights thoughtfully for big ones.

‍

Speed and rigor aren't enemies. They're partners in a portfolio approach where each decision gets the right level of research investment. The teams winning aren't choosing between speed and rigor—they're choosing the appropriate blend for each situation.

‍

Last night, Optimal brought together an incredible community of product leaders and innovators for "The Automation Breakthrough: Workflows for the AI Era" at Q-Branch in Austin, Texas. This two-hour in-person event featured expert perspectives on how AI and automation are transforming the way we work, create, and lead.

‍

The event featured a lightning Talk on "Designing for Interfaces" featured Cindy Brummer, Founder of Standard Beagle Studio, followed by a dynamic panel discussion titled "The Automation Breakthrough" with industry leaders including Joe Meersman (Managing Partner, Gyroscope AI), Carmen Broomes (Head of UX, Handshake), Kasey Randall (Product Design Lead, Posh AI), and Prateek Khare (Head of Product, Amazon). We also had a fireside chat with our CEO, Alex Burke and Stu Smith, Head of Design at Atlassian. 

‍

Here are the key themes and insights that emerged from these conversations:

‍

Trust & Transparency: The Foundation of AI Adoption

‍

Cindy emphasized that trust and transparency aren't just nice-to-haves in the AI era, they're essential. As AI tools become more integrated into our workflows, building systems that users can understand and rely on becomes paramount. This theme set the tone for the entire event, reminding us that technological advancement must go hand-in-hand with ethical considerations.

‍

Automation Liberates Us from Grunt Work

‍

One of the most resonant themes was how AI fundamentally changes what we spend our time on. As Carmen noted, AI reduces the grunt work and tasks we don't want to do, freeing us to focus on what matters most. This isn't about replacing human workers, it's about eliminating the tedious, repetitive tasks that drain our energy and creativity.

‍

Enabling Creativity and Higher-Quality Decision-Making

‍

When automation handles the mundane, something remarkable happens: we gain space for deeper thinking and creativity. The panelists shared powerful examples of this transformation:

‍

Carmen described how AI and workflows help teams get to insights and execution on a much faster scale, rather than drowning in comments and documentation. Prateek encouraged the audience to use automation to get creative about their work, while Kasey shared how AI and automation have helped him develop different approaches to coaching, mentorship, and problem-solving, ultimately helping him grow as a leader.

‍

The decision-making benefits were particularly striking. Prateek explained how AI and automation have helped him be more thoughtful about decisions and make higher-quality choices, while Kasey echoed that these tools have helped him be more creative and deliberate in his approach.

‍

Democratizing Product Development

‍

Perhaps the most exciting shift discussed was how AI is leveling the playing field across organizations. Carmen emphasized the importance of anyone, regardless of their role, being able to get close to their customers. This democratization means that everyone can get involved in UX, think through user needs, and consider the best experience.

‍

The panel explored how roles are blurring in productive ways. Kasey noted that "we're all becoming product builders" and that product managers are becoming more central to conversations. Prateek predicted that teams are going to get smaller and achieve more with less as these tools become more accessible.

‍

Automation also plays a crucial role in iteration, helping teams incorporate customer feedback more effectively, according to Prateek.

‍

Practical Advice for Navigating the AI Era

‍

The panelists didn't just share lofty visions, they offered concrete guidance for professionals navigating this transformation:

‍

Stay perpetually curious. Prateek warned that no acquired knowledge will stay with you for long, so you need to be ready to learn anything at any time.

‍

Embrace experimentation. "Allow your process to misbehave," Prateek advised, encouraging attendees to break from rigid workflows and explore new approaches.

‍

Overcome fear. Carmen urged the audience not to be afraid of bringing in new tools or worrying that AI will take their jobs. The technology is here to augment, not replace.

‍

Just start. Kasey's advice was refreshingly simple: "Just start and do it again." Whether you're experimenting with AI tools or trying "vibe coding," the key is to begin and iterate.

‍

The energy in the room at Q-Branch reflected a community that's not just adapting to change but actively shaping it. The automation breakthrough isn't just about new tools, it's about reimagining how we work, who gets to participate in product development, and what becomes possible when we free ourselves from repetitive tasks.

‍

As we continue to navigate the AI era, events like this remind us that the most valuable insights come from bringing diverse perspectives together. The conversation doesn't end here, it's just beginning.

‍

Interested in joining future Optimal community events? Stay tuned for upcoming gatherings where we'll continue exploring the intersection of design, product, and emerging technologies.

‍

Despite AI being the buzzword in UX right now, there are still lots of concerns about how it’s going to impact research roles. One of the biggest concerns we hear is: is AI just going to replace UX researchers altogether?

‍

The answer, in our opinion, is no. The longer, more interesting answer is that AI is fundamentally transforming what it means to be a UX researcher, and in ways that make the role more strategic, more impactful, and more interesting than ever before.

‍

What AI Actually Does for Research 

‍

A 2024 survey by the UX Research Collective found that 68% of UX researchers are concerned about AI's impact on their roles. The fear makes sense, we've all seen how automation has transformed other industries. But what's actually happening is that rather than AI replacing researchers, it's eliminating the parts of research that researchers hate most.

‍

According to Gartner's 2024 Market Guide for User Research, AI tools can reduce analysis time by 60-70%, but not by replacing human insight. Instead, they handle:

‍

• Pattern Recognition at Scale: AI can process hundreds of user interviews and identify recurring themes in hours. For a human researcher that same work would take weeks. But those patterns will need human validation because AI doesn't understand why those patterns matter. That's where researchers will continue to add value, and we would argue, become more important than ever. 
• Synthesis Acceleration: According to research by the Nielsen Norman Group, AI can generate first-draft insight summaries 10x faster than humans. But these summaries still need researcher oversight to ensure context, accuracy, and actionable insights aren't lost. 
• Multi-language Analysis: AI can analyze feedback in 50+ languages simultaneously, democratizing global research. But cultural context and nuanced interpretation still require human understanding. 
•  Always-On Insights:  Traditional research is limited by human availability. Tools like AI interviewers can  run 24/7 while your team sleeps, allowing you to get continuous, high-quality user insights. 

‍

AI is Elevating the Role of Researchers 

‍

We think that what AI is actually doing  is making UX researchers more important, not less. By automating the less sophisticated  aspects of research, AI is pushing researchers toward the strategic work that only humans can do.

‍

From Operators to Strategists: McKinsey's 2024 research shows that teams using AI research tools spend 45% more time on strategic planning and only 20% on execution, compared to 30% strategy and 60% execution for traditional teams.

‍

From Reporters  to Storytellers: With AI handling data processing, researchers can focus on crafting compelling narratives. 

‍

From Analysts to Advisors: When freed from manual analysis, researchers become embedded strategic partners. 

‍

Human + AI Collaboration 

‍

The most effective research teams aren't choosing between human or AI, they're creating collaborative workflows that incorporate AI to augment researchers roles, not replace them: 

‍

• AI-Powered Data Collection: Automated transcription, sentiment analysis, and preliminary coding happen in real-time during user sessions.
• Human-Led Interpretation: Researchers review AI-generated insights, add context, challenge assumptions, and identify what AI might have missed.
• Collaborative Synthesis: AI suggests patterns and themes; researchers validate, refine, and connect to business context.
• Human Storytelling: Researchers craft narratives, implications, and recommendations that AI cannot generate.

‍

Is it likely that with AI more and more research tasks will become automated? Absolutely. Basic transcription, preliminary coding, and simple pattern recognition are already AI’s bread and butter. But research has never been about these tasks, it's been about understanding users and driving better decisions and that should always be left to humans. 

‍

The researchers thriving in 2025 and beyond aren't fighting AI, they're embracing it. They're using AI to handle the tedious 40% of their job so they can focus on the strategic 60% that creates real business value. You  have a choice. You can choose to adopt AI as a tool to elevate your role, or you can view it as a threat and get left behind. Our customers tell us that the researchers choosing elevation are finding their roles more strategic, more impactful, and more essential to product success than ever before.

‍

AI isn't replacing UX researchers. It's freeing them to do what they've always done best, understand humans and help build better products. And in a world drowning in data but starving for insight, that human expertise has never been more valuable.

‍

AI is transforming how businesses approach product development. From AI-powered chatbots and recommendation engines to predictive analytics and generative models, AI-first products are reshaping user interactions with technology, which in turn impacts every phase of the product development lifecycle.

‍

Whether you're skeptical about AI or enthusiastic about its potential, the fundamental truth about product development in an AI-driven future remains unchanged: a product is only as good as its user experience.

‍

No matter how powerful the underlying AI, if users don't trust it, can't understand it, or struggle to use it, the product will fail. Good UX isn't simply an add-on for AI-first products, it's a fundamental requirement.

‍

‍

Why UX Is More Critical Than Ever

‍

Unlike traditional software, where users typically follow structured, planned workflows, AI-first products introduce dynamic, unpredictable experiences. This creates several unique UX challenges:

‍

• Users struggle to understand AI's decisions – Why did the AI generate this particular response? Can they trust it?
  ‍
• AI doesn't always get it right – How does the product handle mistakes, errors, or bias?
  ‍
• Users expect AI to "just work" like magic – If interactions feel confusing, people will abandon the product.
  ‍

AI only succeeds when it's intuitive, accessible, and easy-to-use: the fundamental components of good user experience. That's why product teams need to embed strong UX research and design into AI development, right from the start.

‍

‍

Key UX Focus Areas for AI-First Products

‍

To Trust Your AI, Users Need to Understand It

‍

AI can feel like a black box, users often don't know how it works or why it's making certain decisions or recommendations. If people don't understand or trust your AI, they simply won't use it. The user experiences you need to build for an AI-first product must be grounded in transparency.

‍

What does a transparent experience look like?

‍

• Show users why AI makes certain decisions (e.g., "Recommended for you because…")
  ‍
• Allow users to adjust AI settings to customize their experience
  ‍
• Enable users to provide feedback when AI gets something wrong—and offer ways to correct it
  ‍

A strong example: Spotify's AI recommendations explain why a song was suggested, helping users understand the reasoning behind specific song recommendations.

‍

‍

AI Should Augment Human Expertise Not Replace It

‍

AI often goes hand-in-hand with automation, but this approach ignores one of AI's biggest limitations: incorporating human nuance and intuition into recommendations or answers. While AI products strive to feel seamless and automated, users need clarity on what's happening when AI makes mistakes.

‍

How can you address this? Design for AI-Human Collaboration:

‍

• Guide users on the best ways to interact with and extract value from your AI
  ‍
• Provide the ability to refine results so users feel in control of the end output
  ‍
• Offer a hybrid approach: allow users to combine AI-driven automation with manual/human inputs
  ‍

Consider Google's Gemini AI, which lets users edit generated responses rather than forcing them to accept AI's output as final, a thoughtful approach to human-AI collaboration.

‍

‍

Validate and Test AI UX Early and Often

‍

Because AI-first products offer dynamic experiences that can behave unpredictably, traditional usability testing isn't sufficient. Product teams need to test AI interactions across multiple real-world scenarios before launch to ensure their product functions properly.

‍

Run UX Research to Validate AI Models Throughout Development:

‍

• Implement First Click Testing to verify users understand where to interact with AI
  ‍
• Use Tree Testing to refine chatbot flows and decision trees
  ‍
• Conduct longitudinal studies to observe how users interact with AI over time
  ‍

One notable example: A leading tech company used Optimal to test their new AI product with 2,400 global participants, helping them refine navigation and conversion points, ultimately leading to improved engagement and retention.

‍

‍

The Future of AI Products Relies on UX

‍

The bottom line is that AI isn't replacing UX, it's making good UX even more essential. The more sophisticated the product, the more product teams need to invest in regular research, transparency, and usability testing to ensure they're building products people genuinely value and enjoy using.

‍

Want to improve your AI product's UX? Start testing with Optimal today.

‍

As AI transforms the UX research landscape, product teams face an important choice that extends far beyond functionality: how to integrate AI while maintaining the security and privacy standards your customers trust you with. At Optimal, we've been navigating these waters for years as we implement AI into our own product, and we want to share the way we view three fundamental approaches to AI integration, and why your choice matters more than you might think.

‍

Three Paths to AI Integration

‍

Path 1: Self-Hosting - The Gold Standard 

‍

Self-hosting AI models represents the holy grail of data security. When you run AI entirely within your own infrastructure, you maintain complete control over your data pipeline. No external parties process your customers' sensitive information, no data crosses third-party boundaries, and your security posture remains entirely under your control.

‍

The reality? This path is largely theoretical for most organizations today. The most powerful AI models, the ones that deliver the transformative capabilities your users expect, are closely guarded by their creators. Even if these models were available, the computational requirements would be prohibitive for most companies.

‍

While open-source alternatives exist, they often lag significantly behind proprietary models in capability. 

‍

Path 2: Established Cloud Providers - The Practical, Secure Choice 

‍

This is where platforms like AWS Bedrock shine. By working through established cloud infrastructure providers, you gain access to cutting-edge AI capabilities while leveraging enterprise-grade security frameworks that these providers have spent decades perfecting.

‍

Here's why this approach has become our preferred path at Optimal:

‍

Unified Security Perimeter: When you're already operating within AWS (or Azure, Google Cloud), keeping your AI processing within the same security boundary maintains consistency. Your data governance policies, access controls, and audit trails remain centralized.

‍

Proven Enterprise Standards: These providers have demonstrated their security capabilities across thousands of enterprise customers. They're subject to rigorous compliance frameworks (SOC 2, ISO 27001, GDPR, HIPAA) and have the resources to maintain these standards.

‍

Reduced Risk: Fewer external integrations mean fewer potential points of failure. When your transcription (AWS Transcribe), storage, compute, and AI processing all happen within the same provider's ecosystem, you minimize the number of trust relationships you need to manage.

‍

Professional Accountability: These providers have binding service agreements, insurance coverage, and legal frameworks that provide recourse if something goes wrong.

‍

Path 3: Direct Integration - A Risky Shortcut 

‍

Going directly to AI model creators like OpenAI or Anthropic might seem like the most straightforward approach, but it introduces significant security considerations that many organizations overlook.

‍

When you send customer data directly to OpenAI's APIs, you're essentially making them a sub-processor of your customers' most sensitive information. Consider what this means:

‍

• User research recordings containing personal opinions and behaviors
• Prototype feedback revealing strategic product directions
• Customer journey data exposing business intelligence
• Behavioral analytics containing personally identifiable patterns

‍

While these companies have their own security measures, you're now dependent on their practices, their policy changes, and their business decisions. 

‍

The Hidden Cost of Taking Shortcuts

‍

A practical example of this that we’ve come across in the UX tools ecosystem is the way some UX research platforms appear to use direct OpenAI integration for AI features while simultaneously using other services like Rev.ai for transcription. This means sensitive customer recordings touch multiple external services:

‍

1. Recording capture (your platform)
2. Transcription processing (Rev.ai)
3. AI analysis (OpenAI)
4. Final storage and presentation (back to your platform)

‍

Each step represents a potential security risk, a new privacy policy to evaluate, and another business relationship to monitor. More critically, it represents multiple points where sensitive customer data exists outside your primary security controls.

‍

Optimal’s Commitment to Security: Why We Choose the Bedrock Approach

‍

At Optimal, we've made a deliberate choice to route our AI capabilities through AWS Bedrock rather than direct integration. This isn't just about checking security boxes, although that’s important,  it's about maintaining the trust our customers place in us.

‍

Consistent Security Posture: Our entire infrastructure operates within AWS. By keeping AI processing within the same boundary, we maintain consistent security policies, monitoring, and incident response procedures.

‍

Future-Proofing: As new AI models become available through Bedrock, we can evaluate and adopt them without redesigning our security architecture or introducing new external dependencies.

‍

Customer Confidence: When we tell customers their data stays within our security perimeter, we mean it. No caveats. 

‍

Moving Forward Responsibly

‍

The path your organization chooses should align with your risk tolerance, technical capabilities, and customer commitments. The AI revolution in UX research is just beginning, but the security principles that should guide it are timeless. As we see these powerful new capabilities integrated into more UX tools and platforms, we hope businesses choose to resist the temptation to prioritize features over security, or convenience over customer trust.

‍

At Optimal, we believe the most effective AI implementations are those that enhance user research capabilities while strengthening, not weakening, your security posture. This means making deliberate architectural choices, even when they require more initial work. This alignment of security, depth and quality is something we’re known for in the industry, and it’s a core component of our brand identity. It’s something we will always prioritize. 

‍

Ready to explore AI-powered UX research that doesn't compromise on security? Learn more about how Optimal integrates cutting-edge AI capabilities within enterprise-grade security frameworks.

‍