![Client requests vs the user experience [Piterskii Punk]](https://lemmy.world/pictrs/image/75980dc9-ffd7-4d2e-b583-f044b9708af0.jpeg){kind=link}
- cross-posted to:
- nonpolitical_memes
- cross-posted to:
- nonpolitical_memes
(I can’t find the artist’s webpage to link to, just some credits saying that this might be a translated Russian comic posted by Piterskii Punk)
(I can’t find the artist’s webpage to link to, just some credits saying that this might be a translated Russian comic posted by Piterskii Punk)
I was gonna say, clients aren’t the only ones.
Feels like a lot of developers and especially UX designers have a bad habit of disappearing up their own asshole nowadays.
It’s a reason why sometimes an open source project manages to be way better than a comparatively well resourced commercial offering. When the developers are the users, they will get the nuance of things.
Works well for a lot of “power user” software where the users are either developers, or at least similar mindset as a developer. Sometimes open source doesn’t deal too well with making things simple without power user features that casual users may find confusing or distracting.
In my experience developing In-House custom software it’s more “Managers” and “End-users”: basically the requirements for the software that’s developed are defined by the manager overseeing an area and hence based on their point of view of the business process they oversee, which is often not at all the same point of view as the people working in that process.
I’ve seen again and again software being made exactly to the spec provided by team/area management and then turning out to have lots of problems for the actual users to use.
In my experience the best results come from having the developers talk directly with the end-users, even if the language the devs tend to speak and their preconceptions at first don’t match those of the end-users.