Workshop Session Example: Requirements Gathering for Mobile Banking App

Date: [Insert Date]
Duration: 3 hours
Facilitator: [Your Name]
Participants:

1. Product Manager
2. Customer Service Representative
3. IT Architect
4. UX/UI Designer
5. A few selected end-users (customers)
   Location: [Specify Location or “Virtual Meeting”]

---

Objectives

1. Identify and prioritize key features for the Mobile Banking App.
2. Understand the needs and pain points of both internal stakeholders and end-users.
3. Collaborate to design a high-level user flow for the app.
4. Capture additional ideas and concerns from participants.

---

Agenda

1. Introduction (15 minutes)
   • Welcome participants and introduce the facilitator and team members.
   • Briefly explain the purpose of the workshop and the expected outcomes.
   • Outline the agenda and set ground rules (e.g., respect each other’s input, time limits for discussions).
2. Warm-Up Exercise (10 minutes)
   • Icebreaker activity: Ask each participant to share one feature they love about their current banking app or a feature they wish it had.
   • Purpose: To get participants thinking about banking app features and set a positive tone for the workshop.
3. Current Challenges Discussion (30 minutes)
   • Activity: Open discussion with the following guiding questions:
     • “What are the biggest pain points with the current banking experience?”
     • “What features do users often complain about or request?”
   • Output: Facilitator writes down key challenges on a whiteboard or virtual board.
4. Feature Brainstorming (45 minutes)
   • Activity: Divide participants into smaller groups and ask each group to brainstorm features they’d like in the new app.
   • Use sticky notes or a digital tool (if virtual) to write down each idea.
   • Output: Each group presents their ideas, and the facilitator organizes them into categories, such as “Must-Have,” “Nice-to-Have,” and “Future Consideration.”
5. User Flow Design (45 minutes)
   • Activity: Collaboratively design a high-level user flow for key tasks, such as:
     • Checking account balance
     • Transferring money
     • Paying bills
     • Viewing transaction history
   • Use a whiteboard or a digital wireframe tool to draw the flow, making sure everyone contributes.
   • Output: A draft of the main user flow that reflects the group’s ideas.
6. Prioritization Exercise (30 minutes)
   • Activity: Use a simple voting system (e.g., dot voting) to prioritize features. Each participant gets a set number of votes to place on the features they feel are most important.
   • Output: A prioritized list of features for the app.
7. Open Forum for Questions and Concerns (20 minutes)
   • Activity: Allow participants to raise any questions, concerns, or additional ideas that haven’t been discussed.
   • Output: Document any remaining feedback or questions for follow-up.
8. Wrap-Up and Next Steps (15 minutes)
   • Summarize key findings and decisions from the workshop.
   • Outline the next steps, including how the gathered requirements will be documented and used.
   • Thank everyone for their participation and input.

---

Materials Needed

• Whiteboard and markers (or virtual collaboration tool like Miro or MURAL)
• Sticky notes and pens (or virtual sticky notes)
• Voting dots (or a digital voting system)
• Projector for sharing wireframes (if in-person)

---

Example Outputs

1. Key Pain Points: Difficulty navigating current app, poor integration with third-party services, lack of bill payment reminders.
2. Must-Have Features: Biometric login, easy money transfers, customizable alerts, bill payment options, and an intuitive dashboard.
3. User Flow: A draft flowchart showing how a user would log in and perform essential tasks.
4. Prioritized Features List: Ranked list of features to focus on in the initial app release.

---

Follow-Up

1. Prepare a detailed summary of the workshop and distribute it to all participants.
2. Schedule a follow-up meeting to refine the requirements based on workshop feedback.
3. Begin prototyping and user testing based on the prioritized features and user flow.