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)

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)

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)

This paper argues for explanatory eliminativism about topics (and cognates, such as subject matters) relative to the domain of conceptual engineering. It has become usual to think that topics serve an important explanatory role in theories of conceptual engineering, namely, to determine the limits of revision. I argue, first, that such limits can be understood either as thenormative limitspertaining to the justification of conceptual engineering, as themetaphysical limitspertaining to the identity of the concepts in question, or as theterminological limitspertaining to (...) usage of the original terminology. Second, I argue that the metaphysical reading is disputable as a theory of concepts and inconsequential for conceptual engineers, and that neither of the two leading accounts of topics that have been presented in the literature—the samesaying account and functionalism—determine the limits of revision in either of the two remaining senses. In the absence of more promising competitors, I conclude that there is no theoretical role for topics to play in theories of conceptual engineering. An upshot of my argument is that conceptual engineers should stop worrying about things like topic (dis)continuity, and instead shift their attention to the issues that really matter for justifying conceptual revisions or replacements, making terminological choices, and underpinning conceptual engineering with a theory of concepts. (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 projects have been criticized for creating discontinuities of subject-matter and, as a result, discontinuities in inquiries: call this the Change of Subject objection. In this paper, I explore a way of dealing with the objection that clarifies its scope and eventually downplays it. First, two strategies aimed at saving subject-continuity are examined and found wanting: Herman Cappelen’s appeal to topics, and the account in terms of concept function. Second, the idea is introduced that one can begin an object-level (...) inquiry either with a ‘semantically conservative’ approach, whereby semantic change is not permitted, or with a ‘semantically progressive’ approach, whereby semantic change is permitted. This distinction helps one significantly downplay the Change of Subject objection. (shrink)

Conceptual engineering is the method for assessing and improving our concepts. Some have recently claimed that the implementation of such method in the form of ameliorative projects is truth-driven and should thus be epistemically constrained, ultimately at least (Simion 2018; cf. Podosky 2018). This paper challenges that claim on the assumption of a social constructionist analysis of ideologies, and provides an alternative, pragmatic and cognitive framework for determining the legitimacy of ameliorative conceptual projects overall. The upshot is that one should (...) not ameliorate for the sake of truth or knowledge, in the case of ideologies—at least, not primarily. (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)

In 2015, ‘marriage’ was redefined in the United States to include same-sex couples. In conceptual engineering, this is often assumed to be a paradigm case of Sally Haslanger’s (2020a, 2020b) semantic amelioration. Semantic amelioration changes a concept’s content to make it better. In the case of [MARRIAGE], [MARRIAGE]’s content was broadened to include same-sex couples – which, many contend, made it morally better. Semantic amelioration faces the following challenge, however: Doesn’t changing a concept’s content ‘change the subject?’ By broadening [MARRIAGE]’s (...) content to include same-sex couples in 2015, didn’t we replace [MARRIAGE] with a new concept that sounds and looks like [MARRIAGE] but nevertheless isn’t [MARRIAGE] – something like, [MARRIAGE*]? This is the topic continuity problem (TCP). Here, TCP assumes content essentialism about concepts, i.e., that a concept’s content is essential to it. Thus, since semantic amelioration changes concepts’ contents to make them better, semantic amelioration necessarily replaces concepts, according to this version of TCP. Haslanger recently resists this notion, however. Instead of embracing content essentialism about concepts, Haslanger embraces functional essentialism about concepts – that a concept’s function is essential to it. And since semantic amelioration leaves a concept’s function unchanged, Haslanger denies that semantic amelioration is conceptual replacement. In this paper, I argue that Haslanger’s functional essentialism integrally links concepts’ functions to their contents, such that changing a concept’s content requires changing its function, on Haslanger’s account. Therefore, semantic amelioration still replaces concepts even on Haslanger’s functional essentialism. I think this is avoided, however, if we incorporate Amie Thomasson’s (2020) recent work on concepts into Haslanger’s. Combining Thomasson’s work with Haslanger’s yields a new functional essentialism about concepts – called proper functional essentialism. Proper functional essentialism allows that some functional changes in concepts don't replace them, and hence, it perhaps reveals how to actually not change the subject in semantic amelioration. (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)

Conceptual engineering projects are sometimes criticized for ‘changing the subject’. In this paper, I first discuss three strategies that have been proposed to address the change of subject objection. I notice that these strategies fail in similar ways: they all deploy a ‘loose’ notion of subject matter, while the objector can always reply deploying a ‘strict’ notion. Based on this, I then argue that at least current formulations of the change of subject objection (together with the response strategies just mentioned), (...) create an overall defective dialectic, whereby no progress can be made on either side. After considering how such defective dialectic could be (at least partly) fixed, it is concluded that current formulations of the change of subject objection may be dismissed on dialectical grounds, even though some practical lessons may still be retained from the objection. (shrink)

The focus of this paper will be to examine the implications that a “practical” approach to conceptual engineering might have for the “traditional” conception of philosophy as uncovering truths about phenomena of philosophical interest. In doing so, I will be building on the ideas of a figure that many take to be the first major philosopher to write on conceptual engineering: Rudolf Carnap. Though the current wave of interest in conceptual engineering goes back less than a decade, many conceptual engineers (...) have found precedent for their views in Carnap’s characterization of what he called “explication.” Interestingly, however, not nearly as much attention has been paid to another Carnapian thesis which seems to me to have deep relevance to methodological questions about conceptual engineering. I have in mind here the distinction between internal and external questions proposed in “Empiricism, Semantics and Ontology” (1950b) and the accompanying claim that external questions lack cognitive content and can be cogently approached only as a matter of pragmatic decision-making. This is the aspect of Carnap’s views upon which I propose to build. I'll first make the case that there is a suggestive similarity between Carnap’s claim that external questions are matters of pragmatic choice and the practical conceptual engineer’s claim that engineering success should be characterized in terms of suitability to a function or purpose. After that, I'll look at potential worries about the Carnapian distinction—including, e.g., the concern that it relies on the analytic/synthetic distinction. Finally, I will propose a somewhat modified and expanded version of the distinction and examine its consequences for the thesis that philosophy aims at discovering truths about phenomena of philosophical interest. (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)

Philosophy strives to give us a firmer hold on our concepts. But what about their hold on us? Why place ourselves under the sway of a concept and grant it the authority to shape our thought and conduct? Another conceptualization would carry different implications. What makes one way of thinking better than another? This book develops a framework for concept appraisal. Its guiding idea is that to question the authority of concepts is to ask for reasons of a special kind: (...) reasons for concept use, which tell us which concepts to adopt, adhere to, or abandon, thereby shoring up—or undercutting—the reasons for action and belief that guide our deliberations. Traditionally, reasons for concept use have been sought either in timeless rational foundations or in concepts’ inherent virtues, such as precision and consistency. Against this, the book advances two main claims: that we find reasons for concept use in the conceptual needs we discover when we critically distance ourselves from a concept by viewing it from the autoethnographic stance; and that sometimes, concepts that conflict, or exhibit other vices such as vagueness or superficiality, are just what we need. By considering not what concepts are absolutely best, but what concepts we now need, we can reconcile ourselves to the contingency of our concepts, determine the proper place of efforts to tidy up thought, and adjudicate between competing conceptions of things—even things as contested as liberty or free will. A needs-based approach separates helpful clarification from hobbling tidy-mindedness, and authoritative definition from conceptual gerrymandering. (shrink)

Conceptual engineering is the process of assessing and improving our conceptual repertoire. Some authors have claimed that introducing or revising concepts through conceptual engineering can go as far as expanding the realm of thinkable thoughts and thus enable us to form beliefs, hypotheses, wishes, or desires that we are currently unable to form. If true, this would allow conceptual engineers to contribute to solving stubborn problems – problems that cannot be solved with our current ways of thinking. We call this (...) kind of conceptual engineering heavy-duty conceptual engineering. As exciting as the idea of heavy-duty conceptual engineering sounds, it has never been developed or defended. In this paper, we pursue a two-fold goal. First, to offer a theory of heavy-duty conceptual engineering that distinguishes it from other kinds of conceptual engineering; second, to show that heavy-duty conceptual engineering is possible, both in theory and in practice, and to explain how it can be applied in the service of solving stubborn problems. The central idea is that heavy-duty conceptual engineering can enhance the semantic expressive power of a conceptual system by the use of bootstrapping processes. (shrink)

This contribution focuses on what type of question “Are mental disorders brain disorders?” is and what task Anneli Jefferson performs in her book with the same title. I distinguish between conceptual engineering and conceptual choice, the former involving the individuation of an adequate concept for a specific goal, and the latter involving the normative problem of whether we should employ the concept at hand. I contend that Anneli Jefferson’s book is a work of conceptual engineering, which is valuable in and (...) of itself, but that this is insufficient to answer an equally essential version of the question, “Are mental disorders brain disorders?”, namely, whether we should adopt the newly engineered concept or not, considering a broader range of goals for mental health research and practice. (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)

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)

