The Implementation Problem for conceptual engineering is, roughly, the problem conceptual engineers face when attempting to bring about the conceptual change they support. An important aspect of this problem concerns the extent to which attempting to implement concepts can lead to unintended negative consequences. Not only can conceptual engineers fail to implement their proposals, but their interventions can produce outcomes directly counter to their goals. It is therefore important to think carefully about the prospect of attempted implementation leading to unintended (...) negative consequences: what sort of negative consequences can conceptual engineers expect? Are some forms of conceptual engineering more likely than others to lead to such consequences? And is conceptual engineering still viable even given the risk of such consequences? This paper addresses such questions. I begin by outlining different forms of conceptual engineering (Section 1), before examining how they can produce unintended negative consequences (Section 2). I then discuss some implications of the fact that attempted implementation can produce unintended negative consequences, suggesting that, among other things, some forms of conceptual engineering are less viable than others (Section 3). I conclude, though, by considering some of the ways in which conceptual engineering is nonetheless a worthwhile pursuit (Section 4). (shrink)

Linguistic interventions aim to change our linguistic practices. A commonly discussed type of linguistic intervention is meaning revision, which seeks to associate existing words with new or revised meanings. But why does retaining old words matter so much? Why not instead introduce new words to express the newly defined meanings? Drawing on relevant psycholinguistic research, this paper develops an empirically motivated, general, and practically useful pro tanto reason to retain rather than replace the original word during the process of conceptual (...) improvement. (shrink)

Should we be worried that the concept of trust is increasingly used when we assess non-human agents and artefacts, say robots and AI systems? Whilst some authors have developed explanations of the concept of trust with a view to accounting for trust in AI systems and other non-agents, others have rejected the idea that we should extend trust in this way. The article advances this debate by bringing insights from conceptual engineering to bear on this issue. After setting up a (...) target concept of trust in terms of four functional desiderata (trust-reliance distinction, explanatory strength, tracking affective responses, and accounting for distrust), I analyze how agential vs. non-agential accounts can satisfy these. A final section investigates how ‘non-ideal’ circumstances—that is, circumstances where the manifest and operative concept use diverge amongst concept users—affect our choice about which rendering of trust is to be preferred. I suggest that some prominent arguments against extending the language of trust to non-agents are not decisive and reflect on an important oversight in the current debate, namely a failure to address how narrower, agent-centred accounts curtail our ability to distrust non-agents. (shrink)

Conceptual engineering concerns the assessment and improvement of our concepts. But how can proposals to engineer concepts be implemented in the real world? This is known as the implementation challenge to conceptual engineering. In this paper, I am concerned with the meta-philosophical implications of the implementation challenge. Specifically, must we overcome the implementation challenge prior to undertaking conceptual engineering? Some critics have recently answered this question affirmatively. I intend to show that they are mistaken. I argue as follows. First, successful (...) implementation is not an integral part of conceptual engineering. Second, the idea that the value of conceptual engineering relies on successful implementation is in tension with widespread assumptions about normative theorizing. (shrink)

A philosopher argues that state-sponsored cyberattacks against central military or civilian targets are always acts of war. What is this philosopher doing? According to conceptual analysts, the philosopher is making a claim about our concept of war. According to philosophical realists, the philosopher is making a claim about war per se. In a quickly developing literature, a third option is being explored: the philosopher is engineering the concept of war. On this view, the philosopher is making a proposal about which (...) concept we should have – even if it deviates from the extant concept, and even if it does not capture ‘what war really is’. The activity or method of proposing such revisionary definitions, as well as the metaphilosophical reflection on it, has become known as conceptual engineering. (shrink)

This paper discusses the logical space of alternative conceptual engineering projects, with a specific focus on (1) the processes, (2) the targets and goals, and (3) the methods of such projects. We present an overview of how these three aspects interact in the contemporary literature and discuss those alternative projects that have yet to be explored based on our suggested typology. We show how choices about each element in a conceptual engineering project constrain the possibilities for the others, thereby giving (...) rise to distinct groupings of possible projects under the banner of conceptual engineering. We conclude with a critical reflection on the potential ethical issues that arise as a result of effectively putting conceptual engineering into practice. (shrink)

Supporters of conceptual engineering often use Haslanger’s ameliorative project as a key example of their methodology. However, at face value, Haslanger’s project is no cause for optimism about conceptual engineering. If we interpret Haslanger as seeking to revise how people in general use and understand words such as ‘woman’, ‘man’, etc., then her project has been unsuccessful. And if we interpret her as seeking to reveal the meaning of those words, then her project does not involve conceptual engineering. I develop (...) and defend an alternative interpretation of Haslanger’s project and argue that, so interpreted, it is a successful conceptual engineering project after all. In so doing, I develop what I call a particularist account of the success conditions for conceptual engineering. (shrink)

Conceptual engineering has strong political roots. But if conceptual engineering is to be a useful tool for promoting social justice, there must be a means by which the concepts we design can take root and propagate in dominant contexts. This is known as the implementation challenge. In this paper, I caution against movements toward a particular methodological perspective on the challenge called dialogical individualism. This perspective centres the role of speakers in speech-situations to persuade hearers to change their minds about (...) currently held concepts. This individualism has a distorting effect: it warps our perception of the size of the challenge. In particular, dialogical individualism ignores the social environmental factors that make conversation an unfriendly site for conceptual change. Moreover, it is not sufficiently attentive to the history of conceptual change in communities of practice. In the end, I argue for a methodological perspective shift: discursive strategies, such as speaker persuasion, should be decentralized in our overall thinking about the best solutions to the implementation challenge. Our attention is better focused on tailoring strategies to deal with the social environment in which concept-users are embedded. (shrink)

As usually understood, ‘conceptual engineering’ is a form of conceptual inquiry aimed at diagnosing problems with extant concepts and finding better concepts to replace them. This can seem like an appropriate response to a skeptical concern that our concepts are cognitively deficient: unsuitable for use in serious inquiry. We argue, however, that conceptual engineering, so understood, cannot reasonably be motivated in this way. The basic problem is that on the first hand, since conceptual engineering is itself a form of inquiry, (...) it cannot succeed by using the problematic concept itself in inquiry (since it is unsuitable for use in inquiry); but, on the other hand, methods for carrying out inquiry directed at concepts without using those concepts are constrained in such a way as to make conceptual engineering very unlikely to succeed. The upshot is that conceptual engineering has no reasonable chance of addressing the skeptical concern about cognitive deficiency. This is an important and previously unarticulated result, about what conceptual engineering can and cannot reasonably be expected to do. (shrink)

Conceptual engineering is sometimes presented as an alternative to conceptual analysis. But one important objection to conceptual analysis threatens to carry across: that philosophy investigates phenomena—knowledge, truth, freedom, etc.—rather than concepts of those phenomena. This poses a prima facie problem insofar as conceptual engineering targets concepts or terms rather than phenomena. Call it the ‘phenomenon objection’. I begin by examining recent discussions of the phenomenon objection by Cappelen and Scharp, rejecting their responses. I then clarify and strengthen the objection, discussing (...) the challenge that the ‘strong phenomenon objection’ poses to conceptual engineers. Finally, I develop a new response to the strong phenomenon objection. In doing so, I motivate, articulate and defend an account of philosophy and its problems on which conceptual engineering is the appropriate method for tackling many philosophical problems—as well as, perhaps surprisingly, some problems in the sciences. (shrink)