UX Workshop Plan
Workshop Agenda & Timeline
Day 1: Ideation & Prioritization
| TimeActivityDescription | ||
| 09:00 - 09:30 | Kickoff & Goal Setting | Define workshop goals and set expectations. |
| 09:30 - 10:30 | Lightning Demos | Review top fintech apps (Revolut, YNAB, PocketGuard) to inspire ideas. |
| 10:30 - 12:00 | Feature Idea Dump (Crazy 8s) | Everyone sketches 8 quick ideas. No critique. |
| 12:00 - 13:00 | Lunch | Informal networking & rest. |
| 13:00 - 14:00 | Present & Cluster Ideas | Group ideas by themes: budgeting, insights, gamification, etc. |
| 14:00 - 15:00 | Dot Voting | Vote on features based on desirability, innovation, and feasibility. |
| 15:00 - 16:30 | Impact–Effort Matrix | Map top ideas to decide what to build first. |
| 16:30 - 17:00 | Summary & Homework | Finalize top 3 ideas and assign overnight research tasks. |
Day 2: Strategy & Execution Planning
| TimeActivityDescription | ||
| 09:00 - 10:00 | Recap & Research Sharing | Participants present findings to validate chosen features. |
| 10:00 - 11:30 | User Flow Mapping | Create initial flows for top 3 features using whiteboard or Figma. |
| 11:30 - 12:30 | Wireframing Sprint | Designers begin sketching basic wireframes in pairs. |
| 12:30 - 13:30 | Lunch | Recharge. Informal discussion on challenges. |
| 13:30 - 15:00 | Define MVP Scope | Product Manager and Design Lead define MVP for each feature. |
| 15:00 - 16:00 | Roadmap & Timeline | Map out a 4-week implementation strategy (design + dev). |
| 16:00 - 17:00 | Final Presentation & Wrap-Up | Present outcomes and next steps to internal stakeholders. |
Tools used
From brief
Topics
Share
Reviews
1 review
Hi Fatima! 👋
Thanks for sharing your UX Workshop Plan for Spendwise. It’s very well-structured, and I can see you've thought through the practical aspects of facilitating a productive two-day session.
The agenda flows logically and balances divergent and convergent thinking across both days. I especially like the mix of activities like Crazy 8s and clustering ideas.
The objectives are clearly stated, and the inclusion of competitive analysis (lightning demos) is a smart way to ground the team in what's already out there before diverging. Good move to include the developer for feasibility checks!! It shows a real-world awareness of cross-functional collaboration. ☺️
The end goals are clearly defined: feature selection, wireframes, and a roadmap. That makes it easier to measure success and maintain alignment post-workshop.
This is a strong, facilitation-ready plan, practical, team-centred, and clearly aligned with product design goals.
Great work! 👏🏼👏🏼👏🏼
You might also like
Fundraising Website
Mobile onboarding flow
NEWFASHON™ - Landing page
HR Management App
Docto
MamaFlow
Design Leadership Courses
UX Design Foundations
Introduction to Figma
Building Agile Teams