Conceptual engineering takes a distinctively normative and reconstructive approach to our conceptual repertoire. This approach is congenial to the ideas defended by philosophers belonging to the multifaceted tradition of American and Cambridge Pragmatism. This special issue is devoted to the investigation and development of these connections. Our introduction maps some of the historical and theoretical entanglements between the two fields and gives a short overview of the contributions to the special issue.

Politicians and engineers are increasingly realizing that values are important in the development of technological artefacts. What is often overlooked is that different conceptualizations of these abstract values lead to different design-requirements. For example, designing social media platforms for deliberative democracy sets us up for technical work on completely different types of architectures and mechanisms than designing for so-called liquid or direct forms of democracy. Thinking about Democracy is not enough, we need to design for the proper conceptualization of these (...) values. As we see it, we cannot responsibly engineer and innovate and shape technology in accordance with our moral values without engaging in systematic and continuous conceptual engineering: This is not only an academic, or theoretical issue, it is also not simply an issue for public policy or politics, or regulators, it has become a central problem for engineering and the world of technology. In this paper, we present a framework for doing the necessary conceptual work in the context of requirement engineering. We draw on the literature on conceptual engineering to lay out a methodology to (1) assess different conceptions and (2) to develop new conceptions. Moreover, we integrate this methodology with extant approaches in the philosophy of technology which aim at designing technological artefacts ethically. In the final section we apply this integrated framework to freedom in the context of social media networks. (shrink)

