Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 17, Issue 51;   December 20, 2017: Conceptual Mondegreens

Conceptual Mondegreens

by

When we disagree about abstractions, such as a problem solution, or a competitor's strategy, the cause can often be misunderstanding the abstraction. That misunderstanding can be a conceptual mondegreen.
Raquel Welch (left) and Gilda Radner (right) from a @Cite{Saturday Night Live rehearsal, April 24, 1976

Raquel Welch (left) and Gilda Radner (right) from a Saturday Night Live rehearsal, April 24, 1976. Radner is in costume as Emily Litella. Publicity photo by NBC Television courtesy Wikimedia.

Mondegreens are words or phrases that listeners believe they've heard, but which weren't actually spoken or sung. They sound enough like what was said, and seem to make sense, but they're wrong. A cousin of the malapropism, which is a word or phrase mistakenly substituted by a speaker, the mondegreen is a word or phrase mistakenly substituted by the listener. Mondegreens [1] are sometimes very funny, but usually they're just dumb [2].

Some famous mondegreens were demonstrated by Gilda Radner, a member of the original cast of Saturday Night Live, an American television program. During the show's simulated news segments, Radner appeared in the role of "Emily Litella," an elderly woman with a hearing problem. As a "columnist," she opined endlessly about topics such as "endangered feces" (species), "saving Soviet jewelry" (Jewry), and "sax and violins on television" (sex and violence). Upon being corrected by the "news anchor," Ms. Litella would sheepishly exit, saying, "Never mind," which became a catch phrase of the day, and remains in use in the U.S.

But I digress.

A conceptual mondegreen is a concept that a discussion participant mistakenly substitutes for the actual concept under discussion. It seems to makes sense, but it's incorrect, causing the misunderstander to miss the point.

For example, in a debate about circumventing arcane accounting rules regarding capitalization of software development, a mondegreen might involve the rules about capitalizing software, instead of software development.

Here are two common situations in which conceptual mondegreens arise.

Problem solving
When trying to explain why a problem solution failed, if the available data is of poor quality or incomplete, formulating a hypothesis can produce conceptual mondegreens. A hypothesis is useful for devising experiments to gather better data, but instead of devising experiments, some people just accept the hypothesis as true. Then they commit the organization to a solution modified on that basis, which can be an expensive error if the hypothesis is incorrect.
When solving A conceptual mondegreen is a
concept that a discussion participant
mistakenly substitutes for the
actual concept under discussion
problems, adopt candidate explanations as mere candidates. Devise experiments to reveal their shortcomings, rather than to confirm their strengths.
Contending with adversaries
Conceptual mondegreens also appear when we try to understand the behavior of adversaries such as political rivals, competitive companies, battlefield opponents, opposing sports teams, or products similar to our own. Observing the adversary's configuration and resources, we project its future behavior. But unlike problem solving, we can't always perform experiments to refine our conjectures. Still, we might try a feint on the battlefield, the playing field, or in the marketplace, to see how the adversary responds. That might provide useful data, but the best data comes from ongoing engagement with the adversary.
Adopt the view that continued engagement with the adversary has value beyond possibly winning the competition. It also provides data that can resolve the conceptual mondegreens pertaining to the adversary's behavior.

When a mondegreen makes an appearance, it can indicate uneven distribution of knowledge or expertise within the group. Unless that's addressed, mondegreens will likely appear again and again. Go to top Top  Next issue: On Assigning Responsibility for Creating Trouble  Next Issue

101 Tips for Managing Conflict Are you fed up with tense, explosive meetings? Are you or a colleague the target of a bully? Destructive conflict can ruin organizations. But if we believe that all conflict is destructive, and that we can somehow eliminate conflict, or that conflict is an enemy of productivity, then we're in conflict with Conflict itself. Read 101 Tips for Managing Conflict to learn how to make peace with conflict and make it an organizational asset. Order Now!

Footnotes

[1]
The term was coined by Sylvia Wright in a 1954 article in Harper's Magazine, "The Death of Lady Mondegreen," November 1, 1954, pp. 48-51. Back
[2]
See also Michael Barber's A Collection of Humorous Mondegreens. Back

Your comments are welcome

Would you like to see your comments posted here? rbrenvmyqjrysrRxggLKIner@ChacBlRAPxskKIRvUXytoCanyon.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.

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 Conflict Management:

One of the Franklin Milestones on the Boston Post RoadManaging Pressure: Milestones and Deliveries
Pressed repeatedly for "status" reports, you might guess that they don't want status — they want progress. Things can get so nutty that responding to the status requests gets in the way of doing the job. How does this happen and what can you do about it? Here's Part III of a set of tactics and strategies for dealing with pressure.
A field of corn severely stunted by droughtToxic Conflict in Virtual Teams: Virtuality
In virtual teams, toxic conflict sometimes seems to erupt spontaneously. People who function effectively in co-located teams can find themselves repeatedly embroiled in conflicts that seem to lack specific causes. What triggers toxic conflict in virtual teams?
A dense Lodgepole Pine stand in Yellowstone National Park in the United StatesAgenda Despots: I
Many of us abhor meetings. Words like boring, silly, and waste come to mind. But for some meeting Chairs, meetings aren't boring at all, because they fear losing control of the agenda. To maintain control, they use the techniques of the Agenda Despots.
Feeling shameShame and Bullying
Targets of bullies sometimes experience intense feelings of shame. Here are some insights that might restore the ability to think, and maybe end the bullying.
Srinivasa RamanujanLinear Thinking Bias
When assessing the validity of problem solutions, we regard them as more valid if their discovery stories are logical, than we would if they're other than logical. This can lead to erroneous assessments, because the discovery story is not the solution.

See also Conflict Management and Effective Communication at Work for more related articles.

Forthcoming issues of Point Lookout

Jeffrey Skilling, in a mug shot taken in 2004 by the United States Marshals ServiceComing 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.
The end of the line for a railroad trackAnd 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.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenRyPLXGZHAMOEYVjtner@ChacYFDVcowQrUCJqwxcoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

Technical Debt Management: Making the Business Case
This Technical Debt Management: Making the Business Caseprogram 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:

The Race to the South Pole: The Power of Agile Development
On 14The Race to the Pole: An Application of Agile Development 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:

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople 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.

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ 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.