DIREKT Prototype Testing

Objective

Validate comprehension and workflow before expensive implementation.

Public Pages constraints

Pages prototypes:

  • use synthetic names, numbers, images and coordinates;
  • contain no functioning authentication;
  • submit no personal information;
  • clearly state “prototype”;
  • may use static HTML/JS only;
  • must not call production/staging APIs.

Required studies

Customer trust comprehension

Tasks: locate a plumber, compare two profiles, explain each badge, identify expired evidence, choose contact method.

Success: participant accurately distinguishes checked identity, qualification, location and limitations.

Provider onboarding

Tasks: identify required evidence, save draft, correct rejected upload, interpret publication state.

Success: participant does not believe payment equals approval and can recover from interrupted upload.

Reviewer workflow

Tasks: inspect evidence, request correction, approve scoped check, identify privacy fields.

Success: consistent reasons and no accidental public disclosure.

Data collection

Record:

  • task completion;
  • time and errors;
  • misunderstood words;
  • confidence;
  • accessibility observations;
  • critical quotes paraphrased without personal identifiers;
  • design changes and decision owner.

Exit gate

No high-severity misunderstanding of “verified”, location precision or evidence currentness remains unresolved.