Saying "no" to someone with superior organizational power can be trying indeed. The unwelcome news doesn't always land easily, and the consequences to a no-sayer's reputation and career can be severe. But we can deliver "no" more effectively, and more safely, if we understand three of the many obstacles to successful delivery of "no."
- Accurate threat assessment
- In unsafe environments, where superiors abuse their power by shaping their subordinates' expressed opinions, the threat to anyone who must deliver "no" is real. Subordinates who assess this threat accurately can experience a sense of intimidation, which can cause them to appear less than confident when delivering their "no."
- Since these no-sayers appear to lack confidence, the recipients of their "n" messages tend to discount what they hear, which can lead some recipients to reject the no-sayer's "no." In this way, the no-sayer's accurate assessment of the threat to the no-sayer can lead to rejection of the "no," even when the no-sayer has mustered the courage to deliver "no."
- Incompetent task difficulty assessment
- Those who lack sufficient competence to recognize impossible task assignments represent another threat to those who would say "no." A typical threat that no-sayers experience, delivered by superiors intent on receiving "yes" instead of "no," is, "If you can't get the job done, I'll find someone who can."
- Superiors who lack competence sufficient to recognize the impossibility of their demands tend also to lack competence sufficient to recognize the incompetence of the people to whom they turn for "yes" when a no-sayer says "no." These powerful people might truly believe that they've found someone who will get the job done, but all they have really found is someone who agrees to take on an impossible task, and who isn't competent to recognize the impossibility of that task.
- Inaccurate message formation
- Superiors who are intent on shaping the expressed opinions of subordinates are more likely than others to withhold from subordinates information about the task at hand and about the environment in which it's hosted. This withholding can result in no-sayers delivering specious arguments as justification for their nos.
- When this happens, recipients A 'No' uttered from deepest conviction
is better and greater than a 'Yes'
merely uttered to please, or what is
worse, to avoid trouble.
—Mohandas Ghandifeel justified in rejecting the no-sayer's position in its entirety, even if the no-sayer's conclusion is valid. Recipients who reason in this way are committing the formal fallacy — an error in logic — known as denying the antecedent. It follows the pattern: (a) If P, then Q; (b) Not P; (c) Therefore, not Q.
Although the recipient rejects the "no" for reasons that aren't logically correct, the recipient might actually recognize the error. Recipients who do so are acting unethically.
Love the work but not the job? Bad boss, long commute, troubling ethical questions, hateful colleague? This ebook looks at what we can do to get more out of life at work. It helps you get moving again! Read Go For It! Sometimes It's Easier If You Run, filled with tips and techniques for putting zing into your work life. Order Now!
Your comments are welcomeWould you like to see your comments posted here? rbrendgbneJjmgDoxbjmNner@ChacaAjtAagkVxMFnUrMoCanyon.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 Workplace Politics:
- Patterns of Everyday Conversation
- Many conversations follow identifiable patterns. Recognizing those patterns, and preparing yourself
to deal with them, can keep you out of trouble and make you more effective and influential.
- Nasty Questions: II
- In meetings, telemeetings, and email we sometimes ask questions that aren't intended to elicit information.
Rather, they're indirect attacks intended to advance the questioner's political agenda. Here's part
two of a catalog of some favorite tactics.
- Managing Pressure: The Unexpected
- When projects falter, we expect demands for status and explanations. What's puzzling is how often this
happens to projects that aren't in trouble. Here's Part II of a catalog of strategies for managing
- How to Stop Being Overworked: II
- Although many of us are overloaded as a result of our own choices, some are overloaded by abusive supervisors.
If you find yourself in that situation, what can you do?
- Failure Foreordained
- Performance Improvement Plans help supervisors guide their subordinates toward improved performance.
But they can also be used to develop documentation to support termination. How can subordinates tell
whether a PIP is a real opportunity to improve?
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 rbrendYuPlQbuJIPpgBruner@ChacjpJPdXApIPcyIANHoCanyon.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.
Beware any resource that speaks of "winning" at workplace politics or "defeating" it. You can benefit or not, but there is no score-keeping, and it isn't a game.