Your user's nervous system arrived before they did

The layer under the user need

Jobs-to-be-done is useful. Personas are useful. User needs are useful.

All three skip the layer underneath: the user shows up in a nervous system state. Anxious. Rushed. Grieving. Defensive. And they didn't get that state from you. They got it from the five minutes before they opened the thing, an argument, a diagnosis, a commute, and you inherit whatever's left.

Most interfaces are built for a person who doesn't exist: calm, available, regulated, arriving from nowhere. For a real chunk of the people who'll actually use it, every one of those assumptions is false the moment they land.

The interface's real job isn't a click. It's the state transition between arrival and exit.

A contact report is not a form

GiveCampus gift officers file contact reports after donor visits. The stated problem: "form is slow. Too many fields." Obvious fix: cut fields.

But that skips the state. A gift officer filing a report is not neutral. Just had a high-stakes conversation. Maybe a long drive. Maybe processing something difficult. Opens the form tired, emotionally loaded, possibly demoralized.

A fifteen-field form in that state isn't slow. It's a tax on someone who's already overdrawn. They file the minimum and bail, and then we call it a completion-rate problem.

The redesign didn't just cut fields. It opened with one text box: "How was the visit?" Not "topics discussed." Not "next steps." That single question treats the gift officer like a person carrying something home from a hard conversation, and lets them set it down before the tool asks for anything structured.

Filing rates went up. Note quality went up. Fields barely changed. The state-handling changed.

Hiki and the cost of default engagement

Infinite scroll isn't neutral. It's a dopamine exploit. Whether it's a feature or poison depends entirely on the nervous system you're building for.

Hiki was a social platform for neurodivergent adults. The standard engagement playbook was actively toxic. Push notifications? Many users have rejection sensitivity. Surprise stimuli trigger fight-or-flight. Infinite scroll? Many have attention dysregulation. That pattern is a trap for them, not a delight. Social proof numbers? Comparison spirals are a documented failure mode for this audience.

"Best practice" engagement assumes a neurotypical user with self-regulation intact who can leave when they want. A lot of our users couldn't. The pattern wasn't neutral. It exploited the specific nervous system shape we were trying to serve.

Building for the full nervous system range makes products better for everyone. The neurotypical user has panic days, grief days, deadline days. A product that works for them on their worst day is a product that works.

The emotional state audit

Before any new screen or major redesign, I run an Emotional State Audit. Three questions. Written.

What state is the user in when they arrive? Not a persona. A state. Anxious. Focused. Rushed. Numb. Whatever is true for this flow.
What state do they need when they leave? Not an outcome ("task done"). A state. Relieved. Confident. Informed. Calm.
What is the interface's role in that shift? This is the design brief. Most interfaces I see try to answer Step 3 without ever having addressed Steps 1 and 2.

Blank audit means the design isn't ready.

A real audit. Three questions, one page. The answers changed every subsequent design decision.

Why this gets skipped

It's uncomfortable. Writing "the user arrives anxious and possibly demoralized" feels presumptuous. You don't know. How can you?

You can know enough. Watch five user sessions. Do five interviews. Read the support tickets. It's not a mystery. It's just a question nobody asked.

And the emotional layer doesn't invoice cleanly. "We cut three fields" is a deliverable anyone can sign off on. "We restructured around the state the user arrives in" asks a stakeholder to care about something they can't see in a screenshot. That's the real reason it gets skipped, and I've dropped it myself when the room wasn't going to buy it.

It's a conversation, not a checklist. But it's the one that separates an interface that feels thought-through from one that feels built for nobody in particular.

Try this week

Pick one flow you own. Answer the three questions honestly. Then open the actual screen and ask one thing: does a single pixel here acknowledge the state I just wrote down?

Usually the answer is no. That's the brief.

Full Emotional State skill is on the tools page. Prompts. Template. Audit format. Take it. Adapt it. Make it yours. The rigor matters more than the template.