The waiter arrived with the cold drinks and started dealing them out. That usually meant that the sandwiches were close behind. The great service was one reason they all liked Mike's.
"Good question," said Kevin, pulling a pen from his pocket. "Napkin, James." James was closest to the napkin dispenser.
So he obliged. "Ah, the old back-of-the-napkin trick," said James. "Can't do it in your head, eh Kev?"
Marian loved watching these two go at each other. They were having fun.
Kevin was thinking, pen poised. "Marian, tell us one more time," he said.
"OK," she said. "64 teams in the tournament. Single elimination. How many games total will they play?"
Kevin thought there was a trick. "So, 32 games in the first round, 16 in the second…like that?"
Before Marian could answer, James solved the riddle. "63 total games," he said, smiling at Kevin. "Next question."
Stung, Kevin looked at James. "How'd you do that?"
James was in his glory. "Easy. Single elimination. Everybody but the winner has to lose once." He smiled again.
Sometimes, especially in meetings, we ask questions for which we don't really need the answers. Like Kevin, we believe we need the answers, but we're mistaken. And sometimes we ask questions for reasons that are even less straightforward.
- We're hoping to catch somebody "not knowing" or better yet, being wrong.
- Sometimes we ask questions
when we don't really need
- We want to keep everyone occupied while we think things through, or until word on an important issue arrives by instant message.
- We realize that spending time on other issues leaves less time for the group to focus on us.
- Piling on
- We're hoping that the volume of questions about someone's task will create an impression that success is in doubt.
- Astuteness proof
- We believe that very few will understand the question we're asking, which will demonstrate yet again that we're so clever that we ought to be in charge of the galaxy. Or at least this team.
Even when the questioner's motives are pure, we can sometimes experience questions as attacks. When we do, we can become fearful or defensive, and the conversation can take a wrong turn.
There is a better way.
Instead of asking others for information, give information about your own internal state. If you're truly confused or ignorant about something, say so. Tell the group, "I don't understand that." Or, "It seems to me that X conflicts with Y."
If the group can clarify things for you, they will. If not, most will turn to the person who's responsible for the item, and then it will be clear that your muddle isn't just your own muddle.
When we replace questions with statements of personal ignorance or confusion, there are many fewer questions, many fewer statements of ignorance, and meetings go faster. Seems obvious to me. Or maybe I just don't understand why we ask each other so many questions. 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? rbrenyylrNLLyMPKlkrlJner@ChacZMDJmyNEsLqGBEIwoCanyon.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 Communication at Work:
- Begging the Question
- Begging the question is a common, usually undetected, rhetorical fallacy. It leads to unsupported conclusions
and painful places we just can't live with. What can we do when it happens?
- An Agenda for Agendas
- Most of us believe that the foundation of a well-run meeting is a well-formed agenda. What makes a "well-formed"
agenda? How can we write and manage agendas to make meetings successful?
- When You Aren't Supposed to Say: III
- Most of us have information that's "company confidential," or even more sensitive than that.
Sometimes people who want to know what we know try to suspend our ability to think critically. Here
are some of their techniques.
- Achieving Goals: Inspiring Passion and Action
- Achieving your goals requires both passion and action. Knowing when to emphasize passion and when to
emphasize action are the keys to managing yourself, or others, toward achievement.
- Bemused Detachment
- Much of the difficulty between people at work is avoidable if only we can find ways to slow down our
responses to each other. When we hurry, we react without thinking. Here's a suggestion for increasing
comity by slowing down.
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 rbreniRFFlzSunbknHzTuner@ChacwUqnmWEPXFRXaqAjoCanyon.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.