Part 2: The C.L.E.A.R. Diagnostic

A five lens system for spotting cognitive leaks in UI and UX (all credit to the incredible minds at growth.design)

Design is not decoration. It is cognitive engineering.

Most teams say they are designing for humans, then accidentally ship interfaces that tax attention, memory, and motivation. Users pay that tax as hesitation, confusion, second guessing, and drop off.

I call those moments cognitive leaks. They are the places where an experience loses momentum because the UI asks the brain to do extra work it did not sign up for.

This framework is how I find and fix those leaks. It is structured enough to be repeatable, but human enough to work in the real world where messy constraints exist. This is part two of a three part series where I dive into how to identify, diagnose, and fix those leaks to leave users feeling delighted, empowered, and understood instead.

Quick recap from Part 1

In Step 1, I set the standard of judgment:

  • the persona rung

  • the dream outcome

  • the emotional contract

With that in place, we can diagnose a UI without falling into preference debates.

Step 2: The C.L.E.A.R. Diagnostic

I use five lenses to find cognitive leaks:

C.L.E.A.R.

  • Copy

  • Layout

  • Emphasis

  • Accessibility

  • Reward

I run them one at a time. This matters because critique becomes chaotic when you try to fix everything at once.

C: Copy

Copy is navigation for the mind.

I look for four common leaks:

Jargon and invented language

If the user has to translate your terms, they lose momentum. If a term is required, define it where it matters. If it is not required, remove it.

Fluff that sounds good but says nothing

Fluff forces users to hunt for meaning. I rewrite it into plain claims:

  • what it does

  • why it matters

  • what happens next

Inconsistency

If the same concept is named three different ways across a flow, users slow down. Consistency is cognitive relief.

Missing microcopy at commitment moments

Users hesitate when risk is unclear.

  • Is this reversible?

  • What happens next?

  • Is there a cost?

  • Will I lose progress?

One sentence of microcopy can remove that hesitation.

L: Layout

Layout answers one question:
Is the path of least resistance the correct path?

I look for:

  • broken reading flow

  • scattered related elements

  • structure that reflects the company, not the user journey

  • pages that ignore scan behavior

Practical check:
If I give someone five seconds with the page, can they tell me what it is and what to do next?

If not, we are leaking attention.

E: Emphasis

Emphasis is hierarchy.

I look for:

  • competing focal points

  • too many “primary” actions

  • important information buried in noise

  • pages where everything is loud

A simple rule:
If two things are equally loud, the user does not know what matters. They guess, freeze, or leave.

Emphasis protects attention. Attention is the most expensive currency in UX.

A: Accessibility

Accessibility is not just compliance. It is clarity and resilience.

I check:

  • contrast and legibility

  • tap target size

  • meaning not conveyed only by color

  • interactive elements that look interactive

  • whether it works under stress and distraction

If an interface only works for a calm, focused user with perfect conditions, it is not truly usable. It is a demo.

R: Reward

Reward is the most underrated lens.

Reward is feedback, progress, and proportional value.

I look for:

  • progress signals

  • confirmation after actions

  • reassurance at high anxiety steps

  • effort that feels worth the payoff

People continue when they can feel progress.
When the UI fails to acknowledge effort, motivation collapses.

What Step 2 produces

At the end of C.L.E.A.R., I have a list of specific leaks, tagged by type:

  • Copy leak

  • Layout leak

  • Emphasis leak

  • Accessibility leak

  • Reward leak

This is useful because it turns “it feels off” into something you can actually fix.

But diagnosis is not the fix. That comes next.

Coming next in Part 3

In Part 3, I will show how I translate findings into psychological root causes and precise, testable solutions. This is the step that makes critique legible to engineering, leadership, and anyone who needs more than “trust me, it feels better.”

Stay Inspired

Get fresh design insights, articles, and resources delivered straight to your inbox.

Latest Blogs

Stay Inspired

Get fresh design insights, articles, and resources delivered straight to your inbox.

