liveBook · Manning

Meeting fatigue

As explained in Think Like a Software Engineering Manager

Meeting fatigue is mental exhaustion or reduced effectiveness caused by excessive or poorly structured meetings.

Meeting fatigue is the loss of energy, focus, or effectiveness caused by excessive or poorly structured meetings. Teams can reduce it by setting shared expectations for how meetings should work. section 11.4.3

A practical meeting bill of rights can require:

  • A clear agenda in every meeting invitation. section 11.4.3
  • Expected outcomes stated before the meeting begins. section 11.4.3
  • The meeting organizer to own responsibility for meeting quality. section 11.4.3
  • The team to review and improve meeting practices collaboratively, such as during a sprint retrospective. section 11.4.3

When meetings take over the sprint

Excessive product-team meetings burdened an engineering team. During a sprint retrospective, the team created and promoted a meeting bill of rights, helping recover control of its time and use meetings more effectively. section 11.4.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Provides a practical intervention with agendas, outcomes, organizer accountability, and retrospective review.
Examples
Uses excessive product meetings, a sprint retrospective, and a team meeting bill of rights as concrete examples.
What it assumes
Assumes participation in team meetings and introduces collaborative expectation-setting through a practical workplace problem.
What you can do after
Apply it by establishing agendas, expected outcomes, organizer responsibility, and collaborative meeting reviews.
How it connects
Connects meeting fatigue with managing expectations, transparent communication, collaboration, and sprint retrospectives.

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.