agentleFS
thewyattbrocatothewyattbrocato/design-and-copy-skills/skills/journey-and-service-mapping/SKILL.md

journey-and-service-mapping

Skill2 starsChanged 12 days agoMITView on GitHub

Use when mapping, planning or critiquing how a person experiences a product or service over time, in any words or language - "make a customer journey map", "map the experience from first contact to renewal", "service blueprint", "what happens behind the scenes", "where do people drop off across the whole service", "which moments matter", "turn this research into a map", "is this journey map any good". Covers scope and who the map is about, phases, touchpoints, what people think and feel, front-stage and back-stage work, the evidence behind the map, opportunities, and how to present and use it. Not for one screen or flow inside a product (interface-behavior), planning or running research (user-research-basics), diagrams that explain how a thing works (teaching-interfaces) or the visual layout of a page (layout-structure).

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Every row answers a question someone asked.

    line 71
  2. Distinctive:

    No quote, name, number or curve without a source.

    line 72
  3. Distinctive:

    Every opportunity names its moment.

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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 and service mapping

A map sets one person's experience beside what the organization does in response, across time, so a group can see the seams no single team owns and agree on what is happening before arguing about fixes. Unguided, a model draws the template: a funnel from Awareness to Advocacy, a row of channel names, a smooth emotion curve with scores nobody measured, a persona with a name, an age and a quote, and closing "opportunities" such as "personalize the experience". It looks finished, states no scope, never says what it stands on and ends with no decision. This skill frames the map, labels its evidence, keeps only rows that earn their place, shows feeling honestly, marks the few moments that matter and ends with who does what next.

Do not produce

  • A persona name, age, job title, quote, count or "customers said" line that is not in the supplied material. Missing evidence becomes a labeled assumption or [to collect].
  • A map with no framing line (the person, where the story starts and ends, the decision it serves) or no status line (assumption draft, or built from named sources).
  • Phase names taken from the organization's funnel (Awareness, Consideration, Purchase, Retention, Advocacy) when the person's own steps can be named.
  • A smooth emotion line, or a 1-to-10 score per phase, with no measurement behind it.
  • A touchpoint row of bare channel names; cells of full sentences; the same words repeated down a row.
  • Marks on every phase, or opportunities attached to no moment ("improve onboarding", "personalize").
  • Padding rows whose cells say "N/A" or something true of every service.
  • A map that ends at the picture, with no next conversation, owner or test.

When to use

  • Making a journey map, blueprint, experience map or day-in-the-life view, from supplied research or from nothing.
  • Choosing which kind of map fits a question, or scoping one: whose map, which stretch, which decision.
  • Finding where people drop out of a whole service, or which moments deserve attention.
  • Critiquing a map, or turning a finished one into hypotheses, a workshop or a plan.

When not to use

  • One screen, flow or step inside a product (how checkout, delete or save behaves, what state shows): interface-behavior. A task flow with no feelings and no backstage needs only a flow diagram.
  • Planning or running research, writing guides, coding raw notes, building personas from evidence: user-research-basics. This skill uses what it produces and states what the map stands on.
  • Diagrams that explain how a mechanism works, onboarding and help: teaching-interfaces. Exercises that train a team in the method: practice-and-assessment.
  • The poster, slide or page grid the map sits in: layout-structure. Judging a finished screen: design-critique. All if installed.
  • An explicit instruction, an existing house template, a design system or a platform convention wins. Fill a given template and still add the framing and status lines. A map that already works gets a yes and at most one change.

When facts are missing

Most requests arrive without research. Deliver an assumption draft for people close to customers to correct, say so in the status line, mark guesses, and use [to measure] for numbers. Ask once, with a default, only when interactive and one answer would change the map; never reply with only questions. Do not invent drop-off rates, durations, survey scores, quotes or customer counts.

Decisions, in order

