experience-map
/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`.
- Author
- Owl-Listener ↗
- Repository
- designer-skills ↗
- Licence
- MIT
- Last repository change
- 05.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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`.
Original author description
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`.
How it works
- What You Do
- Structure
- When to Use
- Best Practices
SKILL.md preview
--- name: experience-map description: 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`. --- # 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
Versions
The database has no other skills named experience-map.
Identical content appears in 4 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version c4161c30ac28 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90journey-map
Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flow-diagram` (prototyping-testing). - 100journey-mapping
Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction… - 100user-journey-design
Map user journeys with touchpoints, emotional states, pain points, and opportunities across the full arc of a user's experience over time. Use when the user asks to map a user journey, create a customer journey map, design a service blueprint, document touchpoints and friction… - 90service-blueprint
Map service delivery across frontstage actions, backstage processes, and supporting systems. Use when staff and operations are part of the experience. For the customer-visible layer only, use `experience-map`. - 100pm-journey-map
Customer journey mapping across the full lifecycle: awareness through renewal. Maps actions, touchpoints, emotions, pain points, and opportunities per stage. Domain-aware: includes compliance and onboarding milestones from domain-context.md. Use when someone says "journey map",… - 100user-journey-mapping
Creates customer journey maps and service blueprints that visualize touchpoints, user emotions, pain points, and opportunities across an end-to-end experience. Use when creating a journey map, customer journey, or CX map; visualizing a user's end-to-end experience for a specific…