journey-mappinglisted

# Journey Mapping ## Purpose Map complete user journeys with entry points, states, emotions, and decision points to ensure features serve real user needs. ## Scope Constraints Reads feature descriptions, user stories, and existing screen documentation for journey analysis. Does not modify files or execute code. Does not access user analytics data or production systems directly. ## Inputs - Feature description or user story - Target user persona (or enough context to infer one) - Existing screens/views if modifying an existing flow - Any known constraints (platform, auth requirements, data dependencies) ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Identify the user persona - [ ] Step 2: Define entry points - [ ] Step 3: Map the happy path - [ ] Step 4: Map alternate paths - [ ] Step 5: Map error and edge paths - [ ] Step 6: Identify friction points - [ ] Step 7: Design delight moments ### Step 1: Identify the User Persona - Who is this for? - What is their context (new user, power user, admin)? - What job are they hiring this feature to do? - What is their emotional state when they arrive (frustrated, curious, task-focused)? ### Step 2: Define Entry Points How does the user discover or arrive at this feature: - Direct navigation (sidebar, menu) - Deep link / URL - Notification or alert - Search result - Redirect from another