Owning end-to-end UX for an event management platform
As Platform UX Designer at MyConferenceSuite, I owned the Event Portal domain end-to-end — from flow to shipped feature — for an event management platform used to run large conferences.
Overview
One domain, owned start to finish.
MyConferenceSuite is an event management platform used to run conferences — speaker scheduling, sessions, attendee logistics. I owned the Event Portal domain: the surface event organizers and speakers use to manage their side of a conference.
Context
Two audiences, one portal, real deadlines.
Event platforms serve two very different audiences at once — organizers running the show and speakers or attendees trying to find their session on time. Owning a full domain end-to-end meant being responsible for both the UX and whether the feature actually shipped, not just how it looked in a file.
Constraints
No safety net, and a date that doesn't move.
Small team, real ownership
As the platform UX designer for this domain, there wasn't a second designer to hand off to — I owned it start to finish.
Live events, fixed deadlines
Conferences happen on fixed dates. A feature that isn't ready by the event doesn't ship "later."
Two audiences, one portal
Organizer workflows and speaker/attendee workflows had to coexist in the same domain without confusing either group.
Developer efficiency
With no dedicated design-ops layer, flows had to be structured clearly enough that engineering could build without repeated clarification.
Process
Design, ship, repeat.
- Owned the end-to-end UX for the Event Portal domain — designed and delivered digital product features directly to production.
- Created Figma-based flows, screens, and prototypes structured to improve developer efficiency, not just look finished.
- Facilitated workshops and cross-functional alignment sessions to define user requirements before design started.
Key decisions
Designing for delivery, not just the file.
Structured for handoff, not just polish
Built flows and prototypes specifically to reduce back-and-forth with developers, since there was no separate design-ops layer to catch gaps.
Requirements before design
Ran requirement-defining workshops up front rather than iterating blind, given the fixed-deadline nature of live events.
Visually distinct modes for two audiences
Kept organizer- and attendee-facing flows visually distinct within the same portal so each audience always knew which mode they were in.
Where it landed
Shipped, on schedule, to production.
- Shipped Event Portal features directly to production supporting real, scheduled conferences.
- Owning a full domain early in my career built the habit of designing with delivery in mind, not just the screen.
Reflection
What I'd tell another designer facing this.
Owning a domain end-to-end — instead of handing off a flow and moving on — is where I learned that a design isn't finished when the file looks right. It's finished when it ships and holds up under a live deadline.