On January 3, 2023, Shopify's leadership did not ask employees to attend fewer meetings. It reached into every calendar in the company and deleted them directly, wiping out every recurring meeting with three or more attendees in a single pass, an action projected to erase roughly 10,000 calendar events, and told staff not to add them back for at least two weeks (Forbes). That is a large-company stunt with a small-company lesson buried in it: a calendar does not fix itself. Someone has to design the week on purpose, then enforce that design with something sturdier than good intentions.
Shopify's own follow-through shows what the design looks like once the purge wears off. About a month later, 85% of employees were complying with the company's new No Meetings Wednesdays rule, and large all-hands gatherings were pushed into a single six-hour block on Thursdays (NPR). Shopify didn't end up with zero meetings. It ended up with meetings concentrated into specific, protected slots, and everything else pushed into writing.
Give the one meeting a fixed shape
A small team doesn't need Shopify's blunt instrument. It needs one recurring meeting with a shape rigid enough that nobody has to negotiate the format every week. The Entrepreneurial Operating System, built by Gino Wickman and detailed in his book Traction, runs on exactly one weekly leadership meeting: 90 minutes, same day, same time, every week, with a fixed seven-part agenda covering Segue, Scorecard, Rock Review, Customer/Employee Headlines, To-Do List, IDS, and Conclude (EOS Worldwide). The value isn't the specific labels. It's that the agenda is decided once and never re-litigated, so the room's time goes to decisions instead of format debates.
Shopify erased roughly 10,000 calendar events in one afternoon. A month later, 85% of employees were sticking to the new rule anyway. The deletion got attention. The compliance is the part worth copying.
Move status out of the room
Most meeting sprawl on small teams isn't decision-making, it's status-reading. Basecamp removed that category entirely with an Automatic Check-in tool that asks every employee "What have you worked on?" daily at 4:30pm and "What will you be working on this week?" once a week, with answers posted asynchronously instead of read aloud (Basecamp Help). Basecamp's Shape Up methodology extends the same logic to project rhythm: work is organized into fixed six-week build cycles followed by a two-week cooldown, with no daily standup or regular status meeting required in between (Basecamp, Shape Up). Once status lives in writing, the one meeting that remains can be reserved for the two or three things that actually need a live conversation.
Read before you talk
Jeff Bezos banned PowerPoint from Amazon executive meetings starting in 2004 and replaced it with six-page narrative memos that attendees read silently for roughly the first 30 minutes of each meeting before any discussion begins (CNBC). Applied to a nine-person team, the translation is simple: whoever owns an agenda item writes it up beforehand, numbers included, and the room reads it instead of watching it get presented live. Presentations persuade. Memos expose gaps, because a bad idea is much harder to hide in three paragraphs than behind a slide.
Automate the reminder, not the judgment
The failure mode for all of this is that the cadence quietly stops running once the founder gets busy. GitLab's Support Engineering team avoids that by keeping its weekly cadence without a live meeting at all: an automated Slack reminder fires every Wednesday prompting staff to add items to a shared document, and an automated cutoff message on Friday opens a Slack thread for async discussion of that week's items (GitLab Handbook). The bot enforces the rhythm. No one has to remember to.
What to build this week
- Pick one recurring meeting to keep, give it a fixed agenda modeled on the EOS structure, and put it on the same day and time every week, permanently.
- Replace any daily or weekly status meeting with a written check-in: what got done, what's next, posted asynchronously.
- Require a short written pre-read for that one meeting, due the day before, so the room starts with discussion instead of a recap.
- Set an automated reminder for when input is due and when the window closes, so the cadence runs even on a week you're slammed.
None of this requires deleting anyone's calendar. It requires deciding, once, which single meeting earns a permanent slot, and moving everything else into writing that runs on a schedule instead of on your attention.