Concepts

Why order fulfillment punishes friction harder than financial review

Extraneous load is near-fatal in warehouse operations and tolerable in loan underwriting. Good UX isn't universal — the same pattern can be right in one domain and wrong in another.

"Reduce cognitive load" is one of the most repeated principles in UX design. It's also, on its own, almost useless — because it treats all cognitive load as equally bad and all reduction as equally good. Whether a given amount of friction is acceptable depends on what happens when the friction compounds.

In a warehouse picking station, an extra modal dialog on each scanned item might cost two seconds per scan. Across a four-hundred-item shift, that's thirteen minutes of lost throughput, multiplied by ten operators, multiplied by two shifts. The modal wasn't adding safety — it was adding thirteen minutes of delay to a system where throughput is the primary success metric.

In a loan underwriting tool, the same extra modal on each application review might be entirely acceptable. The underwriter is spending eight minutes per application anyway. Two extra seconds for a confirmation step is noise. And if that step prevents a single incorrectly marked application from moving to the wrong queue, the math is different.

Same friction. Different consequence. Different design decision.

Domain load weightings

TheDesignAgent's corpus includes load weightings by domain type. These weightings reflect how much damage different kinds of cognitive load do in different operational contexts. They're not arbitrary — they're derived from the observable structure of the job.

Throughput-critical domains (warehouse operations, support queues, content moderation, data entry): extraneous load is heavily penalised. The job is repetitive and high-volume; the user performs the same action hundreds of times per session. Friction that costs one second per action costs minutes per hour, and those minutes are the product's primary cost. Germane load — the kind that builds expertise — is fine and expected early in the user's tenure, but should reduce as they become expert. The interface should accelerate toward low load for experienced users.

Deliberation-critical domains (loan underwriting, legal review, clinical decision support, compliance auditing): intrinsic load is expected and appropriate. The job requires deep engagement with each record. Extraneous load is tolerable as long as it contributes to accuracy — a confirmation step that forces a brief review is acceptable. Germane load for building domain expertise in the tool itself is a feature, not a bug.

Mixed-cadence domains (SaaS operations, account management, customer success): the load profile shifts across the day-shape. Some tasks are triage; others are deliberate. The weighting model has to account for which task is active at evaluation time.

Pattern: cognitive load costs aren't universal. The domain determines what friction is tolerable and what's fatal. "Reduce friction" is the right directive in throughput jobs; "support deliberation" is the right directive in review jobs. The same modal can be wrong in one and right in the other.

How this changes scoring

When TheDesignAgent evaluates a build, the domain weighting is applied before the score is calculated. A extraneous_load sub-score of 65 means something different in a warehouse picking tool than in a financial review tool.

In the warehouse context, 65 on extraneous load is a significant concern — the patching priority is high, and the patches are aggressive. Strip ceremony from routine actions, replace confirms with undo, move actions inline. The goal is to make the frequent path frictionless.

In the financial review context, 65 on extraneous load might not trigger a high-priority patch at all if the friction is deliberate — confirmation steps on high-consequence decisions, required field validation that forces completeness, a step that makes the user read a key piece of context before proceeding. The domain weighting doesn't excuse bad friction; it changes what counts as bad.

Why agents miss domain context

Agents apply UX principles uniformly because the principles they've learned are usually presented without domain qualification. "Reduce clicks" is presented as a universal good. "Fewer fields in forms" is standard advice. "Minimize modals" appears in every pattern library.

These principles are correct in their domain of origin — usually consumer-facing products with intermittent use, where friction causes abandonment. They're less obviously correct in enterprise operational software with daily power users and high task volume. And they can be actively wrong in compliance-heavy domains where slowing down is the safety mechanism.

Domain weightings are how TheDesignAgent translates "this is right" into "this is right here, for this job, for this kind of user." Without them, every evaluation collapses to the same general-purpose advice — which is how generic-looking, generic-feeling products get built.