It is often assumed that how we talk about the world matters a great deal. This is one reason why conceptual engineers seek to improve our linguistic practices by advocating novel uses of our words, or by inventing new ones altogether. A core idea shared by conceptual engineers is that by changing our language in this way, we can reap all sorts of cognitive and practical benefits, such as improving our theorizing, combating hermeneutical injustice, or promoting social emancipation. But how (...) do changes at the linguistic level translate into any of these worthwhile benefits? In this paper, we propose the nameability account as a novel answer to this question. More specifically, we argue that what linguistic resources are readily available to us directly affects our cognitive performance on various categorization-related tasks. Consequently, our performance on such tasks can be improved by making controlled changes to our linguistic resources. We argue that this finding supports and extends recent motivations for conceptual engineering, as categorization plays an important role in both theoretical and practical contexts. (shrink)

Conceptual Engineering, the practice of stipulating a change in the meaning of a word in order to improve it in some fashion, for some end, has proved a popular topic among philosophers of language in recent times. Deutsch (Philos Stud 177:3935–3957, 2020) has argued that it has received an undue degree of interest since its implementation falls onto one of the horns of a dilemma: either the change to be effected is in the global semantic meaning of the given word/concept, (...) in which case it is infeasible, or it is merely in the local speaker-meaning, in which case it is largely trivial. I suggest, however, that there is a deeper, more troubling, objection to Conceptual Engineering. My criticism does not strictly take the form of a dilemma, since some cases may fall upon both horns at once and others may be able to squeeze through the gap, but it does involve highlighting two potential weaknesses of the project: one of those, as with Deutsch, is the danger of triviality, although it is not concerned only with the division between semantic and speaker meaning. It seems clear that there are cases where a particular authority or legislature has the capacity to alter a word’s legal meaning; others where certain groups may discuss the best way to use a technical term, each putting forward their preferred suggestions; and individual speakers are at liberty to choose to use a word with a particular intention. None of this is new, nor controversial, and, thus, is largely trivial. In all cases, but particularly where meanings are manipulated without due authority, inexplicitly, or in order to further a particular theoretical conception, however, there is a strong chance that the engineer will be led to commit one of the fallacies of language to which philosophy is particularly vulnerable (Hinton Evaluating the language of argument, Springer, Cham, 2021). These include fallacies of vagueness, equivocation, and persuasive definition. In this paper, I use examples to illustrate the likely fallaciousness of conceptual redefinitions and highlight in particular the ‘Philosophical Fallacy’, outlined by Nelson (A theory of philosophical fallacies.Translated by Leal F, Carus D. Springer, Cham 2016). I conclude that, as a method for philosophers, Conceptual Engineering is, in broad terms, either trivial or fallacious. (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)

According to a prevailing view, conceptual engineering introduces a revolutionary philosophical methodology, challenging traditional conceptual analysis. However, in our paper, we argue that closer scrutiny reveals not only the falsity but also the inherent ambiguity of this narrative. We explore four interpretations of the "Anti-Novelty Claim", the claim that conceptual engineering is not a new way of doing philosophy. Discussing the Anti-Novelty Claim from the perspective of a text’s producer, the text’s consumers, and the exegetical potential of the text, we (...) examine each perspective’s metaphilosophical implications and demonstrate that taking each perspective requires different methods. Adopting these different methods, we argue that the different interpretations of the Anti-Novelty Claim range from nearly trivially true to unlikely but untested. Importantly, we emphasize that each interpretation offers unique philosophical insights, yet addressing them requires diverse types of evidence, preventing a singular, straightforward answer to whether conceptual engineering is new. (shrink)

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)

