There’s this old word in product development: antifeature. In many ways, antifeatures are like features. You have to put effort into developing them, which means they cost real time and money, and take opportunity away from other improvements to your product. They exist because somebody wants them. And once they’re in your software, you’re maintaining them for a very long time.
The difference between a feature and an antifeature is that a feature adds customer benefit; something your marketing department is proud to put “on the box” (or really, on the website). It empowers the people who use your software. That empowerment fills them with pride; they can do things they couldn’t do before. They recommend your software to people like them who would become similarly awesome. They share tricks in their communities about how they did even more amazing things using your tools.
An antifeature removes customer benefit; it makes people worse off because they use your product. Typically these antifeatures get added because they protect revenue or make upselling easier; short-term benefits that ultimately make people less sticky. People take to social media to say “ugh”; your product isn’t enabling them, it’s getting in their way.
Your product manager had a good reason to plan the antifeature (actually, they probably did it because they saw their competitors doing it and thought it was normal). They want to “keep the honest people honest”. But that isn’t the message customers see. They see: we don’t trust you. We don’t want to make you the best version of yourselves. We put our interests before your own.
What does user empowerment look like? It looks like the freedom to define how they work, and how they use your software (and anyone else’s). It looks like respect for their privacy, dignity, security, and safety. It looks like putting your effort into helping them get better, not getting you better at their expense.
Think about how to make your customers the best versions of themselves they can be, and optimise for that.
