Remote Usability Testing When You Only Have a Week

Remote usability testing fits Hong Kong product calendars: distributed users, busy stakeholders, and decisions due before build. You do not need a lab — you need a clear task, five participants, and discipline in synthesis.

Day 1: Define tasks, not features

Write three realistic jobs (book a service, compare options, fix a failed payment). Tasks should mirror intent, not click-by-click instructions. Success is completing the job, not finding a button.

Days 2–3: Recruit and schedule

Five sessions surface most critical issues. Use customers, waitlists, or social posts. Short screening questions filter for people who match your actual audience — not only friends who say everything is fine.

Days 4–5: Run and record

• Think-aloud protocol — ask users to narrate choices.
• One facilitator, one note-taker (or recording).
• Avoid leading questions; probe with what did you expect?

Day 6–7: Synthesize into fixes

Cluster issues by severity and frequency. Ship the top three fixes that unblock the core flow. Share a one-page summary with clips or timestamps so skeptics see the same pain you did.