Skip to content

Environmental Design

This page is generated. Do not edit it by hand — run scripts/atlas-vocab.py.

part of Print & Physical Design · tier 2 · Image · 1 pieces of work carry it · 6 crafts it is confused with

The craft, and who hires it

Hired for experiential marketing and retail: trade show and exhibit design, retail experience design, in-store displays and PoS, pop-up activations, event scenography and venue branding, office environments, and signage/wayfinding systems.

Design of branded physical spaces and their graphics — retail environments, trade-show booths and exhibits, pop-ups, event stages and scenography, signage and wayfinding — turning brand identity into built, walk-through experience. Design of physical branded spaces, such as trade show booths or retail environments, to create immersive experiences.

Tag it when…

Tag when a designed physical brand space or its environmental graphics are the showcased work. Checkable signals: booth/exhibit builds, storefronts or interiors carrying brand graphics, stage and scenic design for brand events, installed large-format signage or supergraphics, spatial wayfinding systems, pop-up structures.

Never tag it when…

Never tag mere footage shot AT an event or venue where the designed environment is not the craft on show — the coverage's own crafts (cinematography, editing) tag instead; 'event coverage' is a content type, not a craft basis (boundary law). Screen content that PLAYS in a venue (stage loops, LED-wall graphics) is the screen craft — animation_motion_graphics / design_motion_identity — not Environmental Design, unless the spatial/scenic design itself is what the item presents. Physical props and product objects go to design_product_design; packs and PoS-adjacent packaging to print_physical_design_packaging_design. The svc_physical_experiential SERVICE row is the credit/offer tier and never a classify target — classification lands here, on the craft leaf.

Easily mistaken for 6 other crafts

Every other page suggests neighbours by similarity. This one navigates by difference: each line names the craft this is confused with, and the rule for telling them apart.

  • animation motion graphics — A motion loop shown on venue screens is Motion Graphics by craft; Environmental Design applies only when the built space/scenic system is the showcased work (the live DevDay-loop exemplar sits exactly on this line).
  • design motion identity — A motion-identity system deployed across a venue's screens and surfaces stays Motion Identity (a Design leaf) for the identity craft; Environmental Design tags additionally only when the venue's built/spatial application is itself part of the shown work — the DevDay exemplar carries exactly this split.
  • svc physical experiential (Physical Activations & Experiential, service L0) — The service is what a vendor SELLS (credit tier); Environmental Design is the craft leaf that content actually tags.
  • print physical design packaging design — The pack and its retail-shelf graphics are Packaging; the shelf, display unit, and store around them are Environmental.
  • design product design — A designed physical object/prop is Product Design; the designed SPACE it lives in is Environmental.
  • disc video production (cinematography/editing leaves) — A film about an activation carries those crafts for the film itself; Environmental Design tags only when the built environment is the subject work, not merely the backdrop.

At what size it applies

Asset tag when the whole item documents the designed environment (booth case film, retail-interior photo set, installation walkthrough) — the item IS environmental-design work to a buyer. A segment inside a broader film where the designed space appears — a stage reveal, a booth flyby — is a MOMENT on that segment.

Pieces that settle the definition

  • DevDay 2025 motion identity — loop 06 — Verified live link (content_disciplines, provenance=analyzer; co-tagged design_graphic_design + animation_motion_graphics). Event-environment deployment of the identity across the physical DevDay venue — a boundary case: the loop itself is screen craft; the environmental claim rests on the venue application

Where to look next

Atlas — the BrandTrackers domain model. Source: git markdown, drift-checked against the live DB.