I help teams make design work.

We're getting closer to launching Helio Glare, our open data-informed design framework. A key focus is connecting design metrics to business results.

In it, we show you how to use a design metrics tree built with UX metrics.

This structures how UX metrics influence broader product and business outcomes. Here’s how it connects:

UX metrics as the foundation

↳ UX metrics like desirability, comprehension, usefulness, sentiment, usability, and success act as the leaves of the metrics tree. These represent the measurable aspects of user experience that indicate how well a design performs in terms of user perception, interaction, and effectiveness.

Design initiatives as the branches

↳ Concept areas bridge UX metrics and product performance. These represent specific design initiatives: changes, optimizations, or experiments in design that are directly influenced by UX metric insights.

Example: If usability scores are low, a design initiative might focus on streamlining navigation or reducing cognitive load.

We've been discussing what makes a KPI in our company. A Key Performance Indicator measures how well a person, team, or organization meets goals. It tracks performance so we can make smart decisions.

But what’s a Design KPI?

Let’s take an example of a design problem. Consider an initiative to launch a new user dashboard to improve user experience, increase product engagement, and drive business growth.

Here might be a few Design KPIs with ways to test them:

→  Achieve an average usability of 80% within the first three months post-launch. Measurement: Conduct user surveys and collect feedback through the dashboard's feedback feature using the User Satisfaction Score.

→  Ensure 90% of users can complete key tasks (e.g., accessing reports, customizing the dashboard) without assistance. Measurement: Conduct usability testing sessions before and after the launch, analyzing task completion rates.

→  Reduce the average time to complete key

Involving your audience in the design process gives you real-time feedback on key aspects of their experience. Tools like Helio can help you capture valuable insights that improve your business KPIs, guided by user experience metrics.

Using usability tests and surveys lets you quickly gather qualitative and quantitative user feedback. Behavioral data collected early in the design process helps you understand a design's success. Emotional indicators are usually trailing, as confusion or lack of clarity can lead to drops in sentiment and feelings.

Here’s the user feedback you can collect to help refine your design decisions with stakeholders:

Usability → Makes sure users can easily and quickly use the product to do what they want.

Comprehension → Ensures users understand the product, how it works, and what it can do for them.

Engagement → Tracks how often and how long users interact with the product, showing their interest and involvement.

Desirability → Checks

But without it, your team is losing:

→ Understanding of user needs

→ Empathy with users

→ Validation of assumptions

→ Informed decision-making

→ Identification of usability issues

→ Market fit and product relevance

→ Prioritization of features

→ Innovation opportunities

→ Risk reduction

→ Long-term customer satisfaction

User research is magical when teams are in a flow. It can provide valuable insights into user needs, behaviors, and problems.

Teams often misunderstand this: user research does not directly dictate specific design solutions. Teams must still make decisions, and designers must consider various signals to choose a direction.

User research is not just about highlighting opportunities, constraints, and user preferences. It's a catalyst for creative solutions, often sparking design intuition, expertise, and iterative testing. This process of innovation is what makes the design process exciting and dynamic.

Designers can use user research to understand the context of user interactions and experiences, translating these findings into a product or solution with creativity

We shared Dr Chloe Sharp’s ideas on fast and slow research several weeks ago. It’s a great way to think about how you conduct your research. Check out the post: https://lnkd.in/g4FcnNa9

Here’s how she breaks down slow and fast research:

→ Slow Research

This approach focuses on deeply understanding customers' and users' needs. It's centered around identifying problems using early-stage, hypothetical concepts to achieve a problem-solution fit and make informed strategic decisions.

The process incorporates qualitative research, such as interviews, and quantitative methods, like surveys. It also involves a lengthy feedback loop, where data is collected and analyzed to refine problems and develop solutions continuously.

→ Fast Research

This approach begins by developing prototypes or an MVP, where ideas have evolved, and the focus is now refining the problem-solution Fit. Prototypes and MVPs prove how well a product meets market demands.

Feedback during this stage is