
"TicketWaze" draws from the Creole word meaning "meeting," reflecting the platform's cultural DNA. This wasn't just clever brandingβit was a commitment. In the markets we serve, events aren't merely entertainment; they're social institutions, community touchpoints, and cultural preservation vehicles. The name signals that we understand this deeper significance.
Lead Product Designer
2024

Web Application
|
Product Design
|
Interaction Design
Discovery Process
After initial discovery calls with the founders, I conducted:
8 in-depth user interviews (potential attendees, ages 22-45)
4 organizer interviews (running 5-50 events annually)
Behavioral observation of current ticket purchase flows
What We Learned
User Pain Points:
"I found an event on Instagram, had to DM the organizer, transfer money to their personal account, then screenshot the confirmation as my 'ticket.' If something goes wrong, I have no recourse." β Sarah, 28
"I want to buy tickets for my friends but I don't have everyone's full address and phone number. Why do I need all that just to get a ticket?" β Michael, 32
"Sometimes I see an event I like but I'm not ready to buy yet. There's nowhere to save it, so I just screenshot and hope I remember to look at my photos later." β Amara, 25
Organizer Pain Points:
"We're using Excel spreadsheets to track ticket sales, sending manual confirmations, and checking people in with printed lists. It's 2025." β David, Event Organizer
Key Insights That Shaped DesignTrust is fragile - Users hesitate with unfamiliar payment systems; we needed to build confidence at every step
Social coordination matters - 67% of users buy tickets for groups, not just themselves
Discovery is broken - Users rely on social media algorithms and word-of-mouth, missing relevant events
Mobile-first necessity - 85%+ of our target users access the internet primarily through phones
Payment infrastructure varies - Different markets prefer different payment methods; flexibility is essential
Before touching pixels, I established principles to guide every decision:
Cultural Authenticity - Honor the communities we serve in language, imagery, and interaction patterns
Radical Simplification - If a step isn't essential, eliminate it
Trust Through Transparency - Always show users what's happening and why
Community Over Transactions - Build relationships between attendees and organizers
Inclusive by Default - Design for varying technical literacy, connectivity, and device capabilities
Structuring the System
Starting with ideation, I typically go about it by putting the PRD on ChatGPT (my go-to AI for this task) and writing a series of prompts (secret sauce) and further prompting the responses for maximum clarity. With this approach, I'm able to get a more granular idea of the application, which puts things into perspective and aids overall definition of the architectureβunderstanding how each navigation functions individually and also as a unit.
This process helps me think through edge cases, identify potential user flows I might have missed, and ensure consistency across different user types. It's like having a conversation with the product itself before it exists, stress-testing the logic before committing it to pixels.
Navigation Structure
The architecture reflects user priorities based on research:
For Attendees: Explore, Upcoming, History, Organizers | Profile, Preference, Settings
For Organizers: Analytics, Events, Finance, Settings
For Admin: Analytics, Attendees, Organizers, Events, Tickets, Payments, Payouts
Each navigation structure tells a story. Attendees need discovery first (Explore), then management of commitments (Upcoming/History), then community (Organizers). Organizers need to see performance (Analytics), manage their events, and understand their finances. Admins need comprehensive oversight.β¨β¨
Core User Flow: Ticket Purchase
I mapped the entire journey from discovery to ticket in hand:
Current State (Competitor platforms):
Discovery β Create Account β Select Ticket β Enter All Recipient Details (name, email, phone, address for EACH person) β Payment β Confirmation β Download
TicketWaze Optimized Flow:
Discovery without account β View Details β Create Account (only when ready to buy) β Select Ticket β One-click if buying for self / Name + Email only for others β Payment β Instant Email Delivery + Auto-redirect to Upcoming
Key Innovation: Reducing the attendee data burden. Research showed users abandon when forced to enter full details for friends. Our solution: if you're buying for yourself, we already have your infoβone click. For others, we ask the bare minimum: name and email. Tickets get delivered, and everyone's happy.
Moodboarding & Exploration
For the design direction, I moodboarded multiple stylesβfrom bold and vibrant (reflecting the energy of events) to clean and minimal (emphasizing usability). The founders and I landed on a direction that balances both: colorful enough to feel alive, structured enough to feel trustworthy.
Color System
To build my color palette, I use tints and shades to generate colors from 100-900 with 500 as the base. This systematic approach ensures consistency and gives me a predictable system for any UI stateβhover, disabled, selected, error.
Color roles in the system:
Primary: Brand identity, CTAs, key actions
Neutral: Text hierarchy, borders, backgrounds
Deep: High-contrast text on light backgrounds
Status colors: Success (green), Warning (amber), Error (red), Info (blue)
Accent colors: Highlight specific event categories or promotional content
This system is flexible enough to accommodate diverse event types while maintaining visual cohesion.