Part 2: The C.L.E.A.R. Diagnostic

A five lens system for spotting cognitive leaks in UI and UX (all credit to the incredible minds at growth.design)

Design is not decoration. It is cognitive engineering.

Most teams say they are designing for humans, then accidentally ship interfaces that tax attention, memory, and motivation. Users pay that tax as hesitation, confusion, second guessing, and drop off.

I call those moments cognitive leaks. They are the places where an experience loses momentum because the UI asks the brain to do extra work it did not sign up for.

This framework is how I find and fix those leaks. It is structured enough to be repeatable, but human enough to work in the real world where messy constraints exist. This is part two of a three part series where I dive into how to identify, diagnose, and fix those leaks to leave users feeling delighted, empowered, and understood instead.

Quick recap from Part 1

In Step 1, I set the standard of judgment:

  • the persona rung

  • the dream outcome

  • the emotional contract

With that in place, we can diagnose a UI without falling into preference debates.

Step 2: The C.L.E.A.R. Diagnostic

I use five lenses to find cognitive leaks:

C.L.E.A.R.

  • Copy

  • Layout

  • Emphasis

  • Accessibility

  • Reward

I run them one at a time. This matters because critique becomes chaotic when you try to fix everything at once.

C: Copy

Copy is navigation for the mind.

I look for four common leaks:

Jargon and invented language

If the user has to translate your terms, they lose momentum. If a term is required, define it where it matters. If it is not required, remove it.

Fluff that sounds good but says nothing

Fluff forces users to hunt for meaning. I rewrite it into plain claims:

  • what it does

  • why it matters

  • what happens next

Inconsistency

If the same concept is named three different ways across a flow, users slow down. Consistency is cognitive relief.

Missing microcopy at commitment moments

Users hesitate when risk is unclear.

  • Is this reversible?

  • What happens next?

  • Is there a cost?

  • Will I lose progress?

One sentence of microcopy can remove that hesitation.

L: Layout

Layout answers one question:
Is the path of least resistance the correct path?

I look for:

  • broken reading flow

  • scattered related elements

  • structure that reflects the company, not the user journey

  • pages that ignore scan behavior

Practical check:
If I give someone five seconds with the page, can they tell me what it is and what to do next?

If not, we are leaking attention.

E: Emphasis

Emphasis is hierarchy.

I look for:

  • competing focal points

  • too many “primary” actions

  • important information buried in noise

  • pages where everything is loud

A simple rule:
If two things are equally loud, the user does not know what matters. They guess, freeze, or leave.

Emphasis protects attention. Attention is the most expensive currency in UX.

A: Accessibility

Accessibility is not just compliance. It is clarity and resilience.

I check:

  • contrast and legibility

  • tap target size

  • meaning not conveyed only by color

  • interactive elements that look interactive

  • whether it works under stress and distraction

If an interface only works for a calm, focused user with perfect conditions, it is not truly usable. It is a demo.

R: Reward

Reward is the most underrated lens.

Reward is feedback, progress, and proportional value.

I look for:

  • progress signals

  • confirmation after actions

  • reassurance at high anxiety steps

  • effort that feels worth the payoff

People continue when they can feel progress.
When the UI fails to acknowledge effort, motivation collapses.

What Step 2 produces

At the end of C.L.E.A.R., I have a list of specific leaks, tagged by type:

  • Copy leak

  • Layout leak

  • Emphasis leak

  • Accessibility leak

  • Reward leak

This is useful because it turns “it feels off” into something you can actually fix.

But diagnosis is not the fix. That comes next.

Coming next in Part 3

In Part 3, I will show how I translate findings into psychological root causes and precise, testable solutions. This is the step that makes critique legible to engineering, leadership, and anyone who needs more than “trust me, it feels better.”

Stay Inspired

Get fresh design insights, articles, and resources delivered straight to your inbox.

Latest Blogs

Stay Inspired

Get fresh design insights, articles, and resources delivered straight to your inbox.

