Install day should be calibration, not problem-solving

Two kinds of install week

There are two kinds of install week. In one, the team is solving problems for the first time on site — under a live deadline, in someone else's building, with no workshop around them. In the other, everything has already been seen before, and the week is calibration: levelling, content load, testing at full visitor flow.

The second kind looks calm. It isn't luck. It's the result of decisions made weeks earlier.

Prototype on the bench, not on site

The single biggest lever is integrating and stress-testing on the workshop floor before anything ships. Hardware mounted, software running, content loaded, the whole thing powered up and left running. Faults surface where there are tools, spares, and time — not in a gallery the night before opening.

By the time it reaches site, the unknowns are gone. What's left is the work that genuinely can only happen in the room: alignment, calibration, and tuning to the real light and the real crowd.

One lead across the seams

Install is where joinery, AV, software, and content all meet at once. If those are four contractors, install week is four diaries and a blame map. If it's one team with one lead, decisions happen in minutes.

Closing

Install day going well is the most visible part of a project and the least where the work happens. Smooth on site is earned on the bench.