No Meeting Day: The Complete Guide (Plus How to Run One)

Quick answer: A no meeting day is a recurring weekday — usually Wednesday or Friday — when a team or company formally blocks internal meetings to protect time for focused work. Citi, Shopify, and Asana all run versions of it. The mechanics are simple: pick a day, ban internal meetings on it, and protect it culturally.

This guide covers what it is, who's doing it, how to implement one at your company, and what to do when your company won't.

What is a no meeting day?

A no meeting day is exactly what it sounds like: a single weekday each week where the company-wide default is "no internal meetings." Some companies extend it to "no synchronous communication at all" — no Slack pings expected to be answered immediately, no recurring stand-ups. Others keep it narrower: internal meetings of 3+ people are off, but 1:1s and external/client calls can still happen.

The goal isn't to eliminate meetings. It's to protect a predictable block of focused, uninterrupted time every week. People who do creative or technical work — engineering, design, writing, research, strategy — disproportionately benefit. Even at companies where the rest of the week is meeting-heavy, one protected day turns out to be enough for most deep work to happen.

The practice goes by different names: No Meeting Wednesday, Focus Friday, Maker Day, Heads-Down Day, Async Day. Same idea, different branding.

Why companies are adopting them

Three forces have pushed no meeting days from "fringe productivity hack" to "policy you can defensibly propose to leadership":

1. Remote work made meetings cheap to schedule. Pre-2020, a meeting required reserving a physical room, walking to it, and reading the room socially before scheduling another. Zoom and Google Meet removed all of that friction. The visible result: more meetings per knowledge worker, especially recurring ones.

2. Calendar tooling made the problem measurable. Modern calendar audits — both manual and automated — let companies see, for the first time, exactly how many hours per week employees spend in meetings. For managers, the numbers are typically higher than leadership expects.

3. High-profile companies made it socially acceptable. When Shopify publicly purged thousands of recurring meetings in early 2023 and Asana's "No Meeting Wednesday" became widely cited, the practice stopped looking like a fringe productivity hack and started looking like a defensible policy choice.

Companies known to run no meeting days

A few well-documented examples:

Citigroup — Zoom-Free Fridays

In March 2021, CEO Jane Fraser announced Zoom-Free Fridays for the entire bank — a response to pandemic-era video-meeting fatigue. The policy: no internal video calls on Fridays. The reasoning was explicitly framed around employee wellbeing, which made it one of the first big-bank examples of meeting culture being treated as a workplace-health issue.

Shopify — the calendar purge

In January 2023, Shopify removed thousands of recurring internal meetings from employees' calendars in a single sweep and banned recurring meetings of 3+ people on Wednesdays. The framing was deliberate: if a meeting genuinely matters, someone will reschedule it. Most weren't rescheduled. It became one of the most-discussed examples of a tech company aggressively cutting meetings from above rather than waiting for the culture to shift.

Asana — No Meeting Wednesday

Asana, the work management platform, has long run a company-wide No Meeting Wednesday. Every Wednesday, the default expectation is heads-down work. Their product philosophy reflects it: project tracking and async updates are designed in part around the assumption that meetings shouldn't be the default coordination tool.

Async-first companies — Doist, GitLab, and others

Several remote-first and async-first companies — Doist, GitLab, Atlassian — have published versions of this practice. Their flavor tends to be lighter (a "Maker Day" rather than a hard ban) because they're already operating mostly async, so a no meeting day is closer to the norm than the exception.

How to implement a no meeting day at your company

The hard part isn't the policy. It's the cultural enforcement. Here's a five-step playbook:

1. Pick the right day

Wednesday is the most common choice. It breaks up the week and avoids the "starting cold on Monday" and "wrapping up Friday" problems. Friday is the second-most-common — better for catching up, worse for momentum into the weekend.

Avoid Monday (too many planning meetings naturally fall there) and Thursday (too close to Friday wrap-ups).

2. Define what "no meeting" actually means

A no meeting day fails when the rules are vague. Be specific:

• Internal recurring meetings of 3+ people: off
• 1:1s: allowed by mutual agreement
• External / client meetings: allowed but discouraged
• Stand-ups: moved to async (Slack, Linear, Loom)
• Urgent decisions: ad-hoc calls allowed; recurring ones cannot anchor here

Get this written down before launch. Ambiguity kills adoption.

3. Get leadership cover

The single biggest determinant of success: senior leaders publicly commit to it. If the CEO has meetings on the no meeting day, everyone else will too. Get explicit commitment from at least the top two layers of management before announcing it.

