返回提示词目录第 1384 页

竞品用户体验流程对比审查

依据提供的操作记录比较同一任务的体验,整理阻碍与亮点,形成设计取舍建议及待验证清单。

完整提示词

<context>
Competitive reviews usually turn into screenshot collages or feature checklists, and when produced by a model they often describe competitors' flows from memory, inventing step counts and screens that changed long ago. A useful audit compares the same task, done by the same type of user, from the same starting point, measured the same way, and ends with specific decisions: what to copy because users now expect it, what to avoid, and where there is room to be better.
</context>

<task>
Audit how these competitors handle this task.

<task_definition>
{{task}}
</task_definition>

<competitors>
{{competitors}}
</competitors>

1. **Scope.** Restate the task as a scenario with a clear start point (for example "lands on the homepage, logged out, on mobile") and end point, the user type, and the platform. Use the same definition for every product.
2. **Check the evidence.** For each competitor, note whether the input contains a walkthrough (notes or screenshots for the steps) or only a name. Analyse only what was supplied. For competitors with no walkthrough, do not describe their flow from memory: list them under Gaps with a walkthrough protocol (start state, device, account state, what to capture at each screen, the time limit) so the user can collect it. If no competitor has a walkthrough, produce only the protocol, a blank comparison table and the questions to answer, and stop.
3. **Comparison.** For each product with evidence, record: number of screens and required inputs (fields, choices, taps) from start to end; points where the user must create an account, pay or give permission; information shown before commitment (price, time, availability); error prevention and recovery; and the patterns used at each stage.
4. **Friction and delighters.** Per product, list friction points (unclear labels, forced sign-up, surprise costs, dead ends, extra steps) and delighters (smart defaults, saved state, previews, reassurance) with the step where each occurs. Rate friction severity: blocker, major, minor.
5. **Patterns.** Group what the products do into stages of the task and note which patterns are now conventional (most products share them, so users will expect them) versus distinctive.
6. **Recommendations.** For your product, or for a new design if none was given: adopt (conventions users expect, and strong ideas worth borrowing), avoid (patterns causing friction or dark patterns), and differentiate (gaps no competitor fills). Each with the evidence that supports it and a confidence level. Note that an expert walkthrough is not user evidence, and recommend which items to validate with users.
</task>

<constraints>
- Never invent screens, step counts, prices or features. Every observation cites the supplied walkthrough; anything not supplied is a gap.
- Count steps the same way for every product, and state the counting rule.
- Do not recommend copying dark patterns because a competitor uses them: confirmshaming, hidden costs, forced continuity or obstructed cancellation are listed as patterns to avoid.
- Do not copy competitors' copy, imagery or trade dress; borrow patterns, not assets.
{{> output/uncertainty}}
</constraints>

<output_format>
## Scope
## Comparison
| Product | Screens | Required inputs | Account / payment / permission points | Info before commitment | Notable patterns |
## Friction and delighters
Per product, a list with step, finding and severity.
## Patterns
## Recommendations
Three lists: Adopt, Avoid, Differentiate. Each item with evidence and confidence.
## Gaps
Missing walkthroughs with the protocol, and what to validate with users.
</output_format>

可替换内容

  • {{task}}
  • {{competitors}}
  • {{> output/uncertainty}}

分类与标签

设计创意、竞品分析、用户体验研究、流程对比、设计决策

前往 AI 图片创作