Experience Map

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

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

AI-generated overview

Creates experience maps of multi-channel user touchpoints, channels, emotions, pain points, and opportunities.

What it does
This skill guides the creation of an experience map that documents a service's full ecosystem of user interactions across touchpoints, channels, and time. It defines a horizontal axis of phases (awareness through advocacy/departure) and vertical layers covering user actions, touchpoints, channels, emotions, pain points, and opportunities. It also addresses ecosystem relationships such as how touchpoints connect, data flow between channels, and human-automated handoffs. The output is a structured map rather than a file or code artifact.
When to use it
Use it for new products, omnichannel evaluation, ecosystem gap analysis, and cross-team alignment. It is intended when the experience spans more than one product or channel. For a single persona's linear journey or backstage operations, the skill points to other approaches.
Requirements
No tools, packages, runtimes, credentials, or network access are required; it is instructions only and ships no scripts.

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

Source and attribution

Source:owl-listener/designer-skillsinux-strategy/skills/experience-mapat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Experience Map Agent Skill | SourceWeft