Demo tooling & operations

Context

Flagship demos and partner reviews depend on fast iteration on map styles, scene data, and packaging. As volume grew, informal workflows made Map Design a bottleneck: every credible demo waited on people who carried years of unwritten practice.

Problem

Demo support mixed chat threads, ad-hoc files, and tribal knowledge. Preparing a scene meant long manual loops on data cleanup, validation, and packaging — hard to parallelize, and rough on specialists who had not inherited that informal know-how. The goal was not “shave seconds off a click,” but an environment where demo teams could produce on a predictable cadence.

Discovery

I interviewed demo specialists and Map Design leads to map where time actually went: not “missing a button,” but repeated manual loops on map data editing, style validation, and scene packaging. Junior operators could not inherit years of practice from chat archives.

“We know how to make it look right—we just cannot parallelize how we get there.” — Demo ops lead, early discovery

Alternatives & trade-offs

Three rounds of lightweight prototypes (browser helpers, schema editors, regional style presets) were tested with the teams that would own maintenance. We rejected a heavy “demo OS” that would need its own ops team. We cut scope where tools duplicated Jira or Mapbox Studio, and doubled down where non-engineers needed safe editing surfaces without breaking production styles.

What shipped

Browser-side helpers for map data where they remove hours of friction; Building Box and related flows for repeatable scene packaging; Style Distillery and validation so issues surface before review — not on stage.

Onboarding patterns and integration kits so more work is self-serve: encoding how experts work so distributed demo teams are not blocked on a single gatekeeper. Where flagship demos needed 3D assets or custom steps (e.g. automotive showcases), clear contracts with content and maps teams.

Outcome

Shorter turnaround for common requests, fewer broken demos at review, clearer ownership between tooling, content, and demo teams. Internal tools are used daily across three org lanes (Map Design, Demo Ops, 3D Content). Common prep that once took days of back-and-forth now closes in hours for repeat scenarios — and scales with headcount instead of calendar time.