April 11, 2019
3 min

How to convince others of the importance of UX research

There’s not much a parent won’t do to ensure their child has the best chance of succeeding in life. Unsurprisingly, things are much the same in product development. Whether it’s a designer, manager, developer or copywriter, everyone wants to see the product reach its full potential.

Key to a product’s success (even though it’s still not widely practiced) is UX research. Without research focused on learning user pain points and behaviors, development basically happens in the dark. Feeding direct insights from customers and users into the development of a product means teams can flick the light on and make more informed design decisions.

While the benefits of user research are obvious to anyone working in the field, it can be a real challenge to convince others of just how important and useful it is. We thought we’d help.

Define user research

If you want to sell the importance of UX research within your organization, you’ve got to ensure stakeholders have a clear understanding of what user research is and what they stand to gain from backing it.

In general, there are a few key things worth focusing on when you’re trying to explain the benefits of research:

  • More informed design decisions: Companies make major design decisions far too often without considering users. User research provides the data needed to make informed decisions.
  • Less uncertainty and risk: Similarly, research reduces risk and uncertainty simply by giving companies more clarity around how a particular product or service is used.
  • Retention and conversion benefits: Research means you’ll be more aligned with the needs of your customers and prospective customers.

Use the language of the people you’re trying to convince. A capable UX research practice will almost always improve key business metrics, namely sales and retention.

The early stages

When embarking on a project, book in some time early in the process to answer questions, explain your research approach and what you hope to gain from it. Here are some of the key things to go over:

  • Your objectives: What are you trying to achieve? This is a good time to cover your research questions.
  • Your research methods: Which methods will you be using to carry out your research? Cover the advantages of these methods and the information you’re likely to get from using them.
  • Constraints: Do you see any major obstacles? Any issues with resources?
  • Provide examples: Nothing shows the value of doing research quite like a case study. If you can’t find an example of research within your own organization, see what you can find online.

Involve others in your research

When trying to convince someone of the validity of what you’re doing, it’s often best to just show them. There are a couple of effective ways you can do this – at a team or individual level and at an organizational level.

We’ll explain the best way to approach this below, but there’s another important reason to bring others into your research. UX research can’t exist in a vacuum – it thrives on integration and collaboration with other teams. Importantly, this also means working with other teams to define the problems they’re trying to solve and the scope of their projects. Once you’ve got an understanding of what they’re trying to achieve, you’ll be in a better position to help them through research.

Educate others on what research is

Education sessions (lunch-and-learns) are one of the best ways to get a particular team or group together and run through the what and why of user research. You can work with them to work out what they’d like to see from you, and how you can help each other.

Tailor what you’re saying to different teams, especially if you’re talking to people with vastly different skill sets. For example, developers and designers are likely to see entirely different value in research.

Collect user insights across the organization

Putting together a comprehensive internal repository focused specifically on user research is another excellent way to grow awareness. It can also help to quantify things that may otherwise fall by the wayside. For example, you can measure the magnitude of certain pain points or observe patterns in feature requests. Using a platform like Notion or Confluence (or even Google Drive if you don’t want a dedicated platform), log all of your study notes, insights and research information that you find useful.

Whenever someone wants to learn more about research within the organization, they’ll be able to find everything easily.

Bring stakeholders along to research sessions

Getting a stakeholder along to a research session (usability tests and user interviews are great starting points) will help to show them the value that face-to-face sessions with users can provide.

To really involve an observer in your UX research, assign them a specific role. Note taker, for example. With a short briefing on best-practices for note taking, they can get a feel for what’s like to do some of the work you do.

You may also want to consider bringing anyone who’s interested along to a research session, even if they’re just there to observe.

Share your findings – consistently

Research is about more than just testing a hypothesis, it’s important to actually take your research back to the people who can action the data.

By sharing your research findings with teams and stakeholders regularly, your organization will start to build up an understanding of the value that ongoing research can provide, meaning getting approval to pursue research in future becomes easier. This is a bit of a chicken and egg situation, but it’s a practice that all researchers need to get into – especially those embedded in large teams or organizations.

Anything else you think is worth mentioning? Let us know in the comments.

Read more

Share this article
Author
Optimal
Workshop

Related articles

View all blog articles
Learn more
1 min read

Radical Collaboration: how teamwork really can make the dream work

Natalie and Lulu have forged a unique team culture that focuses on positive outputs (and outcomes) for their app’s growing user base. In doing so, they turned the traditional design approach on its head and created a dynamic and supportive team. 

