# Do No-Meeting Days Actually Work?

Source: https://lessmeeting.com/blog/boycott-a-meeting-day/

No-meeting days went from a 37signals experiment to a norm at Asana and Shopify. They protect focus time but don't fix bad meetings.

---

The idea of a company-wide "no-meeting day" started as a bit of a rebellion. Jason Fried and the team at [37signals](https://37signals.com/) helped popularize it with a "Boycott a Meeting Day," and the practice has since become mainstream — companies like Asana, Shopify, and Facebook have all run some version of protected, meeting-free time.

And the appeal is obvious. Knowledge work needs long, uninterrupted stretches ("maker time"), and a calendar sliced into back-to-back meetings destroys it. Blocking out a full day where no one can schedule a meeting gives people a reliable island of focus every week. If your team is drowning in meetings, a no-meeting day is a genuinely good intervention.

**But here's the catch:** a no-meeting day treats the symptom, not the cause.

Think of it like a recurring headache. Declaring one meeting-free day is like saying "I'll just avoid the thing that gives me headaches once a week." It helps, but it quietly accepts that the other four days are going to hurt. The meetings don't get better; they just get quarantined into the days that remain (often making *those* days even more crowded).

The deeper fix is better meetings, not fewer of them. A meeting that has a **clear agenda**, **effective moderation**, **quality notes**, and **accountable action items** is worth showing up for, and it earns its place on the calendar. Get that right and most of the meetings you were trying to escape either get shorter, get combined, or disappear on their own.

So by all means, protect a no-meeting day for your team's focus time. Just don't let it become a substitute for doing the harder work: making every meeting you *do* hold one worth attending.