Case studies

Visual cognitive load on a financial review screen: when the data was right but the layout fought the eye

The JTBD was correct. The workflow was sound. The screen still felt like work to look at. A visual lens evaluation on a loan review tool where the problem wasn't structure — it was parse cost.

Not every evaluation finds a structural problem. This one found a well-structured interface with a visual problem — and that distinction matters, because the fix is entirely different.

The interface was a loan application review tool for underwriters. Each application was a record; the underwriter's job was to review the key risk signals, read the applicant summary, and make a recommendation — approve, flag for committee review, or decline. The workflow was correctly shaped: one application at a time, the key signals visible without navigation, the recommendation action at the end of the review flow.

The JTBD sub-score was 81. Solid. The extraneous_load score was 76. The job was right and the ceremony was low.

The /visual scores told a different story. hierarchy: 51. density_fit: 48. critical_path: 44.

What the visual evaluation found

The interface had seven distinct visual regions: an application header with key identifiers, a risk signal panel with six badge-style indicators, a financial summary table, an applicant background section, a property details panel, a notes and history section, and an action bar at the bottom. All seven regions were rendered at approximately equal visual weight — similar card styling, similar typography scale, similar border treatment. The page had no dominant focal point.

An underwriter opening this screen had no visual guidance about where to look first. The risk signals — the highest-value information for a quick triage decision — were in a panel that looked identical to the property details panel. A first-time user would scan the entire page to find them. An experienced user would have memorized the layout and compensated for it with habit. Neither outcome is what the design intended.

The critical_path score of 44 named this directly: the most important information for the job — risk signal status — was not the most visually dominant element on the screen. Something else was claiming the primary visual focus: the application header, which had the largest type on the page, used for identifiers the underwriter already knew from clicking into the application.

The parse cost in practice

Visual cognitive load compounds with volume. An underwriter reviewing thirty applications in a day pays the parse cost thirty times. If each screen takes three seconds longer to orient to than it should — because the hierarchy doesn't guide the eye to the risk signals immediately — that's ninety seconds of accumulated overhead per day, across a job where deliberation time is already at a premium.

The subtler cost is attention quality. A screen that requires active scanning to find the important information is consuming working memory before the actual review starts. The underwriter arrives at the risk signals having already spent cognitive resources locating them. A screen where the hierarchy puts the risk signals first — visually dominant, immediately readable — lets the underwriter start the review at full attention.

Pattern: visual cognitive load is paid before the user does anything. On a screen visited thirty times a day, even small parse costs accumulate into real time and real cognitive overhead. Hierarchy is the fix, not reduction.

The patches

The visual patches were specific. They didn't reduce information — the underwriter needed all seven regions. They restructured visual weight so the hierarchy expressed priority.

Risk signals to primary visual prominence. The six risk badge indicators were pulled out of their equal-weight panel and placed at the top of the content area in a larger, more visually distinct treatment. High-risk and flagged signals received strong color differentiation — not decorative color, but semantic color that conveyed meaning at a glance. The panel became the first thing the eye landed on.

Application header de-emphasized. The applicant name and ID were real information, but not review-critical. The header type size was reduced from the largest on the page to a secondary level. The identifiers were still present and findable; they were no longer competing for primary visual attention.

Financial summary table: hierarchy within the table. The table had twelve rows of financial data at equal weight. Four of them were the key signals underwriters use for threshold decisions: LTV, DTI, income verification status, and property appraisal gap. These four received a distinct typographic treatment — slightly heavier weight and a subtle left-border accent on the row — so an experienced underwriter could locate the threshold values without reading all twelve rows every time.

Reduced competing focal points. Three other elements on the page had been styled with calls-to-action that competed visually with the primary action bar. Two were secondary links; one was a "print" button with icon treatment identical to the primary recommendation buttons. Visual weight was redistributed so the action bar at the bottom read as the singular destination for decision.

The result

The /visual scores after the patches: hierarchy: 84. density_fit: 79. critical_path: 81. The JTBD scores were unchanged — the structural changes hadn't affected the workflow fit, only the parsing ease.

The practical difference was observable in user sessions: orientation time to the risk signals dropped. Experienced underwriters confirmed they were spending less time scanning and more time on the actual risk assessment. The information hadn't changed. The hierarchy now expressed what mattered.

This case is useful precisely because the structural problem wasn't there. When jtbd_alignment is already high and the score is still low, the remaining work is visual — and visual problems require a different kind of analysis than structural ones. The /visual lens is where that work happens.