Case study product/opinionlab · OpinionLab · [TODO: years]

Enterprise SaaS dashboards

Empowering the voice of customers to improve the brands they care about. At OpinionLab I led all UI and UX initiatives to bring new features and functionality into a new reporting application.

Role
UI/UX Designer, lead for all UI and UX initiatives
Timeline
Nearly two years · [TODO: Mon YYYY – Mon YYYY]
Team
Product, the analytics department, and marketing
Stack
[TODO: tools — e.g. Sketch · InVision]
FIG 01 · Hero — the new-generation dashboard application: a trending dashboard with the live filter bar along the top
FIG 01 The new-generation reporting application.

O-Lab

Helping brands hear their customers

For nearly two years I was at OpinionLab, where we helped companies gather feedback from their customers. In addition to collecting their Net Promoter Score, we could aggregate data to help brands make more timely and impactful decisions based on real customer pain points. We offered different forms of analysis of all that data: reports, consulting services, and a self-service dashboard application that I was in charge of.

Comment card

Where every data point started

Our company started with a feedback tab and a comment card. Living on our clients' websites, we were there for customers to leave their sentiment, give feedback and submit an NPS.

Our comment cards captured user data based on the Net Promoter Score as well as our own custom Likert scale. We tested multiple variations of scale, type and taxonomy, but ultimately found a 5-point scale worked best for our needs.

The main goal for the comment cards was accessibility. Per our contract agreements, the cards had to comply with the full Web Content Accessibility Guidelines (WCAG).

FIG 02 · The feedback tab and comment card on a client site, with the NPS question and the 5-point Likert scale
FIG 02 The feedback tab and comment card: NPS plus our 5-point scale, fully WCAG compliant.

Data viz

A new application, one feature at a time

The new-generation application was still a brand new offering, slowly taking shape as we added more features. From a competitive standpoint we aimed to include the complexity of tools like Qualtrics and Looker, with the ease of use of Survey Monkey and Usabilla.

FIG 03 · The original product I began working on — the existing client web portal
FIG 03 The original product I began working on.
FIG 04 · My first release of the new platform, living inside the existing portal
FIG 04 My first release of the new platform.

We had a web portal where clients accessed all of their data. The "new gen" application would temporarily live inside that interface until it could stand on its own.

O-Trend report

The 20-page report that set the roadmap

O-Trend was a 20-page report used by 75% of our clients to digest their data, and a lot of the features we prioritized came from this one report. It focused on specified sections, or custom reports, that tracked month-over-month and year-over-year trends to make user behaviour and engagement easy to spot. Our first goal was to improve filtering, so users could replicate the original report's views themselves.

FIG 05 · A sample O-Trend report — a spread of pages showing the month-over-month and year-over-year trend sections
FIG 05 A sample O-Trend report: everything clients were used to, and the baseline for what the app had to offer.

I wanted an overview of everything O-Trend offered clients, to find ways to give them all the information they were used to while empowering them to do more.

Advanced filtering

Release the complexity gradually

Filtering was going to be a long, ongoing improvement. We planned to include all of our taxonomies, variables and custom IDs that clients could control. But we knew the upgrade would have to be released gradually, slowly increasing the complexity.

As with a lot of the projects I worked on, I started by learning from subject matter experts and looking at the data on current usage. Through surveys and internal critiques I gathered feedback on my decisions by showing work in progress.

FIG 06 · The three base filtering templates side by side — basic, all options exposed, and categorized
FIG 06 Three base templates for filtering. Usage data and internal interviews set the list order, grouping and industry standards used in the final design.

Mapping complexity

Design the most complex state, then work backwards

The hardest part of managing all the changing components was having multiple versions of the product at once: the working web portal, a newer version we planned to release, and a future version for user testing. It was simpler to map out every component from its most complex state and work backwards, to make sure the patterns we were using would hold up.

Part of the challenge was our own Likert scale. There was a marketing need to prove its worth as a valuable and informative measure of how engaged our clients' users were with their brand.

FIG 07 · One component mapped from its most complex state back to its simplest, across the three product versions
FIG 07 One component, three product versions, mapped from most complex backwards.
FIG 08 · A series of Likert-scale visualization variations
FIG 08 Variations on the Likert scale, meeting marketing's requirements while managing the product team's growing complexity.

Trending dashboards

Four views, one live filter bar

I decided to create four different dashboard views that together could hold the majority of the information in our O-Trend reports. Combined with a new live filtering system along the top, we could give users quick access to the metrics and views they used most.

I built four prototypes and circulated them with my team and our analytics department to get feedback on the views, and on the functionality needed to make them most useful.

FIG 09 · Dashboard view one, with the live filter bar along the top
FIG 10 · Dashboard view two
FIG 11 · Dashboard view three
FIG 12 · Dashboard view four

Location dashboard

Stop catching up. Lead with something unique.

The truth was that our application was chasing a market with giants, and despite our efforts to come out with new features, we were really only catching up. Location services offered a trait that was unique in the market. Our new goal became releasing an industry-leading feature to bridge the gap between captured reviews and physical experiences.

Just a demo

To release the new functionality in such a short time, I had a short window to ideate different mapping techniques that would meet our needs and be simple enough to implement.

FIG 13 · The location dashboard demo — a map of a client's locations with captured feedback plotted against each one
FIG 13 The location dashboard demo: reviews plotted against the physical places they happened.

[TODO: Business impact — what the location demo led to, e.g. a client win, a release, or a roadmap decision.]