> ## 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.
# User Story Match
> A measurable UX pattern where product flows succeed or fail based on how well they align with the user’s underlying goal, context, and expectation.
## Users arrive with a story already in mind
Users do not arrive as blank states.
They arrive with:
* a goal
* a context
* an assumption about how things should work
This implicit narrative is the **user story** — even if it is never written down.
When the product flow aligns with that story, progress feels natural. When it doesn’t, users hesitate, adapt, or abandon.
## What breaks when user stories don’t match
User story mismatches are subtle.
Users often:
* follow the flow, but feel friction
* complete steps without confidence
* question whether they are “doing it right”
* slow down near decision points
* abandon despite understanding the interface
This is not confusion. It is **narrative mismatch**.
## Observable behavior linked to story mismatch
When user stories and product flows diverge, behaviors include:
* detours from the expected path
* skipping steps users feel are irrelevant
* backtracking to validate assumptions
* hesitation before committing actions
* abandoning after partial completion
These signals indicate the product is asking users to play a different role than they expected.
## Where user story alignment matters most
Users are forming their initial mental model.
Risk:
* the product assumes knowledge users don’t yet have
* steps appear out of order relative to user intent
Result:
* uncertainty disguised as exploration
Users expect confirmation of their reasoning.
Risk:
* the flow jumps ahead of the user’s confidence
* important reassurance appears too late
Result:
* hesitation or reversal near commitment
Users want resolution, not explanation.
Risk:
* the product introduces new concepts mid-flow
* the system reframes the problem unexpectedly
Result:
* frustration or abandonment
## Story mismatch is measurable
Users do not say: “This flow does not match my user story.”
Instead, Heurilens observes:
* skipped steps
* alternative path exploration
* pauses before irreversible actions
* repeated confirmation behaviors
* exits after partial success
When these patterns cluster, a **User Story Match breakdown** is flagged.
## How Heurilens evaluates story alignment
Heurilens infers likely user intent based on entry points, referrers, and early interactions.
The system evaluates whether the next steps match what a user with that intent would expect.
Heurilens checks whether reassurance, validation, or confirmation appears at the right moments.
The system assesses whether the flow maintains a consistent story from start to finish.
## Example output from Heurilens
Users follow the flow but hesitate before completion.
The product introduces steps that do not align with the user’s original intent and mental model.
## Fix directions suggested by Heurilens
Heurilens does not suggest rewriting user stories.
Instead, it highlights:
* where the flow jumps ahead of user confidence
* where assumptions replace validation
* where context is missing
* where reassurance appears too late
The goal is not to change the user — but to **meet them where their story already is**.
## Why user story match matters
When user stories align:
* flows feel shorter
* decisions feel obvious
* users move forward without resistance
When they don’t:
* even correct flows feel exhausting
* confidence erodes quietly
* conversion and retention suffer
Story match is not about empathy alone. It is about **behavioral alignment at scale**.
## Related patterns
Flow continuity depends on narrative alignment.
Expectations guide story progression.
Language reinforces or breaks the story.
Emotional cues validate the user’s role.
Run an analysis and see where your product flow diverges from user intent.