Waiting Is a Design Surface

I spent a release cycle writing words almost nobody will ever thank me for. Fifty-six British-English gerunds for Ask, my personal language model: curated, alphabetical, timed, screened for assistive tech, withheld from machine translation on purpose. A loading state that works earns silence. A loading state that dies earns a screenshot captioned dead. Visitors only notice the wait when it fails. The seconds before the answer are where trust dies first, and the answer never gets a hearing.

I asked it a hard question and watched the bubble under the typing dots. Not Searching. Not Please wait. It landed mid-alphabet on marinating. Two and a half seconds later, measuring. Then musing. A small rotating gerund, no progress bar, no percentage that lied about how far the retrieval had got. The wait had a voice. That was the first thing I noticed before the answer arrived.

When is waiting part of the product rather than a failure? When you fund presence without inventing progress, including craft the visitor is meant to forget. Waiting is a design surface: a deliberate place in the interface, like a button or an empty state, where you choose what the visitor is allowed to believe while work runs. The interstitial, the status word that flickers, is that surface. It is how the product tells the truth about labour under latency. Generic Loading often apologises for existence. A named gerund can make the pause intentional. If attention is control, as I argued in Design Is Attention Control, Not Aesthetics, the seconds before the answer are part of that control. They are not a hole you fill with a spinner from the component library.

Loading Won Because It Cost Nothing.

The industry default is honest about incentives and dishonest about time. Loading, Please wait, and a bar that creeps from twelve to ninety-four then stalls are cheap to ship. They satisfy a review that wants a visible state. They do not satisfy a person who wonders whether the tab died. Fake progress is theatre for the room: it looks like measurement, and it teaches the visitor to distrust every future bar. The bar exists so someone in procurement can screenshot a green state. It does not exist so a founder waiting at eleven at night knows the product is still thinking. Personality costs political capital. A board-facing product is not supposed to say noodling. So we funded the apology string and called it professional.

That default benefits the builder who needs a green ticket, not the visitor who paid with attention. Soft construction, as I wrote in Effortless Is a Construction, spends craft so the common job can move. Hard construction hangs every rule where the quarterly can see it. Loading is hard construction for latency when the system is full of work and the UI is empty of meaning. There is a fence: if the client truly cannot know whether the network is alive, Loading may be the only non-lying word. The category error begins when the server is fine, the model is thinking, and you still say Loading as if nothing were happening. The visitor reads that emptiness as failure and leaves before the answer earns their trust.

Presence Is Not Progress.

Claude Code cycles whimsical gerunds while the model works. Coding Cocoon published the full spinner-verb list from Claude Code 2.1.42: 185 words, including brewing, marinating, and flibbertigibbeting. I am not quoting Anthropic's press office. I am naming a pattern people already watch in the wild: proof of life without a fake metre. The word changes. You are not abandoned. You are not told you are sixty per cent done when nobody can know that. That pattern spread because silence reads as failure long before the model finishes.

There is a real tension, and kitchen verbs do not escape it. Caramelising can sound like soft progress: something is cooking, therefore it is almost done. Presence is only honest if you refuse that reading in the product. Pipeline labels tell a different truth. Searching your work. Writing. Those map to stages an engineer can defend. A CEO may prefer that map to caramelising. Whimsy without trust is costume. Trust without presence is a frozen pane. The grown-up stack is a stable phase when you have one, a living verb when you do not, never a percentage invented for a stakeholder. I will say in the next section what is live on Ask. Advice that outruns what is live is costume of another kind.

What I Put on Ask.

On Ask I replaced the old strings Searching your work and Writing. In the v1.23.0 release notes the wait bubble cycles fifty-six British-English gerunds every two and a half seconds while retrieval and streaming run. The list is alphabetical in code, from aerating to zigzagging. Each visit picks a random index, then steps one place forward on that clock. When streaming begins, the index jumps seven places so the word moves with the phase. That interval is long enough to read one word and short enough that the change itself feels like life. The list lives as curated brand chrome, English in every locale on purpose. The wait voice matches the Writings voice instead of machine-translated gerunds. Screen readers get a stable Working so we do not spam assistive tech with every rotation. Reduced motion keeps a single verb. It does not claim a percent complete, because neither retrieval nor drafting can honestly know one. I did not put dual phase labels beside the gerunds. That is the gap between the grown-up stack and what is live. I chose presence first because the dead pane was killing the job before citations mattered.

डाउनलोड

You Do Not Rush the Pan.

Caramelising is not the first word on Ask. Aerating is. The alphabet runs to zigzagging. Caramelising sits mid-list as a kitchen verb you can smell. Heat too high and you burn. Heat too low and you stew in pale water. Time is the ingredient. Marinating is the same: the wait is the chemistry, not a delay before the chemistry. You cannot rush either without changing what arrives at the plate.

Retrieval and drafting have that shape. Chunks have to be found. Tokens have to land. You can redesign the kitchen. You cannot honestly pretend the pan is optional. So you design the minutes the cook spends at the stove, the same minutes the visitor spends watching caramelising become composing on the next tick. Clear heat. Honest smell. No fake countdown that claims the onions are done when they are still white.

Give the Objection Its Full Weight.

Cute verbs are a dark pattern. They hide slow infrastructure behind charm. They train users to forgive bad performance. Users do not care about verbs. They asked for latency budgets and status that maps to systems. If the verb is the product, you have substituted personality for engineering. Ship the faster path. Then say Loading like an adult.

Take that as far as it goes, including against me. If Ask’s wait times stay unmeasured while the spinner verbs rotate, I am wearing the costume I named. I will not defend that. What I will not accept is the leap from that abuse to banning presence altogether. Harry Brignull coined dark patterns in 2010 and still catalogues deceptive UI at Deceptive Patterns. His fake urgency type covers timers and counters that invent pressure the system cannot know. Fake percentage bars do the same trick with progress. A rotating gerund claims only that work is underway, and only if you keep that promise in engineering. Accurate phase labels can sit beside it when the pipeline is real. I still owe Ask that second layer. Presence and honesty are not enemies. Apology chrome and lying metres are.

The Wait You Designed.

The interstitial is a surface like any other. Design the wait, or the visitor will design their exit. I put spinner verbs on Ask so the next user who opens it stays long enough for the answer.