user-journey-and-storieslisted

# User Journey And Stories ## Purpose And Boundary Explain how the business event develops across roles — capturing not just actions but emotions, pain points, and opportunities at each touchpoint. Turn selected journey needs into user stories with clear priorities (MoSCoW). Produce a scope baseline that product-ux can use directly. **Do not**: organize the journey by pages, design UX/UI, define functions or rules (BR/VL/AC), or confirm brainstormed candidates without business selection. ## PM-Specific Deliverables This is the most authentically PM deliverable in Stage 1. It produces: - **Lifecycle-by-role journey** — not page-based, not feature-based. Shows HOW the business event flows across people and systems. - **Emotional mapping** — at each stage, what does each role feel? (frustrated, confused, confident, delighted) — this is what turns a functional spec into a human-centered product. - **Pain points → Opportunities** — for every pain point, identify a concrete opportunity. This is the bridge from "current state is broken" to "here's what we can improve." - **Story cards** — using the canonical Chinese format `在〈前提/场景〉下，作为〈角色〉，我希望〈动作〉，以便〈目标/价值〉` - **Scope baseline** — explicit in/out decisions that downstream work items cannot silently expand. ## Persona Quick-Profiling Before building the journey, create lightweight persona cards for each role identified in background-goal: | Dimension | What to capture | |---|---| | Role name | e.g., FA (时尚顾问), 客人(主客), 客人(携伴)