In this paper, I examine Max Deutsch’s dilemma for the implementation of newly engineered concepts. In the debate over this dilemma, the goal of conceptual engineering tends to be set either too high or too low. As a result, implementation tends to be seen as either very unlikely to succeed or too easily achievable. This paper aims to offer a way out of this dilemma. I argue that the success conditions for implementation can be better understood if we distinguish between (...) different stages in the implementation process. Implementation is a complex process involving several stages, each of which can be evaluated as a success or a failure. I argue that even if an implementation does not reach the final stage in which a new concept is widely used in the society at large, it may not be a complete failure: conceptual engineers may not even aim for a new concept to be widely used in the society at large; or even if they do and a new concept only circulates in a smaller subgroup, this can still be a significant achievement. The upshot is that we should take more seriously the possibility that conceptual engineering can be implemented locally at the subgroup level. (shrink)

How feasible are conceptual engineering projects of social concepts that aim for the engineered concept to be widely adopted in ordinary everyday life? Predominant frameworks on the psychology of concepts that shape work on stereotyping, bias, and machine learning have grim implications for the prospects of conceptual engineers: conceptual engineering efforts are ineffective in promoting certain social-conceptual changes. Specifically, since conceptual components that give rise to problematic social stereotypes are sensitive to statistical structures of the environment, purely conceptual change won’t (...) be possible without corresponding world change. This tradition, however, tends to ignore that concepts don’t only encode statistical, but also causal information. Paying attention to this feature of concepts, I argue, shows that conceptual engineering is not only possible. There is an imperative to conceptually-engineer. (shrink)

Conceptual engineering is the enterprise of evaluating and improving our representational devices. But how should we conduct this enterprise? One increasingly popular answer to this question proposes that conceptual engineering should proceed in terms of the functions of our representational devices. In this paper, we argue that the best way of understanding this suggestion is in terms of normative functions, where normative functions of concepts are, roughly, things that they allow us to do that matter normatively (for example, things in (...) virtue of which we have normative reasons to have these concepts). Not only does this introduce a novel view about functions to the literature. This proposal also fits more naturally than the alternatives with conceptual engineering as a normative enterprise, and it allows functions to play all of the explanatory roles assigned to them in the conceptual engineering literature. Our discussion of the explanatory advantages of normative functions also advances the understanding of the ways in which concepts can be authoritative, what this means for conceptual engineering, and highlights the importance of political philosophy for thinking about conceptual engineering in practice. Furthermore, the paper explicates what kind of role considerations about function can and should actually play in conceptual engineering. (shrink)

Conceptual engineering wants analytic philosophy to be centered around the assessment and improvement of philosophical concepts. But contemporary debates about conceptual engineering do not engage much with the vast literature on conceptual change that exists in philosophy of science. In this article, I argue that an adequate appreciation of the history of philosophy of science can contribute to discussions about conceptual engineering. Specifically, I show that the evolution of debates over scientific conceptual change arguably demonstrates that, contrary to what is (...) commonly assumed in the literature about conceptual engineering, conceptual change is possible within an externalist metasemantics and that any adequate theory of conceptual change should be metasemantically plastic. (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)

According to predictive processing, an increasingly influential paradigm in cognitive science, the function of the brain is to minimize the prediction error of its sensory input. Conceptual engineering is the practice of assessing and changing concepts or word meanings. We contribute to both strands of research by proposing the first cognitive account of conceptual engineering, using the predictive processing framework. Our model reveals a new kind of implementation problem as prediction errors are only minimized if enough agents embrace conceptual changes. (...) This problem can be overcome by emphasizing the importance of social norms and conceptual pluralism. (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)

Communication strategies to shape public opinion can be applied to the philosophical program of conceptual engineering. I propose to look for answers to the implementation challenge for conceptual engineering on similar challenges that arise in other contexts, such as that of social movements. I claim that conceptual engineering is successfully practiced in other areas with direct consequences on the political landscape, and that we can apply to philosophy what we might learn from those successful practices. With that end in mind, (...) I explain the psychological approach to conceptual engineering. I present what has been called “the implementation challenge”, which is the problem that emerges from the possibility of control over the content of our concepts. The challenge consists in that if there is not such a control, conceptual engineering is not implementable. Then, I review some of the reactions that have been given to that challenge, and I defend the feasibility of conceptual engineering appealing to the collective action frames that social movements endorse as an instance of a successful kind of conceptual engineering and derive some strategies that might be of use for conceptual engineering in philosophy. Finally, I reply to some anticipated objections to my proposal. (shrink)

