myTickets—Discovery and Purchase Tickets
Redesigned the discovery to purchase flow, empowering users to find their next live event.
OVERVIEW
myTickets is an early stage ticketing startup that allows users discover live events and purchase tickets. The team needed to improve synergy between new features, such as the AI Chat interface, and the existing user flows. As a product design intern, I redesigned the core discovery-to-purchase flow to improve user retention and experience. I adapted to a lot of ambiguity and shifting priorities, learning to design within tight deadlines and limited resources. I worked cross-functionally with developers to on quality assurance and address critical visual bugs. The project is currently shipped, with newer changes continuously in production.
ROLE
Product Design Intern
TIMELINE
May 2025 - Aug 2025
TEAM
CEO 5 Developers
TOOLS/SKILLS
Figma, User Flows, Competitive Analysis, User Research, Prototyping
A Quick Glance at the Results
Built a cohesive and visually consistent flow from event discovery to checkout using reusable components and unified UI patterns. Drove a 30% increase in user conversion and a 10x increase in click-through rate.
PROBLEM STATEMENT
How might we create a more cohesive user experience by redesigning current user flows and incorporating new features like AI chat?
Current flows lacked visual consistency, and many users dropped off during checkout.
Goal
Create a cohesive experience that helps users quickly browse and discover artists/groups, events, and tickets and in turn make a purchase. Lay the groundwork for scalable components and new features.
Analyzing User Research and Current Flows
I was provided with user interview recordings and reviewed them to understand how and why users buy tickets to live events. Users prioritize factors like price, location, and genre. Users also liked to compare and quickly scan event dates/times, tickets, and seats. After, I audited the current designs, which lacked visual consistency and hierarchy, and made notes of my initial reactions. This process also allowed me to familiarized myself with the existing flows. Team stakeholders wanted more images across pages and to incorporate the AI Chat feature.
Addressing User Needs in the User Flow
I mapped the user journey from discovery to checkout, making it easier for users to browse and return to where they came from. For example, on the events page, users can quickly jump back into Explore or AI Chat. On the Ticket Detail page, they can easily return to Ticket Offers to compare options.
Incorporating Competitive Analysis into Wireframes
I studied competitors to understand industry standards and information hierarchy, while spotting opportunities for scalable components. Using these insights, I created low-fidelity wireframes that defined the content structure and reusable elements like event cards. These early visuals made it easy to test ideas and gather feedback quickly before moving into visual design.
With a tight launch deadline, the team prioritized mobile since most users accessed the platform there. I adapted my designs for smaller viewports and accounted for Safari’s navigation bar. The focus was on refining the AI chat, moving from low to high-fidelity designs. Early swipe-based interactions revealed issues with thumb reach and unclear labels, which led to a redesign of a navigation bar to separate features and improve clarity.
Creating the Design System Foundation
Since many early designs were high-fidelity, I started building a visual system with consistent spacing, iconography, typography, and scalable components for both mobile and web. Even in its early stage, this system improved visual consistency and made developer handoff smoother across key user flows.
Final Discover and Event Pages
The new Discover pages surfaces event categories and trending artists with clean cards, while the Events page focuses on event options and artist details. These pages use reusable components to stay consistent across the product. I had to work back and forth with devs to ensure that the designs were followed closely.
Making it Easier to Browse Tickets
I reinforced user needs by designing multiple ways to quickly browse ticket offers. Compact offer cards highlight section and price at a glance, while filters make it easy to narrow by quantity and price.
During checkout, I reinforced accuracy by displaying ticket and purchase details twice, ensuring users could confirm key information before paying. A back button in the top bar lets them revisit details or return to ticket offers. All checkout details fit on one screen, allowing users to review and confirm quickly without unnecessary scrolling.
FINAL DESIGNS
More Ways to Explore and Browse Live Events
Compared to the initial designs, the updated interface integrates the new AI chat feature while offering multiple ways to explore events. Filters by location, date, and genre help users quickly find what they want, while compact event cards display key details at a glance for easy browsing.
Clarified Checkout Process
Previously, users had to scroll excessively to confirm key payment details, making important information easy to miss. The updated design introduces a sticky CTA and a more compact layout, supporting easy browsing and quick back-and-forth navigation, directly addressing insights from our user research.
TAKEAWAYS
Results
Built a cohesive and visually consistent flow from event discovery to checkout using reusable components and unified UI patterns. Drove a 30% increase in user conversion and a 10x increase in click-through rate.
REFLECTION
Learned how to prioritize user needs while balancing product constraints in a fast-paced startup environment. Improved skills in visual hierarchy and consistency. Gained experience explaining design decisions to key stakeholders, collaborating with developers, and QA-testing handoffs. Learned to iterate rapidly based on feedback and constraints.
Next Steps
If I had more time, I would have conducted additional user research and usability testing to validate designs and explore alternative layouts. Tight deadlines and limited resources made formal user recruitment and interviews particularly challenging.
