Role
Lead Designer
Timeframe
2 Months
Toolkit
Figma, FigJam, Chat GPT
Collabortors
Product Manager, Developer
After completing the redesign of our A/B testing and preview tools, I was asked to lead the second phase of the Inline platform update: the AdServer admin interface. This system was critical for managing ad widgets but had become overly complex and difficult to use. Over the course of six weeks, I led the redesign to simplify workflows, enhance navigation, and make the tool more intuitive. Through research, design, and testing, we delivered a streamlined interface that drove a 30% increase in usability, enabled adoption by four additional teams, and produced measurable productivity gains across the company. This project marked the next step in modernizing our internal software, following the successful overhaul of the A/B testing tool.
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.
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.
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.














