No Meetings on Wednesdays: How We Ship Faster

No Meetings on Wednesdays: How We Ship Faster is simple: if a model hurts customers, we do not copy it.

One day a week with zero meetings. No standups, no syncs, no ‘quick calls.’ Just eight hours of uninterrupted work. We write from operating experience, not trend-chasing.

The Real Cost of a Meeting

A 30-minute meeting doesn’t cost 30 minutes. It costs at least two hours.

Here’s why. A developer working on a complex feature — say, rebuilding our invoice PDF renderer — needs about 20 minutes to load the full context into their head. The data model, the edge cases, the thing they tried yesterday that didn’t work, the approach they’re about to try. That context is fragile. One interruption and it collapses.

Now put a 30-minute meeting at 2:00 PM. The developer stops productive work around 1:30 because there’s no point starting something deep with 30 minutes on the clock. The meeting runs until 2:35 because they always run over. Then 15 minutes to context-switch back. Then 20 minutes to reload the mental model. Real work resumes around 3:10 PM. That “30-minute” meeting ate one hour and forty minutes of deep work.

Paul Graham wrote about this in 2009. He called it the maker’s schedule versus the manager’s schedule. Seventeen years later, most companies still haven’t learned the lesson.

What Happens on Wednesdays

We ship more on Wednesdays than any other two days combined. That’s not hyperbole — I tracked it for six months.

Here’s a real example. Our expense management module — the one that handles receipt scanning, categorization, and reimbursement workflows — was built almost entirely on Wednesdays. Supriya, who led that feature, said the same thing every Thursday standup: “I got more done yesterday than Monday and Tuesday combined.”

Last Wednesday, one of our engineers built the entire first pass of our new CSV export system. Designed the interface, wrote the backend logic, added tests, opened a PR. On a normal day with two meetings, that’s a three-day task. On a Wednesday, it’s done by 5 PM.

The math is simple. An uninterrupted 8-hour block is not 33% more productive than a fragmented 6-hour day with meetings. It’s 200% more productive. Flow state compounds. Ideas connect. Complexity becomes manageable when you can hold the full picture in your head without someone asking you to join a call.

The Rules

They’re simple and non-negotiable:

1. No internal meetings. Not even “important” ones. If it’s truly urgent, it can wait until Thursday. Almost nothing is truly urgent.
2. No Slack DMs expecting immediate responses. Post it, and it’ll be read tomorrow. Or better yet, write it in a GitHub issue where it belongs.
3. External client calls are the only exception. We’re a consulting company too. Clients come first. But we try hard to schedule client calls on other days.
4. No guilt. Nobody apologizes for not responding on a Wednesday. That’s the point.

Try It

Pick a day. Any day. Block it for your entire team. No meetings, no exceptions, for eight weeks. Measure what ships. I guarantee you’ll never go back.

Your team doesn’t need more meetings. They need fewer interruptions. One meeting-free day per week is the cheapest productivity investment you’ll ever make.

Hard Stop

If you agree, build this way. If you disagree, test the opposite and measure the real cost.

Start with Miru or read the docs.

Vipul A M

Co-founder at Saeloun. Building Miru. Rails contributor. Shipping from Pune, India.