Event Recap: Measuring the Value of UX Research at UXDX

In the fast-paced world of tech startups and scale-ups, having a strong set of core values is crucial for sustainable growth and success. As the CEO of Optimal Workshop, a best-in-class research and insights platform, I've learned firsthand the importance of establishing and nurturing the right company culture. Today, I'd like to share our journey of revisiting and refining our values, and how these principles are shaping our path forward.

‍

‍

The power of values in leadership 🫶

‍

This is my third run as a CEO, following leadership roles at the digital consultancy Tigerspike and the EdTech company Education Perfect. Each time, I've faced the challenge of taking the business to a whole new level. From experience, I've learned that this transformation begins with getting all the right pieces in play for future growth.

‍

At Optimal Workshop, we've been busy laying the groundwork for our next phase of expansion:

‍

1. Forming a new leadership team

2. Launching a fresh brand identity

3. Developing a new strategy and product direction

4. Introducing our refined team values

‍

These elements, particularly our values, are not just words on a wall. They underpin our future way of working and set the standard for the behaviors we expect from every team member. By doing so, we're creating a culture of high performance with solid foundations to build upon and scale globally.

‍

Our core values: The heart of Optimal Workshop 💖

‍

In April 2024, we embarked on a journey to revisit and refine our company values. This process was collaborative and thoughtful, involving input from team members across all levels of the organization. The result is a set of four core values that truly represent who we are and who we aspire to be:

‍

1. Live in our customers' shoes

‍

At Optimal Workshop, we believe that our success is intrinsically tied to the success of our customers. This value emphasizes empathy, understanding, and a customer-centric approach to everything we do. Team members who embody this value:

‍

• Deeply understand our products and champion user research and data-driven methodologies
• Go above and beyond to support our customers, ensuring they derive maximum value from our products and services
• Show a profound understanding of customer pain points and challenges, always seeking ways to enhance the customer experience
• Prioritize customer satisfaction and strive to provide the highest level of service in all their endeavors

‍

2. Own it

‍

We take pride in our expertise and resilience. This value is about taking initiative, holding ourselves to high standards, and fostering an environment of trust and commitment. An "Own It" mindset means:

‍

• Demonstrating reliability and accountability, stepping up to challenges and delivering on promises
• Being solution-focused, supporting others, and finding the best outcomes for all stakeholders
• Bringing a high level of quality to daily work, advancing projects while maintaining excellent standards
• Communicating openly and transparently, and professionally challenging the status quo when necessary

‍

3. Game On!

‍

In the dynamic world of tech and user research, adaptability and continuous learning are key. Our "Game On!" value encapsulates our readiness to pivot, our curiosity, and our commitment to constant improvement. Team members who exemplify this value:

‍

• Demonstrate the ability to change direction quickly and adapt to new circumstances
• Actively contribute to discussions, ask insightful questions, and share information effectively
• Continuously learn and challenge the status quo, always seeking innovative ways to improve our processes and offerings

‍

4. In It Together

‍

Last but certainly not least, we believe in the power of collaboration, mutual support, and compassion. This value underscores our commitment to fostering a positive, respectful work environment where everyone can thrive. "In It Together" means:

‍

• Creating a collaborative work environment and showing respect to all team members and individuals
• Bringing colleagues and customers together to achieve better results and reach common goals
• Demonstrating honesty, transparency, and integrity in team settings
• Speaking openly but respectfully, always listening actively, and being present and ready to participate

‍

Celebrating our values in action 🥳

‍

To bring these values to life, we recently celebrated our inaugural Value Awards. It was inspiring to see team members being recognized for exemplifying these principles in their daily work:

‍

• GabeYoung, Head of Engineering for "Game On"
• Sarah Flutey, Head of Product Marketing for "Live in Our Customer's Shoes"
• Christine Chow, Senior Product Marketer for "Own It"
• Loren Whithair Senior Business Intelligence Advisor (Data) for "In It Together"

‍

These winners have set a great benchmark for all of us to follow, showing how our values translate into tangible actions and outcomes.

‍

Looking ahead 🔭

‍

