Work

Designing Events That Last: Event Creation & Ticketing for OpenWav

Timeline:

2 months to MVP launch

Timeline:

2 months to MVP launch

Timeline:

2 months to MVP launch

Role:

Lead UX Designer (sole designer)

User Researcher

Role:

Lead UX Designer (sole designer)

User Researcher

Role:

Lead UX Designer (sole designer)

User Researcher

Collaborators:

Product Manager

Development & Business Teams

Collaborators:

Product Manager

Development & Business Teams

Collaborators:

Product Manager

Development & Business Teams

Tool:

Figma

Tool:

Figma

Tool:

Figma

Project Overview

What is the project

Turning one-off events into lasting fan communities.

OpenWav helps indie artists earn from events, merch, and content. I redesigned how events are created and joined.

Shipped to 5% of users

↑ 23% engagement

Events: creators’ #1 monetization pick

The Problem

Hosting was a chore, and events didn’t build anything lasting.

What existing OpenWav creators told us:

📝

Too many forms

Setting up an event was long and complicated.

🔕

Missed updates

Attendees missed changes, and the experience suffered.

💸

Free events don’t pay

They drive traffic but earn nothing.

🎟️

Paid events feel empty

They make money but lack community and soul.

Target Audience

Events end. The connection ends with them.

Events end. The connection ends with them.

James

Host · Indie artist

Cindy

Fan · Music lover

“Setting up an event takes 8–10 hours—and afterward, I never hear back from the people who came.”

— James, indie artist who hosts events

8–10 hrs

Spent on setup & marketing

77%

Of hosts get no attendee feedback

Project Goal

What if an event were the start of a community, not the end?

Lack of engagement was the #1 reason attendees didn’t join more events. Events aren’t the end; they’re the beginning of a community.

The Solution

Create an event in under a minute.

Create an event in under a minute.

Every event gets a built-in chat that keeps fans close.

Ideation

How might we connect fans before, during, and after?

Three directions I brought to the team.

BEFORE

✓ Shipped in MVP

💬

Event chat after RSVP

Fans join a group chat the moment they RSVP.

Fans join a group chat the moment they RSVP.

DURING

Phase 2

⚡

Live engagement tools

Polls and live Q&A while the show is happening.

Polls and live Q&A while the show is happening.

AFTER

Phase 3

🧭

Event recommendations

Suggest next events from chat connections.

Suggest next events from chat connections.

BEFORE

✓ Shipped in MVP

💬

Event chat after RSVP

Fans join a group chat the moment they RSVP.

DURING

Phase 2

⚡

Live engagement tools

Polls and live Q&A while the show is happening.

AFTER

Phase 3

🧭

Event recommendations

Suggest next events from chat connections.

Event Creation

Information Architecture

Only 5 fields to publish.

Only 5 fields to publish.

“I want to create an event as easily as possible.” —James, indie music artist

“I want to create an event as easy as possible.” —James, indie music artist

“I want to create an event as easy as possible.” —James, indie music artist

01 · Overview

Mandatory first, optional next, advanced tucked away.

Fields are grouped by how often hosts actually need them.

Mandatory

5 fields

Cover image

Name

Date & time

Venue

Category

Optional

2 fields

Description

Ticketing

Advanced

Collapsed ▾

Co-host

Private event

Limited capacity

02 · Mandatory

The 5 essentials, up top.

Cover image, name, date & time, venue, and category are all it takes to publish.

Mandatory

03 · Optional

Extras come right after.

Description and ticketing help promote the event, but never block it.

Optional

04 · Advanced

Rare settings stay collapsed.

Co-host, private event, and limited capacity are there when needed, out of the way when not.

Advanced

Mandatory

5 fields

Cover image

Name

Date & time

Venue

Category

Optional

2 fields

Description

Ticketing

Advanced

Collapsed ▾

Co-host

Private event

Limited capacity

Design Challenge

Ticketing: a second step, or one long form?

Ticketing: a second step, or one long form?

01 · Option 1

2-step flow (my proposal)

Basics first. Ticketing only appears if “Paid Event” is on.

2-Step

02 · Option 2

One-sheet form (PM & dev)

Everything on one page—simpler to build.

One Sheet