A small task starts at the decision it touches.

  1. Map or something lighter. Default: a map when the trouble sits between teams, channels or visits and nobody owns the whole stretch. Change to a plain flow diagram for one team's process with no consequence for the person, and to interface-behavior for one screen. Name the decision the map serves; if none is given, propose one in a line.
  2. Frame in three lines. Person: one primary person with a one-line stub from sources, never a biography. Slice: where the story starts and ends; start a step before the obvious start, end where the goal is met or the person leaves. Decision: what someone will choose after seeing it. Default: one person per map; change to several only if each gets the same rows on one timeline. State the trade: wide gives the picture with thin detail, narrow gives depth.
  3. Status line. Default: one line under the frame, either "assumption draft from the brief, to be corrected by people near customers" or "built from 6 interviews and 140 tickets, March to May; backstage rows rest on staff accounts only". Quotes and numbers carry their source; guessed cells are marked. Never dropped from anything shown to others. See evidence on the map.
  4. Family from the question. Default: journey for how people find, use and stay with one offering; blueprint for why delivery fails or what happens behind the scenes; experience map when the goal exists whatever brand serves it, so no purchase phase is required. Mental-model and ecosystem views are for gaps and relationships, with no time axis. Name the choice and why in one line; hybrids are fine when the purpose is stated. Details in families and scope.
  5. Phases from the person's side. Default: five to eight, named by what the person is doing or trying ("Work out which size", "Wait for the pickup slot"). Change to real time units for a day or week view; past twelve, split the map or narrow the slice. Show repetition as a loop, unordered activity as a cluster, ongoing activity once. Waiting and deciding between visits are phases even if no system sees them.
  6. Rows earn their place. Default for a person-centered map: what they do, what they think or ask, how they feel, where it touches the organization (with its need, time and place), what goes wrong, and opportunities last. Add backstage rows only when the cause is internal, one row per actor when roles differ, metrics or rules only if someone will use them. Seven rows at most; drop any row that would be generic. See rows, cells and feeling.
  7. Cells and feeling. Default: three to seven words per cell, one sentence shape per row (verb-led actions, questions for thoughts, an -ing phrase for pain, a noun with context for touchpoints, a plain word for feeling). Longer evidence goes under the map with its source. Feeling is one or two named words per phase, mixed allowed; plot a line only when it was measured, and say how. Quantities as text, bars or a funnel shape, never more precise than collected.
  8. Mark few moments. One or two, three at most on a long map, each with a reason: a decision, a hand-off, a wait with no status, an earlier promise meeting delivery, a step that cannot be undone. Mark by evidence; without it, mark as "suspected" and name the check. A blueprint also marks where the service is most likely to break and its expected time. See blueprints and other views.
  9. From map to decisions. Each opportunity starts with a verb and attaches to a marked moment. Default: end with up to three hypotheses, "for [person] at [moment], doing [change] should produce [effect], seen as [measure] by [date]", each with an owner (a role, or [owner]) and a date (or [date]), a baseline placeholder where none was given, and the unchosen ideas shelved with a reason. Keep any future state beneath the current one, labeled a hypothesis. Change to a short fix list for a ticket-sized friction. See using the map.
  10. Present it. Frame and status first, then tell the story in order rather than row by row, and ask the room to correct it. As a page, the framing sits above the map and the whole phase strip is visible without sideways scrolling; as text, phases are columns up to six and rows beyond that. Polish matches the audience: a sketch for the team, a clean page for the board.

Narrow questions

"Which moments matter", "where do people drop off" and "which kind of map" get a short answer, not a full map. Drop-off is measured at the transitions between phases and includes exits outside the product; without counts, list suspected exits with the one measure that would confirm each. See evidence on the map.

Reviewing a map

Findings in this order, each with the evidence on the page and a fix: scope and status; family against the question; evidence behind the rows; rows and cells; honesty of the feeling and the numbers; moments, opportunities and the next step. Say what works first, rank by consequence, and rewrite only what was asked.

Output discipline

Deliver the map first (framing, status, the map, marked moments, next step), with no preamble, method essay or persona biography, because the reader came for the work. Give exactly the count or format asked for and honor any length cap. After the work, at most two one-line notes (an assumption, what a human must do).

Quick checks

  • One line names the person, the start and end, and the decision; one line states the status.
  • Phases are the person's steps, five to eight, not a funnel.
  • Every row answers a question someone asked; no cell is a paragraph or "N/A".
  • No quote, name, number or curve without a source; guesses are marked.
  • One or two moments are marked, each with a reason.
  • Every opportunity names its moment; the end names an owner, a measure and a date.

References

  • references/families-and-scope.md: load to choose the kind of map, set altitude, breadth and the primary person, or size the effort.
  • references/evidence-on-the-map.md: load when research is supplied, when there is none, or for drop-off, "which moments matter" and opportunity ranking.
  • references/rows-cells-and-feeling.md: load when drawing, building or reviewing the rows, cell wording, feeling, numbers and the page.
  • references/blueprints-and-other-views.md: load for a blueprint, hand-offs and fail points, or a day, job, mental-model or ecosystem view.
  • references/using-the-map.md: load for a workshop, a future state, hypotheses, follow-through or a review.

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.