All Methods
Implementation

Usability Testing — Early Concepts

Implementation TrackScope KnownEarly Stage

What it is

Moderated or unmoderated sessions in which representative users attempt tasks with a low-fidelity prototype, to surface fundamental usability problems before visual design.

Why use it

Problems found in wireframes cost far less to fix than those found after high-fidelity design or development.

Use this when

  • A testable low-fidelity prototype covers the main flows
  • Key workflow decisions are untested with real users
  • Significant design investment is about to begin

You may not need this when

  • Prior testing or strong evidence supports the approach
  • The feature is a minor, low-risk change
  • Earlier research already answered the usability questions

Dependencies — what you need

  • Access to representative users
  • A testing environment or tools (Hubble, Microsoft Teams, in person)
  • Defined task scenarios and success criteria
All dependencies by type

People involved

  • Design
  • Research
  • Product

Typical outputs

  • Session recordings and notes
  • Prioritized usability issues, with how many participants hit each
  • Design recommendations for each issue
  • Evidence on how core workflows worked for the people tested

Template

Usability Testing (Early) template

A fill-in structure for running this method: what to prepare, what to do, what to record, and how to read the result.

Preview

How AI can help

AI as augmentation — not replacement

  • Draft a test plan and task scenarios from the prototype scope
  • Draft screener criteria for recruiting
  • Find patterns across session notes, citing sessions
  • Draft a findings summary with prioritized recommendations

AI prompt

A prompt for any AI assistant. It works only from material you paste in, keeps assumptions apart from findings, and leaves the decisions to you.

Preview

What might come next