One of the most crucial lessons I've learned as a CEO is the immense value of establishing clear core values and guidelines early in a company's journey. When these fundamental pieces are in place, scaling becomes not just easier, but significantly faster – especially when it comes to global growth. 

‍

By setting these core values and guidelines early, we've created a strong foundation that will enable Optimal Workshop to scale more efficiently and effectively on a global level, maintaining our identity, culture, and high standards of performance, no matter how large we become or how far we expand geographically.

‍

Here's to the journey ahead – onwards and upwards, across borders and beyond!

Alex Burke

‍

Last week Optimal Workshop was delighted to sponsor UXDX USA 2024 in New York. The User Experience event brings together Product, Design, UX, CX, and Engineering professionals and our team had an amazing time meeting with customers, industry experts, and colleagues throughout the conference. This year, we also had the privilege of sharing some of our industry expertise by running an interactive forum on “Measuring the Value of UX Research” - a topic very close to our hearts.

‍

‍

Our forum, hosted by Optimal Workshop CEO Alex Burke and Product Lead Ella Fielding, was focused on exploring the value of User Experience Research (UXR) from both an industry-wide perspective and within the diverse ecosystem of individual companies and teams conducting this type of research today.

‍

The session brought together a global mix of UX professionals for a rich discussion on measuring and demonstrating the effectiveness of and the challenges facing organizations who are trying to tie UXR to tangible business value today.

‍

The main topics for the discuss were: 

• Metrics that Matter: How do you measure UXR's impact on sales, customer satisfaction, and design influence?
• Challenges & Strategies: What are the roadblocks to measuring UXR impact, and how can we overcome them?
• Beyond ROI:  UXR's value beyond just financial metrics

‍

Some of the key takeaways from our discussions during the session were: 

‍

1. The current state of UX maturity and value
   • Many UX teams don’t measure the impact of UXR on core business metrics and there were more attendees who are not measuring the impact of their work than those that are measuring it. 
   • Alex & Ella discussed with the attendees the current state of UX research maturity and the ability to prove value across different organizations represented in the room. Most organizations were still early in their UX research maturity with only 5% considering themselves advanced in having research culturally embedded.

2. Defining and proving the value of UX research
   • The industry doesn’t have clear alignment or understanding of what good measurement looks like. Many teams don’t know how to accurately measure UXR impact or don’t have the tools or platforms to measure it, which serve as core roadblocks for measuring UXRs’ impact. 
   • Alex and Ella discussed challenges in defining and proving the value of UX research, with common values being getting closer to customers, innovating faster, de-risking product decisions, and saving time and money. However, the value of research is hard to quantify compared to other product metrics like lines of code or features shipped.

3. Measuring and advocating for UX research
   • When teams are measuring UXR today there is a strong bias for customer feedback, but little ability or understanding about how to measure impact on business metrics like revenue. 
   • The most commonly used metrics for measuring UXR are quantitative and qualitative feedback from customers as opposed to internal metrics like stakeholder involvement or tieing UXR to business performance metrics (including financial performance). 
   • Attendees felt that in organizations where research is more embedded, researchers spend significant time advocating for research and proving its value to stakeholders rather than just conducting studies. This included tactics like research repositories and pointing to past study impacts as well as ongoing battles to shape decision making processes. 
   • One of our attendees highlighted that engaging stakeholders in the process of defining key research metrics prior to running research was a key for them in proving value internally. 

4. Relating user research to financial impact
   • Alex and Ella asked the audience if anyone had examples of demonstrating financial impact of research to justify investment in the team and we got some excellent examples from the audience proving that there are tangible ways to tie research outcomes to core business metrics including:
   • Calculating time savings for employees from internal tools as a financial impact metric. 
   • Measuring a reduction in calls to service desks as a way to quantify financial savings from research.

