Gallup’s workplace research now shows global employee engagement fell for a second consecutive year, reaching 20% in 2025—its lowest level since 2020. The State of the Global Workplace 2026 estimates that low engagement costs the world economy about $10 trillion annually, equivalent to 9% of global GDP.

Those figures do not prove that meetings caused the engagement decline. They do, however, sharpen the question raised by overloaded calendars. Microsoft’s 2025 Work Trend Index found that employees were interrupted by meetings, emails, or messages every two minutes during the workday, adding up to 275 interruptions when after-hours activity was included.

We are drowning in passive, low-value syncs. High-impact deep work is routinely displaced by back-to-back status updates where half the attendees are quietly catching up on email. This pattern is not random. It is a predictable outcome of a powerful economic principle adapted for the modern workplace: Gresham's law of meetings.

In this case study, we will explore how that principle erodes team velocity, examine what Shopify’s calendar purge actually changed, and show how remote teams can replace passive video calls with active work sessions. If your team cannot find time for real work, understanding Gresham's law of meetings is the first step toward taking the calendar back.

Understanding Gresham's Law of Meetings

Gresham's law of meetings means low-effort recurring meetings crowd high-value focused collaboration off the calendar. Every meeting consumes the same scarce currency—time—even though its return differs. When easy status calls recur automatically, demanding problem-solving sessions and uninterrupted execution must compete for whatever fragments remain.

The original Gresham's Law is a monetary principle commonly summarized as "bad money drives out good." If two forms of commodity money circulate at the same legal face value, people tend to spend the debased currency and retain the more valuable one. The "good" money gradually disappears from everyday circulation.

Applied to corporate time management, the principle becomes: Low-effort, recurring status meetings drive out high-value, deep collaborative work. The status call is easy to schedule, requires little preparation, and creates visible activity. A productive working session demands context, pre-reading, facilitation, decisions, and concentrated mental effort.

That imbalance compounds. Recurring invitations renew themselves, while focus time must be defended repeatedly. An organizer experiences the convenience of booking the meeting, but every attendee absorbs its preparation, interruption, recovery, and opportunity costs. The cheap meeting therefore becomes expensive for the organization even when it feels painless to its creator.

Hybrid work adds another layer. Gable’s 2026 hybrid-work statistics roundup collects indicators showing that flexibility remains a central employee concern. Flexibility itself is not the problem; the danger appears when distributed coordination defaults to another call instead of choosing deliberately among documents, messages, recordings, or live collaboration.

AI transcription does not automatically solve that design problem. A summary can free participants from manual note-taking, but it can also make optional attendance feel harmless. The test is not whether a transcript exists. It is whether the people in the room must contribute, decide, create, or resolve something that could not be handled effectively on their own time.

The Shopify Case Study: Eliminating Meeting Sprawl

Shopify’s 2023 calendar purge was a deliberate reset of recurring coordination, not a proven cure for productivity. The company removed recurring meetings involving three or more people, restored meeting-free Wednesdays, constrained large gatherings, and later exposed meeting costs. Its most defensible result was reclaimed calendar capacity.

On the first working day of January 2023, Shopify launched an internal intervention that COO Kaz Nejatian described as a "Chaos Monkey." According to his account in Fast Company, the reset abruptly cancelled recurring meetings of three or more people and removed unnecessary internal Slack channels.

The action mattered because it reversed the burden of proof. Before the purge, an old meeting continued unless somebody challenged it. Afterward, an organizer had to decide that the meeting was valuable enough to recreate. That single change made passive recurring coordination more expensive while immediately returning larger blocks of focus time to employees.

The Three Pillars of Shopify's Calendar Purge

Shopify kept meeting sprawl from immediately returning through three forms of structural friction: a mass deletion that forced reconsideration, protected weekly focus time, and visible financial costs at scheduling time. Together, these controls changed the default from automatic recurrence to conscious justification.

The reported totals evolved as Shopify counted the recurring time it had removed. Nejatian later told NPR that the company had deleted 322,000 meeting hours, which he equated to adding roughly 150 employees. That figure represents calendar capacity, not an independently audited productivity gain, so it should not be read as proof that every reclaimed hour became valuable output.

The enduring lesson is the reset mechanism, not one headline number. Removing recurring inventory creates space immediately; rules and scheduling friction protect that space afterward. Similar radical approaches appear in the Asana Meeting Doomsday Case Study, showing why aggressive calendar pruning can be especially useful when a scale-up has accumulated years of unattended rituals.

Why Passive Video Undermines Remote Team Collaboration

Passive video undermines remote collaboration when the call makes listening optional and contribution invisible. A grid of faces can transmit conversation, but it does not automatically create shared work. Without an artifact, decision, or facilitated activity, attendees can become spectators while the meeting continues consuming everyone’s focus.

Distributed work is not disappearing. McKinsey’s people and organizational performance research recommends intentional choices about where work happens and reserving office time for the moments that benefit from it. Its guidance on healthy hybrid work emphasizes purpose rather than treating presence as an outcome by itself.

Hiring data points in the same direction. Alongside the broader resources at FlexJobs, its latest Remote Work Index reports that remote postings in the FlexJobs database grew 22% quarter over quarter in Q2 2026, with computer and IT becoming the fastest-growing remote category. The statistic is specific to that database, but it reinforces the need to design distributed collaboration well.

