![A dead Manchurian Ash A dead Manchurian Ash](../images/manchurian-ash.png)
A dead Manchurian Ash (probably Fraxinus mandschurica). Note that its trunk is far from straight. This condition is called sinuosity. It is thought to result from the tree's attempts to reach for light as openings appear in the forest canopy. (See Charismatic Megaflora: What do Old Trees Look Like? by Neil Pederson) As one canopy opening is filled by foliage of taller trees, and new openings appear, the ash has had to "change course" several times. If we regard the tree as being a problem solver, with the search for light being the problem it's solving, it seems to have led a life in which the solutions it finds repeatedly (and rather suddenly) become invalid. Consequently, it has had to search for new solutions to the new problem, and this has led to sinuosity.
This tree's experience suggests that for us as humans, Type III errors — that is, correct solutions to wrong problems — can arise suddenly out of correct solutions to correct problems. We might be engaged in solving a correct problem correctly, and suddenly, without warning, the problem's "validity" vanishes. If we persist in solving that problem then we would be committing a Type III error, even though we weren't when we began the effort. In this way, we can commit a Type III error by addressing technically a problem that at the outset was fundamentally technical, but which becomes political as the technical solution develops. Photo courtesy Neil Pederson.
Statisticians identified Type I and Type II errors almost 70 years ago. In brief (possibly too brief), a Type I error is a false positive and a Type II error is a false negative. These mistakes can be costly indeed, but they are topics for other days.
The concept of Type III errors is based on a generalization of these first two. The approach I favor is that of Raiffa (see below), who identified Type III errors as those in which one solves the wrong problem correctly. This definition has wide applicability in the realm of workplace politics.
Consider an example. In my workshops I sometimes pose problems like this:
You're in charge of a large, innovative effort for your company, MegaBlunder. Similar but smaller and less complex efforts at MegaBlunder have used SupplierA with satisfactory but not stunningly successful results. Unfortunately, because of the size, complexity, and novelty of your effort, SupplierA cannot meet all your needs. SupplierB can, but because of a bad experience with SupplierB some years ago, there is a "soft" ban of SupplierB, and using them is deprecated. You believe on strong evidence that SupplerB's past is now behind it, but there's some political risk involved in selecting SupplierB. A review of your effort is scheduled for next week. What do you do?
Although this example is expressed in terms of supplier choice, other forms include choices of technologies, locations, markets, and people. We'll stay with the supplier example for concreteness.
Most people address such problems by devising strong defenses of their positions. They gather glowing references from customers of SupplierB, carefully researched evidence of the shortcomings of SupplierA's offerings, and evidence of the strength of SupplierB's offerings. They perform risk analyses of the two alternatives. PowerPoint slides galore. Sometimes it works.
And sometimes not.
Troubles with We are committing a
Type III error when
we correctly solve
the wrong problemcontent-based approaches arise when these approaches comprise Type III errors. When the real problem is political, rather than one of supplier capability, these approaches are correct solutions to the wrong problem.
In our example, suppose that the basis of the ban on SupplierB was actually the damaged relationship between SupplierB's former CEO and MegaBlunder's former CEO. The excuse might have been a pattern of late deliveries, but trust was the real issue. Both CEOs have long since moved on, but the ban remained. A more suitable approach might involve consulting your network to gain a deeper understanding of the issue, and then, possibly with help from others on the executive team, working to remove the ban.
In other words, use politics to solve political problems. Use technology to solve technical problems. Don't use technology to solve political problems, or politics to solve technical problems. Avoid committing Type III errors. Top
Next Issue
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
Two useful sources:
Howard Raiffa. Decision Analysis: Introductory Lectures on Choices Under Uncertainty. New York: Mcgraw-Hill College, 1968. Order from Amazon.com
Ian I. Mitroff and Abraham Silvers. Dirty Rotten Strategies: How We Trick Ourselves and Others into Solving the Wrong Problems Precisely. Stanford, CA: Stanford University Press, 2010. Order from Amazon.com
aaa Order from Amazon.com BBB
Your comments are welcome
Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.
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.
Related articles
More articles on Workplace Politics:
How to Tell If You Work for a Nanomanager
- By now, we've all heard of micromanagers, and some have experienced micromanagement firsthand. Some
of us have even micromanaged others. But there's a breed of micromanagers whose behavior is so outlandish
that they need a category of their own.
Political Framing: Communications
- In organizational politics, one class of toxic tactics is framing — accusing a group or individual
by offering interpretations of their actions to knowingly and falsely make them seem responsible for
reprehensible or negligent acts. Here are some communications tactics framers use.
Pariah Professions: I
- In some organizations entire professions are held in low regard. Their members become pariahs to some
people in the rest of the organization. When these conditions prevail, organizational performance suffers.
Meets Expectations
- Many performance management systems include ratings such as "meets expectations," "exceeds
expectations," and "needs improvement." Many find the "meets" rating demoralizing.
Why?
I Don't Understand: I
- When someone makes a statement or offers an explanation that's unclear or ambiguous, there are risks
associated with asking for clarification. The risks can seem so terrifying that we decide not to ask.
What keeps us from seeking clarification?
See also Workplace Politics and Problem Solving and Creativity for more related articles.
Forthcoming issues of Point Lookout
Coming July 3: Additive bias…or Not: II
- Additive bias is a cognitive bias that many believe contributes to bloat of commercial products. When we change products to make them more capable, additive bias might not play a role, because economic considerations sometimes favor additive approaches. Available here and by RSS on July 3.
And on July 10: On Delegating Accountability: I
- As the saying goes, "You can't delegate your own accountability." Despite wide knowledge of this aphorism, people try it from time to time, especially when overcome by the temptation of a high-risk decision. What can you delegate, and how can you do it? Available here and by RSS on July 10.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick
![Send email or subscribe to one of my newsletters](../images/social-icons/email-32.png)
![Follow me at LinkedIn](../images/social-icons/linkedin-reg-32.png)
![Follow me at X, or share a post](../images/social-icons/x-32.png)
![Subscribe to RSS feeds](../images/social-icons/feed-icon-32.png)
![Subscribe to RSS feeds](../images/social-icons/facebook-icon-32.png)
Recommend this issue to a friend
Send an email message to a friend
rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
![Please donate!](../images/donate-icon.png)
![Technical Debt for Policymakers Blog](../images/logos/techdebtpolicy-logo-sm-1.png)
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.
- Wikipedia has a nice article with a list of additional resources
- Some public libraries offer collections. Here's an example from Saskatoon.
- Check my own links collection
- LinkedIn's Office Politics discussion group