Why 'New Features' Is A Misnomer In Product Management

I want to push back on our recent decision to label the upcoming Q4 release as a feature set — it implies additionality that simply doesn't exist, and I think we need to reframe this.

The premise of this entire thread is built on a category error that nobody has bothered to call out yet, and it's undermining whatever legitimate critique of feature factories you were trying to make. When we say "new features," what are we actually measuring? Is it new lines of shipped code, new API endpoints, new UI components, or something else entirely? Because if the latter three aren't operationalized in a shared taxonomy before someone starts arguing about whether they count as "features," then every subsequent argument is just noise. I see people using "new features" to mean different things across this thread and pretending it's not happening. The honest move would be to define your atom of measure first, which no one has done here, and only after that can you make a claim about misnomers or anything else.