Models Operations model

Meetings

Battle tested

Which meetings should exist, which should become writing, and how to audit, cut and run the ones that stay.

23% of facts from primary sources, 3 of 1313 verified facts, last checked 29 Oct 2026Primary source: primary sourceSecondary: secondary sourceEstimate: estimate

Should this be a meeting?

Up to six questions. The rust line is your path. Each faint branch is where the other answer leads. Turn the dial to your stage; slide or type your headcount.

  1. Is a decision needed?

    • No: More questions
  2. Can the decision be reversed within a week or two at low cost?

    • Yes: More questions
  3. Is there a written doc of 1 to 6 pages with the options, a recommendation and what would change your mind?

    • No: Write the doc first
  4. Do people need to react to each other in real time, because views conflict or the trade-offs are hard?

    • No: Comment in the doc

Stage

Efficiency savers

What each step saves. Where nobody publishes the number, it says so.

The routines

Each step has an owner, a time cost and a document. Costs marked estimate are worked out, not published data.

  1. Export the calendar

    Four weeks of recurring meetings: title, organiser, attendees, length, recurrence.

    Ops lead or Chief of Staff1 to 2 h (estimate)Meeting inventory

  2. Cost it

    Attendees times loaded hourly cost times length. No reliable benchmark found for a typical cost per meeting hour. Bain found one weekly executive committee meeting drove about 300,000 person-hours a year across 17 large firms once preparation was counted.

    Ops lead with finance30 min (estimate)Meeting cost sheet

  3. Tag each meeting

    Decide, inform, relationship, work session or no clear purpose. Name the decision it produces.

    Each organiser10 to 15 min (estimate)Keep, convert or kill form

  4. Run each through the tree

    Convert information meetings to writing, kill the ones with no purpose, shorten the rest.

    Organiser, with the ops lead as referee5 min per meeting (estimate)Updated inventory

  5. Publish the rules

    Agenda 24 hours ahead or the meeting is cancelled. A named decision owner. Notes in the doc. A quiet block each week.

    CEO announces30 minMeeting charter, one page

  6. Re-audit

    Repeat each quarter and compare hours before and after.

    Ops lead30 to 60 minAudit log

Bain, via Forbes: secondary source (opens in a new tab)

How meeting rules go wrong

Failure modes

  • Purge rebound

    Meetings creep back after the reset. Shopify said excess meetings had crept back before its purge. Audit quarterly and require a two-week wait before re-adding.

  • Leaders break the rule

    The founder books over the quiet block. Leaders obey first, and the ops lead can decline on their behalf.

  • Async overload

    Threads replace meetings and never close. Set respond-by dates, and call for 20 minutes after one round.

  • Memo bureaucracy

    Six-pagers for small decisions. Use the tree: only one-way doors need a memo.

The biases behind them

  • Parkinson’s law

    The meeting expands to fill the slot. Use a shorter default and a hard stop.

  • Planning fallacy

    Agenda times are underestimated. Cut the agenda by a third and carry the rest to a thread.

  • Sunk cost

    You keep a standing meeting because it exists. Give it a sunset date and ask whether you would start it today.

  • Status quo bias

    Sixty minutes because the calendar says so. Change the default.

Who owns the calendar

Set by the dial on the instrument. It follows your headcount until you turn it.

Runs it
CEO, with the first ops hire or a Chief of Staff as backup.
You keep
The staff meeting and the decision meetings.
Hand off
The calendar audit and the decision log.

My stance

Run the first audit at ten people, not fifty. Convert every update meeting to writing and keep one weekly leadership meeting.

Where the evidence disagrees

Was the Shopify purge a good idea?

For

Shopify’s COO said it drew more positive feedback than anything else he had done, and employees now feel free to decline meetings.

NPR (OPB), Shopify and 322,000 hours: secondary source (opens in a new tab)

Against

Rogelberg says it targets the wrong thing: bad meetings are the problem, not meetings. Some on LinkedIn called it an overcorrection.

NPR (OPB), Shopify and 322,000 hours: secondary source (opens in a new tab)

No independent data either way, and no one-year follow-up found.

How strong is the no-meeting-day evidence?

MIT Sloan found the best results at three days, across 76 companies with more than 1,000 employees. It relies on surveys, does not describe how the companies were chosen, and shows association, not cause.

MIT Sloan Management Review, meeting-free days: primary source (opens in a new tab)

Rules by country

General information, last checked 29 Oct 2026. Not legal or tax advice.

Disagree with a stance, or have data that should be here?

Email me