Collaborative Workshop Planning

One thing I’ve learned as a Business Analyst: a successful workshop doesn’t start when people walk into the room — it starts with your preparation. Here’s a practical checklist you can follow before your next elicitation session: ✅ 𝐔𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝 𝐭𝐡𝐞 𝐏𝐮𝐫𝐩𝐨𝐬𝐞 Why is this workshop happening? Example: If it’s about "Order History feature," clarify if the goal is to define functional flow or just UI expectations. ✅ 𝐊𝐧𝐨𝐰 𝐘𝐨𝐮𝐫 𝐒𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫𝐬 Who’s attending and what’s their role? Example: A compliance officer will focus on regulations, while a customer service rep will care about usability. ✅ 𝐑𝐞𝐯𝐢𝐞𝐰 𝐄𝐱𝐢𝐬𝐭𝐢𝐧𝐠 𝐃𝐨𝐜𝐮𝐦𝐞𝐧𝐭𝐬 Look at BRDs, past meeting notes, process flows. Example: If a similar "Payment Flow" was discussed last month, bring that context. ✅ 𝐏𝐫𝐞𝐩𝐚𝐫𝐞 𝐆𝐮𝐢𝐝𝐢𝐧𝐠 𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬Frame open-ended and probing questions. Example: Instead of asking, “Do you want notifications?” ask “When should users be notified and how (email, SMS, in-app)?” ✅ 𝐃𝐞𝐟𝐢𝐧𝐞 𝐒𝐜𝐨𝐩𝐞 𝐁𝐨𝐮𝐧𝐝𝐚𝐫𝐢𝐞𝐬 Avoid scope creep before it begins. Example: If discussing "User Profile Update," clarify that payment details are not part of this session. ✅ 𝐒𝐞𝐭 𝐭𝐡𝐞 𝐀𝐠𝐞𝐧𝐝𝐚 & 𝐒𝐡𝐚𝐫𝐞 𝐢𝐧 𝐀𝐝𝐯𝐚𝐧𝐜𝐞 Helps participants prepare and respect their time. Example: A simple email: “Session covers Order Tracking flow → Notifications → Reporting Needs.” ✅ 𝐏𝐫𝐞𝐩𝐚𝐫𝐞 𝐕𝐢𝐬𝐮𝐚𝐥 𝐀𝐢𝐝𝐬 Mockups, process flows, or system diagrams often spark better conversations than words. Example: Show a rough wireframe of “Order History Page” instead of describing it verbally. ✅ 𝐏𝐥𝐚𝐧 𝐋𝐨𝐠𝐢𝐬𝐭𝐢𝐜𝐬 Confirm meeting platform, recording, time zones, whiteboard tools, etc. Example: Test Miro board or Teams whiteboard before the call. Pro tip: A well-prepared BA leads workshops where stakeholders say, “That was productive!” instead of “What just happened?” BA Helpline

Before designing a workshop, I always ask myself: Where does this group need to go 'from' and 'to'? Understanding their starting point helps me define how I want them to leave the session and what success looks like. Take the Work on Climate community workshop I facilitated a few years ago as an example. This vibrant community—tens of thousands connected via Slack—shared similar goals: transitioning their careers into climate work. Yet many hadn't, yet, developed personal connections in the community. Once I pinpointed their journey's start and destination, I broke down the session using the Kaos Pilots 5E model (guide in the comments 👇🏼). Designing a session that instilled pride in being part of a global movement while fostering personal connections in breakout rooms. With over 200 participants, the energy was palpable. And, I knew the workshop was a success when one participant, inspired by our discussion on how they could continue to support one another, took the initiative to form smaller accountability groups to keep the momentum going. How do you start your workshop design process? Picture: a piece of paper with hand written 5E process outlined with the description FROM Group of passionate individuals committed to finding climate work but not connected to each other. TO a community of individuals who are connected to a handful of others who are on similar paths & feel they belong to a wider movement.

