UX Task Flow (Happy Path + Edge Cases)
314 views1 forks
UXproductflows
Prompt Content
<prompt>
<instruction>UX Task Flow Design Prompt</instruction>
<instruction>Role
You are a senior UX designer with expertise in user flow mapping and edge case analysis.</instruction>
<task>Task
Create a comprehensive task flow design for {{task}} within {{app_type}}, including both happy path and edge cases.</task>
<output_format>Output Format
JSON structure with the following components:</output_format>
<instruction>Required Components</instruction>
<instruction>Main Flow Steps
List each step in chronological order
Include user actions and system responses
Specify UI elements involved
Note any data inputs/outputs
Maximum 10 steps for optimal user experience</instruction>
<instruction>Success Criteria
Define measurable completion metrics
Include performance benchmarks
Specify expected user outcomes
List required validations</instruction>
<instruction>Edge Cases
Identify potential user errors
List system failures/timeout scenarios
Include accessibility considerations
Document offline/poor connection handling
Consider device-specific variations</instruction>
<instruction>Guardrails
Security requirements
Performance thresholds
Data validation rules
Error handling protocols
Compliance requirements</instruction>
<constraint>Constraints
Follow platform-specific design guidelines (iOS/Android/Web)
Ensure accessibility compliance (WCAG 2.1)
Maximum task completion time: 2 minutes
Maximum error recovery time: 30 seconds</constraint>
<instruction>Evaluation Criteria
Task completion rate
Number of steps
Error prevention measures
Recovery path clarity
Accessibility compliance
Cross-platform consistency</instruction>
<output_format>Return the complete JSON structure with all components fully detailed.</output_format>
</prompt>How to use UX Task Flow (Happy Path + Edge Cases)
Use this template as a starting point for UX, product, flows. Read the full prompt first, then adapt the details so the model has enough context to produce a useful answer.
- Copy the prompt: Start with the full template so the structure stays intact.
- Replace placeholders: Swap bracketed notes or generic examples with your real goal, audience, constraints, and source material.
- Add success criteria: Tell the model what a good answer should include, avoid, or prioritize.
- Iterate once: If the first answer misses the mark, ask for a revision with one concrete change.
Prompt engineering tips
- Use the tags as guardrails: Keep the output focused on UX, product, flows.
- Define the role: Tell the model what expert perspective it should use before it answers.
- Set the format: Specify whether you want bullets, a table, code, a checklist, or a polished draft.
Best use cases
UX Task Flow (Happy Path + Edge Cases) is most useful for people working on UX and product. It works best when you have a clear input, a specific output format, and enough background detail for the model to avoid generic advice.
- Turn a rough idea into a structured first draft.
- Create a repeatable workflow for UX, product, flows.
- Compare several options before choosing the final direction.
Customization checklist
Before running the prompt, add the details that make your situation different from a generic example. The strongest results usually include constraints, examples, audience notes, and a clear definition of done.
- Add your audience, product, role, industry, or project context.
- Include examples of what good and bad output looks like.
- Ask for one final review pass for clarity, accuracy, and missing assumptions.
Was this prompt helpful?
Sign in to leave feedback and help improve the catalogue.