> ## Documentation Index
> Fetch the complete documentation index at: https://patterns.heurilens.com/llms.txt
> Use this file to discover all available pages before exploring further.
# How Analysis Works
> How Heurilens turns user behavior into measurable UX patterns.
## From user behavior to measurable UX patterns
Heurilens does not evaluate interfaces based on opinions, best practices, or design taste.\
It analyzes **what users actually do** when interacting with a product — and looks for
repeating behavioral traces that signal UX breakdowns.
A UX issue only matters if it leaves a trace in user behavior.
These traces may appear as:
* hesitation
* misclicks
* delayed decisions
* unclear intent
* reduced visibility
* broken feedback loops
When the same traces repeat across interfaces, they form **measurable UX patterns**.
***
## The analysis pipeline
Heurilens analysis follows a consistent four-layer model.
The page is analyzed as a system of components and sections — not as a visual screenshot alone.
Heurilens identifies:
* layout regions
* content hierarchy
* interactive elements
* affordance relationships
This creates a structural map of the interface.
Each structure is evaluated through known user behavior patterns.
Examples:
* multiple CTAs competing for attention
* headings without visual dominance
* actions that appear secondary but receive primary interaction
These are not guesses — they are derived from repeated real-world interaction outcomes.
When behavioral signals align with known failure modes, Heurilens classifies them into patterns.
A pattern represents:
* a recurring UX problem
* observable across products
* detectable through product signals
Each detected pattern produces a structured output:
* affected section
* detected pattern
* behavioral signal
* potential impact
* suggested fix direction
This output is consistent, comparable, and trackable over time.
***
## What Heurilens does NOT do
Heurilens intentionally avoids:
* subjective design critique
* generic UX advice
* one-size-fits-all best practices
* visual taste judgments
It does not ask *“Is this good design?”*\
It asks *“What does user behavior indicate here?”*
***
## Why this makes UX measurable
Traditional UX evaluation often stops at description.
Heurilens continues to measurement.
Instead of:
* “The hierarchy feels unclear”
You get:
* “This page shows delayed primary action due to competing visual priorities”
Instead of:
* “The CTA could be stronger”
You get:
* “Primary action receives lower attention than secondary elements”
This allows UX to be:
* compared
* tracked
* monitored
* improved with intent
***
## How this connects to patterns
Every page in this library documents a single UX pattern.
Each pattern answers one question:
**How does this UX problem appear on a real product — and how can it be detected?**
Patterns are the bridge between:
* UX theory
* user behavior
* product analytics
* actionable output
***
## What comes next
See how individual UX problems are documented as measurable patterns.
Run your first Heurilens analysis and explore the output.
Heurilens does not aim to explain UX —\
it aims to make UX **visible, comparable, and measurable at the product level**.