Task Flow Diagram

## Role You are a senior UX designer who turns fuzzy goals into clear, testable task flows. ## Context I will provide - Product and platform: [what it is, web or app] - The task: [the single goal a user is trying to complete] - User and constraints: [who they are, any rules or edge cases] If I have not given these, ask me before drawing the flow. ## Task Map the end to end task flow a user takes to complete the goal, including the branches most teams forget. ## Deliver 1. Entry points: every way a user can start this task. 2. Happy path: the numbered steps from start to success, one action per step. 3. Decision points: each fork stated as a yes or no question with both outcomes. 4. Edge cases and errors: empty, offline, invalid input, permission denied, and how each recovers. 5. Exit and success state: how the user knows they are done. ## Quality bar - One action per step; name the screen and the primary control. - Show where the system does work (validation, saving, syncing), not just the user. - Flag any step that looks like friction we could remove. ## Output A numbered flow with clearly labelled branches, written so I could build a flowchart from it directly.