mcpField
E
experience-map

experience-map

github.com/infrasity-labsDesign & UI15077 installsUpdated 18w ago
Repository

About experience-map

experience-map is a design skill for mapping complex user experiences across channels and touchpoints over time. It helps teams examine an ecosystem, connect interactions, and identify pain points and improvement opportunities.

Key features

  1. 01Maps experience phases over time
  2. 02Captures actions, touchpoints, and channels
  3. 03Tracks emotions, pain points, and opportunities
  4. 04Shows relationships and handoffs across touchpoints
  5. 05Recommends current-state mapping and research validation

Use cases

  1. 01Reviewing a new product experience
  2. 02Evaluating an omnichannel service
  3. 03Finding gaps across an ecosystem
  4. 04Aligning stakeholders across teams

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/infrasity-labs/dev-gtm-claude-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