In this video clip, Director of the Office of Management and Budget Sylvia Burwell is testifying before the Senate Committee on the Budget. She is being questioned by Senator Jeff Sessions (R-Alabama) about the proposed spending for the implementation of the Affordable Care Act, at levels above those previously enacted. Those increases are offset by savings elsewhere, called "pay-fors" in Washington argot. Although this is common practice, Sen. Sessions isn't interested in that explanation. He wants the witness to say simply that the administration is proposing additional spending, without mentioning the pay-fors. That would enable him to claim that the administration is raising spending, contrary to the facts in evidence. Director Burwell uses a variety of techniques to avoid such a statement, probably because she is aware that the video of such a statement could be used by partisan news outlets, out of context, as proof that the administration is burdening taxpayers. The stakes are high. Perhaps that's why the Senator repeatedly pursues the Director, with apparent hostility and growing irritation, even employing condescension and, some would say, sexist remarks to fluster the witness.
Rarely are such tactics used so blatantly in business meetings. But Director Burwell here provides a model of aplomb, and many examples of circumventing demands for "a simple yes or no." Video excerpt by C-SPAN hosted by YouTube. View her entire testimony at C-SPAN.org.
You're in a meeting. Because you have special expertise, your role is consultative. The agenda includes an important decision about releasing a product that has some unfortunate defects. Some favor release (call them Fs), and some oppose release (call them Os). You know that your opinion will be helpful to the Os, and unhelpful to the Fs.
One of the Fs asks, "In your modeling studies, didn't you find that revenue during the first six quarters would far exceed the cost of product liability litigation?"
You begin to reply, "Well, in the first six quarters following release, …"
The questioner interrupts you. "That was a yes-or-no question."
Now, the truth is that in the first six quarters following release, your models do project revenue far greater than the cost of litigation, but you don't want to answer "Yes." Time delays between actual sales and the filing of lawsuits cause litigation costs to lag sales significantly. Another factor introducing still more lag is that consumer injury incidents happen only after the product is used for a time. Moreover, the news of the lawsuits can, over time, affect revenue for the company's other products, even though they're defect-free. And then there are the inevitable product recalls. All told, over the first five years after release, your models project severe financial difficulties for the company.
But you can't figure out how to fit all that into a yes-or-no response, especially when the right answer to the question as asked is "yes," which would be extremely misleading.
This is just an example. What can you do when someone uses the yes-or-no trap?
- Recognize the effects of restricting the response
- Restricting the response almost inevitably limits your ability to convey a true impression of the situation. Distorting your response is often the intent of the questioner, but other intentions are also possible. For example, the questioner might be relatively ignorant of the finer points of the issue, and might be reluctant to have that ignorance revealed.
- In any case, Because restricting your answers to
"Yes" or "No" generally degrades the
quality of your response, acting to
evade the restriction is usually
helpful to the organizationbecause requiring a yes-or-no response generally degrades the quality of the response, acting to evade the restriction is usually helpful to the organization.
- Call it
- One way to respond to the yes-or-no trap, before the questioner insists explicitly on a yes-or-no response, is to acknowledge the trap, and then decline politely to step into it. For example, "I understand that you want a yes or a no answer, and I could provide one, but it would be misleading to do so, and I'm sure you don't want that." Then pause.
- Few questioners would then say, "Go ahead and mislead me." When you get the "please continue," you can provide a more complete response.
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info
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 Communication at Work:
- Dangerous Phrases
- I recently upgraded my email program to a new version that "monitors messages for offensive text."
It hasn't worked out well. But the whole affair got me to think about everyday phrases that do tend
to set people off. Here's a little catalog.
- Virtual Communications: I
- Participating in or managing a virtual team presents special communications challenges. Here are some
guidelines for communicating with members of virtual teams.
- 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.
- On Facilitation Suggestions from Meeting Participants
- Team leaders often facilitate their own meetings, and although there are problems associated with that
dual role, it's so familiar that it works well enough, most of the time. Less widely understood are
the problems that arise when other meeting participants make facilitation suggestions.
- Some Truths About Lies: IV
- Extended interviews provide multiple opportunities for detecting lies by people intent on deception.
Here's Part IV of our little collection of lie detection techniques.
Forthcoming issues of Point Lookout
- Coming September 18: The Planning Fallacy and Self-Interest
- A well-known cognitive bias, the planning fallacy, accounts for many unrealistic estimates of project cost and schedule. Overruns are common. But another cognitive bias, and organizational politics, combine with the planning fallacy to make a bad situation even worse. Available here and by RSS on September 18.
- And on 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.
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.