> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/ux-methods/discovery/user-flows.md). # User Flows {% hint style="info" %} AKA User Flow Diagrams, Flowcharts {% endhint %} User flows, flow diagrams or flowcharts, illustrate the path a user takes through a system or website to accomplish a specific task or goal. These visual representations depict the sequence of steps, decisions, and interactions that a user experiences while navigating the interface. User flows use symbols and connectors to demonstrate the flow of information and actions between different screens, pages, or components. They help designers and stakeholders understand the logical progression of user interactions and identify potential bottlenecks or opportunities for improvement. User flows provide a visual roadmap of the user journey, highlighting the key touchpoints and decision points along the way. They assist in designing intuitive and seamless experiences, ensuring that users can accomplish their goals efficiently and effectively. User flows serve as a valuable communication and documentation tool, facilitating collaboration among designers, developers, and stakeholders throughout the design process. #### Further Viewing {% embed url="" %} #### Further Reading {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.designreference.xyz/ux-methods/discovery/user-flows.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.