Prompt Examples

Here are some example prompts you can use with Arc to generate journey maps. These examples show different levels of detail and various use cases.

Simple Prompts

These work well for straightforward journeys:

E-commerce Checkout

A customer browses products, adds items to cart, enters shipping information, 
pays, and receives order confirmation.

User Onboarding

A new user signs up, completes their profile, takes a tutorial, and makes 
their first action in the app.

Detailed Prompts

More context helps Arc generate richer insights:

SaaS Trial Experience

A potential customer discovers our product through a blog post, visits the 
landing page, signs up for a free trial, goes through the onboarding wizard, 
explores key features, hits usage limits, receives upgrade prompts, and 
eventually converts to a paid plan. They're evaluating multiple tools and 
need to see value quickly.

Healthcare Appointment Booking

A patient needs to schedule a follow-up appointment. They search for the 
doctor's contact info, navigate the clinic website, find the booking system, 
check available slots, select a time, fill out forms, confirm details, and 
receive appointment reminders. They're anxious about their condition and 
want the process to be simple.

Industry-Specific Prompts

Food Delivery

A hungry customer opens the delivery app, browses restaurants, filters by 
cuisine and delivery time, adds items to cart, applies a promo code, 
enters delivery address, reviews order, pays, tracks delivery status, 
receives food, and rates the experience.

Financial Services

A first-time homebuyer researches mortgage options online, compares rates 
from different lenders, fills out a pre-approval form, uploads documents, 
waits for approval, reviews loan terms, signs documents, and closes on 
their home.

Flexible Scope

Journey maps don't always need to be broad, end-to-end experiences. Arc adapts to whatever scope you need:

Zoom in on a single flow

Map just the sign-up process: user lands on the page, fills out form, 
verifies email, sets preferences, and sees the welcome screen.

Focus on one phase in detail

Show me the "Checkout" phase with all micro-steps: reviewing cart, 
entering payment info, applying discounts, confirming order.

Narrow the scope

Create a journey from sign-up to first purchase, breaking it into 
5 detailed phases.

You can ask Arc to generate a full 5-phase journey spanning the entire customer lifecycle, or zoom in on just one small part of the experience. The map adapts to your level of detail.

Tips for Better Results

  1. Include context: Mention the user's goals, constraints, or emotional state.
  2. Be specific: Name the actual steps, not just "user does X".
  3. Add pain points: If you know where users struggle, mention it.
  4. Set the stage: Describe what happens before and after the main journey.
  5. Adjust scope: Specify if you want a broad overview or a deep dive into one area.

What Makes a Good Prompt?

  • Clear phases: Natural breaks in the journey (Discovery → Consideration → Purchase)
  • Specific actions: Concrete steps users take, not abstract concepts
  • User context: Who is this person? What are they trying to achieve?
  • Emotional cues: Frustration, excitement, confusion—these help Arc understand the experience

Example Output

When you use a prompt, Arc generates a structured journey map with:

  • Phases: Natural breaks in the journey (number varies based on your prompt)
  • Multiple steps per phase: Each with experience notes, friction points, and opportunities
  • Experience curve: Visual representation of emotional highs and lows
  • Industry insights: Benchmarks and context where relevant
  • Actionable solutions: Specific improvements for each pain point

For example, a broad "pizza ordering" prompt might create 5 phases (Discovery → Menu Exploration → Customization → Checkout → Post-Order), while a focused "sign-up flow" prompt might create 3-4 phases zooming in on that specific experience.

Try starting with a simple prompt, then iterate by adding more detail based on what Arc generates.

Was this page helpful?