As long as you treat yourself as a pixel pusher, this is a side effect. When you understand that you are a mirror for ideas, you will empower yourself.
“Listen boss, I know you wanted me to create it in a certain way, but I am not a pixel pusher alright?! I am a mirror of ideas, so I made something completely different from what you pay me for, what do you mean I’m fired?”
If you say it that way, then yes, even the nicest person will call you a cunt and fire you. If you ask questions, as a user, and showing patterns that support your thesis, this becomes a conversation, rather than a “do it that way”.
edit: People are not all knowing. Once you start asking the right questions, you’ll see that - “Ok, and what happens when the user presses this? And what happens if they delete that?” It’s obviously a very abstract example, but if their ideas can’t stand a single user test, then they shouldn’t be surprised if the feature flops.
I agree in principle but when I’m building something I’m normally 3 - 5 people removed from the people who want it. It’s hard to push your ideas back through project managers, project engineers, program managers, presale engineers, contract managers, feed managers and then onto the actual company that asked you to implement the “solution”.
Developers don’t decide that. Blame UX folk for making things simple.
As a UX person often my job is to implement somebody else’s vision rather than being able to design something that makes sense.
As long as you treat yourself as a pixel pusher, this is a side effect. When you understand that you are a mirror for ideas, you will empower yourself.
“Listen boss, I know you wanted me to create it in a certain way, but I am not a pixel pusher alright?! I am a mirror of ideas, so I made something completely different from what you pay me for, what do you mean I’m fired?”
If you say it that way, then yes, even the nicest person will call you a cunt and fire you. If you ask questions, as a user, and showing patterns that support your thesis, this becomes a conversation, rather than a “do it that way”.
edit: People are not all knowing. Once you start asking the right questions, you’ll see that - “Ok, and what happens when the user presses this? And what happens if they delete that?” It’s obviously a very abstract example, but if their ideas can’t stand a single user test, then they shouldn’t be surprised if the feature flops.
I agree in principle but when I’m building something I’m normally 3 - 5 people removed from the people who want it. It’s hard to push your ideas back through project managers, project engineers, program managers, presale engineers, contract managers, feed managers and then onto the actual company that asked you to implement the “solution”.
I meant it a more general sense as anyone involved with the software development life cycle, but I see your point, good catch