agentleFS
miguelclavelmiguelclavel/ux-research-skills/skills/journey-map/SKILL.md

journey-map

Skill1 starsChanged 38 days agoMITView on GitHub

Build a current state customer journey map from research: stages, actions, thinking, feelings, pain points and opportunities, with evidence for each. Use when someone asks for a journey map, experience map, a service blueprint starting point, or wants to see where an experience breaks down.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prioritize.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • blueOctopusAISkill

    prioritize

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Evidence: Every pain point has a source: participant ids, an analytics drop off, a support ticket theme.

    line 15
  2. Distinctive:

    Don't map the ideal journey and call it research.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Journey map

Map what happens today, from evidence, before mapping what should happen.

Steps

  1. Scope. One persona or segment, one scenario, a clear start and end ("from renewal notice to new policy").
  2. Stages in the person's words, not the company's org chart (four to seven).
  3. For each stage: what they do, what they're thinking (with a real quote), how they feel (a simple high, neutral, low line), the channels and touchpoints, and the pain points.
  4. Evidence. Every pain point has a source: participant ids, an analytics drop off, a support ticket theme. Mark anything assumed.
  5. Moments that matter. The two or three points where people decide to continue or leave.
  6. Opportunities framed as "How might we..." questions tied to specific pain points, not solutions.
  7. Behind the scenes (optional): the systems and teams behind each touchpoint, which turns it toward a service blueprint.

Output

A table with stages as columns and the rows above, then the moments that matter and the opportunity questions. Keep it readable in one screen.

Don't

  • Don't map the ideal journey and call it research. Don't smooth over the low points.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.