Stipulation gives us a degree of control over meaning. By stipulating how I will use a term I am able to determine the meaning it will receive on future occasions of use. My stipulation will affect the truth conditional content of my future utterances. But the mechanisms of stipulation are mysterious. As Cappelen (2018) argues, meaning is typically determined in an inscrutable way by a myriad of external factors beyond our control. How does stipulation override these factors? And the powers (...) of stipulation are limited. Firstly, the power of stipulation is typically short-lived. Sec-ondly, some stipulations simply don’t get off the ground. What explains the limits of stipulation? I consider two related approaches to stipulation and argue that they are unable to capture stipulation’s metasemantic effects. I then provide an explanation of the metasemantic effects of stipulation: Stipulation determines meaning by determining the word use it is fitting to hold the speaker to. This account is able to capture the mechanisms and limits of stipulation, whilst also explaining why we should care about stip-ulative success. I close by briefly drawing out some lessons for conceptual engineering. -/- . (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)

We argue for an intimate relation between semantic externalism and semantic deference and propose a typology of speakers’ metasemantic views as revealed by their deferential attitudes. Building on this typology, we then offer a classification of metasemantic disagreements understood as verbal disputes between speakers who (consciously or unconsciously) hold divergent metasemantic views about the same word. In particular, we distinguish lower-order metasemantic disagreements between speakers who disagree on the exact source of meaning determination for a word yet agree on the (...) kind of deferential attitude this word is liable to, from higher-order metasemantic disagreements between speakers who do not even agree on the suitable kind of deferential attitude. We demonstrate the fruitfulness of our classification through the concrete implications it has for conceptual engineering. (shrink)

The paper investigates to what extent the method of cases can be interpreted as either a descriptive or a normative enterprise. I demonstrate that although most instances of the method of cases in most philosophical theories could be interpreted as being intended to either discover or revise the meaning of their target concepts, within a theory of reference this method cannot be used to shift the meaning of the concept of reference. The reason for this is that intuitions of extension (...) in a theory of reference constitute a set of data that needs to be explained, while in most other philosophical theories they could either be abandoned in favor of intuitions of intension or serve as a criterion for the adequacy of the proposed definition of the target concept. This feature of a theory of reference is caused by the fact that an implicit understanding of what reference is in a theory of reference is usually assumed and is out of discussion. In effect, the claim in paradigmatic instances of the method of cases within a theory of reference does not concern whether an expression does or does not refer in particular cases, but rather what the reference of a certain expression is, and therefore it cannot be justified by intuitions of intension. (shrink)

The linguistic meaning of a word in a language is what fully competent speakers of the language have a grasp of merely in virtue of their semantic competence. The meanings of words sometimes change over time. ‘Meat’ used to mean ‘solid food’, but now means ‘animal flesh eaten as food’. This type of meaning change comes with change of topic, what we are talking about. Many people interested in conceptual engineering have claimed that there is also meaning change where topic (...) is retained. For example, they claim that the meanings of ‘fish’ and ‘pasta’ have undergone such change, and that the meaning of ‘marriage’ would change this way after gay marriages become legal and widely accepted. In this paper, I relate two sets of relatively independent literatures: mainstream philosophy of language and conceptual engineering to argue that on a plausible and widely accepted Minimalist view of meaning that is part and parcel of anti‐descriptivism, none of the above sorts of cases involve meaning change with topic retention. I do this by showing how to distinguish minimalism about meaning from the related theses of externalism and anti‐individualism about intension and how to separate meaning from intension in a way that allows meaning and topic to remain the same despite changes in intension. The larger lesson is that much like we should not disregard the boundary between the narrowly meaning‐related (‘semantics’) and the more broadly communication‐related (‘pragmatics’), and we should not disregard the boundary between the former and the more broadly thought‐related, conceptual or cognitive (‘cognition’). (shrink)

