Skip to content

User Test Files ​

Every session with real users gets its own file in docs/records/user-tests/, dated and numbered (<date>-user-test-<n>.md), in the shape of a playtest file (Playtest Files): the date, the version with a link to its changelog, the focus, a short summary and the feedback as a flat list.

Why ​

A user test records what real users did with a version, and the next version is held against it.

How To Apply ​

  • The head names who took part by role, such as two shop employees and one store manager, never by name.
  • The tasks the users were given come before the feedback, one per bullet.
  • What a user did and what a user said are separate items, since the two often differ.
  • The feedback stays in the file until the director has reviewed it: no ticket and no agent brief from it before that review.
  • The number, the H1 with the DEV day, a version in progress and the summary follow Playtest Files.