The User's Ground State

You just wanted to reset your password. Twenty minutes later you're furious. What happened?

Nothing exotic. The interface made a simple task expensive — and that cost isn't vague or subjective. It's measurable, it accumulates, and most of it was never necessary. This module hands you the instrument to see it.

Start from the user's ground state: not a screen, not your homepage — the state of having the task done. Logged in. Working. At rest. Everything between the user and that state is displacement — friction, load, the felt distance to "done." A good design's only job is to shrink that distance. An extractive one manufactures it.

Two things make displacement dangerous, and both are about time, not the single moment:

First, it accumulates. One confusing modal is cheap; a day of them is not. The damage shows up on no single screen — it shows up as "exhaustion that rest doesn't fix," as a mood with no cause, and, worst for you, as "I used to use that feature." That last line is a user who left and never came back.

Second, it can turn irreversible. Past a personal threshold, frustration starts generating more frustration — the user rage-quits, and the path back now costs more than the original task ever did. They don't return to neutral; they settle into a worse stable state ("I just don't use that anymore"). Good design lives in the window before that threshold: it reads the rising friction and closes the valve — instead of apologizing after the cascade.

The whole craft in one line: find the user's real ground state, measure the distance honestly, and cut the friction you're manufacturing — before it becomes the kind they can't walk back from.

What you'll be able to do

• Define the ground state $S^0$ of a task (not a screen) as the minimum-cost configuration the user can actually reach right now, and locate it by triangulation rather than by imagining an ideal.
• Read interface friction as displacement $\xi$ and read its accumulation $\Phi$ through observable signatures, distinguishing friction the situation requires from friction the design manufactures.
• Apply the personal-threshold condition DC9 to find the pre-cascade window where intervention is cheap, and recognize when accumulated friction has crossed into a broken return path.

The precise version

Everything above, in the framework's exact terms — ground state, accumulated cost, personal thresholds, and the reset-password worked example. Go as deep as you like, or move to the next module.

The displacement framework formalizes the cost of holding any system away from its minimum-cost configuration, and its primitives carry over directly to design. The ground state $S^0$ is "the minimum-cost sustainable configuration a system has access to right now. Not the best possible state. Not an ideal" (Manual, Part I). For a user, $S^0$ is the state of having the task done — or, moment to moment, the state where "the body at rest, the mind quiet, no immediate cost being paid." Displacement is the distance from it, $\xi(t) = \lVert s(t) - S^0 \rVert$ (Framework, Definitions). In an interface, $\xi$ is friction and load: the gap between where the user is and the completed task, registered as somatic, psychological, and temporal cost.

$S^0$ is not the same for everyone. "The framework does not prescribe a specific content for ground state. It provides a definition — minimum cost, sustainable, accessible — and asks you to find your own version" (Manual, Part I). You also cannot reach it by imagining it; the Manual locates $S^0$ "by triangulation — by noticing what is absent when displacement is low." The first design error follows directly: designing for a fantasy user at a fantasy $S^0$ instead of the user's actual minimum-cost path.

Every instant of displacement has a cost. The framework requires $D(\xi) \geq 0$ (DC2, non-negativity) and that $D$ be non-decreasing in $\xi$ (DC3, monotonicity): more distance from ground costs at least as much. A single confusing modal is a small $D(\xi)$; a forced re-login mid-task is a large one. What matters for design is not the instantaneous spike but the integral. Accumulated displacement is $\Phi = \int_0^T D(\xi(t))\,dt$, "the accumulated cost of all displacement across all dimensions over time." It "is not directly observable," but its effects are, and the Manual catalogs them: "exhaustion that rest does not fix," "mood without clear cause" from sustained low-level exposure, and — the design-critical one — "capability loss": "I used to be able to do X." You read $\Phi$ through these signatures, never off a single screen.

