Interaction Quality

Pain Point

A point in an experience where users encounter difficulty, friction, uncertainty, failure, or avoidable burden.

Concept facts

A pain point is a specific difficulty, friction, uncertainty, failure, or burden that negatively affects a person’s ability to complete a task or move through an experience.

Also known as
User problem, friction point, barrier, breakdown, service difficulty, critical incident
Used in
UX research synthesis, journey mapping, service evaluation, usability testing, field research, service recovery planning
Interpret with
Evidence source, user goal, severity, frequency, context, affected group, service consequence, and organizational cause

Plain-language explanation

A pain point is a moment where the experience becomes difficult for the user. It may involve confusion, delay, extra effort, missing information, unclear instructions, technical failure, service mismatch, or emotional stress.

The term is common in UX and service work, but it should be used carefully. A pain point should be grounded in evidence, not just a team’s assumption or a general complaint.

A strong pain point description explains what happened, who was affected, where it occurred, why it mattered, and what consequence it created.

Why it matters

Pain points help teams focus on problems that affect real user outcomes. They can reveal where users abandon tasks, make errors, lose confidence, ask for help, repeat work, or experience service failure.

They also help connect user experience with organizational causes. A pain point may come from unclear content, weak navigation, inaccessible controls, policy complexity, delayed staff response, or mismatched expectations.

Without clear definition, “pain point” can become vague. Rigorous use requires evidence, context, and prioritization.

Use contexts

  • Journey mapping
  • UX research synthesis
  • Usability testing analysis
  • Service evaluation
  • Field study findings
  • Complaint and support analysis
  • Prioritization workshops

Application guidance

Describe pain points specifically. Avoid broad labels such as “bad UX” or “confusing process.” Explain the user goal, the barrier, the evidence, and the likely impact.

Separate symptoms from causes. “Users call support after submission” may be a symptom. The cause may be weak confirmation, unclear status, delayed response, or missing next-step guidance.

Prioritize pain points using severity, frequency, affected users, service consequence, and feasibility of improvement.

Practical example

Applicants for a public legal aid service upload required documents but do not understand why some cases remain “pending verification” for weeks.

The pain point is not simply “slow service.” It is a specific breakdown: unclear status language, no explanation of the verification stage, no expected timeline, and no escalation path. This creates repeated office visits, support calls, and anxiety for people seeking legal protection.

Interpretive boundaries

  • A pain point is not automatically a design requirement.
  • Pain points should be evidence-based, not invented in workshops.
  • User frustration may be a symptom, not the root cause.
  • Some pain points come from policy or service rules rather than interface design.
  • Pain points should be prioritized by impact, not only visibility.

Applied at Userhub

Pain point analysis is relevant when Userhub identifies where people experience friction, uncertainty, errors, barriers, or service breakdowns in digital and institutional journeys.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

  • Flanagan, J. C. (1954). The critical incident technique. Psychological Bulletin, 51(4), 327–358. https://doi.org/10.1037/h0061470
  • Bitner, M. J., Booms, B. H., & Tetreault, M. S. (1990). The service encounter: Diagnosing favorable and unfavorable incidents. Journal of Marketing, 54(1), 71–84. https://doi.org/10.1177/002224299005400105
  • Lemon, K. N., & Verhoef, P. C. (2016). Understanding customer experience throughout the customer journey. Journal of Marketing, 80(6), 69–96. https://doi.org/10.1509/jm.15.0420
  • ISO. (2019). Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems (ISO Standard No. 9241-210:2019). International Organization for Standardization.

—

Cite this entry

APA

Userhub. (2026). Pain Point. UX Reference. https://userhub.com.bd/reference/pain-point/