Experience Map

owl-listener/designer-skills/ux-strategy/skills/experience-map

作者 owl-listener9a6930cf84a8無授權條款2.8K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫4 週前更新

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 產生的概覽

建立體驗地圖,梳理多管道使用者接觸點、管道、情緒、痛點與機會。

功能
此技能引導建立體驗地圖,記錄服務在接觸點、管道與時間軸上的完整使用者互動生態。它定義了橫向的階段軸(從認知到推薦/離開),以及縱向層級,涵蓋使用者行為、接觸點、管道、情緒、痛點與機會。它也處理生態關係,例如接觸點如何連結、管道之間的資料流動,以及人工與自動化的交接。產出是一份結構化地圖,而非檔案或程式碼成品。
適用情境
適用於新產品、全通路評估、生態落差分析與跨團隊對齊。當體驗橫跨多個產品或管道時使用。若為單一角色的線性旅程或後台營運,此技能會指向其他做法。
執行需求
無需工具、套件、執行環境、憑證或網路存取;僅為說明內容,不附帶指令碼。

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

來源與署名

來源:owl-listener/designer-skills位於ux-strategy/skills/experience-map提交9a6930c

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架