How customer journey mapping can improve your docs and customer experience
summary
Shows how customer journey maps turn research into concrete doc work: gather analytics and interviews, pick personas, list touch points and map emotions, then run sticky-note workshops to surface pain points. Tools used include Miro and Lucidchart. Example follows a Jupyter notebook install journey where docs lack FAQs and install steps fail newcomers. Outcome is actionable items, prioritized fixes and cross‑team owners; pitfalls are missing customer data, not updating maps, and leaving out critical departments.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:42About Hari Priya
- 1:25My experience
- 2:11Tips
- 3:08What is Customer Journey Mapping
- 4:52Elements of Customer Journey Mapping
- 8:36Customer Journey Mapping Requirements
- 11:41Who performs Journey Mapping
- 12:14How to conduct a workshop
- 13:36Journey map
- 16:57Benefits
- 17:30Who should be involved
- 18:08Common problems
- 19:27Mistakes to avoid
- 20:11Conclusion
- 20:35QA
- 20:52Questions
- 25:54Cognitive load
- 26:39Learning goal
- 30:36Other practices
related talks
38mWhy Journey Mapping is Essential for Digital Products
16mNo UI, Still a Journey: Mapping UX for the Unseen
40mDocumentation as User Experience
30mExample Mapping: A Structured, Collaborative Discovery Technique
51mGetting Real Value out of your Planning Efforts with Story Mapping
18mNavigating the Dev's Journey: Crafting an Effective Roadmap for Success
26mJust-In-Time Documentation: Employing Agile Methodology To Create Living Documentation
26mCustomer Obsession