Exaptation

Exaptation describes a feature useful in its present role that was not originally shaped by selection for that role. The feature may have served another function or originated without an adaptive function. The concept separates current utility from historical origin. Practical repurposing is a useful analogy, not proof that most innovation follows this mechanism.

Exaptation separates a feature's current use from the historical process that produced it. Gould and Vrba introduced the term for useful features not built by selection for their present role, including co-option of features that previously served another role or were not adaptations for a function. Current usefulness is therefore not enough to infer an origin story.

For practical innovation, inventory a capability and ask which properties might serve a different need. The old context may hide assumptions that fail in the new one. Compare adaptation costs, reliability, and a purpose-built alternative before treating reuse as the economical choice. This is a design analogy, not evidence that most innovation is exaptation or that repurposed tools are automatically better tested for their new use.

When to use it

When investigating a feature's historical origin, considering a new use for an existing capability, or comparing reuse with a purpose-built solution.

How it can help

Identify properties of existing capabilities that might meet a different need, then test the new fit and the costs of adaptation. Compare reuse with a purpose-built alternative and check inherited assumptions.