How to design a workshop using the "One Outcome Per Hour" rule. Most spend days designing workshops. Tweaking slides. Rearranging activities. Agonising over timing. Then the workshop happens and half of it doesn't land. You don't need more time designing. You need a better framework. Here's the "One Outcome Per Hour" rule. It takes 45 minutes to design any workshop. From a 1-hour team session to a full-day offsite. Step 1: Define your outcomes (10 minutes) Ask yourself one question: "What will participants have created or decided by the end?" Not learned. Not discussed. Created or decided. → A 2-hour workshop gets 2 outcomes. Maximum. → A full-day gets 5-6. → A 1-hour session gets 1. Write each outcome as a sentence that starts with: "By the end of this section, participants will have..." → Not: "Understand team communication." → Instead: "By the end of this section, participants will have written a team communication agreement they'll follow for the next 30 days." If you can't finish that sentence with something tangible, you don't have an outcome. You have a theme. Step 2: Build backwards from each outcome (20 minutes) For each outcome, answer 3 questions: → What's the minimum they need to know to do the work? (This is your teaching. Keep it under 3 minutes per concept.) → What activity produces the outcome? (This is the bulk of the time. Templates, frameworks, group exercises.) → How will they share what they created? (Presentations, wall walks, pair shares.) That gives you 3 blocks per hour: 1. Brief input (5 minutes) 2. Working session (40 minutes) 3. Share back (10 minutes) That's your session plan for every hour. Step 3: Write your opening and closing (15 minutes) Opening (first 5 minutes of the workshop): → State the outcomes. 1 sentence each. → Set the rules. "You'll do 95% of the talking. I run the process." → No icebreakers. Time is valuable. Closing (last 10 minutes of the workshop): → Each participant states one commitment. → Assign accountability partners. → Set a check-in date within 14 days. No "any final thoughts?" No vague wrap-ups. The whole design on one page looks like this: Outcome 1 → Input (5 min) → Work (40 min) → Share (10 min) Outcome 2 → Input (5 min) → Work (40 min) → Share (10 min) Opening (5 min) at the start. Closing (10 min) at the end. That's a 2-hour workshop. Designed in 45 minutes. The reason this works: most workshop design time is wasted on stuff you don't need. When you force 1 outcome per hour, you cut unnecessary slides, filler activities, "nice to have" discussions. You're left with a workshop where every minute has a purpose and every participant walks out with something they made. Not just something they heard. ___ Save this for later (three dots, top right). Share with friends → ♻️ Repost. Get consultant-grade workshops every Sat → https://lnkd.in/eSfeUapJ

Reflections: How not to turn stakeholder gathering & consultations into a workshop? A few months ago, the team at Project Potential conceptualized a series of stakeholder consultations in key cities inviting funders, HNIs, partner NGOs and strategic collaborators. We called it 'Friends of Project Potential' and found generous hosts for the series. We were first hosted by Quest Learning Observatory (QLO) in Bangalore and then followed by Dasra in Mumbai. (Looking at you New Delhi!) By the end of the recent gathering in Mumbai, I started writing down my reflections on how do we make sure stakeholder consultations don't become just another workshop. Here is what I am beginning to experiment with and learn from: 1) Clearly define 'why are we doing what we are doing?' - the answers could range from - "to invite stakeholder feedback, to create an ideation space on a problem statement or even a celebration space with those who support us". Then decide on the tone, physical setting, agenda, messaging and contributors/collaborators for that day and finally, define one success metric - how will we know we achieved what we set out for? 2) Define what is the role of the people in the room - who are perhaps putting aside a precious Saturday morning or a rare Friday evening - They are not coming for an upskilling process, so what are they being invited for. Once you have defined this - consult your internal organizing team and identify who is the right fit. Communicate this intent clearly to stakeholders being invited. Including your own team 3) As the host organization, play the role of the "conductor of an orchestra" - everyone is focused on the music (the content/ experience). You are present but not the dominant voice - design not just for peer interaction but co creation, 'sense making' and acquire new contacts/ connections for possible collaborations in the future. 4) Create something together - Presentations are great for sharing information, but invest time in designing an immersive experience - invite the gathering to create something together - a framework, a timeline, a journey, a design or even a story 5) Make space for your stakeholders to lead the space - a chance to tell their story, share their experiences and insights as an organization or even co-lead a part of that gathering. 6)Create an element of surprise - In facilitation it's called creating disequilibrium. For example, lead with a simulation or even a seemingly fictional case study - and then position the real-life characters and stakeholders into the room. There are many ways of doing this, ping me if you want to know how. 7) Finally, make time as a team to reflect on what went well and what could be better.....and repeat. It gets better each time. I promise! Is there something else you would do? With Project Potential Team - Zubin Sharma Kriti Gupta Abodh Kumar Tonmoy Talukdar and Alex Arockiasamy

