Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 23, Issue 14;   April 5, 2023: The Fallacy of Division

The Fallacy of Division

by

Errors of reasoning are pervasive in everyday thought in most organizations. One of the more common errors is called the Fallacy of Division, in which we assume that attributes of a class apply to all members of that class. It leads to ridiculous results.
Bust of Aristotle. Marble. Roman copy after a Greek bronze original

Bust of Aristotle. Marble. Roman copy after a Greek bronze original by Lysippos from 330 BCE. The alabaster mantle is a modern addition. Aristotle identified the fallacy of reasoning known as the "Fallacy of Division" (and 12 others) in his work, Sophistical Refutations. [Aristotle 350 BCE] Image courtesy Wikimedia.

The fallacy of division is an error of reasoning. It occurs when we conclude that entity A, which is a member of class B, must have attribute C solely because class B has attribute C. For example, "Last year, our IT project budget overran the plan by 13%. All of our access management projects are IT projects. Therefore all of our access management projects overran the plan by 13%." Most of us can easily identify this fallacy when it's applied in such an artificial example.

Examples of the Fallacy of Division

In real life, the fallacy of division can be difficult to spot. When it escapes notice, trouble lurks. Here are five examples.

Studies suggest that for software development projects, overall, Scrum has produced disappointing results
Translation: Since we do most of our work as projects, Scrum will produce disappointing results if we try it for our projects.
This line of reasoning ignores many possible conditions of the projects that were studied, including:
  • Scrum might have been deployed in a defective manner
  • The people using Scrum might not have been properly trained
  • The people using Scrum might have opposed it and intentionally circumvented it
The conclusion might be valid, but any possible basis for that conclusion is absent.
Research has shown that in organizations generally, meetings are a wasteful way for teams to reach decisions
Translation: Because we are an organization, and we conduct meetings, they will be a wasteful way for us to reach decisions.
The problem here is that the reasoning fails to account for differences between the meetings as conducted in the studied organizations, and the meetings as conducted in "our" organization.
Because sales will decline by 15% over the next three quarters, we must curtail spending across the board
Translation: Every department, including the Sales Department, must reduce its spending by 15% over the next three quarters.
In this In real life, the fallacy of division
can be difficult to spot. When it
escapes notice, trouble lurks.
example, there is a hidden assumption that operating expenses are directly proportional to sales, which is almost certainly invalid. But even if it were a valid assumption, across-the-board expense reductions are rarely justifiable. This example actually advocates "level" reductions in the Sales Department, which is most likely counter-effective.
Studies suggest that most corporate training is ineffective and wasteful
Translation: We must immediately review our training programs. Unless our metrics can show that a training program is producing added value, we must terminate that program.
This example shows how to avoid the Fallacy of Division by insisting that the problem of zero-value training be shown to be present in the organization before the training program is ended. However, it also illustrates the effect of succumbing to the fallacy, because the review of the training program suddenly appears on the organizational agenda. The hidden assumption is that if training programs are problematic elsewhere, they must be problematic here.
Employee compensation accounts for 80% of expenses
Translation: If we must reduce expenses by 10%, then 80% of that reduction must come from employee compensation.
The error here is the idea that since employee compensation accounts for 80% of expenses, it must bear its "fair share" of the overall reduction. This approach is erroneous for multiple reasons. Some examples:
  • It's possible that reducing employee compensation could reduce revenue even more.
  • Opportunities for improving efficiency might not be evenly distributed across expense categories.
  • The real problem might be that employee compensation is too low, which has limited the organization's ability to recruit the people needed to compete more effectively in the market.

Last words

Instances of the use of the Fallacy of Division escape notice, in part, because they seem so reasonable. Devious actors can use this property of the fallacy to persuade others to adopt positions that might be favorable to the devious actor, while harming the organization. Go to top Top  Next issue: Commenting on the Work of Others  Next Issue

303 Secrets of Workplace PoliticsIs 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

Footnotes

Comprehensive list of all citations from all editions of Point Lookout
[Aristotle 350 BCE]
Aristotle. On Sophistical Refutations. Written approximately 350 BCE. Translated 1994 by W. A. Pickard-Cambridge. Available here. Retrieved 20 March 2023. Back

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

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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:

Patterns of ConversationPatterns 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.
A dead Manchurian AshWorkplace Politics and Type III Errors
Most job descriptions contain few references to political effectiveness, beyond the fairly standard collaborate-to-achieve-results kinds of requirements. But because true achievement often requires political sophistication, understanding the political content of our jobs is important.
A10 Thunderbolt II "Warthog"Not Really Part of the Team: II
When some team members hang back, declining to show initiative, we tend to overlook the possibility that their behavior is a response to something happening within or around the team. Too often we hold responsible the person who's hanging back. What other explanations are possible?
Children playing a computer gameHigh Falutin' Goofy Talk: III
Workplace speech and writing sometimes strays into the land of pretentious but overused business phrases, which I like to call "high falutin' goofy talk." We use these phrases with perhaps less thought than they deserve, because they can be trite or can evoke indecorous images. Here's Part III of a collection of phrases and images to avoid.
Henny Youngman in 1957The Risks of Humor at Work
Humor at work can be useful for strengthening relationships, making connections, and defusing tension. And it can be risky, too. Some risks: irrelevance to the here and now, leaving out the funny, or ambiguous sarcasm. Read this post for five more risks.

See also Workplace Politics and Critical Thinking at Work for more related articles.

Forthcoming issues of Point Lookout

A meeting in a typical conference roomComing April 3: Recapping Factioned Meetings
A factioned meeting is one in which participants identify more closely with their factions, rather than with the meeting as a whole. Agreements reached in such meetings are at risk of instability as participants maneuver for advantage after the meeting. Available here and by RSS on April 3.
Franz Halder, German general and the chief of staff of the Army High Command (OKH) in Nazi Germany from 1938 until September 1942And on April 10: Managing Dunning-Kruger Risk
A cognitive bias called the Dunning-Kruger Effect can create risk for organizational missions that require expertise beyond the range of knowledge and experience of decision-makers. They might misjudge the organization's capacity to execute the mission successfully. They might even be unaware of the risk of so misjudging. Available here and by RSS on April 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:

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-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 Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.