Map User Journeys with Flow Diagrams

Creates comprehensive, actionable user flow diagrams that map user journeys, decision points, system interactions, and edge cases for digital products, combining diagramming technique with UX principles.

Use this skill when mapping a new user journey or feature flow, documenting decision points and branching logic, designing error state and recovery flows, planning cross-platform touchpoints, or structuring an onboarding flow architecture. Not a fit for high-fidelity visual design (that belongs to prototyping) or for backend system architecture diagrams unrelated to user-facing flows.

Defines standard flow notation: ovals for entry/exit points, rectangles for process steps/screens/actions, diamonds for decision points, parallelograms for input/output operations, circles as connectors for complex flows, arrows for direction, and dotted lines for optional paths or system processes. Structures flows into a hierarchy of primary path (ideal journey), alternative paths, error paths, and edge cases.

Best practices start with defining clear user goals, personas, and emotional states before mapping, using a documentation template capturing flow title, user type, entry point, success criteria, and assumptions. Provides worked flow diagram examples: a screen-level CTA-click decision flow, a multi-path product search flow with results/no-results and filter branches, and a login error-state flow handling invalid credentials, retry attempts, and account lockout with recovery options.

Cross-platform integration guidance covers mapping touchpoints across web, mobile, and email, system notifications and triggers, and offline/online state handoffs. Interaction design integration covers micro-interaction mapping (hover states, loading states, gesture interactions, animation timing) and accessibility considerations (keyboard navigation paths, screen reader announcements, focus management, voice interface alternatives).

Flow validation follows a four-part stakeholder review process (technical, business, UX, content) and a testing/refinement loop (flow step to prototype to usability test to iteration). Analytics mapping guidance covers defining conversion funnels, event tracking for key interactions, drop-off point identification, and A/B test opportunities. Complex flow patterns include progressive disclosure (overview to detail to action) and conditional logic flows branching by account type/tier. A six-stage onboarding flow architecture covers welcome/value prop, account creation, profile setup, feature introduction, first success moment, and ongoing engagement.

Documentation guidance provides a flow specification format (trigger, preconditions, numbered steps with system responses, exit conditions, edge cases) and handoff guidelines covering interaction specs, content requirements, technical constraints, responsive behavior, and performance considerations, plus version control practices for tracking flow changes and archiving deprecated flows.

Produces diagram specifications intended for handoff into design/prototyping tools and analytics platforms for funnel and event tracking, without dependency on a specific diagramming tool.

UX designers and product teams mapping user journeys who need standard notation, decision-branch documentation, and error-state coverage rather than an ad hoc, undocumented flow sketch.

Flow Step -> Prototype -> Usability Test -> Iteration -> Refinement