📈 Business Impact
• Designed a production-ready feature for a smaller product team with no dedicated designer
• Delivered a clean, intuitive comparison table that simplified internal QA workflows
• Drove alignment across Product and Engineering through a fast, collaborative, and feedback-driven process
🎯 Project Role
Brought in as a design resource while working full-time in a Design Operations role. Led the end-to-end design effort for a lightweight feature used by internal B2B users, delivering the solution in ~10 hours.
🛠 Skills Used
• Product Design
• Interaction Design
• Rapid Prototyping
• Enterprise UX
• Visual Design
• Design Systems
• Stakeholder Communication
• Problem Framing
• B2B Workflow Design
• Lean UX
Problem
A smaller product team at Ticketmaster needed help designing a comparison table to help internal users quickly identify and resolve ticket listing conflicts. The team didn’t have a dedicated designer and had already sketched out some rough ideas.
I was working full-time in a Design Ops role but was asked to assist—and had just 10 hours to contribute.
Step 1: Assess the Starting Point
I began by reviewing what the Product team had already prepared: rough sketches and a conceptual idea of how the table might work.
Equally important, I gauged how much design exposure the team had and how open they were to new thinking. In this case, the Product Manager was open and collaborative, which made it possible to move fast.
Step 2: Determine the Need for User Testing
To assess whether user testing was necessary, I asked myself:
• Is the change disruptive to an existing workflow?
• Is the feature complex?
• Is there ambiguity around what’s frustrating users?
In this case, the answers were mostly "no." The feature was relatively low-risk and targeted a small set of internal users. We decided user testing wasn’t needed in this instance.
Step 3: Reframe the Goal
The core problem: users needed to quickly scan a table of events and spot inconsistencies in ticket types—e.g., identifying events missing required upsell or standard ticket categories.
This became the design goal: make errors or conflicts immediately scannable.
Step 4: Set the Bones
Rather than sketching, I jumped directly into Figma using the existing design system to structure a 1440px desktop layout. I aligned the grid, padding, and typography from the start to reduce handoff friction and work efficiently.
Step 5: Show Something Early
I quickly produced an early draft and shared it with the Product team. This served several purposes:
• Demonstrated progress
• Invited collaboration
• Surfaced constraints and misassumptions early
• Helped Engineering weigh feasibility
Getting a tangible artifact in front of stakeholders quickly was key to establishing momentum and direction.
Step 6: Iterate Quickly
With each round of feedback, I refined the design. One common challenge in enterprise tools—column bloat—surfaced here. As new requirements emerged, more data columns were added.
Rather than push back abstractly, I showed what excessive columns would look like in a scrollable table. Once the team saw the cost to usability, they reversed course and agreed to simplify.
The Final Design
By the 4th draft, I landed on a minimal, elegant solution:
• No extra clicks
• Conflicts marked inline with asterisks
• Dropdowns only where necessary
• Clean visual hierarchy
This design balanced simplicity, scannability, and developer feasibility—earning unanimous support from the team.
The Results
• Feature was approved and implemented quickly
• Saved time across QA workflows by clearly surfacing conflicts
• Reinforced the value of design—even on small teams and low-scope features
This project proves that even in 10 hours, thoughtful design can improve internal tools, build trust with cross-functional partners, and deliver real value.