03 · Usability test

Splitting the form beat one long page.

“There was too much going on. I panicked and guessed,” one tester said of the long form. No one abandoned the 2-step flow, so we shipped it.

“There was too much going on. I panicked and guessed,” one tester said of the long form. “There was too much going on. I panicked and guessed,” one tester said of the long form. No one abandoned the 2-step flow, so we shipped it.

Usability test · 6 first-time hosts

2-Step

Shipped

Completion rate

100%

Avg. time

1:22

“Breaking it up helped me focus. I felt less rushed.”

One-Sheet

Completion rate

67%

Avg. time

2:13

“There was too much going on. I panicked and guessed.”

2-Step

What Testing Revealed

Creators wanted speed, and to look like themselves.

Creators wanted speed, and to look like themselves.

The same test sessions surfaced two more problems.

⏱️

40%

of setup time went into picking a cover image.

“My events look the same as everyone else’s. Where’s the ‘me’ in this?”

Full-time creator, usability test

So we redefined the design goals:

Effortless hosting. Events that grow into communities.

⚡

Fast by default

Quick setup, flexible when needed.

🤝

Built for connection

Events live on before and after the show.

🎨

Room for personality

Visuals that show each creator’s vibe.

⚡

Fast by default

Quick setup, flexible when needed.

🤝

Built for connection

Events live on before and after the show.

🎨

Room for personality

Visuals that show each creator’s vibe.

Design Solution

Fast and personal.

Fast and personal.

Pick a theme in one tap, or upload your own artwork.

Pick a theme in one tap, or upload your own artwork.

01 · Explorations

Three ways to balance speed and personality.

The team loved themes + uploads in one place; the MVP launched with five themes.

02 · Themes

One-tap themes for casual events

A pre-designed theme gets a small party live in seconds.

03 · Custom uploads

Custom uploads for ticketed shows

When visuals matter, hosts upload their own artwork.

04 · Event form

Ordered the way hosts think

When → where → what → tickets. A live map catches venue mistakes.

05 · Design Challenge

Share first, then chat

PM wanted to send hosts straight into chat. But right after publishing, hosts want to share. We agreed on one screen: confirm it’s live, make sharing easy, then introduce chat.

Registration

Fan Needs

Ease FOMO, keep fans informed, keep the excitement going.

“As a music lover, I want to meet like-minded people through events and support my favorite artists!” —Cindy, indie music fan

“As a music lover, I want to meet like-minded people through events and support my favorite artists!” —Cindy, indie music fan

Design System

One system, one experience for hosts and fans.

I built 50+ reusable components with 180 variants, so creating, joining, and chatting all share the same buttons, RSVP states, headers, and navigation.

Buttons · default, on tap, disabled

RSVP status

Creator header + follow

Text fields · every state

Chat entry

Bottom navigation

Dropdown + location list

Drawer · 50%, 75%, 90%, modal

Design Impact

Events became the #1 monetization method creators want to use on OpenWav.

↑ 23%

Engagement rate

↑ 46%

Satisfaction rate

↑ 17%

Booking completion

↑ 12%

Repeat attendance

What's Next

Ship small, learn, then grow.

Phase 1 tested one question: will fans actually use event chat?

PHASE 1

Shipped · 5% users

Validate event chat

Ship the core flow to 5% of users and see if fans actually use event chat.

Event creation · RSVP · Auto-generated chat

PHASE 2

Up next

Boost live interaction

Give creators more control over chat, and add polls and live Q&A for the show.

Flexible chat · Polls · Live Q&A

PHASE 3

Later

Grow communities

Turn chat connections into event recommendations and lasting fan circles.

Friends-of-friends recommendations

Project Takeaways

Build the system early — shared components kept host and fan flows consistent as features grew.

Let data settle debates — six quick test sessions decided 2-step vs. one-sheet.

Follow the user’s next move — new features land better when they don’t interrupt it.

Build the system early — shared components kept host and fan flows consistent as features grew.

Let data settle debates — six quick test sessions decided 2-step vs. one-sheet.

Follow the user’s next move — new features land better when they don’t interrupt it.

More work

@ 2024 Portfolio

@ 2024 Portfolio

@ 2024 Portfolio