Installation Tips and Tricks

Building an installation is no small feat. It takes creativity, planning, technical skill, and a lot of communication to turn “this would be cool” into something real that behaves the way you imagined. There are always lessons, surprises, and happy accidents that shape the work. After a decade and 200+ installations—from projection mapping to pseudo-holograms to giant building displays—these are some of the core practices I keep coming back to.

Alignment and Intention

This is the simplest and most overlooked part of a project: why are you doing this?

Your intention is the anchor around which everything else orbits. It’s the reason you choose one interaction, material, or effect over another. Sometimes the answer is practical—“because this is what we can do within budget”—but there’s also an audience-facing “why am I doing this” that must be balanced with your own intention:

• “I’m an explorer in a new world.”
  
• “I’m uncovering the mystery of the pyramids.”
  

Once that story is clear, it becomes a filter for every decision: does this choice support the intention or distract from it? It also gives you something to return to when the project gets messy: a stake in the ground that helps you see what can change and what can’t.

Set Your Milestones

Intention is the compass; milestones are the map.

Setting clear goals (per week, per day, or per phase) helps align your expectations with reality. Early on, I’d set a few simple goals for the day, then check in halfway and at the end:

• What did I actually get done?
  
• How far off was my estimate?
  
• What patterns keep repeating?
  

Over time, this builds a sense of how you work, how long things actually take, and where you tend to under/overestimate. Instead of beating yourself up for missing a huge, vague goal, you’re tracking smaller steps, seeing improvement, and learning to trust your gut. And there’s nothing better than looking back over a list of milestones and realizing how much you quietly completed.

Iteration and Reflection Points

Milestones also create natural reflection moments.

Pausing to ask, “Is this still serving the intention?” is as important as writing code, building rigs, or hanging projectors. As you move forward, you might find something isn’t landing. Maybe an interaction feels confusing, an effect is too subtle, or a narrative beat is missing. Those are moments to adjust the plan, not suffer through it.

Intentional reflection turns your process into a loop instead of a straight line:

1. Plan
   
2. Build
   
3. Reflect
   
4. Adjust
   

That loop also supports collaboration. You can show work-in-progress to your team or client with clear checkpoints: “Here’s what we tried, here’s what we learned, here’s how we’re changing direction.” It makes the whole project feel like a shared experiment rather than a fragile one-shot, while making pieces feel less precious and the end product feel more refined.

Know Your Dependencies

Some things in a project are flexible; some are hard dependencies that can break everything.

I try to line up my milestones with the biggest unknowns and address them early. A few examples:

• Internal APIs / data feeds: You can dream up beautiful data visualizations, but until you hit the real API and see how the data comes in—its structure, frequency, and weird edge cases—you’re guessing.
  
• Ambient light and environment: You might pitch a gorgeous projection mapping piece, only to discover a giant skylight dumping midday sun right on your projection surface. That may mean changing content, adding physical treatments, or shifting showtimes.
  

Finding these constraints early frees you to be more creative later. You’re not waiting for a last-minute surprise to blow up the plan; you’re making space for them at the front and planning for the unknowns to be known.

Test Your Gear

Even after a decade, I still get anxious when a project depends on gear I’ve never actually used.

Every installation is a slightly different puzzle of projectors, media servers, sensors, controllers, and mounts. You might find a few “go-to” pieces you trust or vendors who will let you test gear ahead of time, but I still try to carve out dedicated prototyping time.

Some practical approaches:

• Request demo units or find local rental houses with similar gear.
  
• Prototype with stand-ins if the exact hardware isn’t available yet. This may help you gauge the amount of time needed for setting it up, or things to have in mind.
  
• Know your baseline: I like having a last-generation PC that I know can run most of my work decently. If it performs well there, I know a more powerful machine will be fine.
  

The more you understand how your tools behave before you’re on-site, the less you’re debugging under pressure.

Know When to Stop

Knowing when to stop is often the most challenging yet most important part of any project.

It’s tempting to keep tweaking—one more shader tweak, one more animation pass—but endless fine-tuning can make things feel chaotic and unfinished rather than refined. I like to set a “pencils down” milestone earlier than the actual deadline. That buffer gives me time to:

• Clean up messy bits in the project file
  
• Remove half-finished experiments
  
• Document the final setup
  
• Decide what to sacrifice to protect the most important parts
  

It also creates a natural moment to get sign-off from a client or team: “This is a version we can live with. If we add more, great, but we can always roll back to this.”

Networking

For most tech-heavy installations, the wild card is the network and how it is set up (or not set up) for you to accomplish your goals.

The first and last person I want to talk to on-site is whoever owns the network: IT, AV, or a dedicated network engineer. I’ve seen seemingly perfect systems suddenly stop talking to anything because:

• The computer got blacklisted by IT
  
• Someone changed VLANs or firewall rules
  
• A new device grabbed a conflicting IP
  

These problems are avoidable with communication:

• Share your device list, IP plan, and ports ahead of time
  
• Talk through any monitoring apps, external APIs, or heavy traffic (LED control, streaming video, etc.)
  
• Confirm the setup once you’re installing and again before you leave
  

A little planning here can save you from mysterious “it just stopped working” calls later.

Document Your Work

Documentation is not something to bolt on at the end, it’s something to plan for.

If you don’t budget time, assign responsibility, or coordinate with the client, documentation either won’t happen or will be rushed and disappointing. Good documentation is not just a record of the project; it’s:

• Material for your reel and portfolio
  
• A way to share the work with collaborators and future clients
  
• A snapshot of your growth and voice as an artist
  

An installation often feels like building an elaborate movie set. The documentation is the film you shoot on that set—except the focus is on the environment itself. If you’ve already built the stage, it’s a missed opportunity not to capture it well.

Thinking about documentation early also shapes how you design experiences, because you now must summarize the experience for fresh eyes through a lens, in words, and in other media beyond the experience itself.

Closing Thoughts

Every one of these tips came from trial and error. The mistakes weren’t fun at the time, but they shaped how I work and strengthened future projects. I hope they save you a few headaches—whether you’re just starting or already deep in your own practice.

The last tip I’ll offer is this: enjoy the work. Building installations is a strange, specific, and wonderful skill set. You’re making worlds for other people to step into. That’s a pretty incredible thing to get to share.