mcpField
E
experience-map

experience-map

github.com/owl-listenerDesign & UI3.1k2.1k installsUpdated 8w ago
Repository

About experience-map

A design skill for mapping user experiences across touchpoints, channels, and time. It helps teams examine ecosystems, handoffs, pain points, and opportunities for new products or omnichannel services.

Key features

  1. 01Map phases from awareness through departure
  2. 02Record actions, touchpoints, and channels
  3. 03Capture emotions, pain points, and opportunities
  4. 04Show relationships and handoffs across touchpoints
  5. 05Map current state before future state

Use cases

  1. 01Map a new product's end-to-end experience
  2. 02Evaluate an omnichannel service
  3. 03Identify gaps across an ecosystem
  4. 04Align teams around cross-channel interactions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill experience-map

After installing, type/experience-mapin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported