Take a hard look at your calendar for the upcoming week. How many recurring blocks actually move projects forward, and how many survive because nobody has challenged them? For many remote and hybrid teams, legacy check-ins, redundant status updates, and habitual syncs quietly crowd out focused work. Asana’s meeting doomsday case study tested a deliberately disruptive response.
Instead of asking employees to trim meetings one invitation at a time, the experiment created a temporary calendar reset. The pilot offered teams a practical way to compare inherited meeting habits with a deliberately rebuilt schedule.
In this deep dive, we will unpack the mechanics of the meeting doomsday case study, examine the psychological barriers to clearing calendars, and provide a step-by-step playbook for pursuing the reported average of 11 reclaimed hours per month. We will also explore how shared communication spaces can help prevent recurring-meeting bloat from returning.
The Anatomy of an Asana Meeting Doomsday
An Asana meeting doomsday is a calendar reset: employees audit recurring meetings, remove them for a 48-hour period, and rebuild only the sessions that still justify their time. The original pilot focused on small recurring meetings, while Asana’s broader public playbook now describes deleting recurring meetings and starting fresh.
Rebecca Hinds documented the experiment at Asana, drawing on work with organizational behavior professor Bob Sutton. The intervention was designed to bypass the friction of optimizing a calendar one invitation at a time. When every meeting remains by default, status quo bias makes a familiar weekly sync feel harmless even when its purpose has faded.
By forcing a temporary wipeout, the Asana meeting doomsday shifted the burden of proof. A recurring meeting no longer returned automatically; its owner had to reconsider its value, duration, cadence, and format.
The Power of the 48-Hour Freeze
The 48-hour freeze creates distance between deletion and reconstruction, so participants must reassess a meeting before habit can restore it. Asana presents the wait as time to sit with a cleansed calendar, consider each meeting’s value, and choose whether to eliminate it, shorten it, reduce its cadence, or redesign it.
This cooling-off period reduces the chance that fear of missing out or social discomfort will immediately recreate the old schedule. It also gives teams a brief opportunity to test whether project boards, direct messages, shared pages, or interactive canvases can carry information without another standing call. That deliberate pause separates a calendar reset from routine invite cleanup.
The Psychology Behind Calendar Bloat: Why We Must Reduce Recurring Meetings
Recurring meetings can accumulate because the cost of keeping them feels lower than the social cost of canceling them. In distributed teams, weak documentation, unclear ownership, and fragmented tools add another pressure: people schedule standing syncs to reconstruct context that could already be visible to participants.
A meeting may begin as a useful bridge between disconnected systems, then remain long after the original coordination problem disappears. When teams use separate tools for project tracking, video, notes, and whiteboarding, synchronous calls often become the place where everyone manually reassembles the latest state of the work.
A related governance lesson appears in The Shirky Principle: A Shopify Meeting Purge Case Study: when meetings are easy to create but socially difficult to remove, periodic resets can restore scrutiny to the calendar.
Conway's Law and the Fragmented Tool Stack
Conway’s Law says systems tend to reflect the communication structures of the organizations that design them. For meeting hygiene, the practical lesson is that fragmented communication can produce fragmented decisions and extra coordination. Better shared context does not remove every meeting, but it can reduce avoidable alignment work.
According to Martin Fowler’s analysis of Conway’s Law, systems are constrained by the communication patterns of their designers. In a remote team, that means tool and information boundaries deserve attention alongside the calendar itself.
When agendas, decisions, visual work, and follow-ups live in one shared workspace, people can inspect more context asynchronously. A platform combining video with an interactive canvas will not make every alignment call disappear, but it can reduce tab switching, missing context, and the need to schedule another meeting simply to reconcile separate artifacts.
The 48-Hour Rule: Executing Your Own Meeting Purge
A practical meeting purge has three non-negotiables: establish a baseline audit, create a shared deletion window, and require explicit redesign before anything returns. The Asana pilot’s signature mechanism was a 48-hour removal period; copying the intervention means protecting that pause rather than letting organizers instantly recreate the old calendar.
Before the purge, agree on scope and exceptions. The original pilot targeted small recurring meetings, whereas Asana’s public guidance now describes a broader recurring-meeting reset. Client calls, regulatory sessions, interviews, and time-sensitive operational meetings may need to remain, but internal exceptions should be explicit rather than assumed.
Step 1: Total Deletion
Start total deletion with a baseline audit: record each recurring meeting’s owner, cadence, duration, attendees, purpose, and last useful outcome. Then cancel the agreed scope on one shared date. The pilot described in Harvard Business Review targeted small recurring meetings with fewer than five attendees, so define your scope before touching calendars.
Pick a date that minimizes operational risk and tell affected collaborators why invitations are disappearing. Save the audit data before deletion so you can compare meeting time after the experiment with the original baseline.
Step 2: The Mandatory Freeze
Keep the selected recurring meetings off calendars for the full 48-hour period, and do not send replacement recurring invites. When work truly cannot wait, use asynchronous updates or a clearly bounded ad hoc meeting. The purpose is comparison: teams need enough distance to judge what is actually missing.
Use the window to identify information that should live in a project page, decision log, or shared canvas. The freeze is not evidence that every missing meeting was useless; it is a structured opportunity to discover which coordination needs remain when habit is removed.
Step 3: Intentional Re-addition
Re-add a meeting only when its owner can state the decision, deliverable, or relationship outcome that requires synchronous time. Give every returning invite an agenda, necessary attendee list, time limit, and review date. If a 15-minute review or lower cadence can do the job, redesign it before reinstating it.
Do not judge success only by the number of canceled events. A weekly 60-minute meeting redesigned as a focused 15-minute review is also a meaningful result. Asana reported that participants shortened some meetings to unconventional lengths and reduced the cadence of others rather than simply eliminating everything.
The Hard Numbers: Analyzing the Meeting Doomsday Case Study Results
According to the Asana Work Innovation Lab account, participants in its one-month Meeting Doomsday experiment saved an average of 11 hours per month by redesigning meetings that were no longer productive. Asana annualizes that result as 17 workdays per person, making 17 days the clearest sourced yearly comparison.
Asana’s January 2026 meeting-management guidance continues to cite the 11-hour average. However, it remains a result from Asana’s experiment, not a guarantee that every participant or organization will reclaim the same amount of time.
A separate follow-up called Meeting Reset studied 60 Asana marketing employees and assessed 1,160 standing meetings. That group saved 265 meeting hours per month in total. The follow-up supports the broader value of auditing and redesigning meetings, but its collective result should not be confused with the initial pilot’s per-person 11-hour average.
Life After the Purge: Moving to Canvas-Led Collaboration
After a purge, the remaining meetings should produce decisions, designs, plans, or stronger working relationships—not repeat information people could read. A shared page or canvas gives participants common context before discussion and a visible artifact afterward, helping a leaner calendar stay useful rather than merely emptier.
Clearing the calendar is only half the battle. If retained sessions remain passive status updates, recurring bloat can return under new names. The more durable alternative is to make synchronous sessions active work periods in which participants review context, resolve disagreements, and create an output together.
The Rise of Page-Led Meetings
Page-led meetings center discussion on a high-quality written document that sets out context, goals, and key decisions. In Atlassian’s format, attendees read the page before discussion, so the group starts from shared information instead of spending the opening minutes reconstructing context verbally.
In Atlassian’s page-led meeting experiment, 85% of page-led meetings accomplished their goals, compared with 69% of control meetings. That finding supports anchoring a live conversation to prepared context, although it does not prove that every document-led meeting will be shorter.
Separately, Atlassian’s 1,000 Days of Distributed Work report found that employees in a calendar-redesign experiment who timeboxed their priorities declined 17% more meetings and spent 13% less time in them. That 13% result belongs to the timeboxing experiment, not specifically to page-led meetings.
Why Coommit is Built for the Post-Purge Calendar
Coommit brings HD video, a shared interactive canvas, and meeting context into one collaborative workspace, so a retained session can focus on creating an artifact rather than narrating status. That design supports the post-purge rule: use synchronous time for decisions and co-creation, then keep the discussion and visual work together.
If you want to permanently stop the meeting after the meeting, participants need to leave with accessible decisions, ownership, and context. Keeping the conversation beside the canvas reduces the need to reconstruct a brainstorm from disconnected notes and screenshots.
Coommit’s contextual AI is designed to synthesize verbal decisions alongside activity on the canvas. An AI coworker for meetings can help turn that combined context into usable follow-up material, but teams should still assign owners and confirm consequential decisions before the session ends.
Sustaining the Momentum: Avoiding the Relapse
Meeting savings last only when teams continually challenge new recurring invites and retire sessions whose purpose has expired. Protect the reset with lightweight quarterly reviews, named owners, expiry dates, and an annual full audit. Treat every recurring meeting as a renewable commitment, not permanent calendar infrastructure.
For quarterly reviews, ask whether each meeting still requires the same attendees, duration, cadence, and synchronous format. Use asynchronous updates for one-way information sharing, while reserving live time for complex decisions, collaborative design, conflict resolution, and relationship-building.
Asana recommends conducting a full meeting doomsday at least once a year. Between resets, require returning meetings to retain an agenda and measurable purpose. A meeting should not exist merely to report work that has already happened; the strongest synchronous sessions are places where meaningful work, decisions, or connection actually occur.