The aim of the paper is to determine the role of intuitions in Gettier cases. Critics of the Method of Cases argue that arguments developed within this method contains a premise that is justified by its intuitiveness; they also argue that intuitions are unreliable source of evidence. By contrast, Max Deutsch argues that this critique is unsound since intuitions do not serve as evidence for premises. In Gettier cases, an intuitive premise is justified by other arguments called G-Grounds. I propose (...) a different view on the role of intuition in Gettier cases. I introduce a distinction between concept-revision arguments and concept-application arguments. On the basis of this distinction and Craig’s and Spicer’s distinction between intuitions of intension and intuitions of extension, I show that (1) intuitions of extension do not serve as evidence for any G-Grounds; (2) intuitions of intension do play an evidential role for all G-Grounds, but (3) in the case of G-Grounds which are used as concept-application arguments, they are a poor source of evidence, while (4) in the case of G-Grounds used as concept-revision arguments, they could be a reliable source of evidence if they are intuitions of intension of a speaker immersed in philosophical discourse. (shrink)

A common objection to the very idea of conceptual engineering is the topic continuity problem: whenever one tries to “reengineer” a concept, one only shifts attention away from one concept to another. Put differently, there is no such thing as conceptual revision: there’s only conceptual replacement. Here, I show that topic continuity is compatible with conceptual replacement. Whether the topic is preserved in an act of conceptual replacement simply depends on what is being replaced (a conceptual tool or a conceptual (...) role) and what the topic under discussion is. Thus, the topic continuity problem only arises from a failure to specify these two things. (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)

New technologies are the source of uncertainties about the applicability of moral and morally connotated concepts. These uncertainties sometimes call for conceptual engineering, but it is not often recognized when this is the case. We take this to be a missed opportunity, as a recognition that different researchers are working on the same kind of project can help solve methodological questions that one is likely to encounter. In this paper, we present three case studies where philosophers of technology implicitly engage (...) in conceptual engineering (without naming it as such). We subsequently reflect on the case studies to find out how these illustrate conceptual engineering as an appropriate method to deal with pressing concerns in the philosophy of technology. We have two main goals. We first want to contribute to the literature on conceptual engineering by presenting concrete examples of conceptual engineering in the philosophy of technology. This is especially relevant, because the technologies that are designed based on the conceptual work done by philosophers of technology potentially have crucial moral and social implications. Secondly, we want to make explicit what choices are made when doing this conceptual work. Making explicit that some of the implicit assumptions are, in fact, debated in the literature allows for reflection on these questions. Ultimately, our hope is that conscious reflection leads to an improvement of the conceptual work done. (shrink)

On a representationalist view, conceptual engineering is the practice of changing the extensions and intensions of the devices we use to speak and think. But if this view holds true, conceptual engineering has a bad rationale. Extensions and intensions are not the sorts of things that are better or worse as such. A representationalist account of conceptual engineering thus falls prey to the objection that the practice has a bad rationale. To account for the assumption that conceptual engineering is worthwhile, (...) we propose to view what is being engineered as inferential devices, as opposed to representational devices. The objective is not to establish that being or having an inferential role is all there is to meaning or conceptual content. Rather, our agenda is to recommend a shift of focus from the representational features of content to the inferential features of content for the purposes of doing and thinking about conceptual engineering. Inferentialism about conceptual engineering makes better sense of the practice than a representationalist approach: In addition to accounting for the rationality of engaging in conceptual engineering, inferentialism provides a sound interpretation of what is at stake in concrete examples of conceptual engineering. (shrink)

This essay focuses on 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. I distinguish the sovereignty-based concern from other ethical worries about conceptual engineering and discuss how one might justify the relevant conceptual engineering projects despite the sovereignty-based reason against them. (shrink)

