Redesign Cloud Dashboard
Overview
Redesigned the Cloud platform dashboard to enhance user satisfaction and accessibility by introducing personalized marketing content and user-driven notifications. This data-backed approach enabled the successful onboarding of AWS, directly aligning the platform with evolving customer needs and expanding service offerings.
Role
Product Designer
I helped lead the design team through problem discovery, user needs identification, UX strategy development, rapid iterations, and A/B testing to shape a solution that addressed both user and business goals.
Keywords
Growth Design
Vendor Integration
Data-Validated Iteration
↑ 4% increase
in revenue
✓ AWS Integrated
to expand service offerings and flexibility
What is the Cloud Platform?
A B2B SaaS marketplace streamlining cloud service management. It enables businesses to purchase and scale solutions from Microsoft, Adobe, and AWS via a unified procurement platform.
Problem: High Traffic, Low Engagement
Using Microsoft Clarity heatmaps, we identified low engagement and underutilized dashboard space. The lack of clear content hierarchy and a dedicated notification area led to user complaints and missed communication opportunities.
Challenge:
The dashboard needed to display a wide range of information, making prioritization difficult.
Multiple cross-functional teams were involved, each with different goals and requirements.
Aligning internal stakeholders while keeping the end-user experience at the center was critical.
We had to deeply consider what users actually needed and expected from the dashboard.
Solution
Design Process
Phase 1: Understand
Who are the stakeholders?
1: ASM Users (Internal Support Team)
Internal team members who access the platform to support customers, troubleshoot issues, and manage service-related tasks.
2: Resellers
Partners who manage multiple end-user accounts. They are responsible for purchasing, provisioning, and overseeing software and services on behalf of their clients.
3: End Users
Direct customers who use the platform to purchase, manage, and track their own software and hardware products.
User research
We conducted 1:1 interviews with each user group to understand their needs, capturing insights on sticky notes to visualize and prioritize key dashboard features.
1. Needing a clear view of account issues
"When I log in, I just want to quickly know what's wrong and how to fix it."
– ASM user (Male, 40s)
2. Staying informed about system updates and releases
"If something changes, like pricing or termsI need to know first. It will affects my customers."
– Reseller (Male, 38)
3. Finding help and services more easily
"Sometimes I just need help, but I don’t know where to go on the site."
– End-user (Female, 45)
Phase 2: Explore
UX Strategy
Structured Value, Higher Engagement
We developed a UX strategy focused on boosting user literacy through a structured reporting journey. By building user confidence and clarity, we aimed to drive independent report management and platform adoption.
Customer User Journey
Instilling strategies into users' journey
To concretize the strategy, we've generated features that will serve each strategy and mapped them on to the users' journey.
Phase 3: Design
New User Flow & Side Menu
We unified the experience into a single, adaptive flow that remains consistent across all user roles. The streamlined journey:
Consolidates access points into a unified starting page
Offers guided steps based on report type and user goals
Highlights saved templates and previously run reports
Clarifies scheduling, editing, and delivery options
Before User Flow & Side Menu
The old experience featured fragmented, inconsistent entry points. Different user roles relied on trial and error through informal paths, leading:
Confusion over which path was correct
Repetitive actions across different pages
Difficulty locating specific reports
Lack of standardization across user types
Ideation
We conducted a comparative usability test by presenting two prototype ideas to stakeholders. We observed how they interacted with each version and asked which one they preferred, helping us identify the more intuitive design.
Preferred Idea 1 for its:
Cleaner layout
Better readability
More modern visual design
Concerns with Idea 2:
Required excessive scrolling
Difficult to locate specific reports (especially with hundreds of entries)
Hard to scan and read long report descriptions
Idea 1
Idea 2
Phase 4: Final Delivery
New report system
Simplified navigation with a unified top bar and clear tabs, and organized reports by category for better readability.
Added a dropdown for report explanations, reducing the need to switch between pages.
Removed clutter and duplicate paths to enhance focus and usability.
New version
Old version
Report Template
The Report Templates section was moved to its own dedicated tab to reduce visual clutter and help users focus more easily.
The “Run” and “Edit” actions are now clearly separated into their own column, making them eas ier to locate and use.
The updated layout supports better scalability, allowing users to view more templates at once without feeling overwhelmed.
New version
Old version
Scheduled Report
Applied a consistent layout to align with the overall report management experience.
Designed a clear empty state view to guide users when no scheduled reports are available.
Added a prominent “Schedule Report” button to help users easily understand how to get started.
New version
Old version
Confirmation Component
Created reusable components for confirmation interactions to maintain consistency.
Designed success message toasts to provide clear feedback after actions are completed.
Built standardized modals for scheduling and editing, making it easier for developers to implement across the tool.
Phase 5: Future development
Report Generate
Postponed development of the report generation detail page due to time and team capacity constraints.
Next steps include unifying the design style across the platform for consistency.
Plan to redesign the report generation detail experience and validate entire experience improvements through A/B testing.
New version
Old version
↑ 12% increase
in usage
✓ 1,200 increase
reports more compared to the previous year.
Personally, it was a fruitful moment for me to contribute to a collaborative effort. Sharing our research insights on the visualized prototypes, we were able to expedite our process by reducing communication loss. Although it wasn't easy to take on this role independently, it was enlightening to see this phase adopted as a formal process in following projects.