Bizwise Website Editor.

UX designer
@ Bizwise

Overview

At this startup tailored to small-business owners, I worked on improving the products section of the website editor. To quantify the user experience, I conducted Maze tests, explored problems with user interviews, and iterated through design explorations, lastly proving that the improvements are statistically significant.

Team

Myself

Duration

6 weeks
Aug - Sep 2021

Tools

Maze
Figma
Google Trends

Summary.

The problem

Bizwise is a startup that offers a suite of digital services for small-business owners. Their customers can use the website editor to create websites and promote their online presence. However, Bizwise received many internal and external complaints about showcasing products on the website.

The solution

From user research, I found that there were confusing user flows, inconsistent component usage, unclear "tech speak", and more. Through sketches and explorations, I iterated on user flows, design components, and screens. Finally, I proved that the improvements are statistically significant using the measured UX metrics. Some of the solutions are highlighted below.

My role: UX researcher & designer

Research: created research questions, conducted usability testing with small business owners, benchmarked UX metrics through Maze (task completion rate, task completion time, misclicks, and user satisfaction), analyzed whether improvements were statistically significant.

Design: designed content using Google trends and interviews, revised existing user flows, created/edited components and style guide, sketched and explored various design solutions, prototyped the new design, presented findings and designs.

Researching the problem.

Bizwise is a startup that offers a suite of digital services for small business owners. Their customers can use the website editor to create websites and promote their online presence.

Defining "improve"

In order to improve something, I first need to benchmark the current system and understand it.

The research goal:

What are the pain points when people try to showcase their products using the web editor?

The Maze test*

To answer the research question and make improvements, quantifying the user experience is what came to my mind.

It can measure and benchmark the current UX metrics while helping me pinpoint where people are struggling.  

With Maze's usability testing tool, I obtained a wealth of insights from 25 tests.

What's wrong?

These main problems were found by examining the affinity diagram, UX metrics, and heat maps.

1. Inconsistent and redundant functions of the save button

The save button is sometimes used as a next button while other times, it functions as a back button (a back button already exists). This contributes to a high misclick rate of 100% for related tasks!

2. Too much "Tech Speak"

Words such as "product variants", "media", and "primary button" are confusing, contributing to a high misclick rate of 52% for these tasks.

3. How to add product options?

To add product options such as size or color in a matrix format, only 67% completed the task with a long completion time of 133 seconds.

4. Forgetting to update pre-populated content

People forget to delete/change the pre-populated images, product options, and product specifications, contributing to a low completion rate of 55% for these tasks.

*The limitations of Maze tests:
I don't have control over who is recruited through Maze. They are not necessarily small business owners. However, there are many similarities between the Maze usability testing and interviews with business owners, indicating that many issues are universal.

Setting the goal.

Through qualitative and quantitative research, it’s observed that the products section of the web editor has poor usability and very poor learnability.

How might we redesign the products section editor so that first-time users can easily and quickly build the section without getting lost

Success metrics

Together with the CEO and technical manager, we prioritized the problem for first-time users due to the upcoming marketing endeavors and numerous new customers.

Each keyword in the how-might-we statement is tied to a specific UX success metric.

Increasing these metrics will achieve the goal of improving the website editor.

Easily

Measured with a high task completion rate.

Quickly

Measured with a short task completion time.

Without getting lost

Measured with a low number of misclicks.

Exploring designs.

From here, a series of ideation, design exploration, and usability testing helped inform the possible designs to achieve the how-might-we.

Ideation through sketches

To address the major problems, these sketches explored various ways to redesign the left bar.

Using the existing style guide, I quickly converted promising ideas to hi-fi prototypes for Maze testing.

2. Eliminating "tech speak"

Many people were confused by "product variants". I brainstormed a few alternatives, such as product options and product variations. Using Google Trends as a guide, "product options" was found as the most used keyword.

Using the same method, I replaced these keywords:
• Product Media > Picture
• Primary button > White Button
• Call to Action> Button

Testing and iterating.

To test the design explorations, I conducted 20 Maze tests on 2 versions and supplemented the findings with 3 usability testing interviews.

Significance testing

I tested for statistically significant differences between version 1, version 2, and the original.

With different users for each test, the Two-sample T Test was used for SUS scores and task time while the McNemar Exact Test was used for completion rate.

More iterations!

With the usability testing interviews, additional issues were discovered and addressed.

This includes adding a scroll down button and darkened shadow for content discovery, moving and enlarging the image search bar, replacing the drag icon, and many more!

Showcasing the final design.

Based on the findings from usability testing and interviews, I revised sections from the user flow level to the component level. The demos below highlight some of the major redesigns.

Simplifying product options

People can now associate price, specifications, and SKU with each product option.

This new design makes adding options simple: no more matrix addition and just one by one edits.

Clarifying image search

In addition to uploading pictures, people can now quickly find and select online stock photos to use.

Design sprints

As a team, we underwent a vigorous cycle of analyzing insights from the previous week, exploring different designs, writing simple and clear content, iterating on the prototype, and conducting cognitive walkthroughs.

Some of the iterations are highlighted below.

Evaluating the outcome.

With the final design, UX metrics were measured through 30 Maze tests. Using statistical significance testing, the task completion rate was increased while misclicks and completion time were decreased!

Although people perform objectively better, their perception of the editor only increased slightly.

This phenomenon could be due to:
• designing on a micro-scale (section specific) instead of the macro-scale (site wide)
• I discovered additional site-wide navigation and content issues, which led to the next steps

Reviewing the success metrics

With the measured UX metrics, I can confidently say that the new design is significantly better than the original!

✓ Easily

All tasks had a higher task completion rate.

✓ Quickly

All tasks had a much shorter task completion time of half

✓ Without getting lost

All tasks had a much lower number of misclicks by at least half.

What's next.

1. Prepare documentation for development

With a final presentation to the CEO and technical manager, this project is finished! Next, I will be creating clear and concise documentation for changes, components, and style guide updates with a hand-off meeting.

2. Redesign navigation

I noticed that people had trouble navigating back to home or back to previous pages during usability testing. From the Maze tests, people also complained about too many clicks and layers. After communicating this issue with the CEO, I will be spearheading the next project of navigation revamp!

3. Rewrite content

While the products section of the website editor has clearer writing, the other sections are still filled with "tech speak". As such, I will be exploring and testing alternative words to use.

Learning-take aways.

1. Pairing quantitative analysis with qualitative interviews

Having never conducted such in-depth quantitative analysis before, I experienced first-hand what was taught in class: quantitative research can lack behavioral insights and the "WHY". As such, I paired the Maze tests with interviews to obtain the missing puzzles, helping me arrive at a great design.

Learning take-aways

1. How to conduct pair writing

The toolkit is content-heavy and touches many sensitive legal topics. Through pair writing hosted by the content designer, I observed first-hand how to write simple language without losing the legal meaning as a team.

2. Working without guidance

While working at this startup, I was one of the most senior designers there. As such, this project was primarily solo work with weekly presentations to the CEO and technical manager. During this project, I scoped and planned all the steps/resources needed. With almost no design guidance, this project helped me become more independent and resourceful!

Up next: