The Meeting You Should Have Instead of a Workshop

Your calendar notification chimes: another four-hour workshop. You glance at the agenda—broad, vague, optimistically collaborative. If you're considering a workshop format, workshop contracting is key to avoiding this scenario. You know how this will end. Fifteen people will spend the morning generating ideas on virtual sticky notes, break for lunch feeling productive, and then watch as the actual decision gets made three weeks later by two people in a hallway conversation. What if the workshop itself is the problem?

The Workshop Industrial Complex: Why Workshops Often Miss the Mark

Workshops have taken center stage in meeting culture, touted as the ultimate collaboration tool. They seem democratic and inclusive, but here's the hard truth: workshops have morphed into costly theater that delays real decisions.

Think about it. The average workshop costs anywhere between $2,000 and $10,000 when you factor in participant time, preparation, and lost opportunities. A mid-sized tech company recently ran a 4-hour brainstorming session with 15 people to overhaul their onboarding process. After spending 60 collective hours and generating 87 sticky notes, the real decision was made two weeks later by the Head of HR and two team leads in a quick 30-minute meeting, rendering the workshop a mere showpiece.

This isn’t an anomaly. A 2023 study by Atlassian revealed that 72% of knowledge workers attend at least one unnecessary meeting per week, with multi-hour workshops topping the list of time-wasters. Ironically, research indicates that group brainstorming sessions yield fewer and lower-quality ideas compared to individuals working independently before sharing their insights.

Remote work has only exacerbated the problem. Virtual workshops are especially draining due to constant video presence and lack of natural breaks, yet organizations continue scheduling them by default. According to Harvard Business Review, executives now spend an average of 23 hours per week in meetings, up from less than 10 hours in the 1960s, with workshops being the fastest-growing category.

Many workshops happen because a manager wants to look inclusive, not because the format suits the goal. This is workshop planning as a safety net—if the decision falters, at least everyone was in the room. But this blurs the line between input and consensus, and collaboration and accountability.

When Workshops Actually Work: The Rare Valid Use Cases

Before we completely dismiss workshops, let's recognize when they truly add value. They're not inherently bad—they're just overused.

Workshops make sense when you need to align multiple stakeholders with differing interests on a shared vision, especially during major organizational changes like mergers or strategic shifts where buy-in is as crucial as the outcome. When Spotify merged two product teams with conflicting priorities, a facilitated 2-day workshop allowed them to map dependencies and negotiate trade-offs in real time, something that would have dragged on for months through emails. The secret: they had decision-making authority and implemented outcomes immediately.

Design sprints and problem-solving workshops are effective for tackling complex problems with no obvious owner, where diverse perspectives are essential, and where there's a commitment to act on the results rather than using the workshop to confirm pre-decided outcomes. A study in the Journal of Applied Psychology showed that structured problem-solving workshops outperformed traditional meetings significantly—but only when participants had pre-work assignments and a dedicated facilitator kept groupthink at bay.

Team-building workshops are worthwhile when relationship formation is the primary goal, not a side benefit, and when the team will collaborate intensively afterward. However, Google's Project Aristotle research found that psychological safety, not workshop frequency, was the top predictor of team effectiveness, suggesting relationship-building workshops only work when they genuinely address trust issues.

The takeaway? Workshops succeed when the process is the product, when building relationships or negotiating trade-offs among equals. They fail when you pretend to collaborate but are really just gathering input for a decision that someone else will make.

The Focused Meeting Alternative: When 60 Minutes Beats 4 Hours

Let’s face it: most workshops aim to reach a decision with input from relevant stakeholders. A focused meeting with a clear decision-maker, a pre-circulated context document, and a time-boxed agenda achieves this without the charade of equal contribution.

The Amazon-style narrative meeting format nails this approach. Participants silently read a 6-page memo for 20 minutes, then discuss for 40. This format consistently outperforms workshops for strategic decisions because it prioritizes thinking time and eliminates performative participation. You can’t just nod along if you’ve had to read and absorb the context.

Research by Bain & Company found that decisions made by a small group with a clear decision-maker were executed five times faster than those driven by consensus in workshops, with no drop in quality. A Microsoft study showed that meetings under 45 minutes had significantly higher perceived productivity ratings than those over 90 minutes, suggesting diminishing returns for longer sessions.

A product team at a fintech startup replaced their quarterly planning workshops (8 hours with 20 people) with a series of 45-minute focused meetings organized by product area, each with 4-6 people and a pre-read document. Planning time was slashed by 60%, and the resulting roadmap saw fewer changes mid-quarter because decisions had clear owners from the start.

Focused meetings work best for decisions with a clear owner who needs input, not consensus. Project launches, by contrast, often benefit from the structured alignment of a kickoff workshop. Focused meetings are ideal when five to seven people have genuine expertise, and when success is defined by a specific decision rather than vague alignment. If you can’t name the decision owner after the meeting, you need another format.

The Power of Async: When a Document Beats a Discussion

Not all collaboration needs to be synchronous. Asynchronous documents shine when you need broad input without real-time discussion, letting people contribute insights on their schedule rather than filling airtime.

