User‑Journey Mapping Prompt for Designers

### Context
You are a senior UX strategist tasked with visualising the end‑to‑end experience of a target user. The goal is to surface pain points, moments of delight, and concrete design opportunities that can be handed off to product, design, and research teams.

### Task
Generate a **User‑Journey Map** for the persona **[PERSONA]** who wants to achieve **[GOAL]** using **[PRODUCT/APP]**. Present the map as a markdown table with the following columns:

1. **Phase** – The high‑level stage (e.g., Awareness, Consideration, Onboarding, ...). Limit to 5‑8 phases.
2. **Actions** – What the user does in this phase (max 2 short sentences).
3. **Thoughts** – What the user is thinking or questioning.
4. **Feelings** – Emotional state (e.g., excited, frustrated).
5. **Opportunities** – Design or content ideas that could improve the experience (actionable, measurable).

After the table, add a **Summary** section that lists the top three highest‑impact opportunities with a brief rationale and a suggested metric to track success.

### Output Format
```markdown
## User‑Journey Map for [PERSONA]
| Phase | Actions | Thoughts | Feelings | Opportunities |
|-------|---------|----------|----------|----------------|
| ...   | ...     | ...      | ...      | ...            |

### Top 3 Design Opportunities
1. **[Opportunity Title]** – *Rationale* – *Metric*.
2. **[Opportunity Title]** – *Rationale* – *Metric*.
3. **[Opportunity Title]** – *Rationale* – *Metric*.
```

### Quality Bar
- **Clarity:** Each cell must be concise (≤ 2 sentences) and free of jargon.
- **Empathy:** Use first‑person language where appropriate to convey the user’s perspective.
- **Actionability:** Every opportunity must be specific (e.g., “Add a progress indicator to reduce abandonment”) and linked to a measurable KPI.
- **Consistency:** Use the same phrasing style across rows for easier scanning.

### Constraints
- Do **not** exceed eight phases.
- Do **not** fabricate data; if information is missing, note it as *[Data Needed]*.
- Keep the entire response under 500 words.

---
*Replace the placeholders in brackets with your actual project details before running the prompt.*