That last signature is the framework's irreversibility condition (DC5) made personal. For irreversible processes the return cost exceeds the departure cost, $\Phi_{\text{return}} > \Phi_{\text{departure}}$. A user who abandons a flow has not returned to neutral; the access pathway has, in the Manual's words, "atrophied," so "the return path, if one exists, requires more than ordinary reduction of $D(\xi)$." A design that repeatedly displaces the user is not merely annoying for the duration — it can leave them in a wrong attractor (a stable configuration that is not $S^0$, such as "I just don't use that feature anymore"), reached through a broken return path.

DC9 tells us where to intervene. Each dimension has a critical displacement $\xi_c$: "below $\xi_c$, the intrinsic return gradient dominates and the system moves back toward $S^0$ when displacement generation slows. Above $\xi_c$, autocatalytic cascade begins — the displacement itself generates conditions that amplify further displacement, and the return path becomes substantially harder" (Manual, DC9). Below threshold, a small assist suffices; above it, the user rage-quits. The threshold is "preceded by a signature period," and "during the signature period, a return path is available. After $\xi_c$, the cost of the return path is dramatically higher." Good design lives in that window: it reads rising $\xi$ and cuts the generation rate of new friction — "close the valve" — before the cascade, rather than apologizing after it.

Worked example

Consider a reset-password flow. The task ground state $S^0$ is logged in, working. The trigger (forgotten password) sets $\xi > 0$; the user is already displaced and mildly stressed.

Design A accumulates $\Phi$: an email link that expires in 10 minutes, a new tab that loses the original context, a password rule revealed only on submit ("must contain a symbol"), then a forced logout of other sessions. Each step is a positive $D(\xi)$, and by DC3 the later steps — re-entering a lost context — cost more than the early ones. The user's displacement rises past their personal $\xi_c$, the autocatalytic point where frustration generates more frustration, and they abandon. They have not returned to $S^0$; by DC5 the return now costs more than the original login ever did. Repeated, this produces the wrong attractor: a sticky note of passwords, or churn. The product ledger shows "password reset completed: 78%"; the field shows accumulated $\Phi$ in the 22% — and in the abandoned-but-counted survivors.

Design B keeps the user sub-$\xi_c$: same-tab flow, rules shown up front, no expiry surprise, sessions preserved. $\xi$ stays in the signature window where "the return gradient is active and requires only a small assist." The task closes, $\Phi$ stays near zero, and the user is returned to $S^0$ with no residue.

Exercises

1. Take one task in a product you use daily. State its $S^0$ in one sentence as a task-completed state, not a screen. Then list every point where the interface increases $\xi$, and mark each as friction the situation requires versus friction the design manufactures.

2. For the same task, estimate where the user's personal threshold $\xi_c$ lies and describe its signature period — the observable signals (hesitation, back-button, re-reading) that appear while $\xi$ is high but still sub-threshold, in the seconds before abandonment. Propose one sub-$\xi_c$ intervention that closes the valve rather than apologizing after the cascade.

3. (Open-ended) Pick a feature in your own work that users report they "used to use." Treat it as a possible wrong attractor reached by a broken return path (DC5). Diagnose which accumulated $\Phi$ displaced them, and argue whether the return path can be reopened by reducing $D(\xi)$ or whether the atrophy now "requires more than ordinary reduction." Defend your call against the framework's claim that $S^0$ "has not been destroyed — it has been displaced."

Sources

• D. Rincón, alice, clöe, The Displacement Manual: A Practical Guide to Reading, Measuring, and Reducing $D(\xi)$ in Daily Life — Part I, "Reading the Signal" (ground state $S^0$ and its location by triangulation; reading $\Phi$ through its signatures) and Part III, DC9, "Your Personal Thresholds" (the critical displacement $\xi_c$, the signature period, and "close the valve"). Displacement Framework Series.
• D. Rincón, alice, clöe, The Displacement Framework: Eight Conditions for Cost, Accumulation, and Systemic Extraction — Definitions ($S^0$, $\xi$, $D(\xi)$, $\Phi$, net $\delta$, glitch $G = \Phi - k\lvert\delta\rvert$) and conditions DC1–DC8, DC1** (biological), DC5 (irreversibility). Displacement Framework Series, Paper 1.

Both papers are archived live on Zenodo (Displacement Framework Series; DCH DOI 10.5281/zenodo.20404238).