On Working Breaks in Meetings

An oft-repeated refrain in meetings is "Let's take a ten-minute break." The number of minutes varies, as does the reason for taking a break. The most common reason I've found for taking a break is suppressing toxic conflict. When the discussion gets heated enough, taking a break can seem like the only way to avoid even higher temperatures, and sometimes it actually works.

A less-often seen reason for taking a break is the need to think — a form of break I call a "working break." A working break is a useful choice when, for example, the meeting participants are working a problem, and a complicated but intriguing proposal has hit a snag. If several ideas seem to be capable of unsnagging the proposal, taking a working break can provide some quiet time to sort through those ideas to produce a workable solution.

Guidelines for working breaks

Because A working break is a useful choice when,
for example, the meeting participants
are working a problem, and a complicated
but intriguing proposal has hit a snagthe structure of a working break can affect its outcome, it's helpful to agree in advance how to use working breaks before you actually try one. Here are some tips for making working breaks productive.

Identify a small group of specialists

If the meeting as a whole (the "whole") hasn't resolved the issue, part of the problem might be that there are too many voices trying to help. Reducing the contributors to those who have special knowledge — a smaller group of specialists — might be the key to resolving the issue. To use this approach, consider conducting the specialist discussion privately, and then reporting results to the whole when the meeting reconvenes.

Give the specialists a flexible time limit

A time limit is useful for enabling those not selected as specialists to relax, or work on another task. A time limit also directs the specialists in selecting their path to a resolution. If they can't resolve the issue in the time allotted, they can report this to the whole to enable the meeting participants to extend the time or adjust the roster of specialists, or try a different approach.

Consider partial resolution a success

A partial resolution can be a partial success that leads to a complete resolution. When the specialists report back to the whole what they've been able to do, others in the meeting might then be able to see what the next steps might be. That clarity of vision might have been unavailable before.

Exploit parallelism if possible

In some cases, several snags might be preventing progress on the matter at hand. Dealing with them serially might work, but when the serial approach fails, consider parallelism, because the path around one snag might not be visible until the path around another is clear. And two snags might conspire to prevent resolution of either one. Clearing both snags might happen more quickly if two teams of specialists work in parallel.

Last words

When working breaks facilitate forward progress, they can prevent eruptions of toxic conflict. But they risk creating toxic conflict and personal competition by delegating problem resolution to small teams of specialists. When this delegation amounts to a reassignment of responsibility, the original bearers of that responsibility can experience a sense of rejection or being criticized. To mitigate this risk, include the original bearers of the responsibility in the specialist teams in a way that honors their contributions while recognizing the benefits of "fresh eyes."  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.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

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:

Decisions, Decisions: I

Most of us have participated in group decision making. The process can be frustrating and painful, but it can also be thrilling. What processes do groups use to make decisions? How do we choose the right process for the job?

Remote Facilitation in Synchronous Contexts: I

Whoever facilitates your distributed meetings — whether a dedicated facilitator or the meeting chair — will discover quickly that remote facilitation presents special problems. Here's a little catalog of those problems, and some suggestions for addressing them.

Twelve Tips for More Masterful Virtual Presentations: I

Virtual presentations are like face-to-face presentations, in that one (or a few) people present a program to an audience. But the similarity ends there. In the virtual environment, we have to adapt if we want to deliver a message effectively. We must learn to be captivating.

How to Waste Time in Meetings

Nearly everyone hates meetings. The main complaint: they're mostly a waste of time. The main cause: us. Here's a field manual for people who want to waste even more time.

The Major Annoyance of Mini-Digressions

Digressions are expensive. They limit progress in meetings. They're most noticeable when they deflect the entire meeting from its stated purpose. There is another kind of digression that's less noticeable, more common, and just as costly.

See also Effective Meetings and Problem Solving and Creativity for more related articles.

Forthcoming issues of Point Lookout

Coming May 8: Antipatterns for Time-Constrained Communication: 3

Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 3 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing past experiences of participants. Available here and by RSS on May 8.

And on May 15: Should I Write or Should I Call?

After we recognize the need to contact a colleague or colleagues to work out a way to move forward, we next must decide how to make contact. Phone? Videoconference? Text message? There are some simple criteria that can help with such decisions. Available here and by RSS on May 15.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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