Many theorists of conceptual engineering appeal to the functions, roles, purposes or aims of concepts to articulate how conceptual engineering ought to be done. The functional approach to conceptual engineering is well-motivated: It promises a good account of the limits of revision, and of what makes some concept good. In this paper, I raise a problem for the functional approach which concerns the existence of harmful and methodologically insignificant concept functions. I examine whether we can deal with these problematic functions (...) by adopting a technical notion of function. I thus review the prospects for using the notions of a contextually stable function, of a designed function, of a proper function, and of a system function as our operative notion of function. None of them help us resolve the problem. On this basis, I argue that advocates of the functional approach should be committed to a comparatively weak claim, according to which functions must be assessed case-by-case, and that we are best served by employing an unsophisticated notion of function, according to which the function of a concept just is something the concept is used for. (shrink)

Conceptual engineering is the design, implementation, and evaluation of concepts. Conceptual engineering includes or should include de novo conceptual engineering (designing a new concept) as well as conceptual re-engineering (fixing an old concept). It should also include heteronymous (different-word) as well as homonymous (same-word) conceptual engineering. I discuss the importance and the difficulty of these sorts of conceptual engineering in philosophy and elsewhere.

Does conceptual engineering as a philosophical method deserve all the attention that it has been getting recently? The important philosophical questions, one might say, are about the world, not about what our concepts are or should be like. This paper fleshes out one way in which conceptual engineering can contribute to philosophical progress. The suspicion that conceptual engineering is getting too much attention presupposes that it is important to distribute our philosophical attention well (for example, conceptual engineering should not get (...) more than its fair share). The paper’s defense of conceptual engineering builds on that assumption. Conceptual engineering, it argues, is a way of configuring philosophers’ patterns of attention for the better: it serves attentional progress in philosophy. (shrink)

Conceptual engineers have recently turned to the notion of conceptual functions to do a variety of explanatory work. Functions are supposed to explain what speakers are debating about in metalinguistic negotiations, to capture when two concepts are about the same thing, and to help guide our normative inquiries into which concepts we should use. In this paper, I argue that this recent “functional turn” should be deflated. Contra most interpreters, we should not try to use a substantive notion of conceptual (...) functions to handle various problems for conceptual engineering. The primary accounts of function appealed to by conceptual engineers, namely etiological and system functions, are not suited to handle many of the problems functions are supposed to handle, and it’s dubious whether any other account of function would do better. Instead of trying to use substantive functions to solve theoretical problems, we should deflate those problems themselves by focusing only on what matters to us, as speakers or theorists, in a given inquiry. (shrink)

Pluralism is relevant to conceptual engineering in many ways. First of all, we face the issue of pluralism when trying to characterise the very object(s) of conceptual engineering. Is it just concepts? Could concepts be pluralistically conceived for the purposes of conceptual engineering? Or rather, is it concepts and other representational devices as well? Second, one may wonder whether concepts have only one function in our mental life (representation) or, rather, a plurality of functions (including non-representational ones). Third, it is (...) a contended question whether conceptual engineering projects should pursue only one set of values and goals (epistemic ones) or, rather, a variety of values and goals, including non-epistemic ones. Finally, the engineering of a concept may result in a form of “local” conceptual pluralism, which gives rise to its own ontological and semantic challenges. Having explored the various ways in which pluralism becomes important for conceptual engineers, this contribution presents and summarizes the articles published in this special issue. (shrink)

Conceptual engineering is commonly characterized as the method for assessing and improving our representational devices. Little has been said, however, on how best to construe these representational devices—in other words, on what conceptual engineering should be all about. This paper tackles this problem with a basic strategy: First, by presenting a taxonomy of the different possible subject matters for conceptual engineering; then, by comparatively assessing them and selecting the most conducive one with a view to making conceptual engineering an actionable (...) method, that is, a method that can be applied effectively and consistently to specific case studies. The outcome is that conceptual engineering should be all about concepts on pain of pragmatic inconsistencies otherwise. (shrink)

Conceptual engineers have made hay over the differences of their metaphilosophy from those of conceptual analysts. In this article, I argue that the differences are not as great as conceptual engineers have, perhaps rhetorically, made them seem. That is, conceptual analysts asking ‘What is X?’ questions can do much the same work that conceptual engineers can do with ‘What is X for?’ questions, at least if conceptual analysts self-understand their activity as a revisionary enterprise. I show this with a study (...) of Russell's metaphilosophy, which was just such a revisionary conception of conceptual analysis. (shrink)

The paper targets conceptual engineers who aim to improve other people’s patterns of inference and attention by shaping their concepts. Such conceptual engineers sometimes engage in a form of epistemic paternalism that I call “paternalistic cognitive engineering”: instead of explicitly persuading, informing and educating others, the engineers non-consultatively rely on assumptions about the target agents’ cognitive systems to improve their belief-forming. The target agents could reasonably regard such benevolent exercises of control as violating their sovereignty over their own belief-formation. This (...) is a pro tanto reason against such engineering. In addition to the relevant projects of conceptual engineering, paternalistic cognitive engineering plausibly includes certain kinds of nudging and evidence suppression. The paper distinguishes the sovereignty-based concern from other ethical worries about conceptual engineering and discusses how one might justify the relevant conceptual engineering projects despite the sovereignty-based reason against them. (shrink)

In this paper, we first briefly survey the main responses to the challenge that experimental philosophy poses to the method of cases, given the common assumption that the latter is crucially based on intuitive judgments about cases. Second, we discuss two of the most popular responses in more detail: the expertise defense and the mischaracterization objection. Our take on the expertise defense is that the available empirical data do not support the claim that professional philosophers enjoy relevant expertise in their (...) intuitive judgments about cases. In contrast, the mischaracterization objection seems considerably more promising than its largely negative reception has suggested. We argue that the burden of proof is thus on philosophers who still hold that the method of cases crucially relies on intuitive judgments about cases. Finally, we discuss whether conceptual engineering provides an alternative to the method of cases in light of the challenge from experimental philosophy. We argue that this is not clearly the case, because conceptual engineering also requires descriptive information about the concepts it aims to improve. However, its primarily normative perspective on our concepts makes it largely orthogonal to the challenge from experimental philosophy, and it can also benefit from the empirical methods of the latter. (shrink)

Conceptual engineers aim to revise rather than describe our concepts. But what are concepts? And how does one engineer them? Answering these questions is of central importance for implementing and theorizing about conceptual engineering. This paper discusses and criticizes two influential views of this issue: semanticism, according to which conceptual engineers aim to change linguistic meanings, and psychologism, according to which conceptual engineers aim to change psychological structures. I argue that neither of these accounts can give us the full story. (...) Instead, I propose and defend the Dual Content View of Conceptual Engineering. On this view, conceptual engineering targets concepts, where concepts are understood as having two kinds of contents: referential content and cognitive content. I show that this view is independently plausible and that it gives us a comprehensive account of conceptual engineering that helps to make progress on some of the most difficult problems surrounding conceptual engineering. (shrink)