A00CWWC99J00ZJJ/FFL33,UU,RRT··BBBA552..6RRCAA-TING SYSTEM

Most experiential work is judged on the photograph at the end. The work that decides whether the photograph happens at all is the part nobody sees: the briefing logic, the stakeholder map, the catalog of approved modules, the build pack the field uses, the install QA loop, the debrief format.

This case study is that layer. It is the operating system I built underneath three years of BAT North America activation work. The diagrams are the deliverable. The photography of the resulting events lives in the McLaren and BAT case studies next to this one.

Every brief arrived in the same shape: a regional GM, a launch window, a venue list, a budget number, and a sentence about brand. Nothing in there was a design problem yet. Everything in there was an alignment problem pretending to be a design problem.

The first artifact in the system is an intake workshop. Two hours, eight participants, one format. By the end of it we have separated what the sponsorship is supposed to do (the jobs) from what it is supposed to look like (the surface). Design does not start until that separation exists.

The second failure mode in regulated-category work is decision drift. Compliance gets pulled in late, the regional GM gets pulled in too early, the sponsor partner gets surprised. The stakeholder map is the artifact that prevents that. It is built once per market and reused across every brief in that market.

The center role is the part this map is really about. There is one named owner of conceptual continuity, and that owner travels with the brief from intake through install. Every other role can rotate without the work falling apart. That role cannot.

Once intake and alignment are clean, the work goes into the catalog. The catalog is not a moodboard and it is not a slide deck. It is a finite set of approved activation modules: threshold, age gate, education kiosk, product trial bay, reaction mechanic, simulator pod, hospitality seating, leaderboard, take-home extension.

Each module is designed, costed, regulator-approved, and fabrication-tendered exactly once. The field never redesigns a module. The field assembles a kit out of the modules that fit the venue.

Most concept loss happens at the wall between design and fabrication. The remedy is a single artifact that crosses that wall: a build pack containing drawings, BOM, materials spec, install sequence, and a compliance annex. Nothing else moves across.

The build pack is the contract. If the fabricator delivers to the pack, the install matches the rendering. If the field requests a change, the change goes back through the catalog, not around it.

Install day is when the system either earns its keep or quietly loses it. The QA artifact is not a punch list of defects. It is a one-page side-by-side: the rendering on the left, the install on the right, annotated with anything that drifted. The owner signs it before the venue opens.

Drift is normal. The point is that drift is named, owned, and routed back into the catalog so the next kit does not inherit it. That is the loop the photograph never shows.

Within five working days of teardown, the activation runs a debrief in the same format every time. The output is not a deck. It is a set of catalog edits: modules that earned their place, modules that did not, new module candidates that emerged from the install, regulatory changes to fold into the annex. The catalog version increments. The next brief opens against the new catalog. The loop closes.

The McLaren and BAT case studies sitting next to this one are what the operating system produces. They look like activation projects because that is what shipped. The reason they shipped looking like the rendering is the system on this page.

If a hiring team takes one thing from this case study, it is this: senior creative leadership in this category is operating-model work. Photography is the byproduct.