Experience Map
Map awareness-through-advocacy phases, touchpoints, channels, emotions, and ecosystem handoffs to align scope before building omnichannel products.
Overview
experience-map is an agent skill most often used in Validate (also Idea, Build) that produces a holistic multi-channel experience map with phases, touchpoints, emotions, and ecosystem relationships.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill experience-mapWhat is this skill?
- Horizontal phases: awareness, evaluation, onboarding, regular use, advanced use, advocacy/departure
- Vertical layers: user actions, touchpoints, channels, emotions, pain points, opportunities
- Ecosystem view: touchpoint connections, data flow, human-automated handoffs
- Best practices: current state before future state, digital plus physical, research-validated
- Cross-org stakeholder alignment for gap analysis
- Six horizontal lifecycle phases listed in SKILL.md
- Six vertical layers plus ecosystem relationships section
Adoption & trust: 566 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are shipping across web, mobile, and support but no shared view of phases, pain points, or handoffs—so scope churns and channels contradict each other.
Who is it for?
Founders scoping new products, omnichannel SaaS, or marketplace flows who need ecosystem-level UX clarity before prototyping.
Skip if: Single-screen UI polish with no multi-touchpoint journey, or teams that already maintain a validated service blueprint with fresh research.
When should I use this skill?
New products, omnichannel evaluation, ecosystem gap analysis, or cross-team alignment on the full user experience.
What do I get? / Deliverables
You produce a research-oriented experience map that exposes gaps and opportunities and aligns what to build first across teams.
- Experience map artifact with phases and layered rows
- Pain point and opportunity inventory
- Ecosystem relationship notes for data and handoffs
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Experience mapping clarifies full-journey scope and gaps early, before heavy Build investment—Validate is the canonical shelf. Scope subphase fits new products, omnichannel evaluation, and cross-team alignment called out in When to Use.
Where it fits
Lay out awareness and evaluation touchpoints to see where indie buyers first hear about the product.
Document onboarding versus regular-use channels to cut scope to the minimum viable journey.
Translate pain points on the map into ordered backlog items for engineering and content.
Extend the map through advocacy and departure to plan retention emails and win-back support paths.
How it compares
Broader than a linear user-journey map for one flow—it emphasizes channel ecosystem and data handoffs.
Common Questions / FAQ
Who is experience-map for?
Solo builders and small product teams planning multi-channel products who need one artifact for journey phases, touchpoints, and cross-channel gaps.
When should I use experience-map?
In Idea when exploring audience paths; in Validate when scoping onboarding and support; in Build when prioritizing which broken handoffs to fix first.
Is experience-map safe to install?
It provides planning templates only; review the Security Audits panel on this Prism page and treat outputs as sensitive if they include customer research data.
SKILL.md
READMESKILL.md - Experience Map
# 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