Sample pitch to leadership:

Subject: Proposal — No Meeting Wednesday pilot

Hi [Name],

Our team's calendar audit for [month] showed [X] hours/week per IC in meetings. I'd like to pilot a "No Meeting Wednesday" policy for [team / department] for 6 weeks, measuring:

• Hours of focused work time recovered
• Self-reported energy and output
• Number of urgent decisions deferred to Thursday

Companies including Asana, Shopify, and Citi have run similar policies publicly. The downside is bounded — if it doesn't work, we restore Wednesday meetings in 6 weeks. The upside compounds: protected weekly time for the deep work that produces most of the team's leverage.

Could we discuss in our 1:1 next week?

4. Communicate the launch widely

Announce in three places, not one: a company-wide email, a pinned message in the main Slack/Teams channel, and a section in the next all-hands. Repetition is what makes it stick. Include:

• Which day
• What's banned and what isn't
• How to handle the inevitable urgent exception
• How long the policy is in effect (call it a pilot if helpful)

5. Defend it for the first 8 weeks

The policy will be tested in the first two months. Someone will schedule a "really important" meeting on the no meeting day. Someone in leadership will accept it. The whole thing unravels from there.

Designate one person — a chief of staff, a head of ops — to politely flag every violation in the first 8 weeks. After that, the norm enforces itself.

What if your company won't do it?

If you can't get a company-wide policy, build a personal one. Three tactics:

Block your own calendar. Pick a day. Put a recurring 9-5 "Focus Day" block on it that's visible to coworkers. Most companies' calendar-visibility norms will handle the rest — people don't schedule over a block that looks intentional.

Spread it informally. Get 3-5 coworkers to do the same on the same day. Once five people are heads-down on Wednesdays, scheduling Wednesday meetings becomes annoying enough that it stops happening organically.

Make the block believable. The hardest part of a personal no meeting day is keeping the calendar block from looking like a single soft "Focus Time" placeholder — those tend to get scheduled over once people learn they're not real meetings. The fix is to use varied, realistic-looking events. We built Look Busy to do this automatically on iPhone — $0.99, one time — and a free Fake Meeting Name Generator you can use right now to come up with the titles.

For more tactical detail on the personal version, see our companion piece: How to Look Busy at Work: 14 Tactics That Actually Work.

Frequently asked questions

What day is best for a no meeting day?

Wednesday is the most common and generally the best choice. It breaks the week, doesn't conflict with Monday planning or Friday wrap-ups, and gives a reliable mid-week deep-work anchor. Friday is the second-most-common pick — better for catching up before the weekend, worse for momentum going into it.

Does a no meeting day actually work?

Anecdotally, yes — companies that have adopted them report meaningful gains in focused work time and employee satisfaction. The underlying mechanism is well-supported by academic work on deep work (Cal Newport) and flow states (Mihaly Csikszentmihalyi): knowledge work benefits disproportionately from long, uninterrupted blocks of attention. A single recurring block per week is enough to produce most of the benefit.

How is this different from "Focus Friday"?

Same idea, different day. Focus Friday is a no meeting day held on Friday. Citi's Zoom-Free Fridays is the most famous example. Wednesday vs. Friday is mostly a matter of team preference and which day's meetings are the easiest to relocate.

What about urgent, cross-functional, or external meetings?

Most well-implemented no meeting day policies allow exceptions for genuine urgency, external/client commitments, and pre-existing 1:1s. The rule is "no internal recurring meetings of 3+ people" — not "no human contact." Spell out the exceptions explicitly when you launch; ambiguity is what kills the policy.

Won't this just push all meetings into other days?

Sometimes, yes — and that's a useful diagnostic. If banning one day causes the other four to become unworkable, you don't have a no-meeting-day problem, you have a too-many-meetings problem. Many companies find that a meaningful share of displaced meetings simply disappear once people are forced to find a slot for them.

How do I get my team to actually respect it?

Three things: (1) get leadership publicly committed before launch, (2) write down the rules so nobody can claim ambiguity, (3) appoint one person to flag violations for the first 8 weeks. After that, the norm enforces itself.

Can I just do this myself without company support?

Yes. Block your calendar. Set a Slack/Teams status. If a single big "Focus Time" block keeps getting overridden, switch to a set of varied, realistic-looking events — see our look-busy tactic list for the manual version, or use Look Busy to automate it.