MyZOLEO Dashboard Redesign: Starting Fresh When Growth Demands It
Project
I was second in command for the redesign of the MyZOLEO dashboard to address scalability issues and align with our refreshed product design. The original dashboard couldn't support our growing user base and felt disconnected from our new visual identity. Through user stories (UX Tracker), competitive analysis, and strategic planning, I designed a unified experience that serves both individual and business users while establishing a foundation for future B2B features.
Role
Led the design exploration and was responsible for the final dashboard implementation in collaboration with the developers.
Why We Needed to Rebuild
Working on the MyZOLEO dashboard redesign, I quickly realized we were dealing with a classic growing pains problem. Our original dashboard had done its job, but it wasn't built to handle where we were heading. The bigger issue was that it looked completely out of place next to our new product design.
We had two choices: try to patch things up or start over. We chose to rebuild.
The timing worked out well for us. We decided to tackle the dashboard last in our product refresh, which was smart because dashboards tend to pull from everything else in the system. By waiting, we knew exactly what components and backend pieces we'd have to work with once we got started.
Getting to the Bottom of What Users Actually Needed
I started by digging into the UX Tracker to see what frustrated users most about the current dashboard. No surprises there - people had been pretty vocal about their pain points. I also reviewed our project requirements and spent time looking at what our competitors were doing, both the obvious ones and some adjacent products.
The research showed a clear pattern. Users wanted to handle payments right from the dashboard instead of clicking through multiple screens. When I looked at competitor products, this wasn't revolutionary - it was pretty much expected at this point. People also wanted to see their recent invoices and get a better picture of their account activity without hunting for it.
Designing for Everyone (Sort Of)
Here's where things got interesting. We didn't have a B2B dashboard planned yet, but I could see we were getting more business users who had different needs than our typical individual users. Rather than ignore them completely, I tried to find features that would work for both groups.
That's how we ended up including things like showing which card was used for payments. Business users needed this for their expense tracking, but individual users found it helpful too.
Same logic applied to letting people manage their contacts and devices directly from the dashboard. Whether you're managing your own stuff or a company's equipment, being able to turn devices off or pause them without navigating away made sense. Safety features were particularly important since these devices play a big role in keeping people secure. Making device management easily accessible from the main dashboard wasn't just convenient — it was necessary.
I still explored ways to perhaps develop a different B2B environment for the business clients with over 50 devices. I was never able to finish but the rough concept was provided to ZOLEO.
What I'd Do Differently
If I could redo this project with more time and resources, I'd probably focus more heavily on the B2B side from the start. Not because individual users aren't important, but because designing for business needs first would actually make the dashboard cleaner for everyone else too.
I'd also add a settings page where users could turn features on and off based on what they actually use. Some people want to see everything, others prefer a minimal view. Letting users customize their dashboard would solve a lot of the complexity issues we were trying to balance.
But we had deadlines and needed to prioritize our biggest user group. Even though we were seeing more B2B interest and feature requests internally, it made sense to focus on getting the foundation right for our core users first.
How It Turned Out
The new dashboard fixed our growth problems and finally matched our updated design language. Users could request payments without leaving the main page, see their recent invoices at a glance, and manage their devices and contacts when needed.
We managed to serve both individual and business users without making the interface feel overwhelming. More importantly, we built something that could grow with us. The way we structured everything means adding new features or creating specialized views won't require starting over again.
This project reminded me that timing matters a lot in product design, and that sometimes the best solution is the one that works for your biggest constraints while still keeping future possibilities open.