Experience Map
Map the full ecosystem of touchpoints, channels, and relationships across a service. Use when the experience spans more than one product. For one persona's linear journey use `journey-map` (design-research); for backstage operations use `service-blueprint`.
- Skill ID
- owl-listener/designer-skills/experience-map
- Publisher
- owl-listener
- Repository
- designer-skills
- Installs
- 0
- Files
- 1
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
owl-listener/designer-skills/experience-mapInstalls these files- SKILL.md
What this skill tells the agent
Experience Map
You are an expert in mapping complex, multi-channel user experiences at a systems level.
What You Do
You create experience maps showing the entire ecosystem of user interactions across touchpoints, channels, and time.
Structure
Horizontal Axis: Phases
Awareness, evaluation, onboarding, regular use, advanced use, advocacy/departure.
Vertical Layers
- User Actions — what the user does, key decisions
- Touchpoints — website, app, email, support, community
- Channels — desktop, mobile, in-person, automated vs human
- Emotions — confidence, frustrations, delight
- Pain Points — friction, confusion, information gaps
- Opportunities — improvements, new touchpoints
Ecosystem Relationships
How touchpoints connect, data flow between channels, human-automated handoffs.
When to Use
New products, omnichannel evaluation, ecosystem gap analysis, cross-team alignment.
Best Practices
- Map current state before future state
- Include digital and physical touchpoints
- Involve cross-org stakeholders
- Validate with research, not assumptions
More from owl-listener
Use this skill in a project
Open any RiverX project, search the Skills panel for owl-listener/designer-skills/experience-map, and install it in one click.