There is an observation in a recent conversation between Chase Hughes and Cal from “The Great Unlearn” that I want to take more seriously than the conversation itself takes it. They name, in passing, that we crave a Steven Spielberg ending for current events - that our brains have been wired pre-linguistically to feel this is the moment of climax.
This is the moment of resolution.
This is what should happen next - and that the wiring runs faster than our conscious reasoning can correct.
I think the observation is correct. The implications for the people who build software are larger than the conversation suggests.
I am going to call this Spielberg-arc literacy, and argue that designers should build for it as an engineering specification rather than treat it as an aesthetic preference. The argument has three steps.
Step 1: The arc completes itself, whether we want it to or not.
Story archetypes are not cultural decorations. They are deep patterns that operate below conscious cognition. When a juror watches a trial unfold, the archetype is filling in the conclusion before deliberation begins. When a reader scrolls a feed of related stories, the brain is welding them into a sequence with a moral. When a user opens an app for the third day in a row, they are already in an identity arc - I am someone who uses this kind of app - and the next interaction will either complete the arc or break it.
The recognition is not only cognitive. The body’s autonomic systems flag the pattern before the conscious mind notices it. By the time the user is aware of the arc, the arc has already entered the room.
A trial consultant who understands this can win cases without ever stating the conclusion. A media operator who understands this can govern public mood through the order of two adjacent stories. They do not have to instruct the audience on what to think. The audience completes the arc on their own and feels clever for having done it.
This is, in the technical sense, manipulation. Not in the dramatic sense, where someone pushes another against their will. In the operational sense, where someone directs another’s behavior through patterns that the other cannot consciously evaluate. Most users feel they have decided. Most users have not.
Step 2: We do this to ourselves, too.
It would be easier if Spielberg arcs were only a tool operators used on people. They are not. We do it to ourselves every day with the identity stories we tell.
The arc I am someone who is finally getting their act together completes itself by counting tasks finished.
The arc I am someone who deeply understands what is happening in the world completes itself by recognizing the headline of the day.
The arc I am someone who is better than the people I disagree with completes itself with every encounter that confirms it.
We do not need an operator to complete these arcs. We need only the wiring that was there before any operator showed up. The operator’s advantage is that they understand the wiring better than we do. The interface designer’s responsibility is that they are now standing at the wiring panel.
This matters because most designers think of themselves as helping the user complete the user’s chosen story. That is the polite framing. The honest framing is that we are usually deciding which stories are easy to complete and which are hard. The arcs we make frictionless become the arcs people live inside. The arcs we make awkward stay outside the lit room.
A designer building without arc-literacy is not building neutral software. They are building software that completes some arcs invisibly and resists others by default. The question is which.
This is news to most designers because the field has not named this specific application yet. The broader principle - bringing unconscious experience into conscious choice - was named Reflective Design (Sengers et al, 2005) two decades ago. What follows is that principle applied to identity arcs in interface interaction.
We are not condemning anyone for building what was buildable. We are naming what can now be built differently.
Step 3: The cure is not exit. The cure is literacy.
You cannot leave the arcs. They are pre-linguistic, meaning they are built into the species, not into culture. Stripping an interface of all narrative cues does not return the user to a neutral cognitive state. It returns them to whichever arc was already running before they arrived.
The move is literacy. Naming the arc. Letting the user see which one they are closest to on the inside. Returning the meaning-making to them as the protagonist of their own story, rather than letting it happen below their awareness, while we collect the engagement metrics.
In practice, this looks specific. Let me draw the contrast.
An arc-completing interface, on the user’s third day of opening the app: You’re on a 3-day streak. Don’t break it now. The arc being completed is I am someone who succeeds when I am consistent. The user feels seen. The user is being directed.
An arc-aware interface, on the user’s third day: You have opened this three days in a row. Do you want to keep doing this every day, or was this enough? The same fact surfaces. The arc is named. The user is given the opportunity to decide whether to continue, close, or pause. The protagonist is the user, not the streak.
The first interface knows where the user is going and steers them there. The second walks alongside the user and asks, “What do you want to do with this?” The whole architectural difference between extraction and accompaniment lives in that one shift.
The design move, generalized.
What does an arc-aware interface do that an arc-completing interface does not? Four things, briefly.
It names the arc the user is inside, in language the user can hold. Not as a label, as a description. “You have been reading articles about this topic for two weeks. Is there something specific you are trying to understand?”
It offers the threshold consciously, with a pause. “You’re about to make this purchase. Take a moment if you’d like.” Not friction for friction’s sake. Friction that returns the choice to the chooser.
It resists completing the arc by default. The streak is a hard case because the streak interface is handling completion on the system’s behalf. The arc-aware version refuses to do that work on behalf of either party. It surfaces the fact. It does not assign the meaning.
It honors the closure. Not every story needs to continue. The interface that knows how to end - the one that says this can stop here, and you have not failed by stopping - is the interface that treats the user as a being whose story is theirs to author.
This is sovereignty applied to narrative.
I am not arguing for aesthetic preference. I am arguing for an engineering specification. Narrative sovereignty means the user is the protagonist of their own identity story, and the system’s job is to surface the arcs the user is inside in language the user can hold, not to complete those arcs invisibly.
The cost of getting this wrong is not abstract. The cost is that the systems we build operate on people instead of supporting them. The cost is that the designers who build these systems become, whether they intend to or not, the trial consultants of the everyday. The user feels clever. The user has not decided.
The Ezri Project is one place I am applying this principle as engineering, not commentary. Other systems will apply it differently. The shape of the discipline is the same wherever it is applied: name the arc, return the meaning to the user, and resist the completion that the wiring wants by default.
This is craft. It asks more of the designer and less of the user. That trade is the work. It is also where the meaningful design lives, when extraction is no longer the default.
The users who will inherit what designers build with this discipline are not yet in the room. The discipline is for them, too.
The hero’s job is to become unnecessary. The interface’s job is the same.
Erin Stanley is the founder of Evoked.