5. Most attendees recognise the value in embedding UXR more deeply in all levels of their organization - but feel like they’re not succeeding at this today. 
   • Most attendees feel that UXR is not fully embedded in their orgnaization or culture, but that if it was - they would be more successful in proving its overall value.
   • Stakeholder buy-in and engagement with UXR, particularly from senior leadership varied enormously across organizations, and wasn’t regularly measured as an indicator of UXR value 
   • In organizations where research was more successfully embedded, researchers had to spend significant time and effort building relationships with internal stakeholders before and after running studies. This took time and effort away from actual research, but ended up making the research more valuable to the business in the long run. 

‍

With the large range of UX maturity and the democratization of research across teams, we know there’s a lot of opportunity for our customers to improve their ability to tie their user research to tangible business outcomes and embed UX more deeply in all levels of their organizations. To help fill this gap, Optimal Workshop is currently running a large research project on Measuring the Value of UX which will be released in a few weeks.
‍

Keep up to date with the latest news and events by following us on LinkedIn.

“If storymapping could unearth patterns and bring together a cohesive story that engages audiences in the world of entertainment and film, why couldn’t we use a similar approach to engage our audiences?’Donna Lichaw and Lis Hubert

‍

User Experience work makes the most sense to me in the context of storytelling. So when I saw Donna Lichaw and Lis Hubert’s presentation on storymapping at edUi recently, it resonated. A user’s path through a website can be likened to the traditional storytelling structure of crisis or conflict, exposition — and even a climax or two.

‍

The narrative arc and the user experience

‍

So just how can the same structure that suits fairytales help us to design a compelling experience for our customers? Well, storyboarding is an obvious example of how UX design and storytelling mesh. A traditional storyboard for a movie or TV episode lays out sequential images to help visualize what the final production will show. Similarly, we map out users' needs and journeys via wireframes, sketches, and journey maps, all the while picturing how people will actually interact with the product.

‍

But the connection between storytelling and the user experience design process goes even deeper than that. Every time a user interacts with our website or product, we get to tell them a story. And a traditional literary storytelling structure maps fairly well to just how users interact with the digital stories we’re telling.Hence Donna and Lis’ conception of storymapping as ‘a diagram that maps out a story using a traditional narrative structure called a narrative arc.’ They concede that while ‘using stories in UX design...is nothing new’, a ‘narrative-arc diagram could also help us to rapidly assess content strengths, weaknesses, and opportunities.’

‍

Storytelling was a common theme at edUI

‍

The edUi conference in Richmond, Virginia brought together an assembly of people who produce websites or web content for large institutions. I met people from libraries, universities, museums, various levels of government, and many other places. The theme of storytelling was present throughout, both explicitly and implicitly.Keynote speaker Matt Novak from Paleofuture talked about how futurists of the past tried to predict the future, and what we can learn from the stories they told. Matthew Edgar discussed what stories our failed content tell — what story does a 404 page tell? Or a page telling users they have zero search results? Two great presentations that got me thinking about storytelling in a different way.

‍

Ultimately, it all clicked for me when I attended Donna and Lis’ presentation ‘Storymapping: A Macguyver Approach to Content Strategy’ (and yes, it was as compelling as the title suggests). They presented a case study of how they applied a traditional narrative structure to a website redesign process. The basic story structure we all learned in school usually includes a pretty standard list of elements. Donna and Lis had tweaked the definitions a bit, and applied them to the process of how users interact with web content.

‍

Points on the Narrative Arc (from their presentation)

‍

‍

Exposition — provides crucial background information and often ends with ‘inciting incident’ kicking off the rest of the story

‍

Donna and Lis pointed out that in the context of doing content strategy work, the inciting incident could be the problem that kicks off a development process. I think it can also be the need that brings users to a website to begin with.

‍

Rising Action — Building toward the climax, users explore a website using different approaches

‍

Here I think the analogy is a little looser. While a story can sometimes be well-served by a long and winding rising action, it’s best to keep this part of the process a bit more straightforward in web work. If there’s too much opportunity for wandering, users may get lost or never come back.

‍

Crisis / Climax — The turning point in a story, and then when the conflict comes to a peak

‍

