People will tell you the meetings are a waste, then rate the last one more kindly than they just complained. A workshop built on the complaint will teach an inbox trick and leave the meeting that spoils the day on the calendar.
Steven G. Rogelberg, Cliff Scott and John Kello set the paradox out in The Science and Fiction of Meetings, MIT Sloan Management Review, January 2007. More than half the employees they surveyed said they complain about meetings in public. Most of that group admitted they did not feel as negative as the public line suggested. In the round numbers the authors give for meetings in general, 17 percent called them very good to excellent, 42 percent good, 25 percent neither and 15 percent poor or worse. A larger share rated the most recent meeting good or better, and half saw room to improve.
What actually spoils the day
The load is the wrong target. The authors report no direct link between how many meetings a person must attend and job satisfaction. The link depends on accomplishment striving, a strong desire to get work goals done. People with that desire report poorer satisfaction as meetings increase. People with less of it may want more meetings, for company or for structure.
In three studies, the strongest factor in job satisfaction was how the person felt about the effectiveness of the meetings they attend. The bad feeling grew as time in those meetings grew. A run of bad meetings left people stressed, dissatisfied and more inclined to leave. The public complaint is not the meeting someone privately rates as poor.
What the day has to rewrite
The authors name two reasons to meet. Unresolved issues are blocking work that depends on more than one person, or the agenda truly needs the group. Do not hold one merely because it is already on the calendar. Decide who must attend, who may stay away and how the people outside will hear the decision. Declining a subject outside one's expertise has to be acceptable. A core drives the subject. Others come only when their input is the point. Explain both roles, so staying out is not a slight.
If it stands, send the agenda and the background ahead, and let people add an item. Agree the problem before the solutions, and agree how a solution will be judged before the options are weighed. For a group that will meet again, set the roles early, with a way to say when a role was missed. Then critique the meeting for the next one: the pace, the flow and whether the rules held.
How a tips session gives itself away
Most employees believe their meeting skills are above average, which cannot be true of most of them. The basics the authors name are ordinary: when to call the meeting, how to prepare an agenda, how to bring people into it and how to handle a conflict. Few organisations ask how meetings are viewed. A proposal that never asks, and never puts that behaviour where a peer can see it, adds a personal method on top of the same room.
If the examples belong to the facilitator, and the follow-up is a poster of inbox habits, the ineffective meeting survives. The finding you are buying is narrower. One meeting, rewritten so it exists for a reason, with the right people and with the problem stated before the solutions.
Collective Campus is building high-performance culture and teams for the AI world. The productivity workshop is for a team that can point at one recurring meeting and is allowed to change who comes and what it may decide. What interruptions do to the work around that meeting is in how to judge the day for a busy team. Why a notes pack fades after the room is in the notes nobody used. Habits that have to outlast the first rush are in turning bad habits into good ones.
What to bring
Bring the meeting, the names of the people who must be in it and the sentence that says why it exists. If every meeting is sacred, or none of them is named, the workshop has nothing to rewrite.
