Functional Fixedness
en.wikipedia.org
en.wikipedia.org
Current society itself also seems to encourage functional fixedness. Whenever there's a problem, there's always a dedicated tool to solve it, marketed for a particular purpose. Like e.g. various safety razors for different sexes and body parts that are all basically the same, sans color and packaging. Or cleaning tools that are just cheap rolls of tape wound backwards. People learn to solve their problems by mindlessly throwing money at prepackaged solutions instead of realizing they could reuse something they already use to solve a different problem.
There is a good reason that we have more complex tools than the 6 platonic simple machines.
I'm also reminded of British architecture critic Reyner Banham's essay "The Great Gizmo" about examples of American technology that are meant for retrofitting and composition more than entirely new things.[2] The outboard motor, for example, as opposed to designing a new boat.
And also Olia Lialina has an essay "Turing-Complete User" about very similar themes in today's software.[3]
1 http://www.amazon.com/The-Practice-Misuse-Consumerism-Contem...
2 http://mashupstudio.pbworks.com/f/Banham_The%2BGreat%2BGizmo...
3 http://contemporary-home-computing.org/turing-complete-user/
I see this in pop psychology a lot: people find a few cases where a common human heuristic fails, and assume that the heuristic must be bad, when all they've proven is that it's flawed. Of course it's flawed: it's an evolved behavior and evolution is essentially a hack that solves problems it doesn't really understand. But these heuristics evolved for a reason: at least at one time, they solved more problems than they caused. It's worth understanding where common heuristics fail, but be careful not to throw the baby out with the bathwater.
For example, if the first step in attempting to solve a physical problem like the candle/wall/box problem is to take itinerary of your tools, it might become more apparent to the problem solver that they could use the box.
Not sure how well that approach would work if the problem were less physical, but I think there might be an equivalent.
I took a crash course with the company that created it. The repeatability of the process impressed me, especially across different groups and problems. You can boil it down to a checklist, (though it's still a meaningful time commitment).
More on the company here: http://www.sitsite.com/ Unfortunately I don't see much on their site about explaining their process, but a lot of "Design Thinking" courses cover similar approaches. Stanford's d.school has an intro here: http://dschool.stanford.edu/dgift/
the aim being to find as many uses as possible of every day objects such as a brick etc.
Needless to say, my mother wasn't always satisfied with the alternative applications I came up with.
By the way, this is how I think a lot of people become functionally fixated - unfortunately the typical parent's reaction to child's creativity is "WTF did you do? Please put it back the way it was before.". By the time they reach maturity, improvisation skills get beaten out of them.
https://s-media-cache-ak0.pinimg.com/736x/70/b5/11/70b511ecc...
If you need it to start moving: WD-40
If you need it to stop moving: duct tape
and it was delightfully fun to pick a mundane object and imagine all possible uses.
that misses the point that in real life, "originality/creative" is often derived from fluency. The best ideas come from people who have the most* ideas (the bad ideas are discarded).
I wonder if this phenomenon might at least partially explain the repeated misguided calls we see for encryption software to have back doors for law-enforcement use. Roughly speaking, people might be thinking that such a back door would not be used for nefarious purposes, because that is not what it is for.
For example, with the tack box in the candle problem, I think people don't empty the box because they don't want to scatter the tacks all over everything, so it's not really testing functional fixedness but rather peoples' willingness to break something to accomplish their goals.
In school my professors pushed me to make ridiculous generalizations from my tiny experiments.
https://en.wikipedia.org/wiki/Fixed-point_combinator
Edit: The difference is that the Haskell implementation (http://hackage.haskell.org/package/base-4.8.1.0/docs/src/Dat...):
fix f = let x = f x in x
relies on recursive let. The Y combinator instead works in the lambda calculus which does not have recursion, and it instead relies on recombining the function for each application.