Functional Fixedness

What It Means

Functional fixedness is a cognitive bias described by Karl Duncker in the 1940s following his candle problem experiments. In the candle problem, subjects are given a candle, a box of thumbtacks, and a book of matches, and asked to fix the candle to the wall so it burns without dripping. Most subjects fail because they see the tack box as merely a container rather than as a potential shelf - they are "fixed" on the tack box's usual function.

The bias describes a general tendency to perceive objects, people, concepts, and processes in terms of their conventional roles and functions, which prevents seeing how they could be repurposed to solve an unfamiliar problem.

Origins and Mechanisms

Functional fixedness is a side effect of efficient categorization. The same cognitive mechanisms that allow you to quickly recognize what something is and how it normally behaves also create an attentional bias toward conventional uses. Non-conventional uses require overriding the initial categorization - noticing that the object could be something other than what it typically is.

Expertise increases functional fixedness in the specific domain of expertise. Experienced practitioners have strong, well-established categories for the things in their domain. These categories are useful for standard problems but can be obstacles when a non-standard solution is required.

In Organizations

Organizational functional fixedness - the inability to see how existing resources could be repurposed - is common and costly. Capabilities that were built for one purpose are not seen as potential assets for a different purpose. People are categorized by their job titles rather than their actual skills. Processes designed for one type of work are not considered for a different type.

Overcoming organizational functional fixedness requires the same approach as overcoming individual functional fixedness: explicitly asking what else a resource could be, rather than assuming its current function is its only function.

Breaking the Fixedness

Techniques for reducing functional fixedness include: listing the properties of an object rather than its name (a box is a rigid container with a certain volume - what could you do with a rigid container?), working in cross-domain teams where different functional categories are in use, and explicitly asking "what else could this be used for?" as a routine part of problem-solving.