Gumshoe · Method reference

Design QA

Check the built product against the approved design to catch implementation drift before release.

Conceptual illustration of design qa.
Effort
Medium
Participants
Not required
Remote friendly
Yes
Evidence / output
Expert review

What it is

A quality-assurance pass where designers compare the implemented product against the intended design specs, flagging visual, interaction, and behavioral discrepancies.

When to use it

During Implement, after development and before release, and after significant builds.

Why (value)

Protects the design intent through implementation, where spacing, states, and behaviors commonly drift from the spec.

How to run it

  1. Gather the approved designs and specs.
  2. Compare the build screen by screen and state by state.
  3. Log discrepancies with screenshots and severity.
  4. File tickets and work with engineering on fixes.
  5. Re-verify after fixes land.

Inputs and outputs

  • Inputs: Approved designs, specs, and the built product.
  • Outputs: A prioritized discrepancy list and verified fixes.

Time and effort

Medium. Scales with surface area and number of states.

Evidence and limitations

Produces expert-review conformance evidence that the build matches intent, not direct-user evidence that the intent is right. See Evidence and limitations.

Tips and pitfalls

  • Check all states, not just the happy path.
  • Provide clear, reproducible issue reports.
  • Separate build defects from design-change requests.

Variations

Visual QA, interaction QA, and cross-device or cross-browser QA.

Need help choosing and applying a method?

Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.

Discuss your project with Gumshoe Explore Gumshoe services

Sources and further reading

Experience orchestration extension (2026-11-07)

Add a proportionate rough-cut walkthrough of connected moments using current designs, communications, operational procedures, and available builds. Check continuity of language, context, permissions, status, timing, and recovery across handoffs. A mixed-fidelity walkthrough surfaces design risks but does not prove executed behavior. Verify submission, acceptance, publication, and downstream use separately where in scope; record unavailable evidence as Unable to verify.

Adapted from Risdon and Quattlebaum, Orchestrating Experiences (Rosenfeld Media, 2018), especially chapters 2–11.

Explore related methods

A general practice reference. This page does not establish that a method was used on a particular client project or that an outcome was measured.