Abstract“Freedom” is a fundamental political concept: contestations or endorsements of freedom-conceptions concern the fundamental normative orientation of sociopolitical orders. Focusing on “freedom,” this article argues that the project of bringing about emancipatory sociopolitical orders is both aided by efforts at engineering fundamental political concepts as well as required by such ameliorative ambitions. I first argue that since the absence of ideology is a constituent feature of emancipatory orders, any attempt at bringing about emancipation should leverage genealogical approaches in order to (...) debunk existing ideological freedom-concepts, which can occur only by exposing the discursive functions these have come to serve for the (re-)production of dominant power relations. I then suggest that establishing and sustaining an alternative, ideology-free conception of “freedom” is a steeper task. Ensuring widespread uptake of any ameliorated concept is contingent on effective change in the relevant social environment. Where fundamental political concepts such as “freedom” are concerned, effective intervention in the relevant social environment requires radical sociopolitical change. But if such change can be brought about and enables the widespread uptake of an “improved” freedom-concept, the concept's content comes to reflect changed social facts, thereby stabilizing the particular emancipatory sociopolitical order which has newly arisen. (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)

I argue that the story of God’s commanding Abraham to sacrifice Isaac can be read as a variant of Kavka’s (1983) Toxin Puzzle. On this reading, Abraham has no reason to kill Isaac, only reason to intend to kill Isaac. On one version of the Kavkan reading, it’s impossible for Abraham, thus situated, to form the intention to kill Isaac. This would make the binding an impossible story: I explore the ethical and theological consequences of reading the story in this (...) way. Finally, I suggest that analytic philosophers may have more to contribute to interpretive projects in philosophical theology than generally practiced. (shrink)

In this paper, I identify a central problem for conceptual engineering: the problem of showing concept-users why they should recognise the authority of the concepts advocated by engineers. I argue that this authority problem cannot generally be solved by appealing to the increased precision, consistency, or other theoretical virtues of engineered concepts. Outside contexts in which we anyway already aim to realise theoretical virtues, solving the authority problem requires engineering to take a functional turn and attend to the functions of (...) concepts. But this then presents us with the problem of how to specify a concept’s function. I argue that extant solutions to this function specification problem are unsatisfactory for engineering purposes, because the functions they identify fail to reliably bestow authority on concepts, and hence fail to solve the authority problem. What is required is an authoritative notion of conceptual function: an account of the functions of concepts which simultaneously shows why concepts fulfilling such functions should be recognised as having authority. I offer an account that meets this combination of demands by specifying the functions of concepts in terms of how they tie in with our present concerns. (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)

Debate over the normativity of virtual phenomena is now widespread in the philosophical literature, taking place in roughly two distinct but related camps. The first considers the relevant problems to be within the scope of applied ethics, where the general methodological program is to square the intuitive (im)permissibility of virtual wrongdoings with moral accounts that justify their (im)permissibility. The second camp approaches the normativity of virtual wrongdoings as a metaphysical debate. This is done by disambiguating the ‘virtual’ character of ‘virtual (...) wrongdoings’. Doing so is supposed to provide illuminating ontological distinctions that inform ethical aspects of the debate. We argue that each approach faces its own set of issues, and as a result, motivates consideration of an alternative. The alternative we suggest turns inquiry concerning the normativity of virtual wrongdoings into a distinctively conceptual question. Rather than asking whether some action is right or wrong, or whether some virtual phenomenon counts as a particular action at all, we argue that research into the normativity of virtual wrongdoings may be guided by reflecting on whether a concept that originated and developed within a non-virtual context should be exported into a foreign virtual domain. We consider this approach and several objections. (shrink)

