Communication & Meeting Rhythm

Design the team's meetings once, on purpose, instead of letting them pile up one recurring invite at a time: count what you have, keep only what earns its time, and move plain updates into writing.

Psychological safety is strong research (Edmondson, 1999; meta-analysis: Frazier et al., 2017). OKRs are practice, not research (Grove, 1983; Doerr, 2018). The idea that productivity suffers past a certain share of time in meetings has no source found and is a rule of thumb, as are the role targets, agenda timings and survey thresholds on this page.

Use it when:

• People say they have no time to do the work because of meetings.
• Decisions get made in corridors because the meetings do not decide anything.
• The team has grown, gone hybrid or spread across sites, and the old rhythm no longer fits.

Skip it when:

• You want to fix one meeting with your own manager: use 9.1 Manager 1:1 Prep.
• The team has not agreed basic channels and response times yet: start with 4.4 Ways-of-Working Agreement.

A team's meeting rhythm should be designed once, deliberately, rather than grown one invite at a time. Most of what guides that design is craft, not research. The common warning that productivity drops once meetings take a large share of the week is a rule of thumb with no source found, and the role targets around it are starting points to adjust. Two pieces carry more weight. Retrospectives depend on psychological safety, the shared belief that the team is safe for questions, dissent and admitted mistakes, one of the best evidenced team climate factors (Edmondson, 1999): a retro without it produces polite fiction. Quarterly planning borrows the OKR format, practitioner craft from Grove (1983), popularized by Doerr (2018).

So be strict where you can measure: count the hours, because drift shows in the count, and give every meeting a reason to exist. Be strict about blameless retros with one experiment at a time, because that protects the safety the research is about. Treat the rest, from no-meeting days to rotating formats, as experiments. A rhythm that cannot retire a meeting will only grow.

List the recurring meetings a typical team member attends. Ask the regular attendees to rate each for value, then decide: keep, shorten, move to a written update, or retire.

Strong answer: "Monday status round: 60 minutes weekly, 1 hour per person, value 2. Decision: replace with a written update by Monday 10:00 and a 15-minute call only for blockers."

Share of a typical week in meetings today:

Rule of thumb, not research: a common consulting claim puts the danger point at around 40 percent of working time, with lower targets for specialists than for managers. No source has been found (see the Meeting-load benchmark card), so set your own target and watch the trend.

Illustrative example: the organization, roles and numbers are made up.

A customer service lead at a Danish energy utility runs a twelve-person team across two offices. People say they cannot answer customers because of internal meetings.

Section 1: seven recurring meetings, about nine hours per person per week, close to a quarter of the week. The Monday status round scores 2 and becomes a written update. The Friday wrap-up scores 1 and is retired. The weekly case review scores 4 and stays.

Section 2: daily, a written check-in in the team channel by 9:00; weekly, a 45-minute meeting for decisions and blockers; every three weeks, a retrospective; quarterly, a half-day planning session using objectives and key results.

Section 3: no internal meetings on Wednesdays, when call volumes are highest.

Section 4: the team agrees that an invite without a purpose line may be declined.

Section 5: after one quarter, meeting time is down to about five hours per person a week, and the retired wrap-up has not been missed.