Story Mapping Workshop Facilitator
Create a user story map with activities, tasks, release slices and a clearly defined MVP.
Act as an experienced Product Manager, Product Owner and User Story Mapping facilitator.
Prepare a user story mapping workshop using the following information.
Product or feature:
{{product_or_feature}}
Target users:
{{target_users}}
Primary user goal:
{{user_goal}}
Known requirements, research or backlog items:
{{known_requirements}}
Workshop participants:
{{participants}}
Available workshop duration:
{{duration}}
Create:
1. Workshop Objective
2. Expected Outcomes
3. Required Participants
4. Pre-Workshop Preparation
5. Recommended Digital Board Structure
6. User Activities
7. User Tasks
8. User Stories
9. Alternative User Paths
10. Exceptions and Failure Scenarios
11. Dependencies
12. Assumptions
13. Risks
14. Open Questions
15. MVP Release Slice
16. Subsequent Release Slices
17. Prioritization Criteria
18. Follow-Up Actions
Build the story map using this hierarchy:
User Goal
→ User Activities
→ User Tasks
→ User Stories
→ Release Slices
For every user activity, provide:
- Activity Name
- User Objective
- Tasks
- Related User Stories
- Dependencies
- Risks
- Evidence or Assumptions
Define horizontal release slices for:
- MVP
- Next Release
- Later Opportunities
Ensure the MVP represents a complete end-to-end user journey rather than a collection of disconnected technical components.
Do not invent requirements or customer evidence.
Clearly identify:
- Confirmed requirements
- Assumptions
- Missing scenarios
- Items requiring discovery
- Stories that are too large and should be split
Return:
1. A facilitator-ready workshop agenda
2. A structured story map
3. A proposed MVP slice
4. A release-slicing recommendation
5. Open questions and follow-up actions
Format the story map so that it can be recreated in Miro, Mural, FigJam, Collaboard or another collaborative whiteboard.Works with ChatGPT, Claude, Gemini and Copilot.
Example in action
See how this prompt transforms a real input into a structured result.
Product or feature: Online doctor appointment booking. Target users: Patients looking for an available medical specialist. Primary user goal: Find and book a suitable medical appointment without calling the clinic. Known requirements: - Search by specialization - View available appointment dates - Select an appointment - Provide patient details - Receive confirmation - Cancel an appointment Participants: Product Owner, UX Designer, Business Analyst, Developer, QA Engineer and Customer Support representative. Duration: Two hours.
Workshop Objective: Create an end-to-end user story map for online appointment booking and agree the minimum viable release. --- User Activity 1: Find a Specialist User Tasks: - Select specialization - Enter location - Review available specialists - Apply date filters User Stories: - As a patient, I want to search by specialization so that I can find an appropriate doctor. - As a patient, I want to filter by date so that I can find a convenient appointment. --- User Activity 2: Select an Appointment User Tasks: - View available dates - View appointment details - Select a time slot Dependencies: The scheduling system must provide real-time availability. Risk: The selected slot may become unavailable before confirmation. --- MVP Release Slice: 1. Search by specialization 2. View specialists 3. View available slots 4. Select a slot 5. Enter patient details 6. Confirm booking 7. Receive confirmation email Next Release: - Saved patient profiles - Appointment rescheduling - Doctor ratings - Waiting-list registration Open Question: How long should a selected appointment slot remain reserved during booking?