Virtual Tour Platform Experience

Establish a reusable virtual tour pattern — navigation, hotspot types, analytics — that could carry different stories without reinventing delivery each show season.

The hard parts were rarely just creative. They were floor reality, feasibility and the people who had to run it live.

• Reuse vs. brand uniqueness

  Each client wanted distinct atmosphere while sharing engineering costs. The platform needed flexible skinning without breaking measurement consistency.

• Capture-to-publish workflow

  Field teams worked under tight pre-show deadlines. Hotspot taxonomy had to be teachable to non-developers publishing under pressure.

• Stakeholder dashboards

  Marketing wanted depth and completion funnels, not vanity views. Event taxonomy had to align across tours for portfolio reporting.

I joined to define the tour framework — scene templates, hotspot classes, and analytics hooks — used across multiple congress deployments. I documented the playbook account teams could reuse.

Standardized navigation verbs and hotspot depth levels while leaving visual and narrative layers open. Paired each deployment with a minimal reporting set leadership actually read.

Visitors experienced brand-specific immersive spaces with familiar navigation cues. Teams published faster, and post-show reviews compared starts, depth, and completions on a shared vocabulary.

Project managers for timelines, content strategists for story mapping, and client analytics leads for KPI alignment.

Supported remote tuning during load-in weeks — default views, idle loops, and kiosk timeouts — without flying engineers to every hall.

Platforms win when producers feel faster, not constrained. I measure this work by how calmly a PM publishes hotspots two nights before open — that is when reuse either pays off or dies.