Natalie, Director of Design at Hatch, and Lulu, UX Design Specialist, recently spoke at UX New Zealand, the leading UX and IA conference in New Zealand hosted by Optimal Workshop, on their concept of “radical collaboration”.

In their talk, Nat and Lulu share their experience of growing a small app into a big player in the finance sector, and their unique approach to teamwork and culture which helped achieve it.

Background on Natalie Ferguson and Lulu Pachuau

Over the last two decades, Lulu and Nat have delivered exceptional customer experiences for too many organizations to count. After Nat co-founded Hatch, she begged Lulu to join her on their audacious mission: To supercharge wealth building in NZ. Together, they created a design and product culture that inspired 180,000 Kiwi investors to join in just 4 years.

Contact Details:

Email: natalie@sixfold.co.nz

LinkedIn: https://www.linkedin.com/in/natalieferguson/ and https://www.linkedin.com/in/lulupach/

Radical Collaboration - How teamwork makes the dream work 💪💪💪

Nat and Lulu discuss how they nurtured a team culture of “radical collaboration” when growing the hugely popular app Hatch, based in New Zealand. Hatch allows everyday New Zealanders to quickly and easily trade in the U.S. share market. 

The beginning of the COVID pandemic spelled huge growth for Hatch and caused significant design challenges for the product. This growth meant that the app had to grow from a baby startup to one that could operate at scale - virtually overnight. 

In navigating this challenge, Nat and Lulu coined the term radical collaboration, which aims to “dismantle organizational walls and supercharge what teams achieve”. Radical collaboration has six key pillars, which they discuss alongside their experience at Hatch.

Pillar #1: When you live and breathe your North star

Listening to hundreds of their customers’ stories, combined with their own personal experiences with money, compelled Lulu and Nat to change how their users view money. And so, “Grow the wealth of New Zealanders” became a powerful mission statement, or North Star, for Hatch. The mission was to give people the confidence and the ability to live their own lives with financial freedom and control. Nat and Lulu express the importance of truly believing in the mission of your product, and how this can become a guiding light for any team. 

Pillar #2: When you trust each other so much, you’re happy to give up control

As Hatch grew rapidly, trusting each other became more and more important. Nat and Lulu state that sometimes you need to take a step back and stop fueling growth for growth’s sake. It was at this point that Nat asked Lulu to join the team, and Nat’s first request was for Lulu to be super critical about the product design to date - no feedback was out of bounds. Letting go, feeling uncomfortable, and trusting your team can be difficult, but sometimes it’s what you need in order to drag yourself out of status quo design. This resulted in a brief hiatus from frantic delivery to take stock and reprioritize what was important - something that can be difficult without heavy doses of trust!

Pillar #3: When everyone wears all the hats

During their journey, the team at Hatch heard lots of stories from their users. Many of these stories were heard during “Hatcheversery Calls”, where team members would call users on their sign-up anniversary to chat about their experience with the app. Some of these calls were inspiring, insightful, and heartwarming.

Everyone at Hatch made these calls – designers, writers, customer support, engineers, and even the CEO. Speaking to strangers in this way was a challenge for some, especially since it was common to field technical questions about the business. Nevertheless, asking staff to wear many hats like this turned the entire team into researchers and analysts. By forcing ourselves and our team outside of our comfort zone, we forced each other to see the whole picture of the business, not just our own little piece.

Pillar #4: When you do what’s right, not what’s glam

In an increasingly competitive industry, designers and developers are often tempted to consistently deliver new and exciting features. In response to rapid growth, rather than adding more features to the app, Lulu and Nat made a conscious effort to really listen to their customers to understand what problems they needed solving. 

As it turned out, filing overseas tax returns was a significant and common problem for their customers - it was difficult and expensive. So, the team at Hatch devised a tax solution. This solution was developed by the entire team, with almost no tax specialists involved until the very end! This process was far from glamorous and it often fell outside of standard job descriptions. However, the team eventually succeeded in simplifying a notoriously difficult process and saved their customers a massive headache.

Pillar #5: When you own the outcome, not your output.

Over time Hatch’s user base changed from being primarily confident, seasoned investors, to being first-time investors. This new user group was typically scared of investing and often felt that it was only a thing wealthy people did.

At this point, Hatch felt it was necessary to take a step back from delivering updates to take stock of their new position. This meant deeply understanding their customers’ journey from signing up, to making their first trade. Once this was intimately understood, the team delivered a comprehensive onboarding process which increased the sign-up conversion rate by 10%!

Pillar #6: When you’re relentlessly committed to making it work

