Business Workshop Scheduling

We tried something new with our retreat format this year, and the data confirms it worked! Here's what we learned in France... Quick recap: Instead of sending 10 teams to different cities around the world for "mini-retreats", we brought everyone to one location outside of Paris, but attempted to maintain the focused team time that made mini-retreats so valuable, while also enabling cross-team collaboration. In other words: 95 people. 60+ workshops. 10 teams. 5 days. 1 location = "Team Connect" The outcome: According to our post-retreat survey, after 10+ years of trying various retreat formats, Team Connect just became our highest-rated retreat ever - both for overall experience AND productivity 🚀 Here's what worked well, according to the survey feedback: - Team-first, company-second approach - As opposed to our annual all-hands retreat (Doist Connect), at Team Connect, we worked hard to protect individual team time, which sparked some incredibly innovative conversations at the level where most of the actual work takes place. - 15 flexible meeting spaces - Teams could spread out, regroup, or pull in other teams as needed. The adaptability was key and meant teams got deep work done while cross-functional breakthroughs happened naturally. Product grabbing Design for impromptu sessions, Engineering teams mapping AI wins together, Finance, People, and Ops implementing company-wide workflows in hours instead of weeks, etc... - Structured flexibility - Clear and balanced agenda so everyone knew when they were working with their teams and when they could connect across the org. - Exceptional venue - Le Grand Mello's staff and attention to detail was world-class, and the "live at home" concept with self-serve food, drinks, games, and activities let people recharge however they needed. Big thanks to our friends Jihanne Cory Nathalia at Chateauform and RetreatsAndVenues.com for the hospitality. - Team-specific activities - Macaron workshops, team-vs-team scavenger hunts, sports tournaments, and cultural excursions. The balance between work and time for connection outside the conference room matters. There's a lot more I could share, but in short, the survey data confirms what we felt during the week, so I'm excited to iterate on this concept for future retreats! Here are a few photos from the week 📸 and I'd be happy to answer any questions you have below 👇

PI Planning Success Depends on Prep Work The success of PI Planning is decided weeks in advance. By day one, you're either facilitating an effective coordination event or panicking during a 2-day recovery operation. Don't romanticize the "energy" of PI Planning. There is no magic. There’s just preparation, role clarity, and discipline. If you under-prepare, the event will devolve into guesswork and grumbling. Effective Prep Work Product Management: PMs prepare the strategic backbone. A prioritized feature set, clear value statements, feasible options, and the “why” behind each investment alternative. None of this should be discovered or discussed for the first time during the event itself. It’s socialized weeks in advance. PMs ready their vision, context, metrics, and what success looks like for the PI. Business Owners: BOs walk in aligned on priorities, value, constraints, and tradeoffs. Their prep is reviewing the "top ten" features early, deciding what matters most, and crafting a clear message. They’re not there to surprise anyone or to react. They’re there to shape the plan. System Architects: Architects prepare the technical runway, and provide constraints, guardrails, interface agreements, and sequencing guidance. They decide whatever open technical items remain undecided before planning. Architecture briefs aren’t filler. They’re boundaries that influence planning. Enablers, diagrams, and decisions should be easily accessible where teams will actually look. Product Owners: POs construct the team runway. Stories, acceptance criteria, refinement sessions, sizing discussions, and surfacing of local (cross-team) dependencies - all happen before the event. POs should also validate tool configuration. Boards should be organized. Features ranked. Story states accurate. A confused backlog will produce a confused plan. RTE: The RTE owns the system. The calendar, agenda, facilitation plan, risk structure, checklists, and an ART-level Planning Board. They confirm team boards reflect reality. They address logistics - room layout, breakout flow, AV, MS Teams links, and timeboxes. If the system isn’t ready, the event is doomed. Scrum Masters: SMs prepare the teams for flow. They assess capacity, PTO, holidays, risks, and impediments. They have candid feasibility conversations, and pre-check boards for accurate statuses, WIP states, and dependencies. They coordinate with other SMs so cross-team constraints are visualized early instead of blowing things up by lunch on day one. Developers: Devs, QA, designers, and analysts bring truth from the front lines. They refine stories, challenge assumptions, identify risks, expose constraints, and surface integration concerns early. They clean up their work items, update estimates, and validate dependencies. They should walk into PI Planning with a sense of what lies ahead. The PI Planning event itself doesn’t make the plan work. The prep does. PI Planning just makes the quality of that prep obvious.

