Meetings have a bad reputation. People complain, but they have to attend, so mostly, they do. Sometimes late, sometimes inattentively, but they do attend. One explanation for this bad reputation is that we just have too many meetings. We could do well with fewer. And one reason why we don't work harder at eliminating or shortening them might be that we don't fully appreciate how expensive they are.
To help fix that, I offer this brief survey of the true costs of meetings, end-to-end. I'm focusing on the cost components that are less-than-obvious, and possibly difficult to quantify with precision. My hope is that the case for fewer, shorter meetings can be strong enough without actual numeric estimates of costs. Let's start with the pre-meeting activities.
- Inviting people
- Someone has to decide who attends. That might involve discussions with responsible parties. These discussions can get complicated occasionally, involving people who can be very busy. Once the invitation list is set, someone has to post invitations in the calendar system, or send email invitations, or whatever. The inviting activity is usually a low-cost task, but if it's delayed by bottlenecks or negotiations about who's available when and for how long, the delay can make scheduling difficult. That's why invitation setting often has a high priority. And when that priority causes delays of other tasks, the costs can mount. Those delay costs are rarely recognized for what they are — a cost of meetings.
- Setting up the facility
- Whether the meeting is face-to-face or virtual, we need a (possibly virtual) place to hold it. Someone has to reserve it. That might require swapping with other contenders for the space, or it might require scheduling the facility so far in When the need to decide the attendance
list takes priority over other work, delaying
that work, those delay costs are rarely
recognized for what they are —
a cost of meetingsadvance that nobody else will be able to claim it. Sometimes the need to schedule in advance causes us to have regularly scheduled meetings even when the primary need we're satisfying is keeping a claim on the facility, rather than the business we transact. That tactic adds to the burden of too many meetings. It's an example of addressing the right problem with the wrong tool, which is rarely a smart way to go. Find another way to lay claim to the facility.
- Getting to and from the meeting
- People who attend in person in a place other than where they work must transport themselves to and fro. Even if the meeting is virtual, attendees at various sites might have to meet in conference rooms for the videoconference or teleconference. People who must travel to attend have an even greater time cost. And people who attend virtual meetings without leaving their own offices might have to set up their connections, log in, and possibly even install software. All of this adds to costs, and it's significant because it affects every attendee.
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 welcomeWould you like to see your comments posted here? rbrenAfaFjaUnsyGzItZiner@ChacoYzHaaUmiopgzSwgoCanyon.comSend me your comments by email, or by Web form.
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.
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.
More articles on Effective Meetings:
- Mastering Meeting Madness
- If you lead an organization, and people are mired in meeting madness, you can end it. Here are a few
tips that can free everyone to finally get some work done.
- TINOs: Teams in Name Only
- Perhaps the most significant difference between face-to-face teams and virtual or distributed teams
is their potential to develop from workgroups into true teams — an area in which virtual or distributed
teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.
- Is the Question "How?" or "Whether?"
- In group decision-making, tension sometimes develops between those who favor commitment to the opportunity
at hand, and those who repeatedly ask, "If we do that, how will we do it?" Why does this happen?
- What Groupthink Isn't
- The term groupthink is tossed around fairly liberally in conversation and on the Web. But it's
astonishing how often it's misused and misunderstood. Here are some examples.
- 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.
Forthcoming issues of Point Lookout
- Coming May 23: Narcissistic Behavior at Work: IX
- An arrogant demeanor is widely viewed as a hallmark of the narcissist. But truly narcissistic arrogance is off the charts. It's something beyond the merely annoying arrogance of a sometimes-obnoxious individual. What is narcissistic arrogance and how can we cope with it? Available here and by RSS on May 23.
- And on May 30: Chronic Peer Interrupters: I
- When making contributions to meeting discussions, we're sometimes interrupted. Often, the interruption is beneficial and saves time. But some people constantly interrupt their peers or near peers, disrespectfully, in a pattern that compromises meeting outcomes. How can we deal with chronic peer interrupters? Available here and by RSS on May 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenpLsoGLvveHPdXxGxner@ChaceCMLeAJRjQlZViduoCanyon.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
- Technical Debt Management: Making the Business Case
- This program
outlines the steps necessary for deploying a program for rational management of technical debt. For
many organizations, adopting a program for rationally managing technical debt entails organizational
change. And unlike some organizational changes, this one touches almost everyone in the organization,
because technical debt isn't merely a technical problem. Technical debt manifests itself in technological
assets, to be sure, but its causes are rarely isolated to the behavior and decisions of engineers. We
can't resolve the problem of chronically excessive levels of technical debt by changing the behavior
of engineers alone. Technical debt is the symptom, not the problem. In this program we outline the essential
elements of an effective business case for adopting a rational technical debt management program. But
this business case, unlike many business cases, cannot be captured in a document. We must make the case
not only at the leadership level of the organization, but also at the level of the individual contributor.
Everyone must understand. Everyone must contribute. We explore five issues that make technical debt
so difficult to manage, and develop five guidelines for designing technical debt management strategies
for the modern enterprise. Read more about
this program. Here's a date for this program:
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield,
Illinois 62701: June 12,
Monthly Meeting, Central
Illinois Chapter of the Project Management Institute. Register now.
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield, Illinois 62701: June 12, Monthly Meeting, Central Illinois Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: The Power of Agile Development
- On 14 December 1911, four men led by Roald
Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen
had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished.
As historical drama, why this happened is interesting enough. Lessons abound. Among the more important
lessons are those that demonstrate the power of the agile approach to project management and product
development. Read more about this program. Here's
a date for this program:
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227:
Monthly Meeting, Cincinnati
chapter of the International Institute of Business Analysis. Register now.
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227: July 17, Monthly Meeting, Cincinnati chapter of the International Institute of Business Analysis. 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.