UX is hard. What usually happens is that you have:
- developers who are bad at UX writing the software and improvising with all the use cases that were not adequately specified in the design document
- end users who are bad at UX giving their input, but can tell when something feels right for their use case
- managers/spec writers who are bad at UX and are trying to translate the wishes of end users to the developers
The result is a worthless spec, garbage in, garbage out.
Sometimes, when the stars align, in your team you get someone who is actually good at UX. I am told this happens, because in my career I have never seen such a unicorn. And even in that case, the end user with no understanding of UX, the one that actually pays for the project, might really, really want that periwinkle blue button, so in pretty much all cases GUIs get through countless rewrites and tweaks.
- developers who are bad at UX writing the software and improvising with all the use cases that were not adequately specified in the design document
- end users who are bad at UX giving their input, but can tell when something feels right for their use case
- managers/spec writers who are bad at UX and are trying to translate the wishes of end users to the developers
The result is a worthless spec, garbage in, garbage out.
Sometimes, when the stars align, in your team you get someone who is actually good at UX. I am told this happens, because in my career I have never seen such a unicorn. And even in that case, the end user with no understanding of UX, the one that actually pays for the project, might really, really want that periwinkle blue button, so in pretty much all cases GUIs get through countless rewrites and tweaks.