Is conceptual engineering feasible? Answering that question requires a theory of semantic change, which is sometimes thought elusive. Fortunately, much is known about semantic change as it occurs in the wild. While usage is chaotic and complex, changes in a word’s use can produce changes in its meaning. There are several under-appreciated empirical constraints on how meanings change that stem from the following observation: word use finely reflects equilibrium between various communicative pressures. Much of the relevant work in linguistics has (...) employed the methods of empirical pragmatics and diachronic semantics. In this way, the study of meaning change can be brought to bear on the conceptual engineer’s normative project. The picture that emerges tells against the sorts of engineering projects most likely to appeal to philosophers. Some may stand to succeed, but they have significantly different contours than the typical ones. (shrink)

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)

Ratio, Volume 34, Issue 4, Page 286-302, December 2021.

Conceptual engineering is thought to face an ‘implementation challenge’: the challenge of securing uptake of engineered concepts. But is the fact that implementation is challenging really a defect to be overcome? What kind of picture of political life would be implied by making engineering easy to implement? We contend that the ambition to obviate the implementation challenge goes against the very idea of liberal democratic politics. On the picture we draw, the implementation challenge can be overcome by institutionalizing control over (...) conceptual uptake, and there are contexts—such as professions that depend on coordinated conceptual innovation—in which there are good reasons to institutionalize control in this fashion. But the liberal fear of this power to control conceptual uptake ending up in the wrong hands, combined with the democratic demand for freedom of thought as a precondition of genuine consent, yields a liberal democratic rationale for keeping implementation challenging. (shrink)

Conceptual engineering is the method for assessing and improving our concepts. However, little has been written about how best to conceive of concepts for the purposes of conceptual engineering. In this paper, I aim to fill this foundational gap, proceeding in three main steps: First, I propose a methodological framework for evaluating the conduciveness of a given concept of concept for conceptual engineering. Then, I develop a typology that contrasts two competing concepts of concept that can be used in conceptual (...) engineering — namely, the philosophical and psychological ones. Finally, I evaluate these two concepts of concept using the proposed methodological framework and I show that, when it comes to making conceptual engineering an actionable method, the psychological concept of concept outclasses its philosophical counterpart on all counts. This provides a baseline from which the concept of concept can be further improved for the purposes of conceptual engineering. (shrink)

Conceptual engineering involves revising our concepts. It can be pursued as a specific philosophical methodology, but is also common in ordinary, non-philosophical, contexts. How does our capacity for conceptual engineering fit into human cognitive life more broadly? I hold that conceptual engineering is best understood alongside practices of conceptual exploration, examples of which include conceptual supposition (i.e., suppositional reasoning about alternative concepts), and conceptual comparison (i.e., comparisons between possible concept choices). Whereas in conceptual engineering we aim to change the concepts (...) we use, in conceptual exploration, we reason about conceptual possibilities. I approach conceptual exploration via the linguistic tools we use to communicate about concepts, using metalinguistic negotiation, convention-shifting conditionals, and metalinguistic comparatives as my key examples. I present a linguistic framework incorporating conventions that can account for this communication in a unified way. Furthermore, I argue that conceptual exploration helps undermine skepticism about conceptual engineering itself. (shrink)

It is largely assumed that conceptual engineering is essentially about revising, introducing, or eliminating representational devices, in particular the intension and extension of words and concepts. However, tying conceptual engineering too closely to representations is risky. Not everyone endorses the notion of representation as theoretically helpful or even real. Not everyone thinks that concepts or meanings should be understood in terms of the notion of representation. Does this mean that conceptual engineering is not interesting or relevant for these skeptics? In (...) this paper, I motivate and propose a non-representationalist construal of conceptual engineering. I argue that conceptual engineers can be understood as primarily engineering linguistic entitlements and commitments rather than representational devices. Note that this account is non-representationalist, but explicitly not anti-representationalist. Representations may play a significant role when it comes to justifying and completing commitment engineering projects. (shrink)

