paul.hanaoka.co

Driving revenue by improving quality across an enterprise platform.

comparison of the old and new nav interfaces
Before
After
Comparing the old and new header components in sitebuilder — helping users focus on their tasks by making the UI more efficient

Problem

Revenue had lagged for consecutive quarters following a major release, new customer growth was notably stagnant.

The biggest problem was the lack of a cohesive vision for how to solve the myriad of UX issues across the platform.

Role

As Product Design lead, I collaborated with the Technical lead and PM to develop a strategy, ideating in tight feedback loops through execution. I consulted with Product Designers while building requirements and coached them through applying improvements in their specific platform areas.

Contributions

  • Workshop facilitation
  • UX and UI Design
  • Prototyping and Usability Testing
  • Quality Assurance

Solution

Given that this was the first initiative of its kind, we imposed strict constraints — briefly, the improvements were focused in:

  1. The header toolbar component — I contributed by designing the overall structure, documentation, and supporting designers implementing in their specific platform areas
  2. The page wrapper — my contributions were designing a rough idea and ideating with engineers in code to arrive at a cost-effective solution
  3. An on-page nav component — an outcome of early header toolbar explorations, this was a new component that I contributed an initial design for and then worked with the Design Systems team to implement

Impact

Reduced Support Costs10

YoY reduction in support tickets for quarter following release

Perceived Value30

Employing Design strategically to provide value

Revenue Growth54

Exceeded revenue goals for new business
comparison of the old and new nav interfaces
Before
After
Comparing the old page layout and header components in a dense UI — increasing the density helped users achieve tasks faster and more efficiently
comparison of the old and new nav interfaces
The new onpage nav component eliminated the unfortunately common pattern of stacked tabs — a critical dependency for improving the header toolbar

Process

My high-level approach:

  1. Go wide: audit the entire platform to identify opportunities
  2. Make sense of the mess: group issues by component
  3. Prioritize ruthlessly: index high on technical complexity and impact on support

Setting a clear vision is the first step to any successful project — I drafted a pitch deck to the rest of the platform teams as a way to inspire them to contribute to the larger goal of improving UX at the platform level.

A graphic showing two diagrams of the mental model for navigation
A graphic showing two diagrams of the mental model for navigation

After hosting an initial async brainstorm with designers to capture the problem screens in their areas, I then categorized and documented the issues at the component level.

Outcomes & Learnings

By all accounts the project was a great success — in addition to increased usability scores (an important component of the perceived value) revenue and new business goals were exceeded in the quarters following this release.

A major contributor to success was the team’s ability to focus and prioritize.

Because we had a clear goal and clear budget constraints we could quickly determine what was feasible and viable, maximizing value produced.

Design was critical to providing a clear vision for what was possible and helping make that a reality.

Next Project
Driving revenue by improving quality across an enterprise platform How focusing on design quality can impact a business
Enterprise
Platform

Driving revenue by improving quality across an enterprise platformHow focusing on design quality can impact a business