As an example, consider a product manager that decides to remove a previously planned feature that one or more people have spent considerable effort working towards. If they can discuss the benefit of keeping the feature (or the cost associated with dropping it) then they stand a better chance of a favorable outcome than if they discuss in terms of how the product manager made them feel.
While I think people are right to have feelings I think they are more likely to achieve the outcome they want if they can understand and express why they feel that way. This is assuming that they are conscientious workers which is the more common case. If they are bonkers then they probably won't be able to pin down a sensible root cause.
As long as it doesn't affect the health of the codebase or force the engineers to work overtime, why do the engineers care about what features get shipped or not? They're paid to code, so if they aren't sacrificing code quality or working overtime they should just focus on coding features that may or may not get shipped. I mean, if we're being strictly objective that is.
If the engineers have feelings they might feel dismissed and devalued if they spend time and effort making features nobody will ever see.
While I think people are right to have feelings I think they are more likely to achieve the outcome they want if they can understand and express why they feel that way. This is assuming that they are conscientious workers which is the more common case. If they are bonkers then they probably won't be able to pin down a sensible root cause.