The problem is therefore not video itself. It is the broadcast pattern that video tools can encourage: one person speaks, everyone else mutes, and another tab wins their attention. Atlassian’s survey of 5,000 knowledge workers found that meetings were considered ineffective 72% of the time, suggesting that access to synchronous tools is not the same as effective collaboration.

This passive environment is fertile ground for Gresham's law of meetings. If accepting a low-value invitation is easier than questioning it, the calendar keeps expanding. Fixing remote collaboration therefore requires more than fewer meetings: teams must reserve live time for work that demands interaction and design every surviving session around visible participation.

Drafting a Ruthless Meeting Cancellation Policy

A strong meeting cancellation policy sets a minimum standard for synchronous time and gives employees permission to decline anything below it. The policy should require an agenda and outcome, limit participation to contributors, and force recurring organizers to explain why an asynchronous alternative cannot achieve the same result.

This is not about punishing organizers or eliminating human contact. It is about making the cost of synchronous coordination visible and protecting it for decisions, complex problem-solving, sensitive conversations, brainstorming, and relationship building. Three practical rules provide a workable foundation.

1. The "No Agenda, No Attendance" Rule

If an invitation lacks a written agenda, relevant context, and a specific desired outcome, attendance should be optional and declining should be normal. This forces the organizer to structure the work before consuming the group’s time. If reading and commenting on a document would achieve the outcome, cancel the call and use that asynchronous path instead.

The agenda should identify the decision owner, the questions participants must answer, and what will exist when the meeting ends. A topic list alone is not enough. For a deeper look at replacing status calls with documented workflows, see the GitLab Async Meetings Case Study.

2. The Two-Pizza Rule (Enforced)

A collaborative meeting should include only the people needed to create, advise, or decide. Once attendance grows beyond roughly six to eight people—the traditional two-pizza threshold—the session often becomes a broadcast. Move observers to notes or a recording, and let employees decline when they have no defined role.

The rule is a useful heuristic rather than a law. A workshop may need more participants if everyone has an active task, while a three-person status call can still be wasteful. The sharper question is whether each attendee knows what contribution only they can make during the session.

3. Mandatory Async Alternatives

Before adding a recurring meeting, the organizer should explain why a document, recorded update, dashboard, or threaded discussion cannot produce the outcome. Status reporting and routine metric reviews usually belong in asynchronous channels. Live time should remain available for ambiguity, conflict, creativity, and decisions that genuinely benefit from rapid exchange.

Every recurring series should also carry an expiration date. Require renewal after four to eight weeks, review attendance and decisions, and cancel it automatically when the purpose disappears. For practical implementation ideas, use this no meeting day policy template to define protected time, exceptions, and enforcement.

The Solution: From Passive Syncs to Active Work Sessions

The durable alternative to passive syncs is an active work session in which participants create a shared artifact, resolve a defined problem, or make a decision together. When contribution is visible and the outcome lives in the workspace, synchronous time becomes harder to waste and easier to evaluate.

The traditional remote-work stack can make that difficult. Teams often talk in one video application, collaborate in a separate canvas, track actions elsewhere, and add another tool for AI notes. That fragmentation increases context switching and gives organizers an easy escape route: talk through the topic now and promise to document the work later.

Combining conversation and creation in one environment removes that excuse. This is the core philosophy behind Coommit. By integrating high-definition video with an interactive real-time canvas, Coommit moves participants beyond a passive grid of faces. Teams can map architectures, design user flows, sort research, or organize sprint work while the conversation is happening.

The session should still begin with a purpose and end with an owner, deadline, and durable output. Software cannot rescue a meeting that should have been an email. It can, however, make active participation the path of least resistance when a live session is justified.

Contextual AI: Beyond the Basic Meeting Summary

Contextual AI is useful when it connects the spoken discussion to the work participants create, rather than merely producing another transcript. In a unified workspace, AI can interpret conversation alongside canvas objects, organize emerging themes, and draft actions grounded in the artifacts the team actually manipulated.

If a team is brainstorming a product launch, for example, the AI can synthesize sticky notes, group visual inputs, and propose action items informed by both the conversation and the canvas. The team remains responsible for validating those outputs, assigning ownership, and correcting missing context; the AI accelerates the work instead of replacing judgment.

That distinction matters because a summary documents activity after the fact, while contextual assistance can support the activity itself. When the meeting’s default state is active collaboration on a shared canvas, low-effort status updates feel visibly out of place. This complements the lesson in the Dropbox Virtual First Case Study: collaboration quality depends not only on location, but on the practices and medium chosen for the work.

Conclusion

Gresham's law of meetings explains why easy recurring syncs can crowd focused work and purposeful collaboration off the calendar. Shopify showed that a forceful reset can reclaim substantial scheduled capacity, but its reported meeting-hour totals should be understood as time removed from calendars—not independently verified productivity created.

Deleting bad meetings is therefore only half the battle. Remote and hybrid teams must protect the time they recover, require agendas and defined outcomes, prefer asynchronous updates, and make the remaining live sessions active. Unified workspaces that combine video, a collaborative canvas, and context-aware AI can support that discipline when synchronous work is genuinely necessary.

If you are ready to stop talking about work and start doing it together, evaluate every recurring invitation before adding another one. Then consider how a platform like Coommit can turn the meetings that survive from passive calendar obligations into focused, visible work sessions.