Internal Product · Shipped · In Active Use

Story Share

Transforming event pages into a scalable social-content engine.

Organization
Lincoln Center for the Performing Arts
Status
Launched August 2026
Role
Product and Design Lead
Period
August 2026 launch
Story Share shown across an event page, mobile sharing flow, and finished social graphic
One connected path from event information to audience-ready content

The brief

Turn event information into audience-ready content.

Polished event graphics depended on repetitive manual production, while audiences had no simple way to create them from an event page. Story Share connects existing event data, approved imagery, and design rules in a self-service sharing experience.

Launch scope & estimated operational value

~27
shows in the initial rolloutAugust 2026 launch
100s
staff hours estimated to be recoveredEstimated repeat-production savings · not measured results

01 / Audience experience

Offer sharing at the point of interest.

I placed Story Share inside the existing event-page experience. People can preview an event-specific graphic and share or download it without assembling information or making design decisions.

The responsive flow keeps the action close to the performance that prompted it. The same capability gives internal teams a repeatable source of branded assets.

Integrated at the point of interest

The event page becomes both the source and the invitation to share.

Desktop Lincoln Center event page with Story Share actionMobile Story Share panel with download and social sharing actions
Responsive sharing within the existing event experience

02 / Visual system

Translate design judgment into dependable rules.

Titles vary in length, imagery has different focal points, and dates and subtitles carry different amounts of information. A useful automated output has to account for those variations.

I defined rules for cropping, typography, metadata, spacing, and brand presence. Structured event information moves through a constrained visual system, producing a considered result without a designer laying out every graphic.

Desktop event page showing the Story Share panel alongside event contentGenerated vertical Lincoln Center Presents social graphic
Rules become outputThe event’s content and imagery are transformed into a polished, brand-aligned asset.

03 / Delivery judgment

Make the exception path part of the product.

Complex date ranges emerged as a challenge before launch. Expanding support immediately would have added development work and put the August timeline at risk.

I established an exception path: events that could not be represented accurately could temporarily disable Story Share and use a custom graphic. That protected public information and let the standard experience launch.

Standard event

Event data + approved imagery

Shared rules for layout and content

Generated social graphic

Exceptional date or content needs

Event cannot be represented accurately

Temporarily disable Story Share

Custom graphic
The launch decision: automate the standard path and preserve an accurate exception path.

Outcome & perspective

A focused product with value on both sides.

Story Share launched for Lincoln Center Presents in August 2026, with an initial rollout designed for approximately 27 shows. Eligible event pages can generate social assets through one shared system.

The operational model is estimated to recover hundreds of staff production hours. Long-term adoption and conversion data are still developing; measurement includes generated assets, completed shares and downloads, referrals, and manual production avoided.

The opportunity was to connect existing capabilities: event content, approved imagery, design standards, and an audience motivated to share.