UPGATHER

Smarter Events. Connected Experiences.

I designed connected event-creation and operational workflows, helping teams organize speakers, registration, content, and publishing around a clear next step.

View Upgather portfolio View prototypeMy role: Principal Product Designer · Enterprise SaaS

PROJECT OVERVIEWCLIENTUpgather

Upgather

A connected event management platform for creating, managing, and publishing events.

The platform brings speakers, organizations, invitations, content, and publishing into one event workflow, so teams can see their next step.

I worked across product design and engineering to shape event creation, operational workflows, analytics, and reusable design-system patterns.

I focused on making complex event work feel clear, connected, and easier to act on.

Project: Event management platform
My role: Principal Product Designer · Enterprise SaaS
Focus: Event workflows · analytics · design systems
Project scope: Event creation · operational workflows · shared platform patterns

01 /Research

The challenge & evidence.

The work focused on making connected event tasks easier to navigate. The supplied materials do not include validated research findings.

Event work connects speakers, organizations, invitations, content, and publishing.

Guided creation and ongoing management need distinct starting points.

Draft states and contextual panels make operational work easier to navigate. These are design directions, not measured usability findings.

Project gallery

3 images

Upgather event operations architecture — Design focus: faster event setup, better attendee management, cleaner data, and simpler day-to-day operations.

Event operations architecture & critical flows — A structured view of Upgather’s product areas, core workflows, and priorities for event operations.

Event owner: create and publish an event — End-to-end journey from starting or duplicating an event through setup, registration, publishing, and ongoing management.

02 /Strategy

The design direction.

Help operators start event and editorial work, see what needs attention, and resume unfinished tasks.

Create

Give event setup a clear start, with reusable layouts and drafts.

Manage

Use operational tables, AG Grid, and contextual panels for connected workflows.

Maintain

Connect hands-on React interface work with Figma components, Storybook, and engineering review. Automation remains an evolving workflow.

ANALYTICS UX · FROM DATA TO DECISIONS

Make event performance easier to find, understand, and act on.

Designed an analytics experience that helps event teams move from high-level performance metrics to actionable insights. I mapped user journeys, defined the information architecture, and explored low-fidelity wireframes before refining dashboard interactions, reporting, and filtering.

01Discover performance
02Filter and compare
03Drill down
04Take action or share

INFORMATION ARCHITECTURE

Analytics working board — Planning board mapping event-team goals, users, pain points, key metrics, dashboard structure, filters, drill-down, and reporting. The notes describe design direction, not validated research findings.

LOW-FIDELITY EXPLORATION

Analytics dashboard wireframe — Low-fidelity dashboard structure exploring performance metrics, trends, event status, and operational data.

REPORTING INTERACTIONS

Analytics reporting wireframes — Wireframe exploration of date filters, KPI detail, reporting, comparisons, and export/share flows. Values shown are illustrative.

The supplied boards and wireframes show design exploration. The sample metrics are illustrative; usability findings and production analytics are not supplied.

Illustrative dashboard data and measures to validate

The figures below are sample data from the event-manager prototype, not results from this project.

Measures to validate

These would need product analytics or usability testing.

Creation flow completionLayout reuse and draft recoveryTime and errors in operational tasks

ILLUSTRATIVE EVENT-SITE DATA · SEP 2026

A snapshot from the event manager

Prototype dashboard sample as of Sep 22, 2026.

Registrations

Selected events · past 30 days

570

Event readiness

Across 24 accessible events

73%

Speakers78%
Agenda71%
Sponsors74%
Registration64%
Website80%

Website status

Selected events · 24 total

24events

Live11
Needs review7
Draft5
Offline1

These are illustrative event-manager prototype figures, not verified outcomes of this Upgather project. Creation completion, layout reuse and draft recovery, and operational time or errors still need product analytics or usability validation.

03 /Design decisions

Three decisions that clarified the workflow.

Decision 01

Give creation a clear start

Separated guided event setup from ongoing management: choose a new layout, reuse an existing layout, or save a draft before returning to the operational workspace.

See upgather event operations architecture

Decision 02

Make complexity navigable

Used AG Grid and contextual panels for operational work, with consistent draft states and deliberate minimize behavior.

See event operations architecture & critical flows

Decision 03

Close the design-to-code gap

Worked with engineering on consistency and change tracking across Figma, Storybook, and the repository. Automation remains an evolving workflow.

Review related research & evidence

Decision 04

Make event insights actionable

Designed an analytics direction that moves from key performance metrics to filters, comparisons, drill-down reports, and a clear next step. Values shown in the supplied concepts are illustrative; measured outcomes are not available.

Explore the analytics UX direction

EVENT CREATION PATHS

Three clear ways to begin.

Choose the starting point that fits the event.

Create a new layout

Start a guided event setup with a new page layout.

Reuse a layout

Use an existing layout as a starting point rather than rebuilding the page.

Save a draft

Preserve unfinished setup and return to the operational workspace.

Conceptual design direction; production results and usability validation are not supplied.

04 /Design system

From design system to production components.

DESIGNING ONCE. BUILDING CONSISTENTLY. SCALING ACROSS THE PLATFORM.

I developed Upgather Design System V2 and partnered directly with design-system engineers to manage the work from design definition through implementation. I also built React interfaces, connecting hands-on implementation with our Figma component library, React specifications, and Storybook documentation. This gave design and engineering a shared reference for consistent product UI.

Figma libraryReact specsStorybook

A REUSABLE TOOLKITComponents designed for real workflows

Core controls

Buttons, form controls, and their variants and states.

Operational data

Registration tables, status badges, and row actions.

Workflow patterns

Side panels, dialogs, and connected event-management flows.

MY FOCUS

Component architecture · design-to-code collaboration · accessibility · scalable engineering handoff

FROM FIGMA TO STORYBOOK

One system. A shared language for design and engineering.

Select the visual to inspect

Upgather design system to React Storybook — A visual overview of the Figma component library, shared patterns, and Storybook-style component documentation.

AI GOVERNANCE · MY APPROACH

AI can assist. Event teams stay accountable.

My governance approach for the AI direction starts with a clear boundary: help teams understand and prepare work, while keeping review and publishing decisions with the people responsible.

Separate suggestions from actions

For the North Star AI direction, I would label generated insights and drafts, let an event manager inspect and edit them, and require an explicit action before publishing or sending.

Proposed human-review boundary

Respect access and context

I would define with Product and Engineering which event, organization, and attendee information each role can use. AI assistance should follow those permissions and show the context behind a suggestion.

Proposed data safeguards

Make behavior reviewable

My React, Figma, and Storybook work provides a shared interface foundation. For AI features, I would extend that review to loading, failure, correction, and approval states, with agreed evaluation criteria before release.

Build foundation → AI validation

React and design-system contributions are documented. The AI safeguards describe the proposed North Star approach, not verified production controls or a completed governance program.

05 /Outcomes

The experience & what comes next.

FINAL EXPERIENCE · ANALYTICS

A clearer view of event health and performance.

The strongest supplied dashboard exploration brings key metrics, trend reporting, filters, drill-down details, comparisons, and sharing into one analytics experience.

Upgather analytics experience exploration — Supplied dashboard and reporting concept. Interface values are illustrative; this image does not establish that the screen shipped or that the metrics were measured.

This is a design exploration, not a production screenshot. No validated analytics outcomes were supplied.

Documented contribution

Guided creation, reusable layouts, contextual panels, and shared system alignment.

The event-creator and system-alignment work are ongoing design initiatives. Integration concepts and automation plans are distinguished from completed production capabilities.

Quantitative launch results are not available in these project notes.