Block one day a week for deep work. MIT studied 76 companies that did exactly this.
The problem with a calendar full of meetings isn't just the time. It's what gets destroyed between them.
Here's the thing: a 30-minute meeting at 10am and another at 2pm don't leave you 3.5 hours of productive work time. They leave you three fragmented blocks — 1 hour, 1.5 hours, 1 hour — each of which needs its own ramp-up. By the time you've recalled your context and gotten into flow, you're 20 minutes in and the next meeting is already looming. Deep work never happens. Sound familiar?
So here's the move: pick one day a week — Wednesday, Thursday, honestly any midweek day — and protect it from meetings entirely. It's backed by real research, it's how some of the most productive companies run, and you can install it on your own calendar today. No mandate, no memo. Below: what the research actually says, what it cost Shopify, and how to run it solo before you spread it to your team.
What the research actually shows
MIT Sloan Management Review (2022)
Across 76 companies that introduced meeting-free days, one protected day a week lifted self-reported productivity by 35%. Two days pushed it to 71%, and three days to 73% — with cooperation up 55% at the three-day mark.
The study, by Ben Laker and colleagues, surveyed businesses worldwide rather than tracking a single controlled group, so read these as self-reported shifts, not lab measurements. The pattern that stuck out: more days off the calendar kept helping, and the companies that ran three meeting-free days a week saw the biggest gains. The honest read, then, is that one day is the easiest win to start with, not the ceiling. (sloanreview.mit.edu/article/the-surprising-impact-of-meeting-free-days)
Atlassian "State of Teams" (2024)
The average employee burns more than 31 hours a month in unproductive meetings — close to four full working days, gone, every month.
Atlassian also found that in organizations with poor meeting cultures, people spend 50% more time in unnecessary meetings than making progress on high-priority work. A no-meeting day is the bluntest possible fix: it just takes the worst offenders off the table for a day. (atlassian.com/blog/state-of-teams-2024)
How Shopify and Meta actually did it
This isn't some theoretical idea. Large organizations have actually done it, at scale, and reported back. A quick caution before the examples, though: company press numbers run optimistic, so treat them as direction, not gospel. The headline most people remember is Shopify's. If the deeper fix you want is fewer pointless meetings rather than zero meetings, that's a different lever — we get into it in No Agenda, No Meeting.
Shopify
In early 2023, a bot went into everyone's calendar and deleted every recurring meeting with three or more people. Employees were told to wait two weeks before adding anything back — and to be "really, really critical" about what they did.
Roughly 322,000 hours of meetings cleared. COO Kaz Nejatian put it in headcount terms: that's the equivalent of adding about 150 people. (npr.org, Feb 2023)
Meta
Meta is among the large tech companies that have publicly leaned on no-meeting days and dedicated "focus weeks" — stretches where recurring meetings are postponed so engineers can ship without the calendar fighting them.
We won't pretend there's a clean public number attached to it — the takeaway is simply that a company this size decided protected focus time was worth defending at all.
How to install it — at any level of the org
You don't need permission from leadership to protect your own calendar. Start with yourself: block Wednesday (or any day) as "Focus: no meetings," make it recurring, and decline anything that lands in that window with a quick note — something like "I protect Wednesdays for deep work, can we find another slot? Happy to make Thursday work." Honestly, you'll get pushback the first two or three times. After that, most people just route around you. And here's the part nobody tells you: one person's meeting-free day quietly resets what the rest of the team thinks is normal.
Once it's working for you, the playbook changes — first to move a team, then to move a whole org. Here's how each one tends to go.
If you're doing it for Your team
Propose it as a 4-week experiment: "Let's protect Wednesdays for deep work for one month and measure whether it changes how we feel about our output." Frame it as a test, not a policy.
In our experience, teams that actually run the full four weeks tend to keep going. Let the before/after make the case so you don't have to.
If you're doing it for Your organization
Bring the MIT / Atlassian research. Show the before/after from your team's experiment. Propose a pilot for one department before asking for org-wide buy-in.
Top-down mandates work, but bottom-up evidence is more durable. If your team loves it and their metrics improve, leadership adopts it — without a memo.
What to actually do on your no-meeting day
Real talk: the most common failure mode is that you protect the day from meetings and then quietly fill it with email, Slack, and other shallow work. The day disappears anyway, and you wonder why you don't feel any more productive. Guilty of this? Most of us have been.
The point is deep work — cognitively demanding tasks that need sustained focus and produce something genuinely valuable. The evening before your no-meeting day, write down the one thing you most need to move forward. Make that your first task, before email, before Slack, before anything reactive. (If async updates are how your team stays in the loop without meetings, automating your status updates protects the day even harder.)
Writing — proposals, strategy docs, analysis, anything that requires sustained thought
Building — code, designs, prototypes, anything that requires flow state
Thinking and learning — working through a complex decision, mapping out a plan, synthesizing research, or finally doing the thing you've been putting off
And one honest non-task: rest your brain when it's spent. A protected day used to actually recover counts more than one you grind into the ground.
The teams that use No-Meeting Wednesdays most effectively treat it like a protected resource — not a perk. They plan for it on Tuesday. They communicate clearly to stakeholders. And they guard it the same way they'd guard a client commitment or a product deadline. The teams that abandon it usually did the opposite: they let it be treated as optional, and it got filled in within a month.
Start with one protected day. Add more if it works.
One day a week is the easiest place to begin — and the MIT data points to bigger gains as you add more. Start with your own calendar. The team tends to follow once they see it working. (And if a job search is what's quietly eating your focus time, that's the exact busywork we built Career Capybara to take off your plate.)