Abstract

According to Herman Cappelen’s Austerity Framework, conceptual engineering doesn’t involve concepts, and barely involves engineering. I begin by raising two objections to the Austerity Framework as it stands: the framework cannot account for important normative aspects of conceptual engineering; and it doesn’t give us an adequate response to Strawson-style objections that conceptual engineering serves only to change the subject. I then supplement the Austerity Framework with an account of semantic normativity, which builds on the speaker/semantic meaning distinction, and show that so-supplemented the Austerity Framework successfully overcomes the two objections. I tentatively conclude that semantic normativity should play a key role in how we understand conceptual engineering.