Big Question
How can we rethink our tools to help HR and L&D admins encourage professional and personal development in their employees?
Company
GoodHabitz
ROLE
Lead Product Designer, Segment Owner
TEAMMATES
Shady Mohammed, Emese Engedi, Mieke Hendriks, Mark Van Kessel
Project Context
GoodHabitz is 12 years old, and most of their client side tools reflected that age. Built without a design system (or single tech stack) and designed without a UX team, the tools were often buggy and inaccurate. Admin users were identified as a key driving factor in renewals and overall success of GoodHabitz at a company- engaged and happy admins had a direct correlation to higher engagement when it came to learning.
Existing Admin dashboard pages were often broken, with missing or irrelevant data getting top priority.
Defining Priorities
GoodHabitz was in the midst of a major transition- educational content that was unique and desired in the market, but a platform that was failing to meet user needs. The UX team was a new addition to the company, and as lead I took the opportunity to host the first cross-functional workshop. We brought representatives from UX, Engineering, Research/Data, Product, Sales, Customer Support, and Education Coaches for an intensive day session with three major goals:
Share the current pain-points and needs collected from UX research, support data, and customer-facing experts.
Define a vision for the future of the Admin experience and how they engage with the platform as well as coaches.
Start to build connections with stakeholders across the company to aid the rollout of new features and build trust with each other.
Bringing stakeholders together- for the first time
Engineering
Update the tech stack
Fix dependent bugs
Restructure back-end
Priorities by Team
Customer Teams
Fix data discrepancies
Lessen manual workload
Create more guidance within the product
UX & Research
Understand the data
Create teams and groups
Easier tools to use
Product & Executives
Create new features
Save $$ on additional tools
Add an SME segment
“This was eye-opening, I can’t believe we have never done this before and I hope this is just the first of many.”
— Coaching team participant
UX Auditing & Planning
Collecting specific feature-based feedback from employees, site data, and user interviews.
The output of this workshop, the UX audit, user interviews and separate journey-mapping project left us with a list of initiatives that could take years to build out. I worked with our Product and Engineering teams to map out the effort it would take to deliver some of these ideas and compared it with the impact it would have on our Admin users. This helped us identify two projects that could be delivered through a refactoring & ‘lift and shift’ re-design using a simple design system and one project, Onboarding, that could follow soon after.
But where to begin….
A refactor-friendly design system
The Admin part of the platform did not have a unified design system or language. So I started by setting some simple parameters including color tone, button styles, inputs, and the menu to better reflect the student experience while still feeling like a different tool, something we heard from users that was essential when moving around the platform. For the sake of speed, we also utilized the DaisyUI library as well as existing components from the student side of the platform that had been validated.
UX Goals
All components must meet AA accessibility standards
Refine the shown data to better match Admin language & need
Simplify number of steps and unique pages needed to complete a single task
Testing & future refinements
Every new feature and refactored page launched went through an extensive beta testing phase- first with internal users & customer support, and then with a pre-selected test audience representing users from several key markets and account types. Feedback from these tests were prioritized after the collection period and either incorporated before launch or placed on a future roadmap.
GoodHabitz Coach
“I really like the activity visit over time but I wonder if there is a better data point there- I would suggest completion instead of visits?”
Admin User, UK