Vertical Tracking Portal

Vertical Tracking Portal

I led the redesign of RVMN’s internal analytics portal to improve navigation, data clarity, and user trust. The new role-based dashboards replaced outdated tools and increased internal adoption by a factor of two.

I led the redesign of RVMN’s internal analytics portal to improve navigation, data clarity, and user trust. The new role-based dashboards replaced outdated tools and increased internal adoption by a factor of two.

Role

Lead Designer

Timeframe

2 Months

Toolkit

Figma, FigJam, Chat GPT

Collabortors

Product Manager, Developer

RVMN’s internal dashboard was outdated and unreliable, leading users to rely on Excel and third-party tools, costing over $40K a year. I led a full redesign to rebuild trust and improve usability. My work covered user research, IA (Information Architecture), wireframes, interaction and visual design, usability testing, and stakeholder collaboration. Key goals: • Improve usability and match real workflows • Speed up data access and reporting • Eliminate reliance on external tools

Results and Findings

Adoption:

  • Daily usage doubled within two weeks of launch

  • Over 25% of analysts stopped using Tableau or Excel for daily reporting

Accuracy & Trust:

  • More users stayed within the platform for KPI discovery

  • Filters and visualizations created confidence in the displayed data

Cost Savings:

  • ~$10,000/month saved in third-party licensing

  • Fewer manual exports and data validation steps reduced analyst workload

UX Outcomes:

  • Onboarding time dropped by 40%

  • 90% of users reported increased satisfaction in post-launch surveys

Results and Findings

Adoption:

  • Daily usage doubled within two weeks of launch

  • Over 25% of analysts stopped using Tableau or Excel for daily reporting

Accuracy & Trust:

  • More users stayed within the platform for KPI discovery

  • Filters and visualizations created confidence in the displayed data

Cost Savings:

  • ~$10,000/month saved in third-party licensing

  • Fewer manual exports and data validation steps reduced analyst workload

UX Outcomes:

  • Onboarding time dropped by 40%

  • 90% of users reported increased satisfaction in post-launch surveys

Problem

The partner portal presented significant UX challenges, including poor navigation, lack of feature discoverability, and limited self-service options. Users struggled to find relevant data, create custom reports, and perform basic account tasks independently. The absence of interactive data visualizations and outdated UI further hindered usability. Additionally, generic content and misaligned vertical information led to confusion and reduced trust in the platform.

Discovery Definition: Workshop Activities

To kick off the project, I facilitated a three-hour discovery workshop with six cross-functional stakeholders from analytics, product, and business operations. The session combined contextual interviews, collaborative pain-point mapping, and rapid sketching exercises. This not only surfaced critical friction points across different roles but also built early alignment within the team.

To dive deeper into edge cases and individual workflows, I conducted five follow-up interviews with key users. These focused on task flows, filtering behaviors, and reporting needs, uncovering widespread inefficiencies in customization, navigation, and trust in the data.

From over 40 collected data points, we identified two primary personas:

Alex, Vertical Lead

Needs: View high-level KPI summaries across business units

Frustration: “I have to check three dashboards just to get a complete picture.”

Taylor, Analyst

Needs: Build, filter, and share detailed, customizable reports

Frustration: “I export to Excel every time because I can’t drill down or customize what I see.”

These personas grounded our design decisions and ensured we addressed both power users and high-level stakeholders.

We synthesized the findings into five key UX challenges:

  1. Usability Gaps: Navigation lacked a clear hierarchy, users were unable to save custom views, and guidance was insufficient. This led to steep learning curves and high abandonment.

  2. Flat Visuals: Data was displayed in static tables with no interactive charts or summaries, making it challenging to gain quick insights and driving reliance on external exports.

  3. Outdated Design System: The UI relied on legacy components with poor spacing and contrast, which undermined both usability and brand trust.

  4. One-Size-Fits-All Layouts: Dashboards were not tailored to roles or verticals, forcing users to sift through irrelevant data.

  5. Access Confusion: Ambiguity around sharing and permissions discouraged collaboration and created reporting friction.

These insights led to our core design question:

“How can we design a flexible and intuitive dashboard that supports diverse workflows and fosters user confidence in the data?”

