Organizational culture is the set of attitudes, values, norms, and beliefs widely held by members of the organization. The elements of culture need not be self-consistent, but they affect the organization's goals, strategies, and structure, and its approaches to setting and achieving its objectives. The people of the organization need not be aware of every cultural element, nor is their behavior always consistent with the culture.
Culture can contribute to troubles in meetings. For example, if harmony is highly valued, people try to please — and avoid displeasing — each other. These tendencies can elevate the chances of taking a Trip to Abilene, which happens when everyone in a group agrees to a proposal that nobody actually wants, because they all believe that everyone else favors it.
Here are three examples of meeting troubles that have cultural causes.
- Insufficient facilities
- Organizations can sometimes be shortsighted about cost control. They invest too little in meeting facilities, especially those for virtual teams, which have expensive requirements. Scarcity of adequate facilities causes teams to claim time slots in advance of known needs. Once they claim a time slot, they feel obliged to meet, and to use the entire slot. This sense of pressure to meet can lead to a waste of everyone's time. If teams cannot secure the facilities they need, they meet in settings unsuited to the task — for example, an audio-only virtual workspace to conduct discussions that actually need an electronic whiteboard. When such mismatches occur, groups tend not to account for the shortcomings of the meeting setting. Meetings run overtime and output quality suffers.
- Reducing facilities Cultures that value teamwork
sometimes confuse working
together with getting togetherexpense is often the most expensive strategy, if we account for the cost of the resulting delays and bad decisions.
- Serial submeetings
- Cultures that value teamwork sometimes confuse working together with getting together. Often, a team meets as one, when meeting as subteams would be more effective. One indicator of this pattern is a meeting consisting of serial submeetings — a sequence of discussions in which few people are involved or qualified to contribute. Each subteam takes its turn, while everyone else looks on.
- For increased effectiveness, the team could have the subteams meet in parallel or at times they choose, reporting afterwards to the whole any issues or surprises. This creates free time for the team to assemble to address shared issues, or to connect socially.
- Ritualized standups
- Standup meetings are increasingly popular, especially in organizations that value Agile processes. Standups are supposedly shorter because of the discomfort of standing. But they don't help at all unless the content of the meeting is suited to that form, which works best for quick check-ins, for a total of at most 15 minutes.
- Extended discussion of complex issues still requires chairs, a table, and maybe other equipment — like a notepad or a laptop and projector. Use a standup only when it fits the agenda.
You've probably seen other examples of cultural causes of meeting troubles. Send them along and I'll include them in a future installment of this growing collection. First 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 welcomeWould you like to see your comments posted here? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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:
- Problem Defining and Problem Solving
- Sometimes problem-solving sessions are difficult because we get started solving a problem before we
know what problem we're solving. Understanding the connection between stakeholders, problem solving,
and problem defining can reduce conflict and produce better solutions.
- Asking Brilliant Questions
- Your team is fortunate if you have even one teammate who regularly asks the questions that immediately
halt discussions and save months of wasted effort. But even if you don't have someone like that, everyone
can learn how to generate brilliant questions more often. Here's how.
- Towards More Gracious Disagreement
- We spend a sizable chunk of time correcting each other. Some believe that we win points by being right,
or lose points by being wrong, but nobody seems to know who keeps the official score. Here are some
thoughts to help you kick the habit.
- How to Hijack Meetings
- Recognizing the tactics meeting hijackers use is the first step to reducing the incidence of this abuse.
Here are some of those tactics.
- A Pain Scale for Meetings
- Most meetings could be shorter, less frequent, and more productive than they are. Part of the problem
is that we don't realize how much we do to get in our own way. If we track the incidents of dysfunctional
activity, we can use the data to spot trends and take corrective action.
Forthcoming issues of Point Lookout
- Coming September 25: Planning Disappointments
- When we plan projects, we make estimates of total costs and expected delivery dates. Often these estimates are so wrong — in the wrong direction — that we might as well be planning disappointments. Why is this? Available here and by RSS on September 25.
- And on October 2: Start Anywhere
- Group problem-solving sessions sometimes focus on where to begin, even when what we know about the problem is insufficient for making such decisions. In some cases, preliminary exploration of almost any aspect of the problem can be more helpful than debating what to explore. Available here and by RSS on October 2.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: Lessons in Leadership
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. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.
Here's a date for this program:
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio
44017: November 7,
Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute.
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute. 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.