Facilitating Agile Meetings That Work

I’ve been thinking a lot about the 90 minute virtual meeting paradox. We spend the first 30 minutes on welcoming everyone and introductions, the next 15 on framing, and then a few people share thoughts. Then, just when the conversation gets meaningful, the host abruptly announces "We're out of time!” and throws a few rushed closing thoughts and announcements together. Sound familiar? We crave deep, meaningful, trust-based exchanges in virtual meeting environments that feel both tiring and rushed. It seems like as soon as momentum builds and insights emerge, it’s time to wrap up. Share-outs become a regurgitation of top-level ideas—usually focused on the most soundbite-ready insights and omitting those seeds of ideas that didn’t have time to be explored further. And sometimes, we even cite these meetings as examples of participation in a process, even when that participation is only surface level to check the participation box.  After facilitating and attending hundreds (thousands?) of virtual meetings, I've found four practices that create space for more engagement and depth: 1. Send a thoughtful and focused pre-work prompt at least a few days ahead of time that invites reflection before gathering. When participants arrive having already engaged with the core question(s), it’s much easier to jump right into conversation. Consider who designs these prompts and whose perspectives they center. 2. Replace round-robin introductions with a focused check-in question that directly connects to the meeting's purpose. "What's one tension you're navigating in this work?" for example yields more insight than sharing organizational affiliations. Be mindful of who speaks first and how difference cultural communication styles may influence participation.  3. Structure the agenda with intentionally expanding time blocks—start tight (and facilitate accordingly), and then create more spaciousness as the meeting progresses. This honors the natural rhythm of how trust and dialogue develop, and allows for varying approaches to processing and sharing.  4. Prioritize accessibility and inclusion in every aspect of the meeting. Anticipating and designing for participants needs means you’re thinking about language justice, technology and materials accessibility, neurodivergence, power dynamics, and content framing. Asking “What do you need to fully participate in this meeting?” ahead of time invites participants to share their needs. These meeting suggestions aren’t just about efficiency—they’re about creating spaces where authentic relationships and useful conversations can actually develop. Especially at times when people are exhausted and working hard to manage their own energy, a well-designed meeting can be a welcome space to engage. I’m curious to hear from others: What's your most effective strategy for holding substantive meetings in time-constrained virtual spaces? What meeting structures have you seen that actually work?

I've carefully observed hundreds of team meetings across industries, and one pattern emerges with striking consistency: the level of frustration team members feel leaving a meeting directly correlates with how clearly everyone understood why they were there in the first place. In one organization I worked with, weekly team meetings had become so unfocused that people openly admitted to bringing other work to complete while "listening." The meeting culture had deteriorated to the point where even the leader dreaded convening the team. Sound familiar? What transformed this team wasn't elaborate techniques or technology—it was implementing what I now call the "Purpose-Process-Outcome" framework. Before every meeting, this framework asks three deceptively simple questions: PURPOSE: Why are we meeting? What specific need requires us to gather synchronously rather than handling this asynchronously? PROCESS: How will we use our time together? What structures and activities will best serve our purpose? OUTCOME: What tangible result will we have produced by the end of this meeting? How will we know our time was well spent? When we implemented this framework with that struggling team, the transformation was remarkable: Meetings shortened from 90 minutes to 45. Participation increased dramatically. Most importantly, team members reported feeling that their time was respected. What made the difference? Each person walked in knowing exactly why they were there and what their role was in creating a specific outcome. One team member told me: "I used to leave meetings feeling like we'd just wasted an hour talking in circles. Now I leave with clear action items and decisions we've made together." Another unexpected benefit emerged: the team began to question whether meetings were always the right solution. They discovered that about 30% of their previous meeting time could be handled more efficiently through other channels. The framework forces clarity that many leaders avoid. When you can't clearly articulate why you're gathering people, what you'll do together, and what you'll produce, it's a signal to pause and reconsider. I've found that when team leaders commit to this framework, they stop being meeting facilitators and become architects of meaningful collaboration. The shift is subtle but profound—from "running" meetings to designing experiences that accomplish specific goals. What's your best tip for making meetings more productive? Share your wisdom in the comments. P.S. If you’re interested in developing as a leader, try out one of my Skill Sessions for free: https://lnkd.in/d38mm4KQ