Conceptual engineering is the method for assessing and improving our representational devices. On its ‘broad‐spectrum’ version, it is expected to be appropriately applicable to any of our representation‐involving cognitive activities, with major consequences for our whole cognitive life. This paper is about the theoretical foundations of conceptual engineering thus characterised. With a view to ensuring the actionability of conceptual engineering as a broad‐spectrum method, it addresses the issue of how best to construe the subject matter of conceptual engineering and successively (...) defends the theses that conceptual engineering should be: (i) About concepts, (ii) psychologically theorised, (iii) as multiply realised functional kinds. Thereby, I claim to theoretically secure and justify the maximum scope, flexibility, and impact for the method of conceptual engineering on our representational devices in our whole cognitive life—in other words, a broad‐spectrum version of conceptual engineering. (shrink)

Every area of knowledge is based on a variety of products of conceptual engineering. This article is programmatic in essence: it aims at introducing a model of how conceptual engineering works and, particularly, how conceptual innovation is achieved in the context of theoretical inquiry. First, it describes the context in which the explicit study of the relevance, scope, mechanisms, and aims of conceptual engineering was born. Secondly, it introduces a distinction between evaluative and instrumental conceptual engineering based on the difference (...) between committed and instrumental conceptual use. According to this, it argues that both evaluative and instrumental conceptual engineering might be formally seen as the result of one function, which, provided a conceptual problem, maps to possible conceptual solutions generating success or failure values. Lastly, it introduces a third kind of conceptual engineering, namely, constructive conceptual engineering. Its core is a function that maps solutions to a representational space of non-considered alternatives, thus generating new conceptual content. In general, the proposed model offers a productive and novel field of inquiry on the conditions and factors that grounds theoretical innovation through conceptual engineering. (shrink)

Steffen Koch raises several objections to my critique of conceptual engineering. Here, I reply to these objections, arguing that Koch fails to adequately defend the “standard rationale” for conceptual engineering, and that the dilemma I have posed for “conceptual re-engineering”, a dilemma that presents this practice as either infeasible or else trivial, survives Koch’s objections unscathed. I conclude that conceptual engineering, both in terms of its conception and rationale, remains problematic.

Conceptual engineers seek to revise or replace the devices we use to speak and think. If this amounts to an effort to change what natural language expressions mean, conceptual engineers will have a hard time. It is largely unfeasible to change the meaning of e.g. ‘cause’ in English. Conceptual engineers may therefore seem unable to make the changes they aim to make. This is what I call ‘the implementation problem’. In this paper, I argue that the implementation problem dissolves if (...) we expand our view of how conceptual engineers could implement the products of their work. I describe four implementation options: Standing Meaning, Meaning Modulation, Speaker-Meaning and Different Language. I query the feasibility and worth of pursuing these options. Unless each option fails because it is unfeasible or not worthwhile, conceptual engineers do not face an implementation problem worth worrying about. I argue that some of the options are feasible and worthwhile, and therefore, that conceptual engineers do not face an implementation problem worth worrying about. (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)

Max Deutsch has recently argued that conceptual engineering is stuck in a dilemma. If it is construed as the activity of revising the semantic meanings of existing terms, then it faces an unsurmountable implementation problem. If, on the other hand, it is construed as the activity of introducing new technical terms, then it becomes trivial. According to Deutsch, this conclusion need not worry us, however, for conceptual engineering is ill-motivated to begin with. This paper responds to Deutsch by arguing, first, (...) that there is a third construal of conceptual engineering, neglected by him, which renders it both implementable and non-trivial, and second, that even the more ambitious project of changing semantic meanings is no less feasible than other normative projects we currently pursue. Lastly, the value of conceptual engineering is defended against Deutsch’s objections. (shrink)

