How to Design a User Journey Using Claude
What this actually means
Using Claude to design a user journey isn't about asking "write me a user journey" and accepting whatever comes back. It's about using Claude as a thinking partner across each stage of the process — research, mapping, gap analysis, copy, and testing — with you supplying the real context and Claude accelerating the structured output.
Step 1 — Define the user and the problem before opening Claude
Claude produces significantly better user journey work when you give it real inputs rather than asking it to imagine a generic user.
Before you start, prepare:
- Who the user is — role, motivation, context
- What they are trying to achieve
- What product or service they are interacting with
- What you already know about where they drop off or struggle
The quality of your input directly determines the quality of Claude's output. A one-line prompt produces a generic journey. A detailed brief produces something you can actually build from.
Step 2 — Build the persona first
Start the conversation by asking Claude to build a research-grounded persona from the context you provide.
Prompt example:
"I'm designing the user journey for a Lithuanian freelancer trying to open a European IBAN account online for the first time. They are self-employed, 28–40 years old, tech-comfortable but not technical, and have been rejected by a traditional bank because they lack a local address. Their primary concern is trust and speed. Build me a detailed persona including their goals, fears, objections, and what a successful outcome looks like for them."
Claude will produce a structured persona you can use as the foundation for every subsequent stage of the journey. Iterate on it — push back on any assumption that doesn't match your real user data.
Step 3 — Map the full journey stage by stage
Once you have a persona, ask Claude to map the end-to-end journey across the standard stages: Awareness, Consideration, Decision, Onboarding, Activation, Retention, and Expansion.
Prompt example:
"Using this persona, map the complete user journey from the moment they first realise they need a European IBAN to the moment they complete their first SEPA transfer. For each stage, give me: the user's primary goal, their emotional state, the actions they take, the touchpoints they interact with, and the questions going through their mind."
Ask Claude to produce this in a table format with one row per stage — it becomes immediately usable as a working document.
Step 4 — Identify friction and drop-off points
This is where Claude becomes most valuable. Once the journey is mapped, ask it to analyse where the journey breaks down.
Prompt example:
"Now review this journey critically. For each stage, identify: what could go wrong, what would cause this user to abandon, what objections they haven't yet voiced, and what competitors are doing better at this specific moment. Flag the three highest-risk drop-off points."
This produces an honest gap analysis rather than an optimistic journey map. Most journey maps show the happy path. Claude's critical review surfaces the friction that actually kills conversion.
Step 5 — Write the copy and messaging for each touchpoint
Once the journey and friction points are mapped, Claude can draft the actual copy — emails, in-app messages, landing page headlines, onboarding prompts — for each stage.
Prompt example:
"Write the copy for the first three emails in the post-registration onboarding sequence for this user. Email one should arrive immediately after sign-up and focus on trust. Email two should arrive at day two and focus on completing KYC. Email three should arrive at day five and be triggered only for users who completed KYC but have not yet made a deposit. Each email should be under 150 words and written in plain, direct language."
Claude will produce drafts you can test immediately. Iterate by feeding back what your real users responded to — "the day-two email had a 12% open rate, here's why we think it underperformed, rewrite it with this angle instead."
Step 6 — Build the re-engagement and retention layer
Most journey design stops at first conversion. Ask Claude to extend the map into retention.
Prompt example:
"This user completed their first SEPA transfer 10 days ago and has not logged in since. Design a re-engagement sequence — three touchpoints maximum — that brings them back without feeling like spam. Each touchpoint should offer something genuinely useful rather than just a reminder."
Claude will generate a sequence you can implement directly in your email or CRM platform.
Step 7 — Stress-test the journey with edge cases
Before finalising, ask Claude to play devil's advocate.
Prompt example:
"Play the role of this user at stage three — they have just seen the account opening fee and are comparing it to Revolut which has no fee. Write the internal monologue of someone about to abandon the sign-up flow. Then tell me what one change to this stage would most reduce that risk."
This forces the journey map to confront real-world competitive pressure rather than assuming the user is fully committed at every stage.
Step 8 — Turn the journey into a testable framework
The final step is converting the journey map into a set of hypotheses you can A/B test.
Prompt example:
"Based on this user journey, give me five specific A/B test hypotheses — one per high-risk stage — with a clear prediction, the metric that would confirm or deny it, and a minimum test duration estimate."
Claude will produce a structured testing backlog you can take directly into your product or marketing team.
What Claude cannot do in this process
Claude cannot replace real user interviews, session recordings, or actual behavioral data. The best user journeys built with Claude use it to structure, draft, and stress-test — but are grounded in real observation. Feed Claude your actual data, real user quotes from interviews, and actual drop-off metrics from your analytics — and the output becomes significantly more accurate and actionable than anything built from assumptions alone.