Questions: User Experience Fundamentals

Question 1

A designer builds a checkout flow she considers intuitive and tests it with three colleagues who all navigate it successfully. She concludes the design is validated. What is the most significant problem with this conclusion?

• A. Three testers is statistically insufficient — at least ten are needed to validate a design
• B. Colleagues who know the product are not representative users; they cannot reveal where first-time users will struggle
• C. Testing should only happen after the final design is built, not during the prototype phase
• D. The checkout flow should be tested by developers, not designers, to avoid bias

Answer: (B)

Designers are experts in their own product, which makes them and their colleagues poor proxies for first-time users. A colleague who watched the checkout flow being built cannot experience the confusion a new user feels when encountering it cold. The gap between designer intent and user reality is exactly where UX problems live — and the only way to find it is to observe real users who have no prior familiarity. Option A reflects a common but secondary concern; the fundamental issue is who is doing the testing, not the sample size.

Question 2

A mobile app is technically usable — users can complete their tasks — but they frequently feel confused by error messages written in technical jargon and frustrated when actions seem to disappear without confirmation. This is primarily a failure of:

• A. UI design — the visual layout and interface components need to be redesigned
• B. Back-end engineering — error handling should be fixed at the system level before the UI is addressed
• C. UX design — the emotional experience of the product fails even though basic usability is achieved
• D. Accessibility — the app likely does not meet WCAG standards for users with disabilities

Answer: (C)

UX extends beyond technical usability into emotional design. A product where tasks can be completed but users feel frustrated, confused, or patronized has failed at the experiential level — and that failure is a UX problem. Clearer error messages (plain language that explains what went wrong), micro-interactions that confirm actions, and loading feedback that sets expectations are UX design interventions, not engineering fixes. Good UI alone cannot compensate for an experience that feels hostile or opaque.

Question 3

A designer who deeply understands how their own product works is well-positioned to predict where new users will struggle, since their expertise gives them a complete picture of the system.

• T. True
• F. False

Answer: False

Designer expertise is actually a liability when predicting user confusion. When you build a system, your mental model fills in ambiguities automatically — you cannot experience the confusion of someone who lacks that model. This is sometimes called the 'curse of knowledge.' A designer might find a three-step checkout obvious because she built it; a new user might abandon the cart because a button looks like a decorative banner. Observing real users is the only way to find the gap between designer intent and user reality.

Question 4

Designing for accessibility — ensuring a product works for users with visual impairments, motor limitations, or cognitive differences — typically improves the experience for all users, not just those with disabilities.

• T. True
• F. False

Answer: True

Accessibility constraints often force design improvements that benefit everyone. Captions on video help users in noisy environments; high-contrast text is easier for all users in bright sunlight; keyboard navigation benefits power users who prefer not to use a mouse; plain-language error messages help all users, not just those with cognitive differences. Good UX treats accessibility as a design constraint that reveals problems in the experience, not a checklist to satisfy for a minority audience.

Question 5

Why does UX quality depend on the number of design iterations rather than the quality of the initial concept? What does this reveal about the nature of design problems?

Model answer: Design problems are discovered through observation, not anticipation. No matter how skilled the designer, each round of user testing reveals problems that could not have been predicted because they emerge from the specific ways real users interpret and interact with the design — interpretations shaped by their prior experiences, expectations, and contexts that the designer cannot fully model. Each redesign addresses discovered problems but may introduce new ones. UX quality accumulates through cycles of testing and refinement, not through brilliance at the start.

This is the core epistemological insight of UX: you cannot fully know your own design's weaknesses from inside it. The iterative process — research, design, test, refine, repeat — is not a sign of inadequate initial thinking; it is the correct methodology for a problem where critical information only emerges through observation of actual use. This is why 'doing user testing' is not a phase at the end of design but a practice woven throughout.