Research Overview

Research Overview (Test Phase)

In the test phase, research validates whether designs work for real users and produces actionable evidence for iteration. In plain terms: even when a product is “ready,” you keep iterating based on what real people do and say during testing.

Note

Source alignment: reflects the “research in the test phase” reading and the course overview wording that frames acceptance testing, benefits of testing prototypes, and how sessions are structured.

Why Test Now

• Catch friction before development commitment grows; reduce rework cost.
• Validate core tasks, language, and feedback; refine flows and UI details.
• Build confidence with stakeholders using direct evidence from sessions.
• Accept that designs can and should be iterated, even near launch, to improve the end‑user experience.

Note

Think of this as acceptance testing from a UX angle: “Does the thing actually work for users the way it’s intended?” If not, refine and try again.

Types of Test‑Phase Research

• Usability study (core method)
  • Assess ease of completing tasks; observe behaviors and collect light KPIs.
  • Moderated or unmoderated; remote or in‑person.
• User acceptance testing (UAT)
  • Confirm the product does what it’s intended to do from the user perspective.
  • Often aligns with pre‑launch readiness checks.
• Quality assurance (QA)
  • Identify errors or broken flows; file reproducible bug reports.
  • Can include accessibility checks as part of definition of done.
• Accessibility evaluation
  • Ensure people with disabilities can perceive, operate, and understand the UI.
  • Combine standards checks with real usability observations using assistive tech.

Tip

When combining methods (e.g., usability + accessibility checks), separate findings by method so it’s clear what’s a bug vs. a design usability issue vs. a standards violation.

Research Structure

• Participants
  • Recruit representative users from the target audience; avoid convenience sampling.
  • Include a range of abilities and demographics.
• Location
  • Lab or remote; ensure reliable recording setup and clear consent.
  • For remote, test platforms with assistive technologies ahead of time.
• Instruments
  • Script with tasks and probes; questionnaires for post‑task and post‑study ratings.
  • Note template keyed to tasks and KPIs; clip timestamps for highlights.

Questionnaire Examples

• Task prompts
  • “Search for a leather shoe in your size. How was your experience searching for it?”
  • “Select the leather shoe and go through checkout up to payment. How did you like the checkout process? What would you improve?”
• General questions (post‑study)
  • “How do you feel about the design and navigation?”
  • “Did you find all the information needed to make an informed decision?”

Tip

Ask task‑specific questions right after the task, then broader reflections after the session. This mirrors how participants experience the product and keeps answers grounded.

Questionnaires

• Task‑based prompts
  • After each task: ease, clarity, confidence (short scales) and “why.”
• Post‑study questions
  • Overall impressions, most/least useful, top improvements, likelihood to use/recommend.

Note

Keep observations descriptive: what users did, said, and where they hesitated. Save interpretation for debrief and analysis so multiple observers can agree on the facts first.

Language & Communication in Research

• Language shapes comfort and candor; match tone to context to help participants be open and honest.
• Your words influence participant wording; choose language that accurately represents participants’ ideas in questions, notes, and transcripts.
• Consider word choices and dialects; when unclear, ask participants to clarify rather than assume.
• Avoid ableist phrases and commanding tone; prefer inclusive alternatives (e.g., “let’s go through the details”).
• Mind context and power dynamics (e.g., seating/standing); adjust to meet participants where they are and create an equitable environment.

Summary: Test‑phase research uses usability studies and complementary checks (UAT, QA, accessibility) to gather evidence. Structure sessions, recruit the right people, and pair questionnaires with observation for a clear picture of how designs perform.