Back to the Playbook
Define & DesignDD-12
How to test a prototype with users
Evaluate observed task behaviour without teaching the intended answer; evidence determines whether another round is necessary.
Product statusAssisted workflowTeklens prepares the tasks and analyses the observations; the sessions are run by people with real participants.
Input3 required inputsPrototype or product version and usability questions · Task scenarios and participant criteria · Initiative focus and approved Product Brain guidance
SkillsPrepare or assess a usability test · Synthesise supplied evidence · Prepare task contextDesigner + Product Designer Agent
OutcomeUsability test plan and findings: study scope, neutral task guide, observed behaviour with severity, and the revision plan.Artifact: Usability test plan
Owner
Designer
Human-led
Participants · Agents
ResearcherProduct ManagerProduct Designer Agent
Trigger
A prototype or working experience raises usability questions.
Required context
Design systemPrototype or product version and usability questionsFilesTask scenarios and participant criteriaProduct BrainInitiative focus and approved Product Brain guidance
Optional context
Meetings · BetaSession recordings or transcriptsCustomer evidencePrior usability findings
Skills
Prepare or assess a usability testSynthesise supplied evidencePrepare task context
Suggested conversation arc
- 1Prepare realistic test tasksTranslate questions into realistic tasks, check prototype coverage and define the relevant participant profile without revealing the intended navigation.Skills: Prepare task context · Prepare or assess a usability test
- 2Observe users attempting tasksRun sessions with appropriate participants, recording success, hesitation, misunderstanding and recovery without coaching. Retain evidence and prototype limitations.
- 3Analyse usability obstaclesRelate observed problems to tasks and severity with evidence links; distinguish recurring barriers from isolated issues or prototype artefacts.Skills: Prepare or assess a usability test · Synthesise supplied evidence
- 4Agree revisions and retestingSelect design changes and decide which uncertainty requires another user round. Preserve the original findings and document the rationale for not changing an item.
Output
Usability test plan and findings: study scope, neutral task guide, observed behaviour with severity, and the revision plan.
Artifacts
Creates: Usability test plan
What good looks like
- Tasks test behaviour without leading the participant.
- Findings are grounded in actual observations.
- Without observed sessions the output is a plan, not a result.
Quality gate
The Designer selects the changes and decides whether another round is needed.
Destination
Teklens onlyConfluence
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Choose the path that matches your role.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.