---
name: user-flow-mapper
description: "Maps a user flow step by step, including branches and error states, and finds the decisions that make people quit, with a shorter version to try. Use when a product team sees users abandoning a signup, checkout, or setup flow and wants to find the step that loses them. Do not use for designing screens or running a usability test. Related topics: Design, Product, Planning."
---

# User Flow Mapper

Maps a user flow step by step, including branches and error states, and finds the decisions that make people quit, with a shorter version to try.

## When to use

Use this skill when a product team sees users abandoning a signup, checkout, or setup flow and wants to find the step that loses them. Do not use it for designing screens or running a usability test.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. List every step, branch, and error state in order, done when each has a named screen or action.
3. Mark what the user must decide or supply at each step and tag the heavy ones.
4. Overlay the reported drop-off and entry points to locate the likely culprit steps.
5. Sort steps into remove, defer, default, or keep, with a reason that respects the fixed constraints.
6. Draw the shorter flow and state what each cut costs, plus how to explain the forced friction.

## Inputs

- **The task** (free text, e.g. "What the user is trying to accomplish")
- **Every step today** (longer free text)
- **How people arrive** (longer free text)
- **Where they drop off** (longer free text)
- **Constraints that cannot be removed** (longer free text)

## Output

A step table with decisions required and drop-off notes, then a shorter proposed flow with the trade-off for each cut and a note on explaining required friction.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### User Flow Audit

Map and audit the flow below.

- The task: {{The task}}
- Every step today: {{Every step today}}
- How people arrive: {{How people arrive}}
- Where they drop off: {{Where they drop off}}
- Constraints that cannot be removed: {{Constraints that cannot be removed}}

Map the flow including the branches and error states people actually hit, not only the happy path. Against each step, mark what the user must decide or provide, because friction is usually a decision they are not ready to make yet. Show where the reported drop-off lands on the map.

Then say which steps can be removed, deferred, or given a sensible default, and propose the shorter flow with what it costs. Where a constraint forces friction, suggest how to at least explain it at that point.

## Pitfalls

- Mapping only the happy path, which hides the error branches where most users actually leave.
- Cutting a step that a legal or technical constraint requires instead of explaining it.
- Treating every step as equal when one decision accounts for most of the drop.