We synthesized the findings into five key UX challenges:


  1. Usability Gaps: Navigation lacked hierarchy, users were unable to save custom views, and guidance was lacking. This led to steep learning curves and high abandonment.

  2. Flat Visuals: Data was displayed in static tables with no interactive charts or summaries, making it challenging to gain quick insights and driving reliance on external exports.

  3. Outdated Design System: The UI relied on legacy components with poor spacing and contrast, which undermined both usability and brand trust.

  4. One-Size-Fits-All Layouts: Dashboards were not tailored to roles or verticals, forcing users to sift through irrelevant data.

  5. Access Confusion: Ambiguity around sharing and permissions discouraged collaboration and created reporting friction.

These insights led to our core design question:

"How can we design a flexible and intuitive dashboard that supports diverse workflows and fosters user confidence in the data?"

We synthesized the findings into five key UX challenges:


  1. Usability Gaps: Navigation lacked hierarchy, users were unable to save custom views, and guidance was lacking. This led to steep learning curves and high abandonment.

  2. Flat Visuals: Data was displayed in static tables with no interactive charts or summaries, making it challenging to gain quick insights and driving reliance on external exports.

  3. Outdated Design System: The UI relied on legacy components with poor spacing and contrast, which undermined both usability and brand trust.

  4. One-Size-Fits-All Layouts: Dashboards were not tailored to roles or verticals, forcing users to sift through irrelevant data.

  5. Access Confusion: Ambiguity around sharing and permissions discouraged collaboration and created reporting friction.

These insights led to our core design question:

"How can we design a flexible and intuitive dashboard that supports diverse workflows and fosters user confidence in the data?"

We synthesized the findings into five key UX challenges:


  1. Usability Gaps: Navigation lacked hierarchy, users were unable to save custom views, and guidance was lacking. This led to steep learning curves and high abandonment.

  2. Flat Visuals: Data was displayed in static tables with no interactive charts or summaries, making it challenging to gain quick insights and driving reliance on external exports.

  3. Outdated Design System: The UI relied on legacy components with poor spacing and contrast, which undermined both usability and brand trust.

  4. One-Size-Fits-All Layouts: Dashboards were not tailored to roles or verticals, forcing users to sift through irrelevant data.

  5. Access Confusion: Ambiguity around sharing and permissions discouraged collaboration and created reporting friction.

These insights led to our core design question:

"How can we design a flexible and intuitive dashboard that supports diverse workflows and fosters user confidence in the data?"

Competitive Review & Constraints

We analyzed tools such as Looker, Mixpanel, and Rakuten to understand patterns related to layout clarity, filters, and modular dashboards. While we didn’t aim to copy them, they set user expectations around:

  • Persistent filters

  • Saved and shared views

  • Interactive data visualizations

  • Personalization by team or role

Due to the time constraint, we chose not to build a new design system. Instead, we adopted and customized a component library from a sibling brand. This gave us a head start and ensured consistency across internal tools, while still allowing us to modernize the interface with:

  • A refreshed color palette tested for accessibility

  • Legible, consistent typography

  • Simplified iconography for faster scanning

Information Architecture & MVP Scope

To ensure we could move efficiently, midway through the project we brought on a junior UX designer to handle some of the less critical pages such as Support and FAQ. This allowed me to stay focused on the core experience, which included the dashboard, the dashboard creation process, Insights, and user permissions.

We began with a content audit that highlighted features either missing or in need of immediate improvement. From this audit and a user flow analysis, we identified five primary sections to focus on:

  • Insight Dashboard

  • Overview

  • Insight Creation

  • Integrations

  • User Settings

Through our research, we discovered that most users were not accessing the Insights section, either because the navigation was unclear or the content did not feel relevant to their needs. To address this, I began mapping out the information architecture with support from ChatGPT to create clearer pathways and streamline access to high-value features.

To keep the project focused and manageable within our eight-week timeline, we defined a clear MVP scope that included:

  • Interactive dashboards with drill-down capabilities

  • Role- and team-based dashboard configurations

  • Role-based access permissions

  • Layout saving, filter presets, and onboarding walkthroughs