Typography: Character Meets Clarity
I paired Bricolage Grotesque (display) and DM Sans (paragraph).
Bricolage Grotesque brings character and personality to headlines and key interface moments. It's distinctive without being distracting, modern without feeling cold. It adds warmthβcritical when you're building trust in a new platform. The slightly playful letterforms reflect the joy of event-going without undermining professionalism.
DM Sans offers exceptional readability at smaller sizes, which is critical for an application where users need to quickly scan event details, dates, times, and pricing information. It's a workhorseβneutral enough to disappear when needed, but with enough character to maintain visual interest across long reading sessions.
The pairing creates natural hierarchy: display moments grab attention, body text sustains comprehension. It works across devices and sizes, ensuring consistency from desktop to mobile.
Component Language
Buttons: Fully rounded corners soften the interface and make it feel more approachableβimportant when reducing friction in the purchase process. Sharp corners can feel rigid; rounded feels inviting.
Icons: Duotone style adds visual interest without overwhelming the interface. The two-tone approach allows for subtle depth while maintaining clarity, and they scale beautifully across different sizes.
Inputs: Consistent styling with clear focus states. Error messaging appears inline, not in modals, keeping users in flow.



Layout Architecture
The interface layout features a transparent nav bar on the left and a white fixed-height inner body container where content stays put or scrolls within, without it diminishing at the bottom of the screen.
This approach creates a consistent spatial frameworkβusers always know where they are and how to navigate because the navigation remains constant while the content changes. The fixed container height also solves a common problem in web applications: content that awkwardly runs off the page or creates inconsistent scrolling behaviors.
Mobile Adaptation: On smaller screens, the left nav collapses into a bottom tab bar, keeping primary navigation accessible without sacrificing content space.

Onboarding layout

