Interrupting Others in Meetings Safely: I

You're in a meeting, and the discussion has gone on for a while. Eric is just now raising an issue that Inez mentioned ten minutes ago, and which everyone, including Eric, had agreed could be deferred until tomorrow's meeting. Time is short. Do you interrupt Eric to tell him that Inez has already raised that issue? Or do you sit quietly while precious minutes slide away, to be lost forever?

During meeting discussions, interrupting others is sometimes useful. But interrupting is risky; it can cause offense and thus lead to bitter, destructive conflict. Some approaches to interrupting without these risks depend on a wide array of politeness tactics. I'll address some examples of these techniques next time. But first I'll explore an alternative method for interrupting without these risks. It depends on "institutionalizing" the interrupt function so as to limit the need for individuals to interrupt each other.

For example, During meeting discussions,
interrupting others is
sometimes useful,
but it's riskyin "First Aid for Painful Meetings," Point Lookout for October 24, 2001, I suggested the usefulness of a role I called Designated Digression Detector (DDD). This person — who could be the chair, or facilitator, or anyone else — is empowered to interrupt at any time to alert the group whenever it has strayed from discussing the current agenda item. These interruptions are unlikely to give offense because the DDD is empowered to keep the discussion on topic.

As a second example, in "An Agenda for Agendas," Point Lookout for May 25, 2005, I suggested the need for a timekeeper to ensure that discussions of agenda items stay within the time bounds set in the agenda. The timekeeper is empowered to interrupt the discussion at preset times — for example, when only five minutes remain, when one minute remains, and when time is exhausted for the current agenda item. These interruptions are unlikely to give offense, because they're objective and pre-arranged. And they indirectly urge people to be concise and to-the-point when they speak, even before the timekeeper has announced any of the preset times.

Finally, a Designated Repetition Detector (DRD) can also be a useful role. The DRD is responsible for interrupting contributors who appear to be repeating the remarks of previous contributors, if they haven't exhibited something new within some predetermined approximate time after beginning their remarks. This person must have a mastery of the content of the meeting, and must pay close attention to all contributors, so as to be familiar with all previous remarks. It's a risky role that must be executed with skill and diplomacy. Humor helps, too. In some instances, if no single person has sufficient mastery of all agenda items, DRDs can be appointed on a per-agenda-item basis.

Appointing an individual to a designated interrupter role has an effect beyond mere execution of the responsibilities of that role. The appointment reduces dramatically the probability that the appointed individual will exhibit behaviors that the designated interrupter is charged with identifying. For example, if Person A habitually digresses, appointing A as a DDD is likely to cause A to reduce his or her own digression behavior. Or if Person B is known to be long-winded, appointing B as timekeeper is likely to cause B to be more concise when he or she makes contributions to discussions.

Rigorous speaker queue management is another approach to limiting the need for individual interruptions. By consistently controlling who speaks, the manager of the speaker queue (usually either the chair or facilitator) encourages people to withhold their comments until recognized. Two approaches to speaker queue management are first-in-first-out (FIFO) and polling. In FIFO, people "sign up" to speak by indicating to the queue manager their desire to speak. The usual indicator is a raised hand (either real or virtual). In polling, the speaker queue manager offers speaking time to each participant in turn, round and round, repeatedly, until a complete round results in no requests to speak. Both methods tend to attenuate the urge to interrupt.

Finally, for standing meetings — that is, repeated regular meetings — we can adopt a "process check" custom. At any time, any participant can interrupt the goings-on to invoke a "process check." The chair or facilitator is then obliged to halt the meeting to address the process check. The person who invoked it then describes what motivated the process check, which must be one (or more) of a number of predetermined process violations. For example, if the DRD has failed to interrupt a contributor who's merely repeating the remarks of others, anyone in the meeting can invoke a process check and explain that he or she feels that the DRD should have interrupted a repetitious contribution. Similarly, meeting participants can call process checks if the DDD or the timekeeper has failed to discharge his or her responsibilities. By prior agreement, the group can have a list of other conditions that are eligible for process checks. Examples:

• People are shouting at each other
• Someone has interrupted someone else
• Two people are over-talking each other
• An agenda item has been addressed out of order without approval of the meeting
• Someone is dominating the discussion, excluding others
• Someone seems to be "checked out" and isn't contributing
• An invalid process check: the invoker is objecting to something not on this list

Next time we'll survey techniques for individuals to interrupt each other while limiting the risk of giving offense.  Next in this series  Top    Next Issue

Do you spend your days scurrying from meeting to meeting? Do you ever wonder if all these meetings are really necessary? (They aren't) Or whether there isn't some better way to get this work done? (There is) Read 101 Tips for Effective Meetings to learn how to make meetings much more productive and less stressful — and a lot more rare. Order Now!

Your comments are welcome

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Effective Meetings:

Games for Meetings: III

We spend a lot of time and emotional energy in meetings, much of it engaged in any of dozens of ritualized games. Here's Part III of a little catalog of some of our favorites, and what we could do about them.

Working Lunches

To save time, or to find a time everyone has free, we sometimes meet during lunch. It seems like a good idea, but there are some hidden costs.

The End-to-End Cost of Meetings: II

Few of us realize where all the costs of meetings really are. Some of the most significant cost sources are outside the meeting room. Here's Part II of our exploration of meeting costs.

How to Waste Time in Virtual Meetings

Nearly everyone hates meetings, and virtual meetings are at the top of most people's lists. Here's a catalog of some of the worst practices.

Stone-Throwers at Meetings: I

One class of disruptions in meetings includes the tactics of stone-throwers — people who exploit low-cost tactics to disrupt the meeting and distract all participants so as to obstruct progress. How do they do it, and what can the meeting chair do?

See also Effective Meetings and Effective Communication at Work for more related articles.

Forthcoming issues of Point Lookout

Coming November 30: Avoiding Speed Bumps: II

Many of the difficulties we encounter when working together don't create long-term harm, but they do cause delays, confusion, and frustration. Here's Part II of a little catalog of tactics for avoiding speed bumps. Available here and by RSS on November 30.

And on December 7: Reaching Agreements in Technological Contexts

Reaching consensus in technological contexts presents special challenges. Problems can arise from interactions between the technological elements of the issue at hand, and the social dynamics of the group addressing that issue. Here are three examples. Available here and by RSS on December 7.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenZLkFdSHmlHvCaSsuner@ChacbnsTPttsdDaRAswloCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info