Increasing engagement rate on enterprise dashboard with UI update
Macabacus is a brand compliance and content sharing tool for finance teams. The goal of this project was to restructure and simplify Macabacus Admin dashboard, which led to boosting pages visits by 18% and features usage by 5%.
August — October 2024
/ user problem
File organization on the Admin dashboard was unintuitive and had high abandon rate
/ my role
Identified areas with low engagement and high abandon rate
Created intuitive and clean designs that meet business goals
Ensured feasibility of design solutions by collaborating with engineers and PM
/ chapter 1
organizing groups
"Groups are crucial for large enterprise customers and anybody with SSO"
— Team Lead, Customer Support @ Macabacus
The question I brought to the team is how can we best display groups and nested content inside them?
step 1: analyze problem and look for references
I analyzed similar sections across other tools and noting ideas that can be incorporated into our UI.
step 2: branstorming on solution
When looking for a solution I prefer using pen and paper as it helps me not to think about colors, sizes, fonts, etc. and focus on the ideation process.
step 3: High-fidelity design
Clean and attractive UI make it easier for customers to navigate across complex context.
/ chapter 2
tagging content
Only 5% of noticed Tags page button and clicked it*
After clicking it, users ended up on unintuitively structured page.
*according to heatmaps tracked via Hotjar
/ how might we…
… improve Tags page UI without recreating a wheel?
To answer this question I looked across our dashboard and asked myself: are there any design solutions that we currently have and can replicate for tags UI?
I made an assumption: because tags are made for content, I can we replicate content groups UI for tags.
tags page High-fidelity design
Improved tags UI increased page engagement by 18%
before
Tags section with unintuitive structure: missing assigned content and instead suggested to create tag without a reason.
after
Familiar navigation, visibility on content assigned to a tag
/ chapter 3
improving filters
/ how might we…
… help user filter out content with missing data?
initial ui had two problems
To change a state a user had to type manually ‘Yes’ or ‘No’
Once 'Yes’ or 'No’ is set a user can't change a state back to blank (N/A)
1st exploraiton
Long toggle switch with intermediate state for content without data.
2nd exploraiton
Each state represented by an icon for better accessibility.
3rd exploraiton
Each state written as text. Takes more space, but eliminates user confusion.
final design
5% more customer started using boolean filter after I improved its design.
before
Several clicks needed to filter the content
after
Content can be filtered with one click
/ outcomes
18% more users started visiting Tags page.
5% more users started using filters when searching across the documents.