The distinction between generic and specific concepts and why it matters for conceptual engineering

Abstract

Conceptual engineering is an approach or method for assessing, improving, adapting and disposing concepts. While recent case studies have shown the possibility and success of conceptual engineering, I argue that not all concepts are equally open to conceptual engineering. It is therefore useful to distinguish between generic and specific concepts. While the latter can be the object of conceptual design, I argue that designing generic concepts is problematic for practical and normative reasons. Nevertheless, attempts can be made to change generic concepts through interventions in larger conceptual repertoires. Contrary to specific concepts, generic concepts do not have a well-delineated function that can provide a normative reference for conceptual engineering. Moreover, they are well entrenched in larger conceptual schemes or repertoires, so that they cannot be engineered in isolation. Generic concepts also raise more and larger challenges in terms of implementation and authority than specific concepts. I discuss the consequences of the distinction between generic and specific concepts for conceptual engineering, the ethics of socially disruptive technology and conceptual ethics.