Head of Product
9/14 - 7/16

Responsible for defining requirements and designing features of a multi-platform venue management and ticket sales platform.

  • Point-of-sale (POS) app design helped win clients such as Museum of Modern Art (MoMA) and New Museum in New York; DeYoung Museum and Red-and-White Fleet in San Francisco.

  • Redesigned product to align with real-world, complex B2B2C ticket sales flows

  • Designed dynamic ticket pricing model which eliminated, at one client, the need for 400+ ticket definitions. 

  • Designed and implemented a consistent template-instance hierarchy and update schema to support multiple use c

Venue and event administration
ACME clients are typically venues such as museums, theaters, and event spaces which host concerts, provide tours, and other activities which draw paying attendees. An event planner can schedule an event, reserve facilities, assign personnel and equipment, price and sell tickets all from the ACME administration portal.

Ticket and merchandise sales
When an event is spec’ed on the backend it automatically appears on the venue’s site and on the POS application. Ticket prices are set based on the venue’s dynamic pricing model.

ACME model use case inconsistencies
The ACME platform uses templates to generate instances and series of events, asset management assignments, and dynamic ticketing services. A key use case is to allow clients to edit templates as well as instances of repeating events. Changes might include times, locations, personnel, pricing, and other factors. Clients might want template changes to apply to all generated instances or only to newly-generated instances. Conversely, clients might want changes to an instance to propagate back up to the master template.

However, it wasn’t clear how any of these edits would really propagate through the system.

So, I designed a complete template/instance update model.
VIEW FULL SPEC ▸

This IA diagram shows the relationship between a repeating event schedule and a single instance of an event generated by the schedule (this is only 25% of the entire diagram).