Show alternatives

Problems demand creative solutions. Conventional wisdom suggests that greater experience and expertise should improve problem-solving ability. Yet designers consistently report that routines obstruct innovation, proven tools limit new applications, and experts are sometimes less creative than novices. The critical questions are: When does experience become an obstacle to innovation? What mental barriers emerge from familiar patterns of use? And what does the evidence reveal about this phenomenon?

Studies

The Candle Problem

Karl Duncker conducted one of the most elegant experiments on functional fixedness at the University of Berlin in 1945. Forty subjects received a candle, a box of thumbtacks, and matches. Their task: attach the candle to a cork wall so that no wax drips onto the floor. The solution requires using the box not as a container, but as a platform—tacking it to the wall and placing the candle on top. In the first condition, the thumbtacks were inside the box—only 41% solved the problem. In the second condition, the thumbtacks were placed beside the empty box—suddenly 86% solved the problem. The remarkable finding: the mere fact that the box was being used as a container blocked participants from perceiving its alternative function as a platform.

The Two-String Problem

Robert Adamson conducted a study at the University of Michigan in 1952 examining how prior use inhibits creative thinking. He asked 60 students to tie together two strings hanging from the ceiling—positioned so far apart that no one could reach both at once. The solution required tying a heavy object to one string as a pendulum weight, setting it in motion, and then grabbing the other string while the first swung within reach. Adamson provided everyone with pliers. Half the participants first used the pliers for five minutes on conventional tasks (cutting wires, tightening screws), while the other half simply observed the pliers without using them. The results were striking: Among those without prior hands-on experience, 67% solved the problem by using the pliers as the pendulum weight. Among those who had used the pliers conventionally, only 39% found the solution. Just five minutes of habitual use nearly halved the likelihood of arriving at a creative solution.

The Diagnostic Experiment

Abraham Kaplan coined the term "Law of the Instrument" in 1964 in his book *The Conduct of Inquiry*, but experimental confirmation came in 1981 through a study by Arthur Elstein and colleagues at the University of Illinois. They observed 40 physicians from different specialties diagnosing identical patient cases. Each physician received the same symptom descriptions for six fictitious patients with ambiguous complaints. The striking result: orthopedists diagnosed musculoskeletal problems in 73% of cases, while internists identified internal medicine causes in 68% of cases—for the same patients. A patient presenting with chest pain and shortness of breath was diagnosed by a cardiologist as having a heart problem, by a pulmonologist as having a lung problem, and by a gastroenterologist as having reflux disease—even though all three had identical information. Specialization shaped problem perception more powerfully than the objective symptoms did.

The Golden Hammer Study

In 2004, Magne Jørgensen from the University of Oslo investigated this phenomenon with 156 software developers. In a controlled experiment, all participants received the same project description: a medium-sized company needed a solution for its warehouse management. The developers were randomly divided into groups, each with different technical specializations. The setup was identical; only the participants' prior experience varied. Developers with a Java background recommended a Java-based solution in 81% of cases, .NET specialists favored Microsoft technology 79% of the time, and open-source enthusiasts suggested Linux solutions in 72% of cases. Even more revealing: when groups were asked to assess the risks of other technologies, they identified an average of 4.2 critical problems with unfamiliar technologies but only 1.1 with their own—even though objective code reviews showed no significant differences in risk distribution. The familiar tool was not only preferred but also systematically perceived as lower risk.

Principle

Which principle for Customer Experience Design can be derived from this? Functional fixedness reveals that customers typically recognize only a product or service's most obvious use, overlooking valuable additional benefits. Companies must therefore actively communicate and demonstrate alternative applications to unlock their offerings' full potential. This approach proves particularly effective with established products customers already know, as well as when new needs emerge or life circumstances change. However, alternative uses must be authentic and relevant—far-fetched applications appear implausible and can create confusion. The following guidelines show how to implement this principle in practice.

Guidelines

Show alternative applications explicitly

Products are perceived only through their primary function. Therefore, actively demonstrate additional use cases through example images, application videos, or customer testimonials. A CRM system is pigeonholed as a 'sales tool'—explicitly showcase its applications for customer success, marketing, and support. A cargo bike is pigeonholed as 'child transport'—show tradespeople, delivery services, and mobile sales stands using it. Customers will not discover alternative uses on their own.

Break down product categories proactively

Categorization locks in perceived function. A "project management tool" automatically triggers the mental schema "for projects." Instead, use functional or benefit-oriented categories: "structure collaboration," "coordinate deadlines," "centralize knowledge." A "fitness tracker" becomes confined to sports—reposition it as a "health coach" to unlock audiences with chronic conditions. Linguistic framing determines which mental models get activated.

Show cross-industry inspirations

Functional fixedness stems from industry-specific conventions. Break through it by examining how other industries solve the same problem. An insurance company can learn from hospitality (treating onboarding as a check-in experience). A B2B SaaS tool can learn from gaming (using gamification for user activation). Specifically: Create 'Inspiration Showcases' that deliberately present successful examples from unrelated industries. The message: 'More possibilities exist beyond the obvious standard solution.'

Use Case Workshops Instead of Feature Demos

CX Guideline: Use-Case Workshops Instead of Feature Demos Traditional product demos reinforce functional fixedness by showcasing features in their standard applications. Replace demos with facilitated use-case workshops where customers describe their specific problems and the facilitator demonstrates unconventional solution approaches using the product. For example, while a CMS is typically viewed as a 'website tool,' workshop participants discover its potential for internal knowledge databases, onboarding journeys, and customer portals. This active problem-solving approach overcomes mental blocks more effectively than passive demonstration.

Explicitly name solution alternatives

Before recommending your specialized solution, explicitly name 2-3 alternative approaches and explain why you consider them less suitable for this specific case. This structured comparative presentation signals to the customer that you've analyzed the problem from multiple perspectives, not just through the lens of your own expertise. Example: "For your warehouse problem, there are fundamentally three approaches: adapt standard software, develop a custom solution, or optimize processes without an IT solution. In your case, I recommend the second approach because..."

Demonstrate the limitations of one's own solution

Proactively communicate which situations or customer types your solution is NOT optimal for. This self-imposed limitation paradoxically builds trust because it counteracts the Law of the Instrument effect. Customers recognize that you're not trying to solve every problem with your hammer. Example: "Our consulting is ideal for companies with 50+ employees when you have at least two years of lead time. For faster or smaller projects, better alternatives exist." This honesty prevents poor purchasing decisions and strengthens your credibility.

Establish structured needs analysis

Implement a standardized question catalog that examines the customer's problem from multiple angles BEFORE discussing any solutions. This discovery phase must be documented and confirmed by the customer. Only after achieving a multidimensional understanding of the problem should you present solution recommendations. This process compels experts to move beyond tunnel vision and prevents premature, cookie-cutter recommendations. Tools such as Solution-Focused Questioning or Jobs-to-be-Done frameworks help you understand the problem independently of existing solutions.

Perspective Shift Through Peer Review

# CX Guideline: Perspective Shift through Peer Review Establish a process where important customer recommendations are reviewed by a colleague from a different area of expertise before communication. The reviewer specifically examines: "What alternative solution approaches were considered? Why were they rejected?" This cross-validation significantly reduces the law-of-the-instrument effect. In medicine, interdisciplinary tumor boards have been shown to reduce misdiagnoses by up to 30%. This principle works in any industry where expertise can lead to tunnel vision.