Part 2: The C.L.E.A.R. Diagnostic

A five lens system for spotting cognitive leaks in UI and UX (all credit to the incredible minds at growth.design)

Design is not decoration. It is cognitive engineering.

Most teams say they are designing for humans, then accidentally ship interfaces that tax attention, memory, and motivation. Users pay that tax as hesitation, confusion, second guessing, and drop off.

I call those moments cognitive leaks. They are the places where an experience loses momentum because the UI asks the brain to do extra work it did not sign up for.

This framework is how I find and fix those leaks. It is structured enough to be repeatable, but human enough to work in the real world where messy constraints exist. This is part two of a three part series where I dive into how to identify, diagnose, and fix those leaks to leave users feeling delighted, empowered, and understood instead.

Quick recap from Part 1

In Step 1, I set the standard of judgment:

  • the persona rung

  • the dream outcome

  • the emotional contract

With that in place, we can diagnose a UI without falling into preference debates.

Step 2: The C.L.E.A.R. Diagnostic

I use five lenses to find cognitive leaks:

C.L.E.A.R.

  • Copy

  • Layout

  • Emphasis

  • Accessibility

  • Reward

I run them one at a time. This matters because critique becomes chaotic when you try to fix everything at once.

C: Copy

Copy is navigation for the mind.

I look for four common leaks:

Jargon and invented language

If the user has to translate your terms, they lose momentum. If a term is required, define it where it matters. If it is not required, remove it.

Fluff that sounds good but says nothing

Fluff forces users to hunt for meaning. I rewrite it into plain claims:

  • what it does

  • why it matters

  • what happens next

Inconsistency

If the same concept is named three different ways across a flow, users slow down. Consistency is cognitive relief.

Missing microcopy at commitment moments

Users hesitate when risk is unclear.

  • Is this reversible?

  • What happens next?

  • Is there a cost?

  • Will I lose progress?

One sentence of microcopy can remove that hesitation.

L: Layout

Layout answers one question:
Is the path of least resistance the correct path?

I look for:

  • broken reading flow

  • scattered related elements

  • structure that reflects the company, not the user journey

  • pages that ignore scan behavior

Practical check:
If I give someone five seconds with the page, can they tell me what it is and what to do next?

If not, we are leaking attention.

E: Emphasis

Emphasis is hierarchy.

I look for:

  • competing focal points

  • too many “primary” actions

  • important information buried in noise

  • pages where everything is loud

A simple rule:
If two things are equally loud, the user does not know what matters. They guess, freeze, or leave.

Emphasis protects attention. Attention is the most expensive currency in UX.

A: Accessibility

Accessibility is not just compliance. It is clarity and resilience.

I check:

  • contrast and legibility

  • tap target size

  • meaning not conveyed only by color

  • interactive elements that look interactive

  • whether it works under stress and distraction

If an interface only works for a calm, focused user with perfect conditions, it is not truly usable. It is a demo.

R: Reward

Reward is the most underrated lens.

Reward is feedback, progress, and proportional value.

I look for:

  • progress signals

  • confirmation after actions

  • reassurance at high anxiety steps

  • effort that feels worth the payoff

People continue when they can feel progress.
When the UI fails to acknowledge effort, motivation collapses.

What Step 2 produces

At the end of C.L.E.A.R., I have a list of specific leaks, tagged by type:

  • Copy leak

  • Layout leak

  • Emphasis leak

  • Accessibility leak

  • Reward leak

This is useful because it turns “it feels off” into something you can actually fix.

But diagnosis is not the fix. That comes next.

Coming next in Part 3

In Part 3, I will show how I translate findings into psychological root causes and precise, testable solutions. This is the step that makes critique legible to engineering, leadership, and anyone who needs more than “trust me, it feels better.”

Stay Inspired

Get fresh design insights, articles, and resources delivered straight to your inbox.

Latest Blogs

Stay Inspired

Get fresh design insights, articles, and resources delivered straight to your inbox.