image

Energyline Usability Test

Turning usability research into better product decisions

Tags:

Product Designer

UI

Design Systems

Project

Testing and refining Energyline's benchmarking experience through user research, usability analysis, and collaborative design.

  • Role: Product Designer
  • Product: EnergylineTRM (MVP)
  • Timeline: February 2025
  • Focus: Usability testing, UX research, data synthesis, interaction design, prototyping
  • Participants: 6 existing MVP users

The challenge

Validate before building

Energyline needed a better way for users to explore algorithms and compare benchmark measures.

I created an initial wireframe exploring a multi-column comparison layout. Before moving into high-fidelity design, we needed to validate whether the proposed experience supported users' actual workflows.

Scroll to view all

Preparing the research

Define what to test

We recruited 6 existing MVP users and prepared a structured testing script covering two activities.

Scroll to view all

Running the tests

Observe behavior, not just opinions

During each session, we tracked task completion time, user interactions, difficulties, and relevant feedback.

Combining observations with SUS responses helped us understand both how users experienced the interface and where they encountered friction.

Measuring usability

Compare the results

I consolidated individual SUS responses into a spreadsheet to compare usability across both activities.

The average scores provided a quantitative baseline, while differences between participants highlighted the need to investigate specific usability issues.

Explore TRM
Benchmark Measure

Finding underlying problems

From observations to patterns

I organized user actions, feedback, and observations into a Rainbow Spreadsheet to identify recurring patterns.

Three main problem areas emerged.

1. Algorithm discoverability

Users struggled to locate algorithms, searching in unrelated areas such as the glossary and Measures table. Some also relied on formulas from savings calculations.

2. Information density and interaction

Algorithms occupied too much screen space. Users preferred previews with the option to expand, alongside more flexibility to copy, edit, or open algorithms separately.

3. Algorithms occupied too much screen space

Users preferred previews with the option to expand, alongside more flexibility to copy, edit, or open algorithms separately.

Hypotheses and learnings

Turn evidence into opportunities

By comparing our initial assumptions with actual user behavior, we identified several opportunities for improvement.

Hypothesis 1 — Improve algorithm discoverability

Users may struggle to find algorithms because information is spread across different areas of the product.

Learning: Users searched for algorithms in the glossary and Measures table, indicating a need for clearer navigation and more structured discovery.

Opportunity: Improve algorithm access and make relevant information easier to find.

Hypothesis 2 — Simplify algorithm comparison

Displaying complete algorithms may make Benchmark Measure difficult to use.

Learning: Users preferred a preview-first approach, with expandable content. They also requested options to copy formulas, edit algorithms, and open them separately.

Opportunity: Reduce visual density and give users more control over how they inspect and interact with algorithms.

Hypothesis 3 — Clarify measure configuration

Users may struggle to identify where to change the STD Measure and understand the relationship between measures and variables.

Learning: Multiple participants searched for this functionality in different areas, while some needed additional guidance to understand the interface.

Opportunity: Make measure configuration more intuitive and provide clearer guidance throughout the workflow.

Additional opportunities: Explore an introductory overlay and a secondary benchmarking flow connected to savings calculations.

Aligning stakeholders

Turn findings into direction

I consolidated the findings, hypotheses, and design opportunities into a research summary for stakeholders.

This created a shared understanding of the usability issues and helped guide several rounds of collaborative brainstorming.

Rather than jumping directly into solutions, we used the research as a foundation to discuss priorities and explore possible directions.

From insights to design

Bringing feedback together

Through several brainstorming rounds, we translated the research findings and stakeholder discussions into a high-fidelity prototype.

The final direction brought the feedback together, moving beyond the initial wireframe toward a more considered benchmarking experience.

Scroll to view all

Outcome

Making research part of the design process

The research established an evidence-based direction for improving Energyline's benchmarking experience.

Research at a glance:

6 users

recruited from the MVP

2 activities

evaluated per participant

12 activity

sessions completed

10 SUS questions

after each activity

80.4 and 79.2

average SUS scores

3 key usability

themes identified

My takeaway: Better design decisions start with understanding how people actually use a product.