More advanced features, such as automation and KPI alerts, were deferred to a second phase to avoid scope creep. As the lead designer, I took full ownership of the high-impact core pages. To stay on schedule, we brought in another designer from a separate team to handle lower-priority pages, such as the FAQ, Payments, and Glossary. MVP scope to focus on scalable improvements that could deliver immediate value and pave the way for future iterations.

To keep the project focused and manageable within our eight-week timeline, we defined a clear MVP scope that included:

  • Interactive dashboards with drill-down capabilities

  • Role- and team-based dashboard configurations

  • Role-based access permissions

  • Layout saving, filter presets, and onboarding walkthroughs

More advanced features, such as automation and KPI alerts, were deferred to a second phase to avoid scope creep.

As the lead designer, I took full ownership of the high-impact core pages. To stay on schedule, we brought in another designer from a separate team to handle lower-lift pages like the FAQ, Payments, and Glossary. VP scope to focus on scalable improvements that could deliver immediate value and pave the way for future iterations.

Ideation & Wireframing

I started sketching early concepts, focusing on a card-based layout with modular content blocks. This structure allowed flexibility while still maintaining visual rhythm. After a few iterations, I moved into low-fidelity wireframes in Figma to explore:

  • Persistent side navigation

  • Filters at the dashboard level

  • Drag-and-drop chart modules

  • Customizable widgets grouped by KPI

We held weekly critiques with the product and engineering teams, using clickable prototypes to test fundamental interactions. A valuable discussion emerged regarding syncing, as real-time data wasn’t technically feasible due to infrastructure limitations. Instead of delaying, we added a visible “Last Updated” indicator near each data block to manage expectations while increasing transparency. These conversations turned technical constraints into thoughtful UX moments.

Agile Execution & Usability Testing

We worked in two-week sprints, ensuring consistent progress and alignment. Each sprint ended in a design/dev sync to manage dependencies. Our workflow included:

  • Daily standups

  • Cross-functional design reviews

  • Figma feedback and Slack async QA

Once our prototype matured, I led usability testing with eight users. The sessions focused on:

  • Navigating between dashboards and views

  • Using filters to find relevant data

  • Saving and sharing personalized layouts

  • Understanding what data others could or couldn’t see

User feedback was overwhelmingly positive, though some still hesitated during view-sharing workflows. We solved this by adding more prominent visibility labels and a preview mode showing what others would see.

Final Design Highlights and Results

  1. Modular Dashboards: Drag-and-drop components with customizable filters and layout presets

  2. Vertical-Specific Views: Tailored dashboards by team, business unit, or function

  3. Smarter User Settings: Saved views by individual or team, default landing views, and permission options

  4. Responsive Grid System: Fully adaptable layouts for different screen sizes and use cases

  5. Simplified Integrations: Step-by-step setup for connecting data sources, with visual health checks

  6. Templatized Insights: We simplified the process by creating templates to help new users generate insights more easily.

We launched the redesigned Portal on schedule. The impact was clear and immediate.

  1. Modular Dashboards: Drag-and-drop components with customizable filters and layout presets

  2. Vertical-Specific Views: Tailored dashboards by team, business unit, or function

  3. Smarter User Settings: Saved views by individual or team, default landing views, and permission options

  4. Responsive Grid System: Fully adaptable layouts for different screen sizes and use cases

  5. Simplified Integrations: Step-by-step setup for connecting data sources, with visual health checks

  6. Templatized Insights: We simplified the process by creating templates to help new users generate insights more easily.

We launched the redesigned Portal on schedule. The impact was clear and immediate.

  1. Modular Dashboards: Drag-and-drop components with customizable filters and layout presets

  2. Vertical-Specific Views: Tailored dashboards by team, business unit, or function

  3. Smarter User Settings: Saved views by individual or team, default landing views, and permission options

  4. Responsive Grid System: Fully adaptable layouts for different screen sizes and use cases

  5. Simplified Integrations: Step-by-step setup for connecting data sources, with visual health checks

  6. Templatized Insights: We simplified the process by creating templates to help new users generate insights more easily.


We launched the redesigned Portal on schedule. The impact was clear and immediate.


Adoption:

  • Daily usage doubled within two weeks of launch

  • Over 25% of analysts stopped using Tableau or Excel for daily reporting


