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 Product Designer

Timeframe

1.5 Months

Toolkit

Figma, FigJam, Chat GPT

Collabortors

Product Manager, Engineers

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

Problem

Before the redesign, the ad server admin interface was plagued by multiple usability issues:

  1. Low adoption: Only one team used the tool consistently due to its confusing layout.

  1. Poor navigation: Users had to click through multiple tabs to complete a single workflow.

  1. Lack of clarity: There was no way to tell what widgets were live, inactive, or in test mode.

  1. Limited search functionality: Users were unable to easily search by ID or track flights effectively.

  1. No historical context: It was impossible to trace when a widget was created, modified, or tested.

These issues not only made onboarding new users difficult but also led to frequent delays in ad testing, miscommunication across teams, and missed revenue opportunities due to faulty ad deliveries..

The Journey of Discovery and Research

I kicked off the project by interviewing 10 internal users from ad operations and QA, and collaborating with two engineers and our product manager. We held open-ended discussions to understand pain points, daily workflows, and desired improvements. Themes quickly emerged:

  • “I never know what’s live and what’s not.”

  • “Finding the test status of a widget takes forever.”

  • “I don’t feel confident using this tool without asking for help.

We also hosted a discovery workshop using FigJam, which allowed us to map user journeys and identify areas of friction. These sessions gave clarity on what a successful redesign needed to accomplish.

In parallel, I audited internal tools with similar complexity. I drew inspiration from admin interfaces that used persistent navigation, inline object editing, and global dashboards. These features became foundational to our strategy.

Finally, I reviewed the feasibility with the engineers. Due to backend limitations, we scoped out bulk ad creation and specific dynamic flows. This helped us stay focused on what would deliver the highest impact with the resources at our disposal.

Ideation and Strategy

With insights and technical boundaries defined, I led a structured ideation session using “How Might We” prompts. Together, we transformed problem statements into solution opportunities:

  • How might we allow users to stay in context while editing?

  • How can we provide a comprehensive view of widget status?

  • How can we minimize the need to switch between linked objects?

We synthesized the results into four key goals:

  1. Streamline ad creation and editing

  2. Create contextual navigation without tab switching

  3. Visualize relationships between ads, widgets, and flights

  4. Enable effective search and debugging

These goals became the foundation for our redesign approach.

Early Exploration & Sketching

After narrowing down potential solutions, the team and I held a workshop where we sketched as many ideas as possible. The focus was on speed and variety, not polished designs, so we could quickly explore different ways to solve the problems.

The sketches revealed a wide range of possibilities and highlighted key elements that appeared consistently across concepts. I then refined the most promising directions into more precise drawings, which served as loose wireframes.

Since this phase was built upon earlier A/B testing workshops, we had already established patterns for flow and layout. That foundation allowed me to transition smoothly from sketches into higher-fidelity designs while keeping both user needs and team input at the core.

Design and Prototyping

Given the aggressive timeline, I jumped straight into high-fidelity designs using existing design system components. I started by mapping core flows: from creating a new widget to viewing test history and debugging delivery paths.

Key Changes:

  • Overview Dashboard: A single page summarizing widget activity, test states, and history.

  • Widget Drill-down Pages: Showing flight associations, test results, and real-time statuses.

  • Streamlined Navigation: Designed to help users stay oriented while switching between objects.

  • Search and Filter Tools: Users could now search by ID, keyword, or path and apply filters by status or type.

I created interactive flows and shared them on a weekly basis with the PM and engineers. These reviews helped us validate our design assumptions and make adjustments based on feasibility. For instance, we replaced dynamically nested elements with modals and breadcrumb-based navigation to reduce engineering complexity.

Throughout this process, I paid close attention to visual hierarchy. I introduced color-coded status indicators, clean typography, and white space to emphasize structure and clarity. Each screen included both primary tasks and helpful secondary information, allowing users to take action quickly.

User Testing & Iteration

Once the prototypes were ready, I conducted usability testing with six users across different experience levels. They were asked to complete everyday tasks such as:

  • Find a widget using its ID

  • Confirm whether a test was live or completed

  • Debug an ad delivery issue

  • Identify which widgets were inactive

Observations:

  • Experienced users completed tasks in half the time compared to the previous version.

  • New users completed tasks without external help for the first time.

  • All testers praised the persistent breadcrumbs and clear status indicators.

Based on feedback, I made refinements, including enlarging hit areas, improving empty state messaging, and streamlining label language. These minor adjustments had a significant impact on clarity and confidence.

Launch and Results

The final product was launched at the end of our six-week timeline. Within two weeks:

  • Adoption: Four additional teams started using the tool, and two retired their previous systems.

  • Efficiency: Average task time dropped from 30 minutes to under five.

  • Usability: Daily usage increased by 30%, and support tickets related to ad testing dropped noticeably.

Teams were able to:

  • Spot broken widgets before deployment

  • Debug delivery issues faster

  • Launch campaigns with fewer errors

Because the interface was easier to use, teams spent less time searching for information and more time improving ad performance. This not only boosted confidence but also allowed teams to scale ad testing with fewer bottlenecks.

Reflections & Next Steps

This redesign exemplified how often-overlooked internal tools can benefit from user-centered design. By prioritizing users and aligning design with actual workflows, we developed a tool that teams not only utilized but also championed.

What Worked:

  • Early user involvement gave us a clear direction

  • Reusing the design system saved time and improved consistency

  • Weekly reviews helped prevent misalignment or scope creep

What I’d Improve:

  • Involve engineers earlier in the ideation phase to flag technical risks sooner

  • Expand testing to include marketing and QA roles for a broader perspective

This project taught me the importance of striking a balance between ambition and clarity. Every decision, from the way we structured navigation to the order of information on screen, was made with the end user in mind. That mindset paid off in the form of better workflows, wider adoption, and stronger outcomes.

Outcome Summary:

  • 30% increase in usability and daily engagement

  • Four new teams onboarded

  • Task time reduced by over 35%

  • Teams replaced legacy tools with the new interface

  • Enabled better QA, faster iteration, and more substantial team alignment

By solving real problems and focusing on clarity, we transformed an underperforming tool into a trusted, central part of team operations.

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.