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)

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)

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)

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 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)

In this paper, I argue that positions from the historical tradition of pragmatism can offer insights into the role that values play in ameliorative projects. By focusing on Sally Haslanger’s ameliorative project regarding gender, I will try to show how the Deweyan idea of the circuit provides a convincing understanding of the mutual interplay between values and conceptual revision within ameliorative approaches. I propose to understand this circuit as a process of articulation, through which our understanding of an initially vague (...) value becomes more detailed and fine-grained. To this end, I will focus on a specific aspect of Haslanger's recent intellectual production, namely the idea that ameliorative projects are inspired and organized by partially indeterminate values. In the final part of the paper, I will discuss a potential moral and political pitfall associated with ameliorative projects – i.e. the proliferation of cultural bubbles which are mutually exclusive and unable to communicate among themselves. This discussion addresses a further challenge for implementation, which is connected to the field of values, and not merely to the domain of concepts. (shrink)

Conceptual engineering is the method (or methods) via which we can assess and improve our concepts. Can conceptual engineering be usefully employed within analytic theology? Given that analytic theology and analytic philosophy effectively share the same philosophical toolkit then if conceptual engineering works well in philosophy then it ought to work well in analytic theology too. This will be our working hypothesis. To make good on this hypothesis, we first address two challenges. The first challenge makes conceptual engineering look to (...) be too inclusive; the second challenge makes it look to be too revolutionary (for analytic theology). To address these challenges, we propose a refined characterisation of conceptual engineering. We then turn to consider a number of case studies where analytic theology and conceptual engineering may fruitfully cooperate. These are: theological disagreements, inter-faith dialogue, meaning change, celibacy, AI, the name of God, and conceptual genealogy. (shrink)

In much of the current academic and public discussion, conspiracy theories are portrayed as a negative phenomenon, linked to misinformation, mistrust in experts and institutions, and political propaganda. Rather surprisingly, however, philosophers working on this topic have been reluctant to incorporate a negatively evaluative aspect when either analyzing or engineering the concept conspiracy theory. In this paper, we present empirical data on the nature of the concept conspiracy theory from five studies designed to test the existence, prevalence and exact form (...) of an evaluative dimension to the ordinary concept conspiracy theory. These results reveal that, while there is a descriptive concept of conspiracy theory, the predominant use of conspiracy theory is deeply evaluative, encoding information about epistemic deficiency and often also derogatory and disparaging information. On the basis of these results, we present a new strategy for engineering conspiracy theory to promote theoretical investigations and institutional discussions of this phenomenon. We argue for engineering conspiracy theory to encode an epistemic evaluation, and to introduce a descriptive expression—such as ‘conspiratorial explanation’—to refer to the purely descriptive concept conspiracy theory. (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)

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)

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)

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)

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)

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)

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

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)

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)

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.