Short-Term vs. Long-Term Installations

I came to installations from live production, where most gigs were “show up and ship”—a single day with a hard out. Over time, those projects stretched to weekends, months, and eventually multi-year deployments. Each horizon rewards different choices. Here’s how short-term and long-term projects differ, strategies for each, and what to prioritize for each.

Why this matters

A weekend pop-up rewards speed and decisive tradeoffs; a year-long installation rewards durability, maintainability, and planned evolution. For both of these, I try to still incorporate the typical pipeline of Concept/Design/Production/Install/Operation but the short term may see much of the first 3 happening very quickly or overlapping.

Reusing old tools or content that can be modified becomes crucial when this is the case to make sure the client sees what they are getting quickly. For long-term projects, you can take the time to breakdown parts in detail but sometimes those short-term projects from the past can help you get your footing faster to get to the fun stuff and know what to look out for.

Short-Term (day to weekend): Ship fast, plan for pivots

Success: it works during show hours, survives real-world chaos, and tears down cleanly.

Scope & expectations

Lock non-negotiables (screen size, interaction trigger, brand beats) and name flexibles (brightness, thresholds, simultaneous users). Tell the client what might move (ambient light, traffic) and how you’ll respond (raise projector output, widen thresholds, simplify effects). On tight timelines, content is the biggest risk: show references or reuse proven modules so the client isn’t seeing it for the first time on show day.

Schedule & budget

Be honest about what’s achievable. Lock milestones, payment triggers, and change-order rules before you arrive. During the show, keep creative/ops separate from finance/scheduling so maker-brain stays focused. I typically request a deposit prior to ordering gear and locking me in that covers hard costs then another for delivery with a final payment following the event. Sometimes milestones can be their content review or pre-stage testing to keep everyone excited and the deliverable progress clear.

Project tracking

Create one tidy home for scope, assets, cues, and decisions. Use daily notes: morning plan of record (what ships today) and evening deltas (what changed, what blocks tomorrow). If you’re a team of one, message the client lead with what you need and when you’ll review. A progress report every 1-3 days is great for the team and the client so no one is kept guessing.

Gear procurement

Shipping risk is existential. Order early, choose gear with same-day substitutes, and keep a bailout plan: a second lens or brightness tier, a spare media player and adapters, and a prepped “lite” build that still meets goals. Pre-stage gear to verify functionality and enable a fast deploy.

Creative & programming

You can’t patch code while supervising a truss hang. Block uninterrupted time for creative and interaction tuning. If possible, have a second person babysit renders and file wrangling so production doesn’t starve the creative.

Advancing & onsite communication

Confirm details that become critical: power, network (static IPs, VLANs, captive-portal bypass), lighting windows for calibration, staging, and access. Onsite, introduce yourself to the people who can make those things happen and trade contacts (you want allies when you ask to kill house lights for ten minutes).

Documentation and load-out

If the client doesn’t have a photographer, bring a phone gimbal or tripod for quick sweeps, save screen recordings of interactive states, and plan for documentation strategy prior to being onsite. Label every case and cable and leave everything as you found it. After loading out, sending a wrap video with highlights and metrics is always an amazing thing to share with the teams you work with.

Long-Term (year+): Design for uptime, evolution, and ownership transfer

Longer timelines add refinement and expectations. Success is stable daily operation, a plan to stay fresh, and a system that can be supported by people who didn’t build it. Many of the short-term guidelines apply here as well but with extra care to the systems you build running without you or with heavier stress over time.

Start with goals and an operations model

Define what the experience should accomplish, the schedule, and—crucially—how it will be run. Clarify staffing (in-house vs. remote, hours of coverage), SLAs (what “down” means, response times, escalation), and access (least-privilege logins, change control). These choices drive every technical decision.

Technical architecture

Short-term rigs can cut corners; long-term rigs cannot. Build in redundancy (mirrored media players or a hot-spare, dual power, failover network), monitoring (health pings, GPU/temp checks, dropped-frame alerts, storage thresholds), serviceability (front-service mounts, labeled runs, links to documentation), and environmental control (BTU-aware cooling, dust filtration, cleaning schedule).

Development Pipeline

When developing it will be crucial to use a file management system for tracking assets, new builds, and testing features. At some point, you will also need to branch your project into staging and production so you have your production ready to ship and you staging ready for any optimizing, new feature testing, or bug triaging. Always make sure you have a strategy to swap out gear/machines with up to date code quickly.

Once your production build is live, always test a reboot of the system with a full run through to make sure anything going live is fully functioning so you don’t get calls the next day. 

Content pipeline

A year is a long time to stare at the same loop. Create a strategy for easily uploading new content or modifying existing content. Use a modular system so you can swap interactions, palettes, or data feeds without touching core code. Maintain staging for previews and approvals, plus version control and rollbacks.

Interaction tuning & analytics

Instrument the wall—interactions per hour, dwell time, peak loads, dead zones. Tune thresholds, prompts, and rewards based on real behavior, and share periodic insight snapshots, not just vibes.

Maintenance & spares

Write a maintenance documentation for daily visual checks and log review. I have my systems restart daily and block updates to when is best for the client. Monitoring software can also help you track systems overtime that need attention. Planning for periodic dust cleaning, projector recalibration, and sensor calibration is also great for the operations team to have in mind. Stock spares for long-lead items and keep a known-good system image for fast rebuilds.

Safety, compliance, and accessibility

Ensure electrical and rigging compliance, clean cable management, and clear egress. Design for accessibility: readable contrast, multiple interaction modes (touch + gesture + button), captions for audio-led moments, and wheelchair viewing angles.

Handoff, training, and documentation

Assume your future self—or another team—must operate the installation without calling you. Provide a tech documentation and Servicing GUIs to allow operation teams to start/stop and do health checks. Annotate photos and diagrams (network, power, signal flow) and have ready backups (OS image, project file, versions, license keys) for if/when there is an issue.

What stays the same

Clarity beats cleverness: define goals in plain language and design interactions to prove them.
People over pixels: relationships with site ops and client owners will help you maintain and sustain when issues arise to make sure your work always looks great!
Evidence wins: photos, metrics, and wrap notes make the next project easier to green-light.

A quick playbook

Short-term:

• Lock non-negotiables and the list of flexibles
• Prep a “lite” build with ability to scale
• Keep one source of truth where you can track updates/changes
• Bring backups and advance power/network/lighting
• Establish good communication with the team helping you execute the project
• Plan how you will capture documentation before the event
• Label everything and plan for a clean exit

Long-term:

• Choose the operations model and SLA before tech to know who you are building it to be maintained by
• Ensure compliance, accessibility, and any long-term requirements
• Build in redundancy, monitoring, and serviceability
• Plan content updates strategically with staging/rollback workflow
• Deliver a tech documentation, diagrams, and ready backups

Final thoughts

Short-term projects are sprints; long-term projects are ecosystems. Know which race you’re running and you’ll make sharper choices, avoid preventable pain, and ship experiences that delight on day one and still delight on day 301.