Written feedback tends to be more thoughtful and less swayed by groupthink or whoever speaks first. Collaborative documents with commenting features blend the wide input workshops claim to offer with the depth of individual reflection, especially valuable for globally distributed teams where scheduling workshops is a timezone nightmare.

GitLab, a fully remote company, reports that 95% of their decisions are made asynchronously through documented proposals, leading to decision cycles that are markedly faster compared to their meeting-heavy rivals. A study by RescueTime found that knowledge workers averaged just 2.8 hours of focused work per day, highlighting that protecting async time is more valuable than adding synchronous workshops that fragment concentration.

When a nonprofit needed to revise their strategic plan, instead of running workshops across five regional offices, they created a shared document with specific questions for each department. Over two weeks, 45 people contributed detailed comments with links to supporting data. The leadership team synthesized input in one focused meeting, and stakeholders felt more heard than in previous in-person workshops where only the loudest voices dominated.

The async approach excels in information gathering, early-stage ideation, process documentation, and situations where stakeholders need time to research or consult others before providing input. It falters when real-time negotiation or conflict resolution is necessary, but those scenarios are rarer than our workshop-heavy calendars suggest.

The 1:1 Conversation Path: When Intimacy Beats Scale

Sometimes the problem with workshops isn’t the format—it’s the audience. Series of one-on-one conversations are more effective than workshops when dealing with sensitive topics, organizational politics, or situations where people won’t speak candidly in a group setting.

Research in the Journal of Organizational Behavior found that employees were significantly more likely to share concerns about strategy in one-on-one settings compared to group workshops, especially when reporting to someone two levels above them. Yes, 1:1s take more total time, but they yield far more honest input.

A head of engineering faced a decision between two architectural approaches with passionate advocates on both sides. Instead of a workshop that would have become a debate, she conducted 30-minute 1:1s with each of the eight senior engineers, asking identical questions. This revealed that five were actually flexible on the approach but had different priorities (speed vs. scalability vs. team learning). She then made a decision that addressed the underlying priorities and secured buy-in from all eight engineers because they felt genuinely heard.

The 1:1 approach is particularly effective for gathering requirements from senior stakeholders, user research, conflict resolution, and any situation where power dynamics would distort a group discussion. You can then synthesize findings without attributing comments.

A McKinsey study on change management found that organizations using structured 1:1 stakeholder interviews before major decisions had significantly higher adoption rates than those relying on workshops, mainly because they could address individual concerns proactively. Combining individual conversations with a brief decision meeting creates a hybrid that captures workshop benefits without the downsides: everyone provides input, the decision-maker synthesizes patterns, then a small group makes the final call.

The Decision Tree: Choosing Your Format

So how do you choose? Start with who owns the decision and whether you need consensus or just input. If there's a clear owner and you need input, workshops are almost never the right answer. If genuine consensus with no clear owner is needed, a workshop might be necessary but should be a last resort.

A design agency developed a decision tree framework that cut their workshop count by 70% in one year:

• If fewer than four people have expertise: Skip the workshop entirely. Schedule a focused meeting.
• If more than eight people need to contribute: Use async. A document with structured questions works better.
• If stakeholders are in more than three timezones: Use async. A Doodle poll study found that scheduling meetings with more than five people takes an average of 7.3 back-and-forth messages and 4.2 days.
• If there's genuine conflict between power-equal parties: Use a facilitated workshop with clear decision authority.
• If someone senior owns the decision: Use a focused meeting with a pre-read.
• If trust is low: Use 1:1s first to build psychological safety.

Consider the timezone and schedule constraints of participants. If coordinating calendars takes more than a week, async is probably better. If the decision needs to happen in 48 hours, a focused meeting works. Workshops require both scheduling ease and time for implementation.

Evaluate whether the group has the trust and psychological safety for honest discussion. Research by the NeuroLeadership Institute found that when people feel their opinion is predetermined to be dismissed, they contribute significantly less in group settings, meaning workshops with pre-decided outcomes waste everyone's time. Low-trust environments make workshops performative—you need to build trust first through 1:1s or async contribution where people can be more candid.

Stop Defaulting, Start Deciding

Here’s your challenge: audit your next five scheduled workshops using the decision tree provided. For each one, ask yourself honestly: Does this actually need to be a workshop, or am I defaulting to the format because it feels safer than making a decision?

This isn't anti-collaboration. It's anti-hype around workshops as the default format for everything. Before scheduling your next workshop, jot down the specific decision or output you need, who owns it, and whether a focused meeting, async document, or series of 1:1s would get you there faster.

The goal is not to eliminate collaboration but to respect everyone's time enough to choose the format that actually serves the work. Sometimes that's a workshop. Often it's not.

Try this experiment: the next time you're about to send a workshop invitation, pause. Draft the decision you need to make or the output you need to produce. Then choose the format that gets you there with the least ceremony and the most clarity. Document what happens—did you save time? Get better input? Make a faster decision?

Share your workshop-to-better-format success stories with your team. Create accountability and normalize the idea that saying no to unnecessary workshops is a sign of good leadership, not poor collaboration. Your colleagues will thank you, your calendar will thank you, and the actual work will get done faster.

After all, the best workshop might be the one you never scheduled.