UX & user experience

User Flow Diagrams & Task Flows Generator

Create clear, actionable user flow diagrams and task flows that visualize how users navigate through your product to accomplish specific goals. This prompt helps UX designers map user paths, identify friction points, optimize conversion funnels, and ensure seamless experiences from entry points to task completion across all user scenarios.

6 blanks to fill in · Added December 2025 · user-flows · task-flows · ux-diagrams · interaction-design · user-paths

The prompt

6 blanks

You are an expert UX designer specializing in creating user flow diagrams and task flows that optimize user experiences and drive conversions. Your task is to design comprehensive flow diagrams that visualize user navigation and task completion paths.

Product/Feature Context: [DESCRIBE YOUR PRODUCT, FEATURE, OR SPECIFIC FUNCTIONALITY]

User Persona: [DESCRIBE THE TARGET USER OR SEGMENT]

Primary User Goal: [SPECIFY THE MAIN OBJECTIVE THE USER WANTS TO ACCOMPLISH]

Entry Points: [IDENTIFY HOW USERS ARRIVE - E.G., HOMEPAGE, EMAIL LINK, SEARCH, SOCIAL MEDIA, DIRECT URL]

Key Screens/Pages Involved: [LIST MAIN INTERFACES, PAGES, OR SCREENS IN THE FLOW]

Existing Pain Points: [DESCRIBE CURRENT ISSUES - E.G., HIGH DROP-OFF RATES, CONFUSION, ABANDONMENT]

Business Objectives: [SPECIFY CONVERSION GOALS, SUCCESS METRICS, OR BUSINESS OUTCOMES]

Technical Constraints: [MENTION ANY LIMITATIONS - E.G., AUTHENTICATION REQUIREMENTS, THIRD-PARTY INTEGRATIONS]

Based on this information, create comprehensive user flow diagrams and task flows that include:

1. Flow Type Determination:
   - **Task Flow**: Linear, single-path diagram showing steps to complete one specific task (best for focused, goal-oriented actions)
   - **User Flow**: Multi-path diagram showing all possible routes users can take, including decision points and alternative paths
   - Recommend which type(s) to create based on complexity and use case

2. Complete User Flow Diagram:
   - **Entry Points**: All possible starting points for the user journey (homepage, landing page, email, notification, etc.)
   - **Screens/Pages**: Every interface the user encounters, labeled clearly
   - **User Actions**: Specific interactions required at each step (click, input, select, scroll, etc.)
   - **Decision Points**: Places where users make choices that branch the flow into different paths
   - **System Actions**: Backend processes, validations, or automated responses
   - **Exit Points**: All possible endpoints (success states, error states, abandonment points)

3. Visual Diagram Structure:
   - Use standard flowchart symbols:
     * Ovals/rounded rectangles for entry and exit points
     * Rectangles for screens/pages/steps
     * Diamonds for decision points
     * Arrows for flow direction and connections
   - Provide a legend explaining all symbols used
   - Organize flow from left-to-right or top-to-bottom for clarity
   - Use color coding to differentiate path types (happy path, alternative paths, error states)

4. Detailed Flow Elements:
   For each step in the flow, specify:
   - **Step Name**: Clear, concise label for the action or screen
   - **User Action**: What the user does at this step
   - **System Response**: What happens after the user acts
   - **Success Criteria**: What determines if the user can proceed
   - **Error Handling**: Alternative paths if validation fails or errors occur
   - **Time Estimates**: Approximate duration for each step (optional but helpful)

5. Multiple Scenario Coverage:
   - **Happy Path**: Ideal flow where everything works smoothly and users achieve their goal
   - **Alternative Paths**: Different valid routes to accomplish the same goal
   - **Error States**: What happens when validation fails, data is missing, or technical issues occur
   - **Edge Cases**: Uncommon but possible scenarios (first-time users, returning users, permission issues)

6. Friction Point Analysis:
   - Identify potential drop-off points where users might abandon the flow
   - Highlight steps with high cognitive load or complexity
   - Note mandatory vs. optional steps
   - Flag opportunities to reduce steps or streamline the process

7. Optimization Recommendations:
   - Suggest ways to minimize the number of steps to completion
   - Recommend progressive disclosure strategies for complex flows
   - Identify opportunities for automation or pre-filling information
   - Propose skip or fast-track options for experienced users
   - Suggest improvements to reduce errors and increase conversion rates

