# The full design process, end to end: what an evaluation actually looks at

> TheDesignAgent doesn't evaluate one thing. It runs through the same process a skilled human design reviewer would — JTBD, cognitive patterns, visual craft, visual cognitive load, component grammar, accessibility — encoded as a rubric an agent can call mid-build.

Source: https://www.thedesignagent.ai/field-notes/the-full-design-process · Workflow · 2026-05-06

A skilled human design reviewer doing a thorough critique of an interface doesn't ask one question. They ask a sequence of questions, each building on the previous. Does this serve the job? Is the cognitive load appropriate? Is the visual hierarchy clear? Is the visual parsing cost low? Does the component grammar feel intentional? Is it accessible? Are the patterns consistent with the decisions already made in this product?

TheDesignAgent runs the same process — encoded as a rubric, executed on every call. Understanding each stage makes scores and patches more legible: they're not arbitrary numbers and suggestions, they're the outputs of a structured review that's asking specific questions in a specific order.

## Stage one: JTBD alignment

The first question is structural: does this artifact serve the job it's supposed to serve, in the shape the job requires?

A deciding job needs a decision surface — inline actions, confidence signals on the record, session-progress tracking at the top. A sequential job needs a layout that mirrors the sequence — a progress rail, not tabs. A monitoring job needs aggregates and trend visibility at the primary level.

JTBD failures are foundational. If the layout is wrong for the job, applying visual fixes to it produces a polished version of the wrong thing. This is why JTBD comes first: structural problems should be diagnosed and fixed before craft-level work begins. The patches for JTBD failures are the largest structural changes in the set — switch layout type, move actions inline, restructure primary navigation.

## Stage two: cognitive patterns

The second question is behavioral: how much cognitive effort does this layout require, and is that effort justified?

This stage looks at intrinsic load (is the task genuinely complex, and is the layout helping the user manage that complexity?), extraneous load (is the interface adding overhead the job doesn't require?), and germane load (is the interface supporting the development of expertise, or preventing it?).

Domain weightings are applied here. A confirmation dialog on a routine action in a high-throughput job has a different cost than the same dialog in a deliberation job. The same feature, different penalty.

Cognitive pattern failures produce patches that address ceremony: replace confirms with undo, collapse modals into inline actions, reduce the number of steps between the user and the action they perform most frequently.

## Stage three: visual craft

The third stage asks: is the design well-made? This is where the `/visual` lens focuses — on spacing, hierarchy, contrast, typography, and density. Not "does it look good" as a subjective judgment, but "does it apply visual design principles correctly."

This stage is independent of JTBD and cognitive load. A layout can be perfectly shaped for the job and poorly crafted — right structure, weak execution. Visual craft failures produce patches that are precise: adjust the font weight of secondary labels, reduce the border-radius to match the density of the surrounding context, establish a primary focal point per section, reduce the competing high-contrast elements from four to one.

## Stage four: visual cognitive load

Stage four asks a related but distinct question: what is the parsing cost of this layout? A screen that's well-crafted on individual elements can still be expensive to read if the elements don't form a coherent visual path.

Visual cognitive load is the tax paid before any task thinking starts. It's high when density exists without hierarchy, when there are competing focal points at similar visual weight, or when the typography creates reading cost rather than reducing it. The `/visual` lens scores this through `hierarchy`, `density_fit`, and `critical_path` — three dimensions that together describe whether the eye is guided or left to do its own work.

## Stage five: component grammar

Stage five asks: do the components feel like they belong to this product? This is distinct from whether they work correctly or are visually well-crafted in isolation. It's about the coherence of the visual system.

Shadcn defaults produce a defensible starting point but not a specific one. Component grammar is what distinguishes a product that feels intentionally designed from one that feels assembled. Low `component_grammar` scores produce patches that are specific to the product's context: radius adjustments, palette refinements, density calibrations that encode the product's own visual sensibility rather than the library's default.

## Stage six: accessibility

Accessibility is evaluated in parallel, not after the fact. Contrast ratios are checked against WCAG 2.1 AA. Interactive elements are evaluated for keyboard reachability. Focus states are checked for visibility. Touch targets are evaluated for minimum size.

Accessibility failures surface as flags, not just patches — because some accessibility failures are blockers, not improvements. A form with no accessible labels isn't "slightly worse"; it's unusable for a portion of the user base. The flag distinction signals severity.

> **Pattern:** the stages aren't evaluated in strict sequence — they run in parallel — but the patches are ordered by stage. Structural patches (JTBD, cognitive) come first. Visual patches (craft, VCL, grammar) come after. Fixing visual issues on a structurally wrong layout wastes the fix.

## Reading a result with failures across multiple stages

When a build has failures across multiple stages, the patch order in the response reflects the priority: JTBD failures are critical priority, cognitive failures are high, visual failures are medium, grammar and accessibility are medium to low unless they're severe.

A result with a critical JTBD failure and several medium visual failures is telling you: fix the structure first, then revisit the visual. If you apply the visual patches before the structural one, the next call will re-run the same structural diagnosis on the new layout, and the visual patches may no longer apply after the structural change.

The design process is a sequence because that's how design review works. The stages build on each other. TheDesignAgent's job is to run that sequence faster and more consistently than it would happen in a human review cycle.