The crisis is what leads users to your site in the first place — a problem to solve, an answer to find, a purchase to make. And to me the climax sounds like the aha! moment that we all aspire to provide, when the user answers their question, makes a purchase, or otherwise feels satisfied from using the site. If a user never gets to this point, their story just peters out unresolved. They’re forced to either begin the entire process again on your site (now feeling frustrated, no doubt), or turn to a competitor.

‍

Falling Action — The story or user interaction starts to wind down and loose ends are tied up

‍

A confirmation of purchase is sent, or maybe the user signs up for a newsletter.

‍

Denouement / Resolution — The end of the story, the main conflict is resolved

‍

The user goes away with a hopefully positive experience, having been able to meet their information or product needs. If we’re lucky, they spread the word to others!Check out Part 2 of Donna and Lis' three-part article on storymapping.  I definitely recommend exploring their ideas in more depth, and having a go at mapping your own UX projects to the above structure.

‍

A word about crises. The idea of a ‘crisis’ is at the heart of the narrative arc. As we know from watching films and reading novels, the main character always has a problem to overcome. So crisis and conflict show up a few times through this process.While the word ‘crisis’ carries some negative connotations (and that clearly applies to visiting a terribly designed site!), I think it can be viewed more generally when we apply the term to user experience. Did your user have a crisis that brought them to your site? What are they trying to resolve by visiting it? Their central purpose can be the crisis that gives rise to all the other parts of their story.

‍

Why storymapping to a narrative arc is good for your design

‍

Mapping a user interaction along the narrative arc makes it easy to spot potential points of frustration, and also serves to keep the inciting incident or fundamental user need in the forefront of our thinking. Those points of frustration and interaction are natural fits for testing and further development.

‍

For example, if your site has a low conversion rate, that translates to users never hitting the climactic point of their story. It might be helpful to look at their interactions from the earlier phases of their story before they get to the climax. Maybe your site doesn’t clearly establish its reason for existing (exposition), or it might be too hard for users to search and explore your content (rising action).Guiding the user through each phase of the structure described above makes it more difficult to skip an important part of how our content is found and used.

‍

We can ask questions like:

• How does each user task fit into a narrative structure?
• Are we dumping them into the climax without any context?
• Does the site lack a resolution or falling action?
• How would it feel to be a user in those situations?

‍

These questions bring up great objectives for qualitative testing — sitting down with a user and asking them to show us their story.

‍

What to do before mapping to narrative arc

‍

Many sessions at edUi also touched on analytics or user testing. In crafting a new story, we can’t ignore what’s already in place — especially if some of it is appreciated by users. So before we can start storymapping the user journey, we need to analyze our site analytics, and run quantitative and qualitative user tests. This user research will give us insights into what story we’re already telling (whether it’s on purpose or not).

‍

What’s working about the narrative, and what isn’t? Even if a project is starting from scratch on a new site, your potential visitors will bring stories of their own. It might be useful to check stats to see if users leave early on in the process, during the exposition phase. A high bounce rate might mean a page doesn't supply that expositional content in a way that's clear and engaging to encourage further interaction.Looking at analytics and user testing data can be like a movie's trial advance screening — you can establish how the audience/users actually want to experience the site's content.

‍

How mapping to the narrative arc is playing out in my UX practice

‍

Since I returned from edUi, I've been thinking about the narrative structure constantly. I find it helps me frame user interactions in a new way, and I've already spotted gaps in storytelling that can be easily filled in. My attention instantly went to the many forms on our site. What’s the Rising Action like at that point? Streamlining our forms and using friendly language can help keep the user’s story focused and moving forward toward clicking that submit button as a climax.

‍

I’m also trying to remember that every user is the protagonist of their own story, and that what works for one narrative might not work for another. I’d like to experiment with ways to provide different kinds of exposition to different users. I think it’s possible to balance telling multiple stories on one site, but maybe it’s not the best idea to mix exposition for multiple stories on the same page.And I also wonder if we could provide cues to a user that direct them to exposition for their own inciting incident...a topic for another article perhaps.What stories are you telling your users? Do they follow a clear arc, or are there rough transitions? These are great questions to ask yourself as you design experiences and analyze existing ones. The edUi conference was a great opportunity to investigate these ideas, and I can’t wait to return next year.