Booking & Operations Platform for a Digital Amusement Park

I. System Context & Constraints

Technical reality: A digital amusement-park brand was entering a new market and needed more than a brochure site — it needed an operational system. Tickets had to be sold online, guests checked in and out at the venue, and sales reconciled by staff, all from one platform rather than a patchwork of manual logs and a separate payment tool.

Director’s constraints: A market-launch date anchored the timeline, the experience had to read as playful and on-brand while staying operationally rigorous, and the booking lifecycle (reservation → check-in → check-out) had to map cleanly onto how floor staff actually work so the system wouldn’t be bypassed on busy days.

II. Critical Path & Architectural Choices

I split the work into a marketing surface and a transactional core sharing one data model. The booking system carries a reservation through its full lifecycle — purchase, on-site check-in, and check-out — so a single record is the source of truth from sale to floor. Online payments are integrated directly into the booking flow, removing the manual reconciliation step that fragments most venue operations.

Behind it sits an admin panel for managing bookings, viewing sales data, and tracking customer clock-in / clock-out. Keeping the customer storefront and the staff back office on the same backend means floor activity and revenue stay in sync in real time instead of being stitched together after the fact.

III. Governance, Risk & Team Topology

I directed product, design, web, and engineering teams through a milestone plan that sequenced the marketing site, the booking and payment core, the check-in/check-out lifecycle, and the admin back office — deliberately ordering revenue-critical flows ahead of nice-to-haves so a slip would never threaten the ability to sell tickets at launch.

Risk centered on money and the live venue: payment flows and the booking lifecycle were staged and reviewed before go-live, and the admin tooling was validated against real operational scenarios (a busy day, a no-show, a refund) rather than only the happy path.

IV. Quantifiable Outcomes