Encompass Reporting

Role

Lead Designer

Company

Encompass Technologies

Timeline

2 months - In beta

Overview

Following customer attrition referencing an "outdated reporting experience," Encompass asked me to modernize our collection of reporting tools and "make them easier to use." I owned the design strategy for the project, starting by getting time with users and leading the team in problem definition exercises.

I played a critical role in prototyping a transformative layout that guided users to the numbers they needed. The design system I had been implementing played a key role in uplifting the outdated look of these tools.

Both our target user base and other user segments had high praise for the beta release of Encompass Reporting Beta. It quickly became the most used beta experience in Encompass products.

Overview

Following customer attrition referencing an "outdated reporting experience," Encompass asked me to modernize our collection of reporting tools and "make them easier to use." I owned the design strategy for the project, starting by getting time with users and leading the team in problem definition exercises.

I played a critical role in prototyping a transformative layout that guided users to the numbers they needed. The design system I had been implementing played a key role in uplifting the outdated look of these tools.

Both our target user base and other user segments had high praise for the beta release of Encompass Reporting Beta. It quickly became the most used beta experience in Encompass products.

Overview

Following customer attrition referencing an "outdated reporting experience," Encompass asked me to modernize our collection of reporting tools and "make them easier to use." I owned the design strategy for the project, starting by getting time with users and leading the team in problem definition exercises.

I played a critical role in prototyping a transformative layout that guided users to the numbers they needed. The design system I had been implementing played a key role in uplifting the outdated look of these tools.

Both our target user base and other user segments had high praise for the beta release of Encompass Reporting Beta. It quickly became the most used beta experience in Encompass products.

Problem definition

Our stakeholders came to me with some key questions regarding the current Encompass reporting experience

Problem definition

Our stakeholders came to me with some key questions regarding the current Encompass reporting experience

Problem definition

Our stakeholders came to me with some key questions regarding the current Encompass reporting experience

Could we significantly cut down on support efforts if analysts were no longer building custom reports for mid-level managers?

What if the reporting platform was modernized and competitive with other tools that our distributors use everyday?

However…

No one had a clear idea of what "modernizing reporting" meant, or what it would take to get our users to build their own reports.

Feedback

I ran a series of customer interviews to understand what kinds of reports they were building, and what pain points they were experiencing while trying to analyze data.

Feedback

I ran a series of customer interviews to understand what kinds of reports they were building, and what pain points they were experiencing while trying to analyze data.

Feedback

I ran a series of customer interviews to understand what kinds of reports they were building, and what pain points they were experiencing while trying to analyze data.

"When am I supposed to create a comparison report instead of a fusion report?"

Our current tools were not giving users a good entry point—a common sentiment.

"I shouldn't have to pay for a training to do this."

Users were upset about being asked to pay for and complete a SQL training to go beyond our basic reports.

"40% of my time is spent building reports for customers."

Our support analysts had good numbers showing how much time they spent doing what should have been basic reports for our users.

Design principles

After synthesizing user feedback and working with stakeholders to understand their goals for the platform, I came up with these core principles that would inform my solutions.

Design principles

After synthesizing user feedback and working with stakeholders to understand their goals for the platform, I came up with these core principles that would inform my solutions.

Design principles

After synthesizing user feedback and working with stakeholders to understand their goals for the platform, I came up with these core principles that would inform my solutions.

Relevant

Users should be able to easily find the common groupings and values they work with every day.

Obvious

It should be obvious and simple for users to make common adjustments to reports. Training shouldn't be required to give users access to powerful data.

Powerful

Power users are the backbone of Encompass reporting as it is today. They should not lose access to powerful, advanced functions as the interface is simplified.

The old approach

I used these principles to audit the current reporting experience and found a few key issues were hindering usability:

The old approach

I used these principles to audit the current reporting experience and found a few key issues were hindering usability:

The old approach

I used these principles to audit the current reporting experience and found a few key issues were hindering usability:

The report header was convoluted due to an incorrect representation of information hierarchy. Page navigation was placed inline with report controls.

The "quick edit" panel was pushed to the right side of the screen, making it difficult to find at a glance.

To add a new "group by," users would drag items from "Additional Group Bys" up to "Parent," "Child," or "Detail." This common action often required required detailed user training.

The new approach

I redesigned the entire platform to address the two major concerns, keeping design principles in mind.

The new approach

I redesigned the entire platform to address the two major concerns, keeping design principles in mind.

The new approach

I redesigned the entire platform to address the two major concerns, keeping design principles in mind.

A reimagined edit panel

Our users already knew what groupings/metrics they were looking for, and were wasting time browsing through an exhaustive list. I designed a custom autocomplete that allows users to directly search for groupings and metrics. No more inconveinent drag and drop!

Easy-to-read timeframe comparisons

One of the most common things our users tried to see in reports were year-over-year comparisons. I designed a new report table making these comparisons easier to read.

A better starting place

The new edit panel made it easier to fit more controls inside of a single report. Our starting reports were simplified, so users didn't have to scan a large list to get started.