I have had an amazing internal discussion today and am putting it here so you can make use of it in the week to follow. As a corporate trainer, deep work has evolved into my seasoned ally, a silent force shaping impact and deep learning in my workshops. As a corporate trainer and L&D practitioner, I often find myself navigating the intricate balance of delivering workshops that not only educate but inspire lasting transformation. Today, I invite you behind the scenes to witness how the principles of Deep Work by Cal Newport have become key for my workshop design. 1. Distraction-Free Learning Zones: Creating an environment conducive to deep work is paramount. Before each workshop, I meticulously set the stage—a distraction-free zone where minds can immerse deeply in the learning experience. From silent zones to minimizing digital interruptions, every detail is curated for optimum focus. 2. Time Blocking for Engaged Learning: Time blocks as a balance for flow are a key element of my workshop agenda. Each segment is a deliberately carved block, dedicated to a specific skill or concept. This ensures not only an engaged audience but also a collective deep dive into the subject matter. 3. Prioritizing High-Impact Content: The essence of deep work lies in prioritizing high-impact tasks. When designing workshops, Newport's perspective guides the selection of content—ensuring that every concept explored is not just informative but has a profound, enduring impact on the participants' professional journey. 4. Engaging Deep Work Exercises: Workshops aren't about imparting information; they're about creating experiences for learning and deep thinking on the subject. Participants engage in exercises, creating an immersive space where they can apply newly acquired skills, fostering a deeper understanding that transcends theoretical knowledge. A challenge that I am taking and extending to you too- This week, experience a focused, distraction-free learning environment where every moment is crafted for maximum impact. Try to churn out the learning from the various tasks/ projects you work on. Get deep, that's where innovation happens. Priya Arora #deepwork #thinking #metacognition #learninganddevelopment #softskills #corporateculture #culturematters #workshop #facilitators #facilitation #traininganddevelopment #training The Female Story

Last week, I saw this play out in a workshop. We gave one group 45 minutes for a task. Another group got 20. Same brief. Same capability. The 45-minute group discussed, debated, went in circles, and kept refining their approach. The 20-minute group got straight to it. Made quicker calls, adjusted on the go, and finished with more clarity. That’s Parkinson’s Law in action. Work expands to fill the time you give it. And most of us don’t realise how often this is slowing us down. It’s not always inefficiency. It’s loose boundaries. When time is generous, thinking becomes loose. When time is tight but realistic, focus sharpens. You prioritize better. You cut the excess. You move faster. A simple shift that works: Stop asking, “How long will this take?” Start asking, “If I were fully focused, how much time should this take?” Then work within that window. Try this with your next three tasks. Define a tighter time block. Remove distractions. Focus only on getting it done, not perfect. You’ll notice how quickly things start moving. Because productivity is not just about effort. It’s about the boundaries you create around your work. Nyra Leadership Consulting #consulting #communication #leadership

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?

One of the most critical contributions of a Business Analyst in any project is ensuring that the right features are delivered at the right time—balancing business value, technical feasibility, and user expectations. 👉 Enter the MoSCoW Prioritization Technique — a tried-and-true method I’ve used recently while working with Product Owners, Marketing, Customer Support, and Tech teams for a freelancing project. 🔍 𝐂𝐚𝐬𝐞: Enhancing the Checkout Experience of an eCommerce Platform The goal? Boost conversions, reduce cart abandonment, and improve user experience. Here’s how we applied MoSCoW to prioritize requirements during the workshop: ✅ 𝐌𝐔𝐒𝐓-𝐇𝐀𝐕𝐄 (𝐂𝐫𝐢𝐭𝐢𝐜𝐚𝐥 𝐟𝐨𝐫 𝐥𝐚𝐮𝐧𝐜𝐡): ➡️ Implement Guest Checkout to avoid forcing account creation. ➡️ Add Multiple Payment Options (Credit Card, UPI, PayPal) for inclusivity. ➡️ Ensure Order Summary with Real-time Price Updates. 📌 These were non-negotiable. Without them, the release would fail user expectations and business KPIs. ✅ 𝐒𝐇𝐎𝐔𝐋𝐃-𝐇𝐀𝐕𝐄 (𝐈𝐦𝐩𝐨𝐫𝐭𝐚𝐧𝐭, 𝐛𝐮𝐭 𝐧𝐨𝐭 𝐯𝐢𝐭𝐚𝐥 𝐚𝐭 𝐥𝐚𝐮𝐧𝐜𝐡): ➡️ Auto-apply Coupons during checkout. ➡️ Add Progress Bar to visually indicate checkout steps. ➡️ Provide Delivery Date Estimator based on pincode. 📌 These enhance user experience but can wait until Phase 2. ✅ 𝐂𝐎𝐔𝐋𝐃-𝐇𝐀𝐕𝐄 (𝐍𝐢𝐜𝐞-𝐭𝐨-𝐡𝐚𝐯𝐞, 𝐨𝐧𝐥𝐲 𝐢𝐟 𝐭𝐢𝐦𝐞/𝐫𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 𝐩𝐞𝐫𝐦𝐢𝐭): ➡️ Add Gift Wrapping Option. ➡️ Enable One-click Repeat Orders. ➡️ Allow Delivery Instructions for Courier. 📌 These create differentiation but don’t impact core functionality. ✅ 𝐖𝐎𝐍’𝐓-𝐇𝐀𝐕𝐄 (𝐎𝐮𝐭 𝐨𝐟 𝐬𝐜𝐨𝐩𝐞 𝐟𝐨𝐫 𝐭𝐡𝐢𝐬 𝐫𝐞𝐥𝐞𝐚𝐬𝐞): ➡️ Integration with Crypto Payment Gateway. ➡️ Launching a Voice-Activated Checkout experience. 📌 Innovative ideas, but postponed based on current ROI and technical constraints. 💬 𝐀𝐬 𝐚 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐀𝐧𝐚𝐥𝐲𝐬𝐭, 𝐦𝐲 𝐫𝐨𝐥𝐞 𝐰𝐚𝐬 𝐭𝐨: 👉 Facilitate the MoSCoW session with cross-functional stakeholders. 👉 Capture business value vs. effort trade-offs. 👉 Document the priorities in JIRA for sprint planning. 👉 Ensure Product Owner and Tech Leads were aligned on scope. 🎯 The result? Clear alignment, reduced scope creep, and focused development sprints. 💡 𝐓𝐢𝐩 𝐟𝐨𝐫 𝐅𝐞𝐥𝐥𝐨𝐰 𝐁𝐀𝐬: MoSCoW isn’t just a matrix—it’s a conversation starter to uncover what truly matters for both users and the business. BA Helpline

