Issues-Only Team Meetings

In addition to administrative tasks such as agenda setting, most team meetings cover a mix of information distribution, status reporting, issue reporting, issue clarification, and problem solving. But meetings are so expensive and difficult to schedule — and as many say, so painful — that shortening them or making them less frequent is a real benefit. One approach to shortening regular team meetings is to move to broadcast media such as email or podcasts any meeting content that doesn't actually require real-time interaction. That would include most information distribution and status reporting. So let's set them aside.

Solving problems of any significant difficulty is probably best approached not in regular team meetings, but in meetings dedicated to solving those problems. There we can ensure we have the time, information, and people we need to evaluate progress on working the problem, to develop new candidate solutions, and to set task assignments for further investigations. So let's set problem solving aside as well.

What remains for regular team meetings, for the most part, is issue reporting and issue clarification. If we spend our time in team meetings focusing on uncovering issues and clarifying them to the extent we can with what we now know, we can shorten meetings and get back to work. This is especially useful for standup meetings, which are intended to be short.

Unfortunately, achieving this objective is rarely straightforward. Pitfalls abound. With that in mind, I offer a set of guidelines for avoiding the pitfalls of issues-only team meetings.

Preparation is even more necessary

Compared to the Compared to the way most regular
team meetings are conducted, the
effectiveness of issues-only team
meetings is more dependent on
diligent preparation by team membersway most regular team meetings are conducted, the effectiveness of issues-only team meetings is more dependent on diligent preparation by team members. Team members must have a current understanding of the material that has been shifted to other channels, including the information and status reports that were moved to podcasts or email. And the larger team is relying on the problem-solving subteams for timely and lucid reports if they encounter new issues.

Circulate an "open issues" summary in advance

Raising an issue that has already been raised is a waste of time, but a brief discussion might be necessary if its status has changed in a material way that might affect anyone beyond the team members who are pursuing the issue. Team members must receive and digest these summaries in advance of the issues-only team meeting.

Classify issues using the Politics by Subject Matter matrix

The Politics by Subject Matter matrix is a 2x2 matrix for classifying issues. [Lowy 2004] Its vertical axis corresponds to increasing importance of the political content of an issue: Low to High. Its horizontal axis corresponds to increasing importance of the subject matter content of an issue: Low to High. Political content relates to resource allocation and availability, or to organizational support for (or opposition to) activity related to the issue — essentially, whether or when we attend to the issue. Subject matter content relates to the methods for attending to the issue — essentially, how we resolve the issue.

As shown in the diagram, the cells of the matrix are Routine Administrative Issues [Low Political, Low Subject Matter], Resource Allocation Issues [High Political, Low Subject Matter], Primarily Technical Issues [Low Political, High Subject Matter], and Strategic Issues [High Political, High Subject Matter].

Begin the process of issue clarification by classifying new issues according to this matrix. After this conversation, determine whether the issue is one that the team has authority, capability, and capacity to resolve. If the issue is within the team's authority, capability, and capacity, assign a task team to deal with it. If the issue is beyond the team's authority, capability, or capacity, bring the issue to the attention of people who can attend to it, and move on.

Avoid trying to resolve issues in regular team meetings

A common anti-pattern in team meetings is premature problem solving. We waste much time solving problems and addressing issues before we have enough information and awareness to ensure that the solutions we find will be workable — or even relevant. (See "The Solving Lamp Is Lit," Point Lookout for September 6, 2006.) Issues-only meetings are for surfacing or clarifying issues, not for resolving them.

Some have expressed concern that issues-only meetings might be very difficult and tense. There is a risk that these meetings can become blamefests, especially if all or most of the issues seem to point in the direction of a few team members. One way to manage this risk is to adjust the culture of the team. Ensure that the team culture includes an understanding that although we might divide our work into tasks to be pursued by specific people, the tasks are all interconnected. An issue that surfaces in the context of one task isn't necessarily a result of malpractice by anyone — including the people responsible for that task. Any issue can have its source in multiple other tasks, or even in work that's beyond the responsibility of the team as a whole. Discovering an issue is most likely a gift — a contribution to the work of the team, rather than a hindrance to achieving success.  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!

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.

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:

Dispersity Adversity

Geographically and culturally dispersed project teams are increasingly common, as we become more travel-averse and more bedazzled by communication technology. But people really do work better together face-to-face. Here are some tips for managing dispersed teams.

Figuring Out What to Do First

Whether we belong to a small project team or to an executive team, we have limited resources and seemingly unlimited problems to deal with. How do we decide which problems are important? How do we decide where to focus our attention first?

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.

Workplace Politics and Social Exclusion: I

In the workplace, social exclusion is the practice of systematically excluding someone from activities in which they would otherwise be invited to participate. When used in workplace politics, it's ruinous for the person excluded, and expensive to the organization.

Pre-Decision Discussions: Reasoning

When we meet to resolve issues related to upcoming decisions, we sometimes rely on reasoning to help find solutions. Contributions to these discussions generally use mixtures of deductive, inductive, and abductive reasoning. How do they differ, and what are their strengths and risks?

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

Forthcoming issues of Point Lookout

Coming April 24: Antipatterns for Time-Constrained Communication: 1

Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.

And on May 1: Antipatterns for Time-Constrained Communication: 2

Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 2 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.

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