Nat and Lulu describe a moment when Allbirds wanted to work with Hatch to allow ordinary New Zealanders to be involved in their IPO launch on the New York stock exchange. Again, this task faced numerous tax and trade law challenges, and offering the service seemed like yet another insurmountable task. The team at Hatch nearly gave up several times during this project, but everyone was determined to get this feature across the line – and they did. As a result, New Zealanders were some of the few regular investors from outside the U.S that were able to take part in Albirds IPO. 

Why it matters 💥

Over four years, Hatch grew to 180,000 users who collectively invested over $1bn. Nat and Lulu’s success underscores the critical role of teamwork and collaboration in achieving exceptional user experiences. Product teams should remember that in the rapidly evolving tech industry, it's not just about delivering the latest features; it's about fostering a positive and supportive team culture that buys into the bigger picture.

The Hatch team grew to be more than team members and technical experts. They grew in confidence and appreciated every moving part of the business. Product teams can draw inspiration from Hatch's journey, where designers, writers, engineers, and even the CEO actively engaged with users, challenged traditional design decisions, and prioritized solving actual user problems. This approach led to better, more user-centric outcomes and a deep understanding of the end-to-end user experience.

Most importantly, through the good times and tough, the team grew to trust each other. The mission weaved its way through each member of the team, which ultimately manifested in positive outcomes for the user and the business.

Nat and Lulu’s concept of radical collaboration led to several positive outcomes for Hatch:

  • It changed the way they did business. Information was no longer held in the minds of a few individuals – instead, it was shared. People were able to step into other people's roles seamlessly. 
  • Hatch achieved better results faster by focusing on the end-to-end experience of the app, rather than by adding successive features. 
  • The team became more nimble – potential design/development issues were anticipated earlier because everyone knew what the downstream impacts of a decision would be.

Over the next week, Lulu and Nat encourage designers and researchers to get outside of their comfort zone and:

  • Visit customer support team
  • Pick up the phone and call a customer
  • Challenge status quo design decisions. Ask, does this thing solve an end-user problem?

Learn more
1 min read

Why Understanding Users Has Never Been Easier...or Harder

Product, design and research teams today are drowning in user data while starving for user understanding. Never before have teams had such access to user information, analytics dashboards, heatmaps, session recordings, survey responses, social media sentiment, support tickets, and endless behavioral data points. Yet despite this volume of data, teams consistently build features users don't want and miss needs hiding in plain sight.

It’s a true paradox for product, design and research teams: more information has made genuine understanding more elusive. 

Because with  all this data, teams feel informed. They can say with confidence: "Users spend 3.2 minutes on this page," "42% abandon at this step," "Power users click here." But what this data doesn't tell you is Why. 

The Difference between Data and Insight

Data tells you what happened. Understanding tells you why it matters.

Here’s a good example of this: Your analytics show that 60% of users abandon a new feature after first use. You know they're leaving. You can see where they click before they go. You have their demographic data and behavioral patterns.

But you don't know:

  • Were they confused or simply uninterested?
  • Did it solve their problem too slowly or not at all?
  • Would they return if one thing changed, or is the entire approach wrong?
  • Are they your target users or the wrong segment entirely?

One team sees "60% abandonment" and adds onboarding tooltips. Another talks to users and discovers the feature solves the wrong problem entirely. Same data, completely different understanding.

Modern tools make it dangerously easy to mistake observation for comprehension, but some aspects of user experience exist beyond measurement:

  • Emotional context, like the frustration of trying to complete a task while handling a crying baby, or the anxiety of making a financial decision without confidence.
  • The unspoken needs of users which can only be demonstrated through real interactions. Users develop workarounds without reporting bugs. They live with friction because they don't know better solutions exist.
  • Cultural nuances that numbers don't capture, like how language choice resonates differently across cultures, or how trust signals vary by context.
  • Data shows what users do within your current product. It doesn't reveal what they'd do if you solved their problems differently to help you identify new opportunities. 

Why Human Empathy is More Important than Ever 

The teams building truly user-centered products haven't abandoned data but they've learned to combine quantitative and qualitative insights. 

  • Combine analytics (what happens), user interviews (why it happens), and observation (context in which it happens).
  • Understanding builds over time. A single study provides a snapshot; continuous engagement reveals the movie.
  • Use data to form theories, research to validate them, and real-world live testing to confirm understanding.
  • Different team members see different aspects. Engineers notice system issues, designers spot usability gaps, PMs identify market fit, researchers uncover needs.

Adding AI into the mix also emphasizes the need for human validation. While AI can help significantly speed up workflows and can augment human expertise, it still requires oversight and review from real people. 

AI can spot trends humans miss, processing millions of data points instantly but it can't understand human emotion, cultural context, or unspoken needs. It can summarize what users say but humans must interpret what they mean.