Accuracy & Trust:

  • More users stayed within the platform for KPI discovery

  • Filters and visualizations created confidence in the displayed data


Cost Savings:

  • ~$10,000/month saved in third-party licensing

  • Fewer manual exports and data validation steps reduced analyst workload


UX Outcomes:

  • Onboarding time dropped by 40%

  • 90% of users reported increased satisfaction in post-launch surveys

  1. Modular Dashboards: Drag-and-drop components with customizable filters and layout presets

  2. Vertical-Specific Views: Tailored dashboards by team, business unit, or function

  3. Smarter User Settings: Saved views by individual or team, default landing views, and permission options

  4. Responsive Grid System: Fully adaptable layouts for different screen sizes and use cases

  5. Simplified Integrations: Step-by-step setup for connecting data sources, with visual health checks

  6. Templatized Insights: We simplified the process by creating templates to help new users generate insights more easily.

We launched the redesigned Portal on schedule. The impact was clear and immediate.

Final Thoughts

This was a fast-moving project with a lot at stake. It required tough decisions, close collaboration across teams, and a strong focus on quality over delivering a long list of features.


What I’m proud of:

  • Listening to real user feedback to guide what we built

  • Working within tight constraints without losing user trust

  • Delivering real value to the business in just eight weeks


What I’d do differently:

  • Push earlier for clearer, more flexible sharing permissions

  • Start remote user testing sooner

  • Check usage data more often to help guide improvements

This project was a great reminder that good UX isn’t about flashy visuals. It’s about making things clear, giving users the right context, and helping them take action with confidence. Despite limited time and resources, we turned an outdated tool into a user-focused experience that made data easier to access and use. That in turn helped teams make faster, smarter decisions, showing how powerful good design can be for the business.

This was a fast-moving project with a lot at stake. It required tough decisions, close collaboration across teams, and a strong focus on quality over delivering a long list of features.


What I’m proud of:

  • Listening to real user feedback to guide what we built

  • Working within tight constraints without losing user trust

  • Delivering real value to the business in just eight weeks


What I’d do differently:

  • Push earlier for clearer, more flexible sharing permissions

  • Start remote user testing sooner

  • Check usage data more often to help guide improvements

This project was a great reminder that good UX isn’t about flashy visuals. It’s about making things clear, giving users the right context, and helping them take action with confidence. Despite limited time and resources, we turned an outdated tool into a user-focused experience that made data easier to access and use. That in turn helped teams make faster, smarter decisions, showing how powerful good design can be for the business.

This was a fast-moving project with a lot at stake. It required tough decisions, close collaboration across teams, and a strong focus on quality over delivering a long list of features.


What I’m proud of:

  • Listening to real user feedback to guide what we built

  • Working within tight constraints without losing user trust

  • Delivering real value to the business in just eight weeks


What I’d do differently:

  • Push earlier for clearer, more flexible sharing permissions

  • Start remote user testing sooner

  • Check usage data more often to help guide improvements

This project was a great reminder that good UX isn’t about flashy visuals. It’s about making things clear, giving users the right context, and helping them take action with confidence. Despite limited time and resources, we turned an outdated tool into a user-focused experience that made data easier to access and use. That in turn helped teams make faster, smarter decisions, showing how powerful good design can be for the business.

This was a fast-moving project with a lot at stake. It required tough decisions, close collaboration across teams, and a strong focus on quality over delivering a long list of features.


What I’m proud of:

  • Listening to real user feedback to guide what we built

  • Working within tight constraints without losing user trust

  • Delivering real value to the business in just eight weeks


What I’d do differently:

  • Push earlier for clearer, more flexible sharing permissions

  • Start remote user testing sooner

  • Check usage data more often to help guide improvements

This project was a great reminder that good UX isn’t about flashy visuals. It’s about making things clear, giving users the right context, and helping them take action with confidence. Despite limited time and resources, we turned an outdated tool into a user-focused experience that made data easier to access and use. That in turn helped teams make faster, smarter decisions, showing how powerful good design can be for the business.

You like my work? Get in touch and learn more about me.

You like my work? Get in touch and learn more about me.

You like my work? Get in touch and learn more about me.

You like my work? Get in touch and learn more about me.