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)

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)

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 (CE) is thought to be generally aimed at ameliorating deficient concepts. In this paper, we challenge this assumption: we argue that CE is frequently undertaken with the orthogonal aim of _conceptual adaptation_. We develop this thesis with reference to the interplay between technology and concepts. Emerging technologies can exert significant pressure on conceptual systems and spark ‘conceptual disruption’. For example, advances in Artificial Intelligence raise the question of whether AIs are agents or mere objects, which can be construed (...) as a CE question regarding the concepts AGENT and OBJECT. We distinguish between three types of conceptual disruption (conceptual gaps, conceptual overlaps, and conceptual misalignments) and argue that when CE occurs to address these disruptions, its primary aim is not to improve concepts, but to retain their functional quality, or to prevent them from degrading. This is the characteristic aim of CE when undertaken in philosophy of technology: to _preserve_ the functional role of a concept or conceptual scheme, rather than _improving_ how a concept fulfills its respective function. (shrink)

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)

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)

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)

Recent work on philosophy of technology emphasises the ways in which technology can disrupt our concepts and conceptual schemes. We analyse and challenge existing accounts of conceptual disruption, criticising views according to which conceptual disruption can be understood in terms of uncertainty for conceptual application, as well as views assuming all instances of conceptual disruption occur at the same level. We proceed to provide our own account of conceptual disruption as an interruption in the normal functioning of concepts and conceptual (...) schemes. Moreover, we offer a multilevel taxonomy thereof, where we distinguish between instances of conceptual disruptions occurring at different levels (conceptual scheme, conceptual clusters, and individual concepts), taking on different forms (conceptual gaps and conceptual conflicts), and leading to different degrees of severity (extending from mild to severe). We also provide detailed accounts through historical examples of how conceptual gaps and conceptual conflicts can occur at different times in the very same process of conceptual disruption. Finally, we make the case that different kinds of conceptual engineering can provide meaningful ways to assess and overcome distinct types of conceptual disruption. (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)

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)

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)