Understanding users has never been easier from a data perspective. We have tools our predecessors could only dream of.  But understanding users has never been harder from an empathy perspective. The sheer volume of data available to us creates an illusion of knowledge that's more dangerous than ignorance.

The teams succeeding aren't choosing between data and empathy, they're investing equally in both. They use analytics to spot patterns and conversations to understand meaning. They measure behavior and observe context. They quantify outcomes and qualify experiences.

Because at the end of the day, you can track every click, measure every metric, and analyze every behavior, but until you understand why, you're just collecting data, not creating understanding.

Learn more
1 min read

UXDX Dublin 2024: Where Chocolate Meets UX Innovation

What happens when you mix New Zealand's finest chocolate with 870 of Europe's brightest UX minds? Pure magic, as we discovered at UXDX Dublin 2024!

A sweet start

Our UXDX journey began with pre-event drinks (courtesy of yours truly, Optimal Workshop) and a special treat from down under - a truckload of Whittaker's chocolate that quickly became the talk of the conference. Our impromptu card sorting exercise with different Whittaker's flavors revealed some interesting preferences, with Coconut Slab emerging as the clear favorite among attendees!

Cross-Functional Collaboration: More Than Just a Buzzword

The conference's core theme of breaking down silos between design, product, and engineering teams resonated deeply with our mission at Optimal Workshop. Andrew Birgiolas from Sephora delivered what I call a "magical performance" on collaboration as a product, complete with an unforgettable moment where he used his shoe to demonstrate communication scenarios (now that's what we call thinking on your feet!).

Purpose-driven design

Frank Gaine's session on organizational purpose was a standout moment, emphasizing the importance of alignment at three crucial levels:

- Company purpose

- Team purpose

- Individual purpose

This multi-layered approach to purpose struck a chord with attendees, reminding us that effective UX research and design must be anchored in clear, meaningful objectives at every level.

The art of communication

One of the most practical takeaways came from Kelle Link's session on navigating enterprise ecosystems. Her candid discussion about the necessity of becoming proficient in deck creation sparked knowing laughter from the audience. As our CEO noted, it's a crucial skill for communicating with senior leadership, board members, and investors - even if it means becoming a "deck ninja" (to use a more family-friendly term).

Standardization meets innovation

Chris Grant's insights on standardization hit home: "You need to standardize everything so things are predictable for a team." This seemingly counterintuitive approach to fostering innovation resonated with our own experience at Optimal Workshop - when the basics are predictable, teams have more bandwidth for tackling the unpredictable challenges that drive real innovation.

Building impactful product teams

Matt Fenby-Taylor's discussion of the "pirate vs. worker bee" persona balance was particularly illuminating. Finding team members who can maintain that delicate equilibrium between creative disruption and methodical execution is crucial for building truly impactful product teams.

Research evolution

A key thread throughout the conference was the evolution of UX research methods. Nadine Piecha's "Beyond Interviews" session emphasized that research is truly a team sport, requiring involvement from designers, PMs, and other stakeholders. This aligns perfectly with our mission at Optimal Workshop to make research more accessible and actionable for everyone.

The AI conversation

The debate on AI's role in design and research between John Cleere and Kevin Hawkins sparked intense discussions. The consensus? AI will augment rather than replace human researchers, allowing us to focus more on strategic thinking and deeper insights - a perspective that aligns with our own approach to integrating AI capabilities.

Looking ahead

As we reflect on UXDX 2024, a few things are clear:

  1. The industry is evolving rapidly, but the fundamentals of human-centered design remain crucial

  1. Cross-functional collaboration isn't just nice to have - it's essential for delivering impactful products

  1. The future of UX research and design is bright, with teams becoming more integrated and methodologies more sophisticated

The power of community

Perhaps the most valuable aspect of UXDX wasn't just the formal sessions, but the connections made over coffee (which we were happy to provide!) and, yes, New Zealand chocolate. The mix of workshops, forums, and networking opportunities created an environment where ideas could flow freely and partnerships could form naturally.

What's next?

As we look forward to UXDX 2025, we're excited to see how these conversations evolve. Will AI transform how we approach UX research? How will cross-functional collaboration continue to develop? And most importantly, which Whittaker's chocolate flavor will reign supreme next year?

One thing's for certain - the UX community is more vibrant and collaborative than ever, and we're proud to be part of its evolution. I’ve said it before and I’ll say it again, the industry has a very bright future. 

See you next year! We’ll remember to bring more Coconut Slab chocolate next time - it seems we've created quite a demand!

Seeing is believing

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