Your participants decided if your workshop was worth it before you said a word. The session hasn't started yet. But it's already half won or half lost. Most facilitators obsess over what happens in the room. The activities. The timing. The transitions. But your participants made 3 decisions before they sat down: → Is this going to be useful or a waste of my time? → Am I going to sit and listen all day? → Does this person actually understand my world? Those decisions were made before you opened your mouth. Here's where workshops are won or lost: 1. The invite email. Most workshop invites read like this: "You're invited to a team development session on Thursday. Please block 9am-12pm. Agenda attached." That tells participants nothing. So they assume the worst: another generic workshop. Laptop open. Emails on the side. Try this instead: "Thursday we're spending 3 hours solving one thing: the handoff process between sales and delivery. You'll leave with a written process your team built together. No slides. No lectures." Same session. Completely different expectations. Participants arrive curious instead of cynical. 2. The pre-work. Not a 20-page pack nobody reads. One question. Sent 3 days before. Takes 2 minutes. → "What's the one thing about our handoff process that frustrates you most?" It gets participants thinking before they arrive and gives you real data to design around. Someone who's already thought about the problem is 10 minutes ahead of starting cold. 3. The room setup. Tables in rows facing a screen says "you're here to listen." Chairs in a circle says "you're here to talk." Clusters of 4-5 around small tables says "you're here to build." Your layout is a promise. Participants read it the second they walk in. If you want collaboration, the room needs to look like collaboration before anyone sits down. 4. What the sponsor says. "I've asked a facilitator to come in and help us" → fine. "I'll be working alongside you because this matters to me personally" → different. When the most senior person is a participant, not an observer, everyone takes it more seriously. 5. Your reputation from last time. If your last session was forgettable, you're starting in a hole. "Here we go again." If last time was useful and things actually changed, you've earned trust before you speak. The best workshops don't start when you start talking. They start with the invite. The pre-work. The room. The sponsor. The memory of last time Get those right and the room is with you before minute one. ___ Save this for later (three dots, top right). Share with friends → ♻️ Repost. Get consultant-grade workshops every Sat → https://lnkd.in/eSfeUapJ

