Unified Leader Dashboard
Overview
I led the redesign of the Leader Dashboard, a core feature for Learning and Development leaders to manage team activity and drive greater value from the platform, including two products, Skills and Flow
Design Lead
My Role
8 months
Timeline
Me + PM + Eng
Starting Team
The Customer Problem
To understand the root causes, I first facilitated interviews with customer-facing teams to identify recurring pain points. I’ve found them to be excellent proxies for customers. Next we spoke directly with customers using both our Skills and Flow products. Their feedback revealed key frustrations:
“I spend a lot of time digging through the various reports, looking for my top performers and people who aren’t using their license.”
“Sometimes I’ll be in a 1:1 and they’ll tell me that they completed the course I shared with them. I had no idea. It catches me off-guard.”
“Is our team’s dedicated learning time translating to fewer missed deadlines or higher-quality code? It’s a black box to us today.”
After a handful of interviews we began to see a key question emerge.
How might we help leaders quickly identify who on their team need attention, while also fostering healthy learning habits?
The Business Problem
We learned that customers who used both Skills and Flow had a lower renewal rate than those using just Skills. The lack of integration between the two products created a disconnect and impacted retention. However, the small number of cross-product users presented an opportunity. If we could create a unified experience, we could improve retention, drive cross-selling, and increase ARR.
Bump in the Road
We initially explored unifying Skills and Flow, but as we dug deeper with the engineering team, it became clear that the technical complexity was too high for the time and resources available. After discussing with leadership, we pivoted to focus on redesigning the Skills Dashboard while leaving Flow as-is for now. This pivot allowed us to focus on delivering immediate value.
Pivot!
Despite the setback, we refocused on the Skills Dashboard and dug deeper into customer needs. I conducted another round of user interviews and created a survey to prioritize dashboard features based on user feedback. The results directly influenced the layout and prioritization of cards in my prototype, ensuring that the final design would be user-centered and drive engagement.
Monthly team digest
MAY 2023
Check out your dashboard
Hi Amy,
Here’s your Pluralsight team’s insights for October.
Some people could use a nudge
4% of team members haven’t signed into Pluralsight in the last 30 days
Proficiency is going up
Your users’ proficiency increased in the Cloud Fundamentals skill
Goals are being reached
52 users have consumed content and been assessed in React
43h 32m
That’s 13% more than last month
October usage
I just wanted to send a quick thank you for completing the “Move to the cloud” channel. Your hard work doesn’t go unnoticed!
Allison Valderrama
Team Manager
Continue learning
Copyright Pluralsight LLC.
All logos and trademarks are the properties of their respective owners.
182 N Union Ave Suite 200 Farmington, UT
Manage your preferences | Privacy Policy
Kudos to you, Jamal!
Allison wrote you a note related to your Pluralsight activity
Usability Testing
To validate the design, I ran two rounds of remote usability testing using Maze. In the first round, two tasks didn’t meet our 71% success benchmark, so I iterated and retested. The second round showed all tasks meeting the success criteria, giving us high confidence that the final design would address customer problems and deliver a usable experience.
Final Thoughts
The longer I work in design, the more I realize that success isn’t just about what happens in Figma. It’s about relationships—with customers, the team, and stakeholders. It’s about clear communication, flexibility, and iteration.
While I led the design, the final solution was shaped by collaboration with the development team, other designers, and most importantly, our customers. This process ensured that the final product not only solved the problems we set out to address but also delivered value where it mattered most.