← All worknow showing ( 06 ) / 24

Nobody was finding the right events

Nobody was finding the right events key visual

stackup's events ran on notion docs, typeform and google sheets. i designed one platform that's easy to attend and gives organisers real control.

Client StackUpDuration 3 months, 2024Role product designerTools figma, figjam, notion, clickup
( 01 ) Challenge

events were happening, just haphazardly.

organisers cobbled it together from docs and spreadsheets. attendees couldn't find the events meant for them, and organisers rebuilt every event from scratch. the ask was one platform. the hard part was making it simple for attendees and flexible for organisers without it feeling like two products.

↗︎↑ mostly black & white. clarity first, on purpose.
( 02 ) What organisers said

the feedback was operational.

control over how registration works( 01 )
an optional approval step before someone gets in( 02 )
reusable templates, so nobody builds the same event twice( 03 )
↖︎↑ gumroad, eventbrite, substack: structure, but light.
( 03 ) Smallest complete version

i always start with the minimum that still feels whole.

for attendees that meant getting from finding an event to registering with no dead ends. organisers needed more. some events are open, others need approval or a custom form. so i designed modular pieces that assemble differently per event type, and kept creating and moderating close together so organisers don't lose their place.

( 04 ) Vocabulary

definitions came before layouts.

what counts as an event on stackup? what states can it be in: draft, live, ended, gated? is a participant the same as an attendee? the whole team had to agree on that before anyone drew a screen. kickstarter's campaign states helped. then i mapped everything in figjam, including edge cases like rejected signups and manual additions.

event ecosystem map in figjam
event ecosystem map in figjam
( 05 ) Admin

fewer modals.

repeatable patterns to keep the admin side manageable( 01 )
minimal navigation with a clear way forward and back( 02 )
stacked navigation and inline actions for approvals and exports( 03 )
( 06 ) Layers

with the pm, i split the work into three layers that could each move on their own.

core: event creation, open and gated registration, public event pages( 01 )
admin: participant views, approvals, manual additions, csv export( 02 )
extras: bookmarking, status tags, social sharing( 03 )
→↑ designed bookmarks early. power users need them.
( 07 ) What it became

it browses like a feed.

attendees find events that match their interests and sign up, whether it's a 10-person workshop or a 500-person conference. organisers set events up quickly and decide how registration works. they can see every participant and export the list when they need it.

the events homepage, then the admin list and drafts
Next track →
From lurking to participating