# Experience Map

> Map the full ecosystem of touchpoints, channels, and relationships across a service.

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`.

- Page: https://ss33.ai/skills/owl-listener/experience-map-31416566117
- Publisher: owl-listener
- Category: [Business](https://ss33.ai/skills/category/business-y1h0vy) › [Branding & design](https://ss33.ai/skills/category/business-y1h0vy/branding-and-design-e25ohe)
- License: MIT
- Source: https://github.com/owl-listener/designer-skills/blob/9a6930cf84a822eb458624bd11c61aac5bbdf224/ux-strategy/skills/experience-map/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/owl-listener/experience-map-31416566117

# 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