Role
Lead Designer
Timeframe
1.5 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.
Problem
User interviews and internal analytics revealed several key issues that explained the low adoption:
The setup flow for split testing was confusing, especially for non-technical users.
There was no clear way to preview or compare test variants before or during a test.
Historical test data were hard to access and lacked visual clarity.
Teams relied heavily on third-party tools, such as Looker, to interpret test results, which fragmented the workflow.
To deepen our understanding, I facilitated an empathy mapping session with seven key stakeholders—marketers, content managers, and data analysts who regularly run tests. These sessions uncovered common frustrations and helped identify two high-impact areas to prioritize in the redesign:
Improve the split testing experience and flow.
Enhance asset preview functionality before and during test setup.
Where do we go, and what does it look like?
After brainstorming, I hypothesized that low adoption came from missing features and limited testing. Our goals were to enhance test feedback, streamline split test workflows, and clarify historical data.
I conducted secondary research on tools like Google Looker, Storyblok, and Salesforce to understand how they present and retrieve data, which directly informed our approach.
From there, I developed a product requirements document, user stories, and outlined key pages and inputs. After aligning with the product manager and confirming feasibility with engineering, I focused on designing MVP test preview pages. This clarified two main areas: split testing and the ad server, with some overlapping insights, but the priority was enabling teams to set up and evaluate tests effectively.
Drawing to discover
After thoroughly reviewing the existing split testing process, I redesigned the flow to simplify the experience. This included introducing new pages and sections while eliminating redundancies to improve usability and efficiency.
Bringing the design to life
Feedback during early stakeholder reviews revealed areas that needed refinement:
The filtering system in the admin dashboard lacked logic and flexibility.
Preview functionality was inconsistent, either too small to be useful or too large to be efficient.
There was no way to view which business unit or vertical a test belonged to.
Teams wanted better visibility of test progress over time, but engineering advised deferring complex charting until after the MVP.
Using this feedback, I adjusted the MVP scope to focus on scalable improvements that could deliver immediate value and pave the way for future iterations.
Testing & Iteration
With one week left before design handoff, I conducted remote usability tests with four internal team members. These sessions were focused on test creation, result interpretation, and filtering.
Findings and solutions:
Unclear Preview Scaling: Users were unaware that they could resize previews. I replaced the manual resizing mechanism with a toggle-based approach that was easier to find and use.
Lack of Onboarding Cues: New users weren’t sure how to get started. I added inline tooltips and empty-state messages with action prompts.
After incorporating these updates, I created a clickable prototype and validated it with stakeholders before passing it to the engineering team.
Final Results
The MVP was launched on time and received strong support across all teams.
Measured impact two months post-launch:
Adoption increased by 14%, nearly doubling the user base.
$21K/month saved through reduced reliance on third-party tools.
Improved efficiency in test setup and result visibility.
Greater confidence among teams, thanks to a centralized platform and precise results.
The tool transitioned from being overlooked to becoming a foundational resource for experimentation.