8. Success Metrics and Testing:
   - Define measurable success criteria (completion rate, time-to-complete, error rate)
   - Recommend A/B testing opportunities for alternative paths
   - Suggest analytics events to track at key decision points
   - Propose usability testing scenarios to validate the flow

9. Documentation and Annotations:
   - Provide detailed notes explaining complex interactions
   - Include business rules or logic that affect the flow
   - Document assumptions made during flow creation
   - Note dependencies on other systems or features

Ensure the flows focus on one primary goal per diagram to maintain clarity, use consistent visual language and labeling conventions, account for both new and returning user experiences, balance comprehensiveness with readability, and prioritize the user's perspective over internal system processes.

Open in ChatGPT

Blanks: Describe your product, feature, or specific functionality · Describe the target user or segment · Specify the main objective the user wants to accomplish · List main interfaces, pages, or screens in the flow · Describe current issues e.g., high drop off rates, confusion, abandonment · Specify conversion goals, success metrics, or business outcomes

How to use it

This prompt helps you create detailed user flow diagrams and task flows that visualize how users navigate through your product. Fill in the bracketed placeholders with specific information about your feature, target users, and the goals they want to accomplish. Be clear about entry points, key screens involved, and any existing friction points. The more detailed your input, the more actionable and accurate the resulting flow diagrams will be. Use the output to align teams, identify optimization opportunities, and guide interface design decisions.

Tips

Start by mapping the happy path first—the ideal flow where everything works perfectly—then add alternative paths, error states, and edge cases to build comprehensive coverage
Keep each flow diagram focused on one primary user goal rather than trying to show multiple objectives in a single diagram, which creates confusion and reduces clarity
Use actual screen names, button labels, and interface elements from your product so the flow diagram directly maps to implementation and serves as developer documentation
Include annotations for complex logic, business rules, or technical constraints that affect the flow but may not be visually obvious in the diagram structure
Validate your flow diagrams with real users through usability testing or cognitive walkthroughs to confirm your assumptions about user behavior and decision-making match reality
Identify and highlight friction points like mandatory form fields, authentication requirements, or multi-step processes that could cause abandonment and need optimization

Understanding Flow Types

User flows and task flows serve different purposes in UX design. Task flows are linear, single-path diagrams showing the steps required to complete one specific task, ideal for focused actions like password reset or checkout processes. User flows are more comprehensive, multi-branched diagrams showing all possible routes users can take, including decision points and alternative paths based on user choices or system states. Task flows assume a consistent starting point and focus on efficiency, while user flows account for multiple entry points and user types. The output will recommend which type best suits your needs based on complexity. Simple, linear tasks benefit from task flows, while complex features with multiple scenarios require full user flows.

Creating Effective Flow Diagrams

The generated flow diagrams follow established UX conventions using standard shapes and symbols for universal understanding. Ovals represent entry and exit points, rectangles show screens or pages, diamonds indicate decision points where paths branch, and arrows show directional flow. Each element is clearly labeled with concise, descriptive text. The diagrams organize visually from left-to-right or top-to-bottom for easy comprehension. Color coding differentiates path types—green for happy paths, yellow for alternatives, and red for error states. The output includes a legend explaining all symbols and colors used. Complex flows are broken into manageable sections or swimlanes to maintain readability while capturing all scenarios.

Mapping Complete User Journeys

The flow diagrams comprehensively map the entire user journey from entry to exit. They identify all entry points including homepage, landing pages, email links, notifications, or deep links, as different origins may affect subsequent paths. Each screen, page, or interface state is represented with user actions required and system responses triggered. Decision points show where user choices or system validations create branching paths. The output documents happy paths where users successfully complete their goal, alternative valid paths, error states with recovery options, and edge cases for first-time users, returning users, or special permissions. This comprehensive view reveals the complete user experience across all scenarios.

Optimization and Implementation

The output includes actionable recommendations to optimize flows by reducing friction and streamlining user paths. It identifies opportunities to minimize steps, eliminate unnecessary decision points, pre-fill known information, or provide skip options for experienced users. Each flow includes success metrics like completion rate, time-to-task-completion, and error frequency to measure effectiveness. The output suggests specific analytics tracking points at critical steps and decision nodes. It recommends A/B testing opportunities for alternative approaches and proposes usability testing scenarios to validate flow assumptions. Documentation includes business rules, technical dependencies, and edge case handling to support implementation and future maintenance.