The paper explores the relationship between conceptual engineering and the methodology of the Lvov-Warsaw School. While conceptual engineering is commonly seen as rooted in Rudolf Carnap's works and his method of explication, this paper argues that LWS predates and informs contemporary understanding of this methodology. The paper establishes that LWS not only engaged in but also systematically developed a method of conceptual revision aimed at enhancing clarity, precision, and coherence with specific theoretical frameworks. The analysis shows that LWS's approach to (...) concepts combined both descriptive and normative methodologies to improve and adapt philosophical concepts to better address actual phenomena and certain theoretical or practical needs. This method, described by LWS members as 'analysis and construction', parallels contemporary conceptual engineering practices, particularly its so-called 'narrow' understanding focused on revising existing concepts rather than on merely introducing new ones. By tracing the historical trajectory of conceptual engineering back to LWS, this paper provides a deeper understanding of its foundational strategies and suggesting that LWS's methodology could serve as a guide for current and future philosophical projects. (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 engineering is the method for assessing and improving our concepts. However, little has been written about how best to conceive of concepts for the purposes of conceptual engineering. In this paper, I aim to fill this foundational gap, proceeding in three main steps: First, I propose a methodological framework for evaluating the conduciveness of a given concept of concept for conceptual engineering. Then, I develop a typology that contrasts two competing concepts of concept that can be used in conceptual (...) engineering—namely, the philosophical and psychological ones. Finally, I evaluate these two concepts of concept using the proposed methodological framework and I show that, when it comes to making conceptual engineering an actionable method, the psychological concept of concept outclasses its philosophical counterpart on all counts. This provides a baseline from which the concept of concept can be further improved for the purposes of conceptual engineering. (shrink)

Conceptual engineering, motivated one natural way, involves the search for new concepts. But to what extent does conceptual engineering as practiced involve such conceptual innovation, and to what extent can it do so? In this paper, I first argue that conceptual engineering as practiced surprisingly does not appear to involve conceptual innovation, and then I discuss problems regarding the extent to which it can involve conceptual innovation.

Building on Wittgenstein’s ideas, I defend a brand of pluralism that associates words with conceptual families and appeals to this notion in the course of philosophical problem solving. I argue that certain problems that the received view of conceptual engineering (‘improvement by replacement’) faces can be more easily overcome if we adopt a pluralist perspective. I show that the proposed approach can circumvent the problem of topic discontinuity, whilst also avoiding the threat of trivialisation, since it can easily accommodate both (...) coarse-grained and fine-grained topics. Finally, I argue that my variant of pluralism is compatible with de novo conceptual engineering insofar as it allows that the paradigm associated with a word may shift overtime thus creating an opportunity for new candidate members to join a conceptual family. (shrink)

Conceptual engineering is the design, evaluation and implementation of concepts. Despite its popularity, some have argued that the methodology is not worthwhile, because the implementation of new concepts is both inscrutable and beyond our control. In the recent literature we see different responses to this worry. Some have argued that it is for political reasons just as well that implementation is such a difficult task, while others have challenged the metasemantic and social assumptions that underlie this skepticism about implementation. In (...) this paper, I argue that even if implementation is as difficult as critics maintain, there is at least one context in which conceptual engineering is extremely impactful and demonstrably so: the design of new technology. Different conceptions of control, freedom, trust, etc. lead to different designs and implementations of systems that are built to embed those concepts. This means that if we want to design for control, freedom, trust, etc., we have to decide which conception we ought to use. When we determine what the appropriate conception of a concept is in a technological context and use this conception to operationalize a norm or value, we generate requirements which have real-world effects. This not only shows that conceptual engineering can be extremely impactful, the fact that it leads to different design requirements means that we have a way to evaluate our conceptual choices and that we can use this feedback loop to improve upon our conceptual work By illustrating the direct impacts of different conceptions on technology design, this paper underscores the practical applicability and value of conceptual engineering, demonstrating how it serves as a crucial bridge between abstract philosophical analysis and concrete technological innovation. (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)