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 do decide a workshop is the right format, workshop contracting is how you avoid this outcome. 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 We Default to the Wrong Format

We've built an entire meeting culture around the workshop as the gold standard of collaboration. It appears democratic, inclusive, and thoughtful. But here's the uncomfortable truth: workshops have become expensive theater that postpones actual decision-making.

Consider the math. The average workshop costs organizations between $2,000-$10,000 when you factor in participant time, preparation, and opportunity costs. A mid-sized tech company recently held a 4-hour brainstorming workshop with 15 people to redesign their onboarding process. After spending 60 collective hours and generating 87 sticky notes, the actual decision was made two weeks later by the Head of HR and two team leads in a 30-minute meeting, rendering the workshop purely performative.

This isn't an isolated incident. A 2023 study by Atlassian found that 72% of knowledge workers report attending at least one meeting per week they consider unnecessary, with multi-hour workshops being the most commonly cited waste of time. The irony? Research shows that group brainstorming sessions produce fewer and lower-quality ideas than individuals working alone then sharing results.

The problem has intensified with remote work. Virtual workshops feel especially draining due to continuous video presence and lack of natural social breaks, yet organizations continue scheduling them out of habit rather than necessity. According to Harvard Business Review research, executives spend an average of 23 hours per week in meetings, up from less than 10 hours in the 1960s, with collaborative workshops representing the fastest-growing category.

Many workshops are scheduled because a manager wants to appear inclusive rather than because the format serves the goal. This is workshop planning as risk mitigation—if the decision goes wrong, at least everyone was in the room. But this logic confuses input with consensus and collaboration with accountability.

When Workshops Actually Work: The Rare Valid Use Cases

Before we throw out workshops entirely, let's acknowledge when they genuinely add value. Workshops aren't inherently bad—they're just dramatically overused.

Workshops work when you need to align multiple stakeholders with competing interests on a shared vision, particularly during major organizational changes like mergers or strategic pivots where psychological buy-in is as important as the output. When Spotify merged two product teams with conflicting roadmap priorities, a facilitated 2-day workshop allowed them to literally map dependencies on a wall and negotiate trade-offs in real-time, something that would have required months of back-and-forth emails. The key: they had decision-making authority and implemented outcomes immediately.

Design sprints and problem-solving workshops work when you have a truly wicked problem with no clear owner, genuinely need diverse perspectives, and have committed to implementing whatever emerges rather than using the workshop to validate pre-made decisions. A study in the Journal of Applied Psychology found that structured problem-solving workshops outperformed traditional meetings by 35%—but only when participants had pre-work assignments and a dedicated facilitator prevented groupthink.

Team-building workshops serve a legitimate purpose when relationship formation is the actual goal, not a side benefit, and when the team will need to collaborate intensively for an extended period 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 pattern here? Workshops work when the process is the product, when you're building relationships or negotiating trade-offs between equals. They fail when you're pretending to collaborate but really just gathering input for a decision someone else will make.

The Focused Meeting Alternative: When 60 Minutes Beats 4 Hours

Let's talk about what most workshops are actually trying to accomplish: reaching a decision with input from relevant stakeholders. A focused meeting with a clear decision-maker, pre-circulated context document, and time-boxed agenda accomplishes this—without the pretense that everyone needs to contribute equally.

The Amazon-style narrative meeting format demonstrates this beautifully. Participants silently read a 6-page memo for 20 minutes, then discuss for 40. This format consistently outperforms workshops for strategic decisions because it front-loads thinking time and eliminates performative participation. You can't hide behind nodding along when you've had to actually read and absorb the context.

Research by Bain & Company found that decisions made by a small group with a clear decision-maker were executed 5 times faster than consensus-driven workshop decisions, with no decrease in quality. A Microsoft study showed that meetings under 45 minutes had 73% higher perceived productivity ratings than those over 90 minutes, suggesting diminishing returns for extended collaboration.

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 dropped by 60% and the resulting roadmap had 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 but not consensus. Project launches, by contrast, almost always benefit from the structured alignment of a kickoff workshop. Focused meetings work best when, situations where 5-7 people max have genuine expertise, and when you can articulate success as a specific decision rather than vague alignment. If you can't name who owns the decision after the meeting, you need a different format.

The Power of Async: When a Document Beats a Discussion

Some collaboration doesn't need to be synchronous at all. Asynchronous documents excel when you need broad input but not synchronous discussion, allowing people to contribute when they have genuine insights rather than filling airtime.

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

GitLab, a fully remote company, reports that 95% of their decisions are made asynchronously through documented proposals, resulting in what they measure as 40% faster decision cycles compared to their meeting-heavy competitors. A study by RescueTime found that knowledge workers averaged just 2.8 hours of focused work per day, suggesting 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 5 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 reported feeling more heard than in previous in-person workshops where only the loudest voices dominated.

The async approach works best for information gathering, early-stage ideation, process documentation, and situations where stakeholders need time to research or consult others before providing input. It fails when you need real-time negotiation or conflict resolution, but those situations 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 work better than workshops when you're 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 3.5 times more likely to share concerns about strategy in one-on-one settings compared to group workshops, particularly when reporting to someone two levels above them. Yes, 1:1s take more total time, but they produce dramatically more honest input.

A head of engineering needed to decide 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 8 senior engineers, asking identical questions. This revealed that 5 were actually flexible on approach but had different priorities (speed vs. scalability vs. team learning). She then made a decision that addressed the underlying priorities and got buy-in from all 8 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 that used structured 1:1 stakeholder interviews before major decisions had 28% higher adoption rates than those that relied on workshops, primarily because they could address individual concerns proactively. Combining individual conversations with a brief decision meeting creates a hybrid that captures workshop benefits without workshop 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? The format decision should start with asking 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 you need genuine consensus with no clear owner, a workshop might be necessary but should be a last resort.

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

• If fewer than 4 people have expertise: Skip the workshop entirely. Schedule a focused meeting.
• If more than 8 people need to contribute: Use async. A document with structured questions works better.
• If stakeholders are in more than 3 timezones: Use async. A Doodle poll study found that scheduling meetings with more than 5 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 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 60% 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, write 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.