In a 1945 monograph, Karl Duncker reported several experiments that demonstrated what he called functional fixedness. [Duncker 1945] Functional fixedness is our tendency to fail to recognize creative uses for objects when we know of — or shortly after we've been reminded of — conventional uses for those same objects. It's one of what we now call cognitive biases, which cause us to make systematic errors of thought or perception.
For example, everyone recognizes that coins are money, and that we can make purchases with them; not everyone recognizes that coins make effective doorstops when wedged into the space between the hinged side of an open door and the jamb. Upon seeing this "trick" for the first time a typical response is surprise — in part because of functional fixedness. (Light reading: "Ten Uses for Coins")
Much has been written about functional fixedness, especially in connection with creativity, because it can prevent people and teams from finding innovative solutions to important problems. But functional fixedness also has a dark side. It causes us to interpret the behavior of others in terms of the goals that those behaviors usually serve, even when those behaviors are serving a very different goal for the person who's using them. Here are three examples. I'll use fictitious names for people: Adrian and Brook.
- Reserving a meeting room or conference facility
- The usual way to reserve a facility for a meeting is to sign up for it using scheduling software. Another perhaps more effective method of reserving meeting space is to schedule a regular meeting in that space for the entire foreseeable future — six or twelve months. The meeting thus serves the purpose of reserving the meeting space, which for many regular meetings, can be more important than any item that ever appears on that meeting's agendas.
- Functional To exploit functional fixedness,
use an everyday behavior
for some other purposefixedness causes us to interpret meetings as meetings, rather than as a means of reserving meeting facilities. - Asking for information
- Usually, when we ask someone about X, what we want to know is X. But sometimes Adrian might ask Brook about X not to find out about X, but to determine whether Brook knows about X.
- Functional fixedness prevents us from seeing this transaction as something different from an attempt to learn about X.
- Delegation blockage
- Usually, when a manager delegates a task T to someone, the purpose is to ensure that T will be completed. But sometimes the purpose of assigning a task T to Adrian is to keep Adrian busy, perhaps as a distraction, or perhaps to ensure that Adrian is unavailable for some other task T'. Maybe the manager doesn't trust Adrian to handle T', or the manager has promised T' to Brook. In such cases, the manager likely cares less about task T than about keeping Adrian from working on T'.
- Functional fixedness can prevent us from seeing delegation as anything other than a way to partition responsibility.
When Adrian's phone rings, and she excuses herself from the meeting to take the call, we tend to assume that it's an important call. But what if Adrian has an app on her phone that makes fake calls? Yes, fake call apps do exist. They "work," in part, because of functional fixedness. Next in this series 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
Footnotes
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:
- Power, Authority, and Influence: A Systems View
- Power, Authority, and Influence are often understood as personal attributes. To fully grasp how they
function in organizations, we must adopt a systems view.
- Not Really Part of the Team: I
- Some team members hang back. They show little initiative and have little social contact with other team
members. How does this come about?
- Conway's Law and Technical Debt
- Conway's Law is an observation that the structures of systems we design tend to replicate our communication
patterns. This tendency might also contribute to their tendency to accumulate what we now call technical debt.
- Intentionally Misreporting Status: I
- When we report the status of the work we do, we sometimes confront the temptation to embellish the good
news or soften the bad news. How can we best deal with these obstacles to reporting status with integrity?
- Cassandra at Work
- When a team makes a wrong choice, and only a tiny minority advocated for what turned out to have been
the right choice, trouble can arise when the error at last becomes evident. Maintaining team cohesion
can be a difficult challenge for team leaders.
See also Workplace Politics and Critical Thinking at Work for more related articles.
Forthcoming issues of Point Lookout
- Coming April 24: Antipatterns for Time-Constrained Communication: 1
- Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.
- And on May 1: Antipatterns for Time-Constrained Communication: 2
- Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 2 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.
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
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