Functional Fixedness

Every organization carries assets that quietly outlive the reason they were acquired. A warehouse built for one product line, a customer service team hired to answer phones, a data platform bought for compliance reporting: each accumulates capabilities beyond its original brief, yet leaders rarely notice because the label attached at acquisition keeps directing attention back to the original purpose. Cognitive psychologists have a name for this narrowing of perception and it explains far more about stalled innovation, wasted capacity and slow reorganizations than most strategy frameworks acknowledge.

The Psychological Roots of the Bias

Karl Duncker, a German Gestalt psychologist, described functional fixedness in the 1930s after running a series of problem-solving experiments with everyday objects. His best-known task, the candle problem, gave participants a candle, a box of matches and a box of tacks, then asked them to mount the candle on a wall without letting wax drip on the floor. Most participants tried to tack the candle directly to the wall or melt wax to glue it there. Few noticed that the tack box itself, once emptied, could serve as a candle holder nailed to the wall. Duncker found that when the tacks were presented separately from an empty box, solution rates roughly doubled, because the box was no longer perceptually locked into the role of "container"1. The American Psychological Association defines the bias as a mental block against using an object in a way that departs from its customary function, a definition that has held steady for nearly a century of follow-up research2. What makes the finding useful to business leaders is not the candle itself but the mechanism:

once a mind assigns a fixed purpose to an object, alternative uses become genuinely harder to perceive, not merely harder to justify

How the Bias Shows Up Inside Organizations

The candle problem is a laboratory version of a pattern that repeats constantly in companies of every size. A piece of software purchased for one department sits unused by three others that could benefit from it, because nobody thought to ask what the tool does rather than what it was bought for. A team assembled to handle a specific product launch keeps working the same narrow brief long after the launch ends, even though its members have built skills the rest of the business needs. A factory floor idled by a demand shift gets marked for closure before anyone asks whether the equipment on it could run a different product entirely. Harvard Business Review has documented this pattern directly, describing functional fixedness as the most persistent obstacle to spotting innovation opportunities that are sitting in plain sight inside a company's own operations3. The common thread across these examples is that the asset never stopped having other uses; the organization stopped looking for them.

Tools and Technology

Enterprise software is a frequent casualty because licenses, dashboards and platforms arrive bundled with a stated purpose in the procurement request. A customer analytics tool bought for the marketing function may hold data structures that finance or product teams could use for forecasting, but the tool's name and its origin story keep other departments from requesting access. Nielsen Norman Group's research on design cognition found that functional fixedness constrains ideation broadly and that professionals working close to a familiar toolset generate fewer novel applications than those exposed to unrelated fields4. The fix is not more training on the tool itself but a periodic audit that asks what the tool can technically do, independent of the department that originally requested it.

Roles and Talent

Job titles function the same way tack boxes do in Duncker's experiment. An operations analyst hired to produce weekly reports may have quantitative skills that a growth or strategy team badly needs, but the title "operations analyst" keeps that skill set filed under one heading in the minds of managers who could redeploy it. This is especially costly during reorganizations, when leadership evaluates people against the roles they currently hold rather than the capabilities they carry. The Chartered Management Institute has flagged this as a leadership decision-making problem specifically, noting that recognizing when structures themselves suppress new ideas matters more than running another ideation workshop5. Skills inventories that describe what people can do, separate from their current job description, are one of the few reliable ways to counter this.

Idle Assets and Capacity

Physical capacity suffers the most visible version of the bias because idle assets show up on a balance sheet as a cost rather than an option. Retail footprints closed during a downturn sit vacant instead of being evaluated for logistics or fulfillment use. Manufacturing lines built for one product get scrapped rather than retooled, even when the underlying machinery could handle an adjacent product with modest reconfiguration. Data centers procured for one workload sit at partial utilization while a different business unit spins up new infrastructure elsewhere in the same company. These decisions get made asset by asset, each time anchored to the question "what was this for", rather than "what can this do."

Why Expertise Makes the Problem Worse, Not Better

A counterintuitive finding runs through decades of functional fixedness research: the bias grows stronger with age, training and domain expertise rather than weaker. Five-year-old children show almost no functional fixedness in candle-problem variants, treating a tack box and a candle holder as interchangeable if the shapes fit. By age seven, children begin prioritizing an object's intended purpose over its physical properties and that prioritization strengthens through adulthood as people accumulate more associations between objects and their conventional roles. This matters directly for organizations staffed by experienced professionals, because the people most likely to know an asset intimately are also the people most likely to have its original purpose locked into their perception. A junior hire unfamiliar with why a system was built often asks the naive question that unlocks a new use, while the veteran who built the system defends its original scope by habit rather than by evidence. Deliberately rotating unfamiliar reviewers through asset, portfolio and talent reviews counters this tendency more reliably than asking experienced staff to think more creatively.

Breaking the Fix: What Actually Works

Research on overcoming functional fixedness converges on a small set of interventions that consulting teams can apply without organizational upheaval. The first is decomposition: describing an asset by its component properties, materials, capacity or skills, rather than by the name attached at acquisition, which strips away the perceptual shortcut that locks perception to one use. The second is distance: exposing decision-makers to how unrelated industries solved similar constraints, since a research summary on functional fixedness notes that professionals who draw on distant domains generate more original and workable solutions than those who stay within adjacent, familiar territory6. The third is friction: building a mandatory review step before any asset, license or role gets retired, sold or backfilled, so someone is forced to ask what else the resource could support before the decision closes. None of these require a large budget. What they require is a habit of separating an object's label from its capabilities, applied consistently enough that it survives past the initial enthusiasm of a single workshop.

We often stop questioning whether an object, behaviour, or tool could be used in new ways

That habit is where consulting engagements add real value beyond the recommendation itself. An outside team walks into a client organization without years of accumulated association attached to its systems, its people or its unused floor space, which is precisely why external reviewers frequently surface capacity that internal teams have stopped seeing. The discipline worth installing is not a one-time audit but a recurring checkpoint, embedded in budget cycles and workforce planning, that asks a version of Duncker's original question:

before this gets replaced, sold or written off, what else could it do

• 1functional fixedness
• 2functional fixedness
• 3why we can't see what's right in front of us
• 4functional fixedness stops you from having innovative ideas
• 5is functional fixedness impeding your leadership decision-making
• 6functional fixedness - an overview