In-app layout
Phase 1: Attendee Application
(This is a slow rollout. Version 1 focuses on the attendee experience, with organizer and admin portals following in subsequent releases.)
Onboarding: First Impressions Matter
The onboarding experience sets the tone for the entire product relationship. Every additional field is a potential point of abandonment, so we're judicious about what we ask for.
Sign Up Flow
1. Account Type Selection
We start by having users select their account type (Attendee / Organizer). This fork in the road allows us to tailor the subsequent experience to specific needs and eliminates unnecessary steps.
Design Decision: Large, clear cards with illustrations showing what each account type offers. No jargon, just "I want to find events" vs "I want to create events."
2. Basic Information Entry
After selection, you enter basic information: name, email, password. That's it for this step. We defer anything non-essential.
3. Account Verification - The Magic Link
Here we implemented magic link verification instead of traditional OTP codes. This was deliberate:
More secure: No codes to intercept or phish
More convenient: Click a link vs. switching contexts to copy/paste
More reliable: Links don't expire as quickly; no transcription errors
Feels modern: Matches patterns from leading consumer apps
User Feedback: In early prototype testing, 7/8 users preferred magic links over traditional verification, citing it as "smoother" and "less annoying."
4. Complete Setup
Finally, you complete setup by filling in secondary detailsβphone number (optional), location preferences, event interests. By deferring these fields to this stage, we've already secured the user's commitment and reduced the psychological burden of signup.
5. Success & Auto Sign-In
Afterwards, you're redirected to success screens and automatically signed in. No tedious "now log in with the credentials you just created" step. You're ready to explore immediately.
For enhanced user experience and balance for business goals, users can explore events on the app from a CTA on the website without creating an account.
The Strategy
What Users Can Do Without Signing Up:
Browse all events
View full event details (description, location, pricing)
See organizer profiles
Use search and filters
What Requires Sign-Up:
Purchase tickets
Save events
Follow organizers
Access cart
Why This Works:
Users see the value before commitment. They're not gambling on whether the platform has events they care aboutβthey can verify first. The conversion gate sits at the moment of highest intent: when they're ready to buy. This approach respects user agency while creating clear incentive to sign up.
Expected Impact:
Based on competitor analysis, we anticipate this approach will increase sign-up conversion by 25-35% compared to gated browsing.
The Explore page is where users find their next experience. The challenge: surface relevant events without overwhelming users with choice.
Research revealed that the average ticket purchase flow takes 4-6 minutes and involves 7-12 form fields. Our goal: cut that in half.
3-Step Purchase Flow
Step 1: Selection
View all ticket classes (General Admission, VIP, etc.) with clear price and benefits
Select quantity for each class
Live summary panel on the right shows:
Ticket breakdown
Fees (clearly itemizedβno surprises)
Total
"Continue" button activates when at least one ticket is selected
Design Decision: The live summary eliminates surprises at checkout. Users know exactly what they're paying before entering any personal information.
Step 2: Recipient Data
This is where we diverge from traditional platforms:
If you're the only recipient:
Your information pre-populates from your profile
You see a confirmation message: "Ticket will be sent to [your email]"
All you do is click "Continue"
If you're buying for others:
Each ticket shows a toggle: "This ticket is for me" or "This ticket is for someone else"
For others, you fill in: Name and Email. That's it.
Why This Works:
Research showed that 45% of users buy tickets for others. Asking for full details creates friction and abandonment. Most users don't have (or want to enter) their friend's full contact information. Name and email is sufficient for ticket delivery.
Step 3: Payment
Saved payment methods display first (if user has any)
Add new card option
Payment processed securely
Instant confirmation screen
Tickets emailed immediately
Auto-redirect to Upcoming tab
The entire flow, from clicking "Buy Ticket" to having tickets in hand: under 2 minutes for returning users, under 3 minutes for first-time purchasers.
The Upcoming tab reduces the time it takes users to find purchased tickets and access event information.
Why This Matters
"Where are my tickets?" was the second most common question in user interviews. By making Upcoming a top-level nav item (not buried in Profile or Settings), we prioritize access to the information users need most urgently as event day approaches.
The History tab serves three purposes:
Personal archive of events attended
Feedback mechanism for organizers
Ticket status tracking
Design Decision:
Making feedback frictionless increases submission rates. The form is already open; all you need to do is share your thoughts. This benefits organizers (who need feedback to improve) and future attendees (who rely on reviews to make decisions).
This nav emerged from a key research insight: in many communities, people don't just attend eventsβthey follow organizers they trust.
Three navigators: Profile, Preferences, Settings. Each serves a distinct purpose.
Challenge 1: Ticket Purchasing for Groups
Problem: Research showed 45% of users buy tickets for others, but competitor platforms make this painfulβrequiring full contact details for each recipient.
Initial Approach: We considered a "group checkout" flow where a primary purchaser enters abbreviated info for everyone.
What We Learned in Prototyping: Even this was too complex. Users don't want to fill forms; they want tickets.
Final Solution: Radical simplificationβif buying for yourself, one click. If buying for others, name + email only. Tickets get delivered; that's what matters.
Trade-off: We sacrifice some organizer data (they get less info about attendees) for user experience. But we believe the increased conversion and user satisfaction outweighs this.
Challenge 2: Building Trust in a New Platform
Problem: Users in our target markets have been burned by unreliable platforms and scams. How do we build trust quickly?
Solutions Implemented:
Transparent pricing: Show all fees upfront, never at checkout
Organizer credibility signals: Ratings, follower counts, event history
Secure payment indicators: Clear badges showing secure processing
Customer support: Accessible help center and live chat
Ongoing Work: We're exploring verified organizer badges and buyer protection guarantees for our full launch.
Challenge 3: Accessibility Across Literacy Levels
Problem: Our user base has varying levels of technical and reading literacy.
Solutions Implemented:
Icons + text labels: Never rely on icons alone
Simple language: Avoid jargon
Visual hierarchy: Important actions are visually obvious
Error messages: Plain language, with clear fix instructions
Minimized text entry: Use selections, toggles, and defaults wherever possible
What Worked
User research drove everything - The insights from interviews directly shaped features like simplified recipient data and the Upcoming tab
Systematic design thinking - Using ChatGPT for architecture ideation helped identify edge cases early
What I'm Proud Of
Designing TicketWaze reinforced that good design isn't about following best practices blindlyβit's about understanding context deeply and making intentional choices. The simplified ticket purchase flow isn't innovative because it uses new patterns; it's innovative because it questions whether the old patterns serve our users.
Organizer Portal focuses on giving event creators the insights and tools they need to run successful events:
Analytics: Attendance patterns, ticket sales velocity, revenue tracking
Event Management: Create, edit, duplicate events with rich content options
Financial Dashboard: Payout schedules, transaction history, fee breakdown
Admin Portal provides platform oversight:User Management: Monitor accounts, handle disputes, enforce community guidelines
Transaction Monitoring: Track payment flows, identify issues, process refunds
Platform Health: Key metrics on events, users, revenue, and engagement
Both are designed with the same attention to user needs and cultural context that shaped the attendee experience.
Full case studies for these experiences coming soon
TicketWaze isn't just a ticketing platformβit's cultural infrastructure. Every decision, from the naming to the navigation structure to the way we handle ticket purchases, reflects our commitment to serving diverse communities with experiences that feel personal, intuitive, and culturally resonant.
We're not just moving tickets; we're facilitating meetings, in the truest sense of the word. We're creating spaces where organizers can thrive, attendees can discover, and communities can gather.
The real measure of this work will come when it launches and people use it to create memoriesβwhen someone discovers an event that changes their perspective, when an organizer sells out their first show using the platform, when a community comes together around something meaningful.
That's what we're building toward.