“Let’s have a meeting to talk about meetings,” said no one ever. But maybe we should. A Microsoft global survey found the #1 workplace distraction is inefficient meetings. The #2? Too many of them. Sound familiar? Last week, I led a meeting effectiveness workshop for a team of 15 at the request of their practice leader—who happens to be my husband. His team’s meeting struggles? Rambling discussions, uneven engagement, unclear outcomes, and lack of follow-through. He thought a meeting AI tool might fix it. Nope. AI can help document meetings, but it can’t make people prepare better, participate more, or drive decisions. The fix? It’s not “Have an agenda”. It’s setting the right meeting norms. My husband was hesitant to put me in the late morning slot–worried the team would tune out before lunch. I told him, “Put me in, coach. I’ll show you engagement.” And I did. For 90 minutes, we tackled meeting norms head-on through interactive discussions and small group exercises. Here are 5 norms they worked through to transform their meetings: 1️⃣ 𝗦𝗲𝘁 𝗰𝗹𝗲𝗮𝗿 𝗰𝗿𝗶𝘁𝗲𝗿𝗶𝗮 𝗳𝗼𝗿 𝗵𝗮𝘃𝗶𝗻𝗴 𝗮 𝗺𝗲𝗲𝘁𝗶𝗻𝗴. An agenda is a list of topics. A purpose answers: What critical decision needs to be made? What problem are we solving? Why does this require a discussion? If you can’t summarize the purpose in one sentence with an action verb, you don’t need a meeting. 2️⃣ 𝗕𝗲 𝗶𝗻𝘁𝗲𝗻𝘁𝗶𝗼𝗻𝗮𝗹 𝗮𝗯𝗼𝘂𝘁 𝘄𝗵𝗼’𝘀 𝗶𝗻 𝘁𝗵𝗲 𝗿𝗼𝗼𝗺. Some discussions only need two people; others require a small group or the full team. Match the participants and group size to the topic and purpose.  3️⃣ 𝗗𝗲𝗳𝗶𝗻𝗲 𝘄𝗵𝗮𝘁 𝗮𝗻𝗱 𝗵𝗼𝘄 𝘁𝗼 𝗽𝗿𝗲𝗽𝗮𝗿𝗲. Before the meeting, define the problem or goal. Identify potential solutions. Recommend one. Outline your criteria for selecting the solution(s). Back it up with data or other relevant information. Preparation = productivity. 4️⃣ 𝗔𝘀𝘀𝗶𝗴𝗻 𝗮 𝗳𝗮𝗰𝗶𝗹𝗶𝘁𝗮𝘁𝗼𝗿 𝘁𝗼 𝗺𝗮𝗻𝗮𝗴𝗲 𝘁𝗵𝗲 𝗱𝗶𝘀𝗰𝘂𝘀𝘀𝗶𝗼𝗻. A good facilitator keeps conversations on track, reins in tangents, and ensures all voices –not just the loudest–are heard. Facilitation matters more than the agenda. 5️⃣ 𝗘𝗻𝗱 𝘄𝗶𝘁𝗵 𝗰𝗹𝗲𝗮𝗿 𝗼𝘂𝘁𝗰𝗼𝗺𝗲𝘀. Summarize decisions. Assign action items. Set deadlines. Follow-up to ensure accountability and progress. A meeting without follow-through is just wasted time. The outcome of the workshop? 100% engagement. (One person even admitted she normally tunes out in these things but stayed engaged the entire time!) More importantly, the team aligned on meeting norms and left with actionable steps to improve. Want better meetings? Set better norms. Focus on facilitation. What’s one meeting tip that’s worked well for your team?