This paper argues for explanatory eliminativism about topics (and cognates, such as subject matters) relative to the domain of conceptual engineering. It has become usual to think that topics serve an important explanatory role in theories of conceptual engineering, namely, to determine the limits of revision. I argue, first, that such limits can be understood either as thenormative limitspertaining to the justification of conceptual engineering, as themetaphysical limitspertaining to the identity of the concepts in question, or as theterminological limitspertaining to (...) usage of the original terminology. Second, I argue that the metaphysical reading is disputable as a theory of concepts and inconsequential for conceptual engineers, and that neither of the two leading accounts of topics that have been presented in the literature—the samesaying account and functionalism—determine the limits of revision in either of the two remaining senses. In the absence of more promising competitors, I conclude that there is no theoretical role for topics to play in theories of conceptual engineering. An upshot of my argument is that conceptual engineers should stop worrying about things like topic (dis)continuity, and instead shift their attention to the issues that really matter for justifying conceptual revisions or replacements, making terminological choices, and underpinning conceptual engineering with a theory of concepts. (shrink)

This article argues against the term and concept of ‘hate speech’ and in favour of using the concept and term ‘discriminatory speech’. ‘Hate speech’ is a misnomer; we should name the harmful speech in question by what it in fact does: it discriminates. The article argues for this conceptual replacement claim by identifying a number of functions the concept ‘hate speech’ has been meant to serve and by arguing that extant concepts of hate speech have not served this function well. (...) Roughly, they do not serve the functions well because of five properties of hate speech: hate centricity, perpetrator centricity, intention centricity, emotion centricity, and individual centricity. The article then proposes a definition of discriminatory speech and argues that it fulfils the conceptual functions better. (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 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)

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)

The advent of intelligent artificial systems has sparked a dispute about the question of who is responsible when such a system causes a harmful outcome. This paper champions the idea that this dispute should be approached as a conceptual engineering problem. Towards this claim, the paper first argues that the dispute about the responsibility gap problem is in part a conceptual dispute about the content of responsibility and related concepts. The paper then argues that the way forward is to evaluate (...) the conceptual choices we have, in the light of a systematic understanding of why the concept is important in the first place—in short, the way forward is to engage in conceptual engineering. The paper then illustrates what approaching the responsibility gap problem as a conceptual engineering problem looks like. It outlines argumentative pathways out of the responsibility gap problem and relates these to existing contributions to the dispute. (shrink)

The function of concepts must be taken seriously to understand the scientific practices of developing and working with concepts. Despite its significance, little philosophical attention has been paid to the function of concepts. A notable exception is Brigandt (2010), who suggests incorporating the epistemic goal pursued with the concept’s use as an additional semantic property along with the reference and inferential role. The suggestion, however, has at least two limitations. First, his proposal to introduce epistemic goals as the third component (...) of concepts lacks independent grounding, except to account for the rationality of semantic change (the Grounding Problem). Second, it is hardly justified to consider epistemic goals as a semantic property (the Misplacement Problem). To remedy these predicaments, we suggest a new perspective that takes concepts as cognitive entities with a 2-layered structure rather than as merely linguistic entities and develop an account of the function of concepts. We provide empirical evidence showing that functional information affects our cognitive processes. It is claimed that the function of concepts is not a semantic property but a type of meta-information regulating a body of concept-constitutive information. (shrink)

Philosophers interested in conceptual engineering take it for granted that the same concept can unproblematically play diverse functions, but this view overlooks the fact that conceptual and functional change often impair concepts and even functions themselves. I demonstrate that while conceptual and functional engineering may improve concepts and functions, they can also produce detrimental effects. Therefore, it is crucial to carefully assess the potential benefits or problems before making any modifications. Frequently, we overlook the fact that, for instance, adding extra (...) functions to our concepts modifies them; this may increase, but also impair, their theoretical and practical efficacy. I analyze and clarify these possibilities through a general classificatory framework encompassing concepts, functions, and conceptual and functional change. The larger aim of this paper is to bring attention to these complex and under-researched relationships and pave the way for further research in this area. (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)

Philosophy and Phenomenological Research, EarlyView.

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)

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