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)

This paper explores the question: What would conceptual engineering have to be in order to promote social justice? Specifically, it argues that to promote social justice, conceptual engineering must deliver the following: it needs to be possible to deliberately implement a conceptual engineering proposal in large communities; it needs to be possible for a conceptual engineering proposal to bring about change to extant social categories; it needs to be possible to bring a population to adopt a conceptual engineering proposal for (...) the right reasons; and it needs to be possible to do – without producing harmful consequences. I show that, of the three dominant approaches to conceptual engineering in the literature, only one of them seems amenable to the idea that it is possible and legitimate to promote social justice in accordance with –. (shrink)

It is fundamental that, in philosophy, we make sure that we are not mistaking merely verbal disputes, or “conceptual” disputes, for substantive ones. This essay presents a tripartite framework that is useful for clarifying cases where it is difficult to tell whether we are engaged in substantive or non-substantive disputes. For this purpose, the essay offers some combinatorial possibilities between the following levels: verbal, conceptual, and objectual. We need to distinguish whether we are arguing about the world, concepts, or words (...) to avoid talking at cross-purposes and to recognize when our disputes are not worth the time. Distinguishing between these three levels can also throw light and guide research on conceptual engineering, metalinguistic negotiations, metaontology, and so on. (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)

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)

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)

Open texture is a kind of semantic indeterminacy first systematically studied by Waismann. In this paper, extant definitions of open texture will be compared and contrasted, with a view towards the consequences of open-textured concepts in mathematics. It has been suggested that these would threaten the traditional virtues of proof, primarily the certainty bestowed by proof-possession, and this suggestion will be critically investigated using recent work on informal proof. It will be argued that informal proofs have virtues that mitigate the (...) danger posed by open texture. Moreover, it will be argued that while rigor in the guise of formalisation and axiomatisation might banish open texture from mathematical theories through implicit definition, it can do so only at the cost of restricting the tamed concepts in certain ways. (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)

Philosophy and Phenomenological Research, EarlyView.

The article reveals the pragmatic implications of Herman Cappelen’s account of ‘topics’ in his contribution to the conceptual engineering literature. I show that Cappelen’s introduction of the category of ‘topics’ serves the pragmatic goal of having a convenient handle to account for ‘continuity in revision’, and that his general insistence on ‘continuity’ is motivated morally and strategically. In asking what accounts for continuity, Cappelen’s ‘topics’ are not defined by content or any other fixed set of rules or criteria. Topics are (...) metaphysically lightweight and defined pragmatically and as we go: speakers talk about the same topic when we (and they) attribute that they do. But why should we do that? Why should we aim for continuity and why should we think it is possible in general? I contrast Cappelen’s insistence on continuity with Rorty’s appeal for discontinuity, and trace both of their positions back to their respective moral background assumptions and their assumptions about what communication is (and is for) and, in turn, what philosophy is (and is about). Further, I question the role the ‘continuity’ claim plays in the current redefinition of linguistic philosophy after the ‘death of the linguistic turn’. (shrink)

Critical discussions can often require conceptual engineering, a process in which speakers are engaged in revising each other’s concepts. We show that the analysis of conceptual engineering can benefit from integrating argumentation theory with models of conceptual representation. Argumentation theory accounts for the argumentative moves of the discussants, allowing the detection of speakers’ conceptual disagreements, for which some fallacies can be seen as cues. Models of conceptual representation, such as Conceptual spaces and the theory of meeting of minds, allow us (...) to study the cognitive side of engineering practices. However, when this integrated framework is applied to practical scenarios, conceptual engineering faces different challenges. In particular, assuming a psychological view about concepts, revisionary strategies are significantly narrowed down, if not impossible, in practice. These criticisms lead to a kind of dilemma for conceptual engineers, highlighting the necessity of further work on the definition of concept embraced by this research program. (shrink)

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)