Well, that's the thing, it's often the case that whilst the client is supposedly doing it for their users, in practice it's not and is doing it for other reasons.

Mind you, I think that is more common when the software is being developed for a client which is basically a Manager in the same company as the users of the software (for example in In-house Development or Consultancy work developing a solution for a company) were in the absence of the very clear pressure vector which is the customers not buying the product (internal end-users are almost never given a choice to use or not that software, though they can at times informally boycot software they think hinders their work and get the project killed) things are often designed for the Manager rather than for the Users.

(Note that this is not necessarily done in a knowing purposeful way: it's just that when it's some external manager providing the requirements to the developers for the software being made for the area that managers overseens - though sometimes it's even more indirect - things tend to be seen from the perspective of said manager not the end-users, hence designed to match how that manager sees things and thinks things work, which is often different from how the actual users see things. This cartoon perfectly illustrates that IMHO - it looks fine for the "manager" whilst looking quite different for the "end-user").

Even is B2C you see that: notice the proliferation of things like Microtransactions in Games, which are hardly the kind of thing gamers - who are the end-users of games - wanted to have but which definitelly the management of the big Publishers wanted.