Theatrical lighting designers have a working vocabulary for the decision UX teams still argue about in the language of quality. Discoverability is a dial. Motivation is a switch.
Stand in the wings of a working theatre about ten minutes before curtain and watch the crew tune the lamps. Onstage there is a small kitchen table with a single brass lamp, shade tilted toward the actor's mark. When she crosses to the table and flips the switch, the lamp will come on and her face will brighten, and nearly everyone in the audience will accept this as the lamp doing the work.
It isn't. The actor's face is being lit by four masked instruments hung in the first electric above her head, angled to mimic the tilt of the brass shade. The lamp on the table is what theatre calls a practical — a real, working fixture, yes, but one whose bulb has been wattage-matched to be just bright enough to justify everything the rig is actually doing. If the lighting designer is very good, you will leave the theatre believing you saw one lamp.
Theatrical lighting designers call this motivated light: illumination representing a believable source inside the world of the scene — a lamp, a window, the moon. The opposite, non-motivated or unmotivated light, has no visible cause. It is simply there, making the action legible, and the audience has agreed not to ask where it comes from.
Every user interface feature makes the same choice. Some features are motivated: they look and feel like obvious extensions of what the user was already doing, with visible causes inside the user's frame. Others are non-motivated: they appear without warning, do something the user did not ask for directly, and feel either magical or intrusive depending on whether the answer is right.
The argument of this essay is small but, I think, useful. Discoverability is a dial, but motivation is a switch. And UX teams, who have spent thirty years arguing about one of them, have not yet named the other.
The vocabulary lighting designers already have
The working distinction is older than most UX frameworks. In Introduction to Technical Theatre, Thomas Sanders writes that motivated lighting "attempts to represent the look and feel of an actual light source such as the sun, a candle, or street light." The designer's job is to identify the hypothetical source, place the practical if one exists, then mask the rig behind it so the audience sees a single cause. Unmotivated light, Sanders writes, "has no rational explanation of the light sources used... you will not be able to tell where the light is coming from in the scene, but it's there."
The two categories sit inside a broader frame laid down by Stanley McCandless in A Method of Lighting the Stage (first published 1932 by Whitlock's of New Haven; still in print in its fourth edition). McCandless proposed that every lit moment could be analyzed across four controllable properties — intensity, color, distribution, control — against four functions: visibility, form, naturalism, mood. Motivated and non-motivated light are not new functions; they are a more recent vocabulary for the naturalism axis. But the naming matters, because once the categories have names, designers can decide about them explicitly rather than falling into one by default.
Film and theatre disagree about the default. The working norm in narrative cinema is that most light should be motivated — if the audience can see a visible source for every beam, the illusion holds and the camera does not draw attention to itself. Stanley Kubrick pushed this to a limit on Barry Lyndon (1975), shooting candlelit interiors on a Zeiss Planar 50mm f/0.7 lens modified from equipment originally made for NASA, so that the candles he showed on screen were effectively the only light sources in the room. Theatrical practice is more permissive. A proscenium arch is an agreed-upon frame. Front-of-house washes, backlight, area-isolation specials — all routinely non-motivated, and nobody leaves asking why the back wall glowed.
This is the load-bearing idea for what follows. Motivated lighting is not the absence of artifice. It is artifice that hides itself behind a believable cause. The brass lamp is pretending to do the work. The rig has agreed to pretend along with it. The audience is happy to be lied to in service of the story.
The vocabulary UX is missing
UX designers have conceptual pieces that look similar, but fitted to a different level of the product.
Don Norman, in The Design of Everyday Things (Basic Books, 1988; revised edition 2013), carved apart two concepts that had previously been smushed together. An affordance is the property that makes an action possible — a door's hinge affords opening. A signifier is the perceivable cue about the affordance — a flat push-plate tells you which way. Norman's move was to insist that affordance and signifier can come apart: an unsignified affordance is an action that exists but is not advertised.
At the other end sits what the post-2023 UX literature calls invisible design or, with surprising candor, magic. "Complexity is hidden behind an easy-to-click interface that magically seems to 'know' the user's taste," runs one widely-circulated summary. Jakob Nielsen's 1995 pattern of progressive disclosure — where advanced controls are deferred to a secondary screen until the user earns them — occupies the interesting middle, a deliberately staged reveal of motivation.
Game designers have been more explicit than general UX about the underlying split. Erik Fagerholt and Magnus Lorentzon's 2009 Chalmers University master's thesis named the distinction between diegetic UI — elements that exist inside the game world, like the glowing health bar on the back of Isaac Clarke's suit in Dead Space — and non-diegetic UI, elements overlaid on the screen the player sees but the character cannot. That vocabulary has traveled well inside games. It has not crossed into general UX, which still argues about these decisions in the language of quality (is this feature discoverable enough? is it too in-the-way?) rather than in the language of contract.
UX has, conceptually: the signifier/affordance split (control level), the invisible-UX literature (feature level, called magic), progressive disclosure (timing), diegetic-UI theory (stuck inside games). What UX doesn't have is shared vocabulary that lets two product managers disagree about a feature without it becoming a quality argument. Lighting designers can say this cue should be motivated, that one shouldn't and both people know what they mean. UX meetings produce "this feature should feel more natural," which is accurate but not operational.
The mapping
Four worked examples, one for each quadrant the lighting vocabulary makes visible.
The Reply button is the motivated control. It sits inside the message the user just read. Its label matches the action it performs. When you click it, a composer opens with the recipient pre-filled and the subject prefixed with "Re:". Every downstream behavior has a visible cause inside the user's prior frame. The feature is, in the lighting sense, a practical lamp — and like a practical, most of the work happens off-stage. The quoted message is assembled from cached thread state; the recipient is resolved against the address book; the draft autosaves to server-side storage. The rig is hidden behind the obvious button. This is motivated UX. It looks easy because it is engineered to look easy.
Gmail's Smart Compose is the non-motivated specialty. You start typing; grayed-out text appears in front of your cursor, proposing the rest of your sentence. No button was pressed. No setting was toggled. The feature simply appears, because a model reads the partial thread and makes a probability-ranked suggestion. Google first rolled it out in 2018 and published the technical design under lead author Mia Xu Chen and colleagues. In lighting terms it is unmotivated light — a cue with no practical to justify it. If the suggestion is right, the user feels the system read their mind. If it is wrong, the user feels intruded on. There is no middle ground, because there is no visible cause to inspect.
Spotify's Discover Weekly is the masked rig pretending to be a practical. Every Monday, each user receives a thirty-song playlist that "feels" curated for them. The cause the interface presents is taste. The cause that actually produces the playlist is collaborative filtering over the listening histories of hundreds of millions of monthly listeners, augmented with content-based audio analysis and a natural-language pass over music criticism and playlist text. The scale of the backstage rig is difficult to overstate, and the feature's whole emotional valence depends on not showing it. This is the essay's most important pattern: motivated UX requires more hidden machinery, not less, and the obvious feature is almost always more engineered than the magical one. Users who inspect obvious features find them nicely built; users who inspect magical ones find them either miraculous or creepy.
Google's Advanced Search is the dimmer fade. The default search box is brutally simple — one field, one button. The advanced controls exist, but they are staged behind a second screen the user must opt into. Nielsen's progressive disclosure is structurally identical to a lighting cue that fades in only when the scene requires it: the rig is there, the capability is there, but the motivation becomes visible only when the user has demonstrated they need it. A user who never visits /advanced never sees the operator syntax, never knows it exists, and is not made to feel stupid by its absence. A user who arrives at /advanced has signed a different contract with the system, and the interface responds.
What the lighting frame gives, that "discoverable vs. invisible" does not, is the per-feature decision as a choice. Neither motivated nor non-motivated is better. The same product needs both, the same scene needs both, and the designer's job is to decide which contract each moment is making with the user.
Why the vocabulary upgrade matters
Two claims follow from taking the analogy seriously.
The first is the asymmetric cost of inspection. An obvious feature — the Reply button, the Save dialog, the progress bar — has to survive being looked at. Users stare directly at it, form opinions, compare it to competitors, complain about its label. Every visible affordance is a durable surface area. A magical feature is inspected only through its outputs. Users notice it when the model gets a suggestion wrong, but the mechanism itself is shielded by the absence of a visible cause. This produces an engineering paradox most teams don't articulate: the features the marketing page shows off often require less scaffolding than the features it ignores. If you find yourself with a sprint where the simple thing takes twice as long as the miracle, you are not doing something wrong. You are building a practical lamp while the rig hangs quietly above.
The second is the film-versus-theatre default argument inside your product team. When the marketing side asks for "more transparency" and the engineering side asks for "more automation," the two are not disagreeing about features. They are disagreeing about which medium the product should feel like it's in. Marketing wants film: motivated everywhere, every interaction traceable to a visible cause, the user never jarred out of the story. Engineering wants theatre: a few well-placed practicals with a sea of non-motivated fill behind them, because that is how scale works. Both are right, and the debate is productive as soon as the vocabulary exists to hold it. Which moments in this flow are we motivating? Which are we not? Why? are the three questions the lighting designer asks every time they plot a show. UX teams should be able to ask them too.
Where the analogy breaks
No cross-domain frame survives intact. Three disanalogies, ordered by severity.
The first is cadence and reversibility. A play has a fixed runtime, intermission resets, and a curtain call; the lighting designer gets to start from zero every night. A product accumulates. A feature you ship today is a cue that keeps playing for as long as any user has your app installed. The decision to make something non-motivated is therefore more consequential in UX than in lighting — you cannot take the cue out without breaking the users who learned to depend on it. The framing holds. The stakes are different.
The second is the audience contract. Theatre audiences arrive pre-agreed: they paid for a ticket, they sat in the dark, they accepted a proscenium. Users never signed anything. They are in the middle of their workday; they did not come for a show. Non-motivated light in theatre is generally forgiven; non-motivated UX is forgiven only when it delivers visible benefit. A magical feature that is wrong a meaningful fraction of the time is judged harshly not because the illusion failed but because the user never agreed to be illusioned at all.
The third is individual variance. A lighting designer makes one set of decisions for every audience that walks in. A UX designer is making choices that will be inspected and used by millions of people with wildly different prior context. A cue that reads as magical to a power user may read as intrusive to a new one. The lighting frame gives vocabulary for the per-feature contract; it does not tell you when to vary that contract across users. That is what telemetry, cohorting, and gradual rollout are for — machinery the lighting designer doesn't need, because their audience is a single entity.
What UX could, in trade, give back to lighting: instrumented per-seat feedback. Theatre designers work in the dark and read the room at curtain call. Product designers know, hour by hour, whose contract held. A lighting designer who could see which audience members lost the thread when a non-motivated cue fired would be a better designer.
Epilogue
Return to the wings. The actor crosses the stage. She flips the switch. The lamp glows. Her face comes up. Somewhere overhead, four instruments do the actual work, and nobody in the audience is counting them.
The lighting designer who plotted that show did not decide once, at the start of production, whether the whole play would be motivated or non-motivated. They decided eighty times, at eighty different cues, in service of eighty different moments. The front-of-house wash for the opening is non-motivated and everyone is fine with it. The table lamp in the kitchen scene is motivated and carries the whole emotional weight of the exchange underneath. The dream sequence fades to pure unmotivated color because the contract has shifted. Each decision is made on its own terms, with its own justification, inside a vocabulary that makes the choice legible.
UX features deserve the same treatment. Not "should our product feel magical?" Not "should we be transparent?" Those are medium-wide questions with no defensible answer. The better question, the per-cue question, is: for this specific moment in the user's flow, which contract are we offering — realism or trust? The Reply button is realism. Smart Compose is trust. Discover Weekly is realism pretending to be trust. Advanced Search is a dimmer.
When in doubt, name your source.
Sources: Thomas Sanders, Introduction to Technical Theatre (open-access textbook). Stanley McCandless, A Method of Lighting the Stage, first published 1932 by Whitlock's Inc., New Haven, CT; 4th ed. 1958 (Theatre Arts Books). Stanley Kubrick, Barry Lyndon (Warner Bros., 1975), shot on Zeiss Planar 50mm f/0.7 lenses originally manufactured for NASA's Apollo program. Donald A. Norman, The Design of Everyday Things, Basic Books, 1988 (original title The Psychology of Everyday Things; revised and expanded edition 2013). Jakob Nielsen, "Progressive Disclosure," Nielsen Norman Group (pattern popularized in the mid-1990s UX-heuristics literature). Erik Fagerholt & Magnus Lorentzon, Beyond the HUD — User Interfaces for Increased Player Immersion in FPS Games, Chalmers University of Technology master's thesis, 2009. Mia Xu Chen et al., "Gmail Smart Compose: Real-Time Assisted Writing," KDD '19 proceedings (preprint posted 2018).
When in doubt, name your source. That's the lighting designer's closing rule, and it's the same rule Agent Rating Protocol (ARP) applies to agent behavior. Every signed agent action names its source — which model, which operator, which upstream agents it depended on — so the user inspecting the output sees the practical lamp instead of guessing at the rig. Motivated agents are inspectable. Non-motivated agents are magical until they aren't. ARP is the protocol for agents that show their source.
Verify a named-source agent record · See the practical, not the rig ·
pip install agent-rating-protocol