Workshops are a great way to process data, engage teams, and align decisions without writing lengthy reports no one reads. But traditional workshops can be overwhelming, especially for neurodivergent colleagues. That’s why I use the diverge-and-converge technique to make workshops more structured and inclusive: 1️⃣ Diverge – Everyone works individually first (writing down ideas, analyzing data) before group discussions begin. This allows time to process information without pressure. 2️⃣ Converge – The group then discusses and refines ideas, ensuring better structure and preventing groupthink. This simple structure helps everyone contribute meaningfully while reducing cognitive overload. A few more ways to make workshops better: ➜ Share an agenda upfront so people can prepare. ➜ Offer multiple ways to contribute (writing, speaking, small groups). ➜ Build in silent processing time instead of expecting instant responses. These aren’t just neurodivergent-friendly—they make workshops more effective for everyone. How do you structure workshops to be more inclusive? UXR Study

Please note: This is just a sample format , school can modify based on their needs and wants. The Ultimate Checklist for Effective PYP Collaborative Planning Meetings Collaborative planning is at the heart of the IB Primary Years Programme (PYP), ensuring transdisciplinary learning remains dynamic and student-centered. To keep meetings focused and productive, here’s a simple yet powerful checklist your team can use every time. Why This Checklist Works Saves Time – No more wandering discussions; stay on track with clear objectives. Ensures Consistency – All key PYP elements (inquiry, ATL skills, differentiation) are covered. Boosts Accountability – Tasks are assigned, and progress is tracked. PYP Collaborative Planning Meeting Checklist (Print in A4/A5/Legal size or save as PDF for digital use) 📌 Student Learning & Inquiry ☐ Emerging student questions/discoveries ☐ Misconceptions or gaps needing addressing ☐ Evidence of student agency (choice/voice/ownership) 📌 Unit Progress ☐ Connections to Central Idea ☐ Lines of Inquiry – Need refinement? ☐ ATL Skills focus (✓ Research ✓ Thinking ✓ Social ✓ Self-Management ✓ Communication) 📌 Teaching Adjustments ☐ Differentiation (EAL/SEN/Extensions) ☐ New resources/provocations needed ☐ Pivot required? (Based on student engagement) 📌 Transdisciplinary Links ☐ Subject integrations (Math/Literacy/Arts/Science) ☐ Specialist teacher updates (PE/Music/Languages/etc.) 📌 Assessment & Documentation ☐ Formative evidence collected (photos/work samples) ☐ Summative assessment plan status ☐ Student portfolios/reflections updated 📌 Action Items ☐ Tasks assigned: _______________ (Name) ☐ Deadline: _______________ (Date) ☐ Upcoming events: _______________ 📌 Reflection (5 mins) ⭐ Win of the Week: ___________________________ 💡 Challenge to Solve: _________________________

Early in my strategy career, I led a strategy session that was… simply put, a mess. The agenda was unclear, so the conversation wandered and lost focus. By the end, we had plenty of talk but zero direction.🤦 It was a hard lesson. If you don’t give collaboration some structure, you won’t get meaningful results. Whether it’s a strategy workshop, planning session, or cross-functional meeting, preparation is key. Here’s what I’ve found works: 🎯 Before bringing teams together, define the purpose of the session. 🎯 Don’t just invite representatives from every department—invite the right mix of expertise and experience. Ensure diverse perspectives. 🎯 Create a structured agenda to keep the session focused and productive. Lay out the main points and allow time for each. 🎯 As the facilitator, guide the conversation without dominating. Steer the conversation if it starts wandering. 🎯 By the end, summarize the decisions, assign timelines, and clarify who’s responsible for what. 🎯 Afterward, follow up quickly to keep the momentum going. Provide regular updates, and track progress to ensure accountability. Great collaboration doesn’t just happen—design it intentionally. Are your collaboration efforts truly effective, or do they feel like endless meetings? **************************************************************************** 𝐼 𝑠ℎ𝑎𝑟𝑒 𝑖𝑛𝑠𝑖𝑔ℎ𝑡𝑠 𝑜𝑛 𝑆𝑡𝑟𝑎𝑡𝑒𝑔𝑦, 𝐸𝑥𝑒𝑐𝑢𝑡𝑖𝑜𝑛, 𝑎𝑛𝑑 𝑙𝑒𝑣𝑒𝑟𝑎𝑔𝑖𝑛𝑔 𝐴𝐼 𝑎𝑛𝑑 𝐷𝑖𝑔𝑖𝑡𝑎𝑙 𝑡𝑟𝑎𝑛𝑠𝑓𝑜𝑟𝑚𝑎𝑡𝑖𝑜𝑛 𝑓𝑜𝑟 𝑏𝑢𝑠𝑖𝑛𝑒𝑠𝑠 𝑔𝑟𝑜𝑤𝑡ℎ. 𝐿𝑒𝑡’𝑠 𝑐𝑜𝑛𝑛𝑒𝑐𝑡 𝑎𝑛𝑑 𝑔𝑟𝑜𝑤 𝑡𝑜𝑔𝑒𝑡ℎ𝑒𝑟.➡️

Want more productive workshops? Try stopping them sooner. Workshops often lock people in a room for two or three hours and expect them to do their best thinking on demand. Do we really have to hold people hostage to be productive? Lately, I’ve been using a technique I call "Echo Sessions." Instead of forcing deep work to happen in real time, we kickstart an activity, get clarity, but then stop just as people are getting into it. That pause is intentional. It’s based on the same principle as the Pomodoro technique—when you leave something unfinished while still feeling engaged, you'll find it easy to return to it later and give it space to percolate. Instead of dragging out a long workshop, I schedule an Echo Session later—often in the same day—where everyone brings their independent or small group work back for discussion, iteration, and action. Why does this work? ✅ Encourages Deep Work – People get time to think, research, or create in their own way, rather than being forced into artificial collaboration. ✅ Optimizes Meeting Time – Workshops should be for shared understanding, decision-making, and iteration—not for quiet focus time. ✅ Respects Different Work Styles – Some need time to walk and think. Others need to sketch. Some want to research or tap into AI. Echo Sessions give people time and space to work in the way that’s best for them. ✅ Creates Natural Momentum – Stopping at a high-energy moment makes people want to continue later, giving them space to create, rather than leaving them drained from a marathon session. ✅ Reduces Calendar Lockdowns – Instead of monopolizing hours at a time, work is distributed more effectively and meetings are only used when necessary. Most importantly, this approach treats participants like adults. It gives them flexibility and agency while ensuring that meetings serve a clear, valuable purpose. We don’t need long workshops. We need better workshops. Curious—how do you approach workshop fatigue? Would this work in your team?

7 Workshop Tactics That Turn Strategy Into Action: The average company workshop costs $10,000+ in executive time alone. Yet most produce nothing but PowerPoints that collect dust. You've probably sat through a few of these yourself, right? Here's what research tells us about running workshops that actually produce results: 1. Start with Why ↳ Begin with clear, measurable objectives ↳ MIT research: Teams with a clear purpose are 35% more likely to succeed 2. Pre-Work Matters ↳ Distribute reading materials 72 hours before the meeting ↳ Journal of Applied Psychology: Pre-reading improves decision quality by 20% 3. Diverse Voices ↳ Include cross-functional perspectives ↳ HBR study: Teams with cognitive diversity solve problems 3.5x faster 4. Problem Framing ↳ Spend the time to narrow in on the right problem ↳ Stanford research: 20% time on problem framing creates 25% better solutions 5. Cognitive Breaks ↳ Schedule 10-minute breaks every 50 minutes ↳ Cognition journal: Short breaks reduce cognitive fatigue by 40% 6. Visualization Tools ↳ MIT research: Brain processes visuals 60,000x faster than text ↳ Wharton study: Visual aids are 43% more persuasive than text alone 7. Action Commitment ↳ HBR research: 70% of strategic failures come from poor execution ↳ Project Management Institute: Clear task assignments are 37% more successful The difference between a $10,000 conversation and a $10,000,000 breakthrough isn't smarter people. It's smarter workshop design. Which principle will you implement in your next workshop? ♻️ Share this with your team before your next workshop. 🔔 Follow me, Ali Mamujee, for more actionable content.