Q2.05.3Focus groups for concept response, not task usabilitydesignresearch

Focus groups elicit concept reactions but do not test individual usability

Aliases: concept reaction · group discussion · usability evidence

What it is

Focus groups reveal how people understand, discuss, and negotiate a concept response, but collective talk does not substitute for individual task usability. Usability evidence requires observing success, error, path, and recovery during interaction. Group opinion is primarily discourse and social-interaction data.

Why it happens

Discussion lets members trigger vocabulary, disputes, and contexts for one another. Actual operation depends on individual attention and action; peer cues, observational learning, and public evaluation alter paths. Asking whether a shown interface looks easy captures expectation, not task completion.

Studying it

Analyze concept comprehension, value language, concerns, and interaction. If usability is also needed, have each participant perform independently before discussion and analyze behavioral and group evidence separately. Do not interpret group vote shares as population preference.

Where it stops holding

For collaborative systems, group operation may be the target behavior, but it still requires observation of a realistic joint task. Early reactions do not predict purchase or sustained use. Focus groups also legitimately study norms, language, and shared meaning beyond marketing.

Applying it

  • Use groups for concept language, conflict, and social meaning.
  • Run usability tasks individually without peer assistance.
  • Report group themes separately from individual behavioral measures.
  • Validate usability through recorded success and error, not consensus.

Related

  • Same group: Q2.05.1 Conformity · Q2.05.2 Dominant speakers
  • Adjacent: Q2.06 Usability testing · Q3.10 Concept testing
  • Search terms: focus group concept testing · task usability · group discussion

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/Q2.05.3