Games for Meetings: II

When we complain that meetings are boring, time-wasting, maddening, or frustrating, it might help to check first about the roles we play ourselves. There are dozens of tactics and ploys, which I've been collecting over the years. Here's the second installment of a little catalog of the more common ones. See "Games for Meetings: I," Point Lookout for February 12, 2003, or "Games for Meetings: III," Point Lookout for March 19, 2003, for more.

PowerGeek

See how good I am at manipulating PowerPoint in arcane, undocumented ways.

Animations, builds, video, audio, and artwork might have legitimate uses, but sometimes we go way too far. When we abuse PowerPoint's abilities, we not only waste our own time, but we also undercut our own messages. If you find yourself doing this sort of thing, ask yourself why you thought it was a good idea. More at "Think Before You PowerPoint," Point Lookout for January 2, 2002.

Techno-Farce

Let's make our networked laptops display the slides so we don't have to look up at the projection screen — or at each other.

For those blessed with the necessary infrastructure, networking audience laptops to display the speaker's slides can be useful, especially for remote audiences. But when a projection screen suffices, use it. The group will stay more connected.

Pretend

You think I'm looking at your slides on my laptop, but I'm actually txting the prsn sttg nx 2 me. [Note]

One of the risks of the networked laptop presentation is that people might find alternative ways to pass the time. As the presenter, be aware of this risk. As a member of the audience, remember that you can be found out.

Not Me

I didn't have anything to do with that horrible disaster.

The old pass-the-buck ploy. If this happens frequently, it could be a sign that you live in a blame-based environment, and that's an unhealthy place to be. Consider moving on. If you're in a position to effect cultural change, start tracking the incidence of this pattern. It's an indicator of the need for an intervention. See "The Blaming Organizational Coping Pattern" for more.

Hot Potato

I don't want to have anything to do with that. Here, you take it.

When we use this ploy, we might gain temporary advantage, but eventually, we'll get caught holding some other potato. Address the issue directly. Try to find a way to share the unpleasant work or at least, the risk.

Serial Status Report

We each report that everything we're responsible for is on track.

A very wasteful pattern. Instead, compile status from everyone in advance of the meeting, and post or distribute the reports to all concerned. Use meetings to discuss issues, rather than to announce status.

See No Evil

Let's all silently agree not to mention the painfully obvious problem(s).

If the problems are threatening enough, any team will fall into this trap. One way to avoid it: designate someone as "Curmudgeon," with responsibility for asking the embarrassing questions. See "Appreciate Differences," Point Lookout for March 14, 2001.

Which of these do you do? Which can you stop doing? What can you do instead? Keep track of what you see in your meetings, and talk about their costs. More coming in future issues — see "Games for Meetings: III," Point Lookout for March 19, 2003. Send me descriptions of your more delightful discoveries.  Top    Next Issue

Do you spendyour 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!

Footnotes

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 Personal, Team, and Organizational Effectiveness:

Take Regular Temperature Readings

Team interactions are unimaginably complex. To avoid misunderstandings, offenses, omissions, and mistaken suppositions, teams need open communications. But no one has a full picture of everything that's happening. The Temperature Reading is a tool for surfacing hidden and invisible information, puzzles, appreciations, frustrations, and feelings.

Abraham, Mark, and Henny

Our plans, products, and processes are often awkward, bulky, and complex. They lack a certain spiritual quality that some might call elegance. Yet we all recognize elegance when we see it. Why do we make things so complicated?

Preventing Sidebars

Sidebar conversations between meeting participants waste time and reduce meeting effectiveness. How can we prevent them?

Contextual Causes of Conflict: I

When destructive conflict erupts, we usually hold responsible only the people directly involved. But the choices of others, and general circumstances, can be the real causes of destructive conflict.

The Utility Pole Anti-Pattern: II

Complex organizational processes can delay action. They can set people against one other and prevent organizations from achieving their objectives. In this Part II of our examination of these complexities, we look into what keeps processes complicated, and how to deal with them.

See also Personal, Team, and Organizational Effectiveness and Effective Meetings for more related articles.

Forthcoming issues of Point Lookout

Coming September 26: Congruent Decision-Making: I

Decision-makers who rely on incomplete or biased information are more likely to make faulty decisions. Congruent decision-making can limit the incidence of bad decisions. Available here and by RSS on September 26.

And on October 3: Congruent Decision-Making: II

Decision-makers who rely on incomplete or biased information are more likely to make decisions that don't fit the reality of their organizations. Here's Part II of a framework for making decisions that fit. Available here and by RSS on October 3.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenUzaxcEveZPrGrZZgner@ChacakwmksVvNLTOotrDoCanyon.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, USD 11.95)
• Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
• Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
• Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)

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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

10 Non-Technical Phenomena That Lead to Technical Debt

When organizations set about gaining control of their accumulated and newly incurring technical debt, a common error of thinking is that the problem can be addressed by modifying their technical processes alone. That can be effective in cases in which the causes of technical debt are found only in the engineering and IT organizations. But those cases are rare. This program surveys ten examples of organizational phenomena that lead to technical debt and which are not restricted to the engineering or IT organizations. Indeed, many of these phenomena cannot be found in the engineering or IT organizations, or if found there, they have relatively small effects on technical debt. For each of the ten phenomena, we describe how it leads to technical debt formation or persistence, and what can be done to mitigate its effects. Most important, we explain how effective control of technical debt requires contributions from a broad array of organizational roles. Read more about this program. Here's a date for this program:

• Wherever you are: it's a teleseminar: September 20, Teleseminar, Computer Aid, Inc. (CAI). Register now.
   

The Power Affect: How We Express Our Personal Power

Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.

• A recording of a program presented 6:00 PM June 29 (Eastern Time), Monthly Webinar, Technobility Webinar Series. You can earn 1.0 Category 'A' PDU by viewing this program. View this program now.