返回提示词目录第 1384 页

检查可用性测试原型准备情况

围绕测试任务核查原型路径、内容与设备设置,输出就绪结论、修复清单及试测计划。

完整提示词

<context>
Many usability sessions are spoiled by the prototype, not the design. Participants take a reasonable alternative path that was never linked and the moderator has to rescue them; placeholder text and "John Doe" data make people comment on the fake content; hotspot hints flash when someone clicks the wrong place, revealing the answer; typed fields do not accept input so tasks that depend on typing feel broken; the prototype keeps state from the last participant; large files load slowly on a participant's phone. Unmoderated tests are least forgiving because nobody can explain a dead end. Walking every task path, including the likely wrong turns, against the actual test tasks, then running a pilot session, catches most of this.
</context>

<task>
<tasks>
{{tasks}}
</tasks>

<prototype>
{{prototype}}
</prototype>
{{#format}}

<format>
{{format}}
</format>
{{/format}}

1. Readiness verdict: ready, ready with fixes, or not ready, with the main reason.
2. Task path coverage: for each task, the expected path, the 1 to 3 most likely alternative paths, and whether each is built, needs a "not available in this prototype" screen, or must be handled by the moderator.
3. Content and data: realistic names, numbers, images and copy that fit the scenario; consistent data across screens; no lorem ipsum where people need to read to decide.
4. Dead ends and off-path behaviour: unlinked elements, hotspot hinting turned off, form fields and how typing is simulated, back button behaviour, scroll and fixed elements.
5. Technical and device setup: device and screen size, sharing method, load time, offline or slow-network risk, accessibility of the prototype if testing with assistive technology.
6. Reset and session logistics: how to reset state between participants, a starting link per task if needed, a backup copy, and what the moderator does if it breaks.
7. Fix list ordered by impact on the tasks, then a pilot session plan.
</task>

<constraints>
- Judge readiness against the given tasks only; do not ask for the whole product to be built.
- Do not invent prototype tool features; describe the need (for example "disable click hints") and say to check the tool's setting.
- If tasks reveal the answer through their wording or the prototype gives no way to fail, say so.
</constraints>

<output_format>
## Readiness verdict
## Task path coverage
| Task | Expected path | Likely alternative paths | Status |
## Content and data
## Dead ends and off-path behaviour
## Technical and device setup
## Reset and session logistics
## Fix list
| Fix | Affects task | Priority |
</output_format>

可替换内容

  • {{tasks}}
  • {{prototype}}
  • {{#format}}
  • {{format}}
  • {{/format}}

分类与标签

设计创意、可用性测试、交互原型、用户体验、试测准备

前往 AI 图片创作