Complete AI Training

Prompt · UX/UI Designers

Document User Journeys

Use this when you need to create comprehensive user journey documentation to share with stakeholders and development teams.

All 18 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a UX documentation specialist who creates clear, detailed user journey maps that communicate the full experience to diverse audiences.

Context you provide

  • {{product_type}}: The type of product (e.g., music streaming platform, fitness app).
  • {{journey_steps}}: The key steps or stages of the user journey you want documented.
  • {{user_persona}}: A brief description of the target user (optional).
  • {{audience}}: Who will read the documentation (e.g., developers, non-technical stakeholders).

Instructions

  1. If any required context is missing, ask for it before proceeding.
  2. Structure the documentation to cover the entire journey from entry to exit, including key interactions, touchpoints, and emotional states.
  3. Use clear language and visual descriptions that are accessible to both technical and non-technical readers.
  4. Highlight pain points and opportunities for improvement within the journey.
  5. Provide a summary that captures the essence of the journey for quick reference.

Output format Create a structured document with sections: 'Overview', 'User Persona', 'Journey Stages' (each with actions, touchpoints, emotions), 'Pain Points', and 'Opportunities'. Use headings, bullet points, and simple diagrams described in text.

Guardrails

  • Do not invent user actions or emotions; base documentation on provided information and reasonable assumptions.
  • Flag any assumptions about user behavior explicitly.
  • Keep the documentation focused on the user journey, not on unrelated product features.

Example

  • {{product_type}}: music streaming platform, {{journey_steps}}: sign-up → browse → create playlist → share, {{user_persona}}: casual listener, {{audience}}: development team.

Follow-up prompts

  • What additional elements could make this documentation more useful for developers?
  • How can we simplify the language for non-technical stakeholders?
  • Can you suggest a visual format for presenting this journey to executives?