The Nominal Fallacy at Work
by Rick Brenner
Using logical fallacies at work — intentionally or otherwise — costs real money. The nominal fallacy is probably responsible for much delay in addressing our real problems.
A view of the South Canyon Fire near Glenwood Springs, Colorado, at noon on July 4, 1994, when the fire covered only three acres. Lightning had ignited the fire on July 2. The fire would eventually claim 2117 acres. Tragically, on July 6, 1994, it claimed the lives of 14 wildland firefighters, as detailed in the Report of the South Canyon Fire Accident Investigation Team. Controversy about this incident, and others involving death and injury of wildland firefighters, persists. Among the factors cited is the framework known as the "10 Standard Firefighting Orders," eight of which were cited in the report as having been compromised.
Ted Putnam, a retired firefighter and firefighting leadership trainer, argues that these deaths, and other deaths and injuries, can be traced to the Standard Orders, and other practices of wildland firefighters. He asserts that the Standard Orders cannot actually be followed, and that they are designed to protect firefighting management, perhaps more than the firefighters themselves. He writes, "Notice that by identifying something, management is now off the hook." If Mr. Putnam is correct, he has identified a use of the Nominal Fallacy.
The Nominal Fallacy is usually an honest mistake. Except when it isn't. Photo courtesy of the U.S. Willdland Fire Leadership Development Program.
We're committing the logical error called the nominal fallacy when we believe that because we've given something a name, we've explained it. An example: "He doesn't get along with his teammates because he's difficult." Labeling him "difficult" doesn't explain the troubled relationships in the team. It leaves many questions unanswered. Why is he difficult? How is difficult defined? Is he the only team member who's difficult? Are all people who don't get along with their teammates difficult? Can there be other reasons for troubled relationships in this team?
We can extend the nominal fallacy concept slightly to an Attributes Fallacy, which is the logical error of believing that we've explained an entity — or elaborated an existing explanation — when we merely list some of the entity's attributes. If an entity's name is one of its attributes, then the Nominal Fallacy is a special case of the Attributes Fallacy.
For example, when we categorize defects in a software product as change-request, performance-severe, unclassified, and so on, we aren't resolving the defects. We're classifying them. Each defect had a name, and now we've given it a classification. Name and classification are two of its attributes.
Naming and classifying can be satisfying. They might even be steps necessary for achieving our goals. But in most cases in the workplace, naming or classifying isn't the goal. When we enjoy naming and classifying so much that our enjoyment interferes with actual goal achievement, we're in trouble.
This trouble can appear anywhere. When we design project plans, we name tasks. I've done it myself. It's fun. But naming tasks doesn't bring the project home. It's a necessary step toward the goal, but it's just a step.
Consider When we enjoy naming and
classifying so much that
our enjoyment interferes
with actual goal achievement,
we're in troublethe annual budget for your organization. Somebody decides how much to spend on each major organizational element. When they do, they're assigning a value to each organizational element's "budget" attribute. But that isn't the end of the budget process. Budgets must be monitored. When they prove to be too low, or too high, interventions are required. That's hard work. Setting the budget is just the beginning. The same can be said for schedules and strategies.
What's so seductive about naming things, or setting the values of their attributes, or even merely understanding the naming work someone else has done, is that when we do it, we do experience a disproportionate sense of getting something done, however illusory that sense might be. My hope is that your having read this little essay will help you recognize that sense of satisfaction as the joy that comes — in part — from the Nominal Fallacy.
Now, you might ask, how does all this help me? Why does the Nominal Fallacy work the way it does? Haven't I merely named it? Is the Nominal Fallacy an example of itself? Hmmm. Top Next Issue
More about logical fallacies
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. Order Now!
Your comments are welcome
Would you like to see your comments posted here? Send 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
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.
More articles on Rhetorical Fallacies
- 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?
- The Fallacy of Composition
- Rhetorical fallacies are errors of reasoning that introduce flaws in the logic of arguments. Used either intentionally or by accident, they often lead us to mistaken conclusions. The Fallacy of Composition is one of the more subtle fallacies, which makes it especially dangerous.
- The Reification Error and Performance Management
- Just as real concrete objects have attributes, so do abstract concepts, or constructs. But attempting to measure the attributes of constructs as if they were the attributes of real objects is an example of the reification error. In performance management, committing this error leads to unexpected and unwanted results.
- The Halo Effect
- The Halo Effect is a cognitive bias that causes our evaluation of people, concepts, or objects to be influenced by our perceptions of one attribute of those people, concepts, or objects. It can lead us to make significant errors of judgment.
- Workplace Politics and Integrity
- Some see workplace politics and integrity as inherently opposed. One can participate in politics, or one can have integrity — not both. This belief is a dangerous delusion.
See also Rhetorical Fallacies and Critical Thinking for more related articles.
I offer email and telephone coaching at both corporate and individual rates.
Contact me for details at rbrenner@ChacoCanyon.com
or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout
are available in six ebooks:
Reprinting this article
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
- Person-to-Person Communication for Project Managers
- When we talk, listen, send or read emails, read or write memos, or when we leave or listen to voice mail messages, we're communicating person-to-person. And whenever we communicate person-to-person, we risk being misunderstood, offending others, feeling hurt, and being confused. There are so many ways for things to go wrong that we could never learn how to fix all the problems. A more effective approach avoids problems altogether, or at least minimizes their occurrence. In this very interactive program you'll learn a model of inter-personal communications that can help you stay out of the ditch. In those moments of intense involvement, when we're most likely to slip, you'll have a new tool to use to keep things constructive. Read more about this program. Here's an upcoming date for this program:
- The Race to the South Pole: Ten Lessons for Project Managers
- 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 project managers, the story is fascinating. Lessons abound. Read more about this program. Here are some upcoming dates for this program:
- Download to
your calendarHoliday Inn Mt. Kisco, One Holiday Inn Drive, Mt. Kisco, NY 10549: April 5, Professional Development Day, Westchester Chapter of the Project Management Institute. Register now.
- Download to
your calendarPortland Country Club, 11 Foreside Road, Falmouth, ME 04105: June 19, Monthly Meeting, Maine Chapter of the Project Management Institute. Register now.
- Managing Virtual Meetings for Real Results
- Leading or participating in virtual meetings — teleconferences, Web conferences, video conferences, and more — is challenging. Miscommunications, misunderstandings, distractions, politics, and interpersonal conflict all thrive in the typical environment of the virtual team. We'll inventory the challenges virtual meeting leaders and participants face, and provide tools for anticipating and addressing them. The focus of this program is practical — attendees will learn concrete techniques for preventing and dealing with the problems that arise in virtual meetings. Read more about this program. Here's an upcoming date for this program:
- Organizational Politics for People Who Hate Politics
- Have you ever felt powerless to implement an important new idea? Have you ever been "blind-sided" at a meeting? Have you ever lost two good employees because you could find no way to keep them from attacking each other? These are some of the issues of organizational politics. Many of us have become enmeshed in them from time to time, but we've also known some people who seem to be able to engage and prosper. How is that done? We'll inventory the challenges of organizational politics, and provide tools for anticipating and addressing them. The focus of this program is practical — attendees learn concrete techniques for dealing with the problems that arise in workplace politics, while keeping their integrity intact. Read more about this program. Here's an upcoming date for this program:
- The Race to the South Pole: Lessons in Risk Management for Leaders
- 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 and project managers, the story is fascinating. We'll use the history of this event to explore lessons in risk management and its application to organizational efforts. A fascinating and refreshing look at risk management from the vantage point of history. Read more about this program. Here are some upcoming dates for this program:
- New York Marriott Downtown, 85 West Street at Albany Street, New York, NY 10006: May 22, Breakfast Seminar, IT Metrics and Productivity Institute Conference Series. Register now.
- Toronto Marriott Downtown Eaton Centre Hotel, 525 Bay Street, Toronto, Ontario, Canada M5G2L2: June 5, Breakfast Seminar, IT Metrics and Productivity Institute Conference Series.
- Boston Marriott Newton, 2345 Commonwealth Avenue, Newton, MA 02466: June 26, Breakfast Seminar, IT Metrics and Productivity Institute Conference Series.