Engineering leadership

Meeting-free Fridays

GrowingEnglish1 min read

Open in the cabin →

Sample note, replace me.

Deep work needs long, unbroken stretches of time. A calendar with a meeting every ninety minutes has no such stretches, however short the meetings are.1 A day without meetings gives everyone at least one.

How it works

Nobody schedules a recurring meeting on Friday. One-off meetings need a reason that cannot wait until Monday. Incidents are the obvious exception. Everything else moves into writing, which is why this habit depends on Docs as artefacts.

What goes wrong

  1. Erosion. One "quick sync" is harmless. The fifth one means the rule is gone. Somebody has to say no, and it should be the manager.
  2. Thursday overload. Meetings do not disappear, they pile up the day before. Cut some instead of moving them.
  3. Silence mistaken for absence. People are working, not hiding. Agree on how to reach someone when it really matters.

What you get

  • Reviews that are read properly instead of skimmed between calls.
  • The hard problem of the week finally gets four hours in a row.
  • A natural moment to write the weekly note.

I have not yet written up how this interacts with regular one-to-one conversations; that will live in one-on-ones-that-matter when it exists.


Start with a trial month and ask the team afterwards. Few people ask for their meetings back.

Footnotes

  1. The classic statement of this is Paul Graham's essay on the maker's schedule and the manager's schedule. ↩

Tags: async, focus, teams

Linked from

  • Docs as artefacts

    A document is not a record of a decision made elsewhere. It is the place where the decision gets made, and the thing the team keeps afterwards.

    EvergreenEnglish1 min read