🎛️ How we keep design decisions in sync across dozens of product teams at inDrive In previous posts, I focused on the designer’s role inside a product team. But every designer is also part of the design department, and that comes with a second set of responsibilities. ✦ Why this is so important Today, a passenger might book a taxi within the city, tomorrow ride between cities, and the next day send a parcel by courier. On the other side, a driver might switch between ride-hailing and courier jobs in the same week. For them, it’s still one product. We want them to feel at home no matter which part they use — whether it’s booking a ride or sending a package — without relearning patterns or stumbling over inconsistent flows. ✦ Product team ↔ design department As part of a product team, a designer works on that team’s specific goals, solving user problems and delivering features. As part of the design department, the same designer contributes to strategic initiatives that run in parallel to product work. These might include: ▸ Evolving the design system and shared patterns ▸ Running cross-product redesigns ▸ Improving design processes ▸ Building a stronger shared design culture This dual role ensures we don’t just hit product team goals, but also improve the overall quality and consistency of inDrive’s design long-term. ✦ Our alignment engine: design syncs The backbone of our alignment is the design sync — regular open sessions for all product designers. In these sessions: ▸ Designers share ongoing work from early sketches to final flows ▸ Peers give feedback and spot overlaps ▸ We catch cross-team dependencies early, before they create friction This keeps patterns aligned across teams and ensures similar problems get similar solutions. ✦ The role of design leads Design leads act as connectors between product teams. They: ▸ Spot when multiple teams are solving the same problem ▸ Facilitate collaboration so we reuse strong solutions instead of reinventing ▸ Coordinate quarterly cross-team initiatives using the DACI framework: — Driver: responsible for moving the initiative forward — Approver: makes final calls on key decisions — Contributors: provide input and expertise — Informed: kept in the loop on progress and decisions ✦ The design function as the glue Our design function supports this alignment by: ▸ Maintaining the design system — common components, patterns, and guidelines ▸ Running and moderating design syncs and critique sessions ▸ Facilitating DACI-based initiatives and tracking their outcomes ▸ Helping onboard new designers into our shared language and standards This layer ensures designers embedded in product teams still act as part of one design culture. ☯︎ Consistency here doesn’t mean every screen looks identical. It means the experience feels coherent — whether you’re booking a ride or sending a parcel. How do you keep your teams in sync when they’re working on very different parts of the product?

One could think - why do several teams need to work in one room and to refine several PBIs at the same time? Wouldn’t it be more locally “efficient” for each team to conduct their own single-team PBR? It is all about adaptiveness and learning not resource utilization. Cool session with Bas Vodde and Jürgen De Smet 💥 about running a Multi Team Product Backlog Refinement. This are tips to try out. 1. One Product Owner, One Product Backlog, Feature Teams: Consider maintaining a unified backlog without pre-selected items. This can encourage teams to collaborate on what’s next, breaking down silos and fostering shared ownership. 2. Refinement for Learning, Not Just Planning: Think of refinement as more than just prep work—it’s an opportunity for teams to learn. Clarifying items up to 3 sprints in advance can help teams better understand and anticipate upcoming work, moving beyond routine execution. 3. Keep Sessions Short and Facilitated: Aim for focused, 20-30 minute sessions with clear facilitation. This helps keep discussions efficient and ensures everyone starts on an even playing field. Over-preparation isn’t necessary; engagement is what counts. 4. Use Diverge and Merge Cycles: Splitting larger groups (e.g., 50 people) into smaller sub-groups of 6-8 and then merging them back to share key insights can boost cross-team collaboration. Share only the main takeaways to keep the focus sharp. 5. Try Re-refinement: Don’t hesitate to revisit items, especially those of lower priority. Discussions around these items can be forgotten, so consider removing the “ready” flag if clarity isn’t there and revisiting them in the next session. 6. Limit Stakeholder Presence: You might find that keeping stakeholders out of PBR sessions can yield better team discussions. Without stakeholders present, teams often think more independently and find their own answers. 7. Document in Real-Time and Use Slack Channels: Enhance refinement by updating the backlog during the session. Take photos of whiteboard discussions and share key findings in dedicated Slack channels for easy reference and transparency. #LeSSWorks #BacklogRefinement #MultiTeamBacklogRefinement #MultiTeamPBR #BusinessAnalysis #RequirementAnalysis #ProductBacklog #Scrum

I've watched dozens of CX teams go through the same cycle. They run a journey mapping workshop, surface 30 or 40 pain points, and then spend the next month debating which ones to fix. The debate isn't really about the pain points. It's about who has the strongest opinion, who has the most organizational influence, and which issue happened to come up in the last executive meeting. That's not prioritization. That's politics dressed up as strategy. The fix is straightforward. Score each pain point on three dimensions: how severe it is per incident, how many customers encounter it, and what it costs the business. Have each person score independently before discussing. That one step, individual scoring before group conversation, is the single most effective way to prevent anchoring bias and dominant voices from skewing the outcome. A pain point that scores high on all three dimensions is almost certainly worth fixing. One that scores high on severity but low on frequency might warrant a recovery playbook rather than a full redesign. The framework doesn't make the decision for you, but it turns a vague discussion into a clear prioritization exercise.