← Journal

Process · 2026-05-01 · 5 min

Brief to Opening Night

Clients rarely ask for a generative system. They ask for a launch, an opening, a concert, a night. The work is turning that into something buildable without flattening it into decoration.

It starts with four questions, asked before any concept: the date, the space, the budget range, and what the event is actually for. Everything else is negotiable. A brief that cannot answer those four is not yet a brief, and starting creative work on top of that gap is the most reliable way to lose a project.

Then comes a concept note, and it is short on purpose. One central idea, stated in a sentence that a marketing director can repeat to their own management. For a Dolby Atmos cinema format, the sentence was that the image follows the structure of the mix rather than its amplitude. For a club residency built around a threshold, it was that the dancefloor is a state between two states. If the idea does not survive being said out loud in one line, it will not survive a production schedule.

The technical study runs in parallel, never after. It covers the surfaces, the signal chain, the power, the sightlines and the failure modes. On a permanent installation this becomes an execution drawing set: at Djerba the scenography was drawn at 1 to 50 by an architecture practice, and our layer mapped every interaction device onto those plans before anything was ordered.

Only then do we build the system. The look first, usually as a shader, then the network that routes and controls it, then the hardware integration if the piece has sensors. The order matters because the look is the thing the client approved, and everything downstream exists to deliver it under the constraints of the room.

Rehearsal is where the project is actually finished. Not the export, the rehearsal. It is the first time the image meets the real surface, the real brightness and the real distance. Plan an hour of technical rehearsal for a festival, thirty minutes of video check for a club, and treat that time as non-negotiable rather than as buffer.

On the night, the work is operation. Someone is watching the room and adjusting, because a generative system is only worth its cost if somebody is steering it. That is the part that does not appear on a quote and makes the difference between a system that responds and a system that merely runs.

Afterwards, the assets stay usable. The shader, the network, the runbook, the component inventory. The next edition starts from parameters rather than from a blank file. That is the whole reason to work this way.