Audience Product · Coded Prototype · In Development
Global Event Discovery & Calendar
Reimagining how audiences discover everything happening across Lincoln Center.
View working prototype- Organization
- Lincoln Center for the Performing Arts
- Status
- In Development · Launching November 2026
- Role
- Product and Design Lead
- Period
- In development · November 2026 launch

The brief
Making a complex campus easier to discover.
Lincoln Center’s calendar was a critical audience entry point, but years of accumulated interface decisions had made its breadth difficult to navigate, especially on mobile. I reframed it as an audience product: a welcoming path from curiosity to a relevant performance or experience.
Audience context · existing scale, before the redesign
- 240K
- active calendar users2025 baseline
- ~1M
- calendar-content interactions2025 baseline
- 1.4M
- outbound organization clicksBroader LincolnCenter.org ecosystem · 2025
01 / Mobile interaction
Make choosing a date a focused task.
Two cross-functional workshops, journey mapping, taxonomy exercises, and stakeholder conversations revealed different starting points: a date, an art form, a price, or simply something interesting to do.
I designed date selection and filtering as focused mobile interactions. A dedicated panel gives those decisions room, while visible filter states help people understand the results they are seeing.
Mobile-first interaction
Useful controls, designed for thumbs rather than shrunk from desktop.
Date selection and filtering become focused, legible tasks on the smallest screen.

02 / Directed discovery
Let audience intent shape the results.
Free events and Date Night provide useful shortcuts through a large inventory. Strong imagery makes the results inviting; dates, venues, and active filters keep the experience practical.
The system balances one campus-wide experience with clear attribution to the organization presenting each event. Those distinctions remain visible as audiences move toward event details and ticketing.

03 / Ways to browse
Support people who start with the schedule.
Imagery-led discovery and a dense calendar view serve different needs. I kept both within the same responsive system, with shared filtering and date navigation rather than separate products.
The prototype’s functional interactions let stakeholders evaluate information density, mobile behavior, and content requirements directly. It uses representative event data; production API integration remains part of delivery.

Outcome & perspective
A shared direction, moving into development.
The prototype established the vision and requirements for a formal development initiative scheduled to launch in November 2026. It connected strategy to concrete decisions about event metadata, responsive behavior, reusable components, and the relationship with the homepage.
The audience figures above describe the existing ecosystem. Post-launch measurement will assess discovery, event-detail visits, ticket referrals, filter use, and mobile task completion.
The central design judgment was deciding which complexity the system should handle so audiences would not have to.