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”.
That’s a problem, I agree. I feel privileged then, because I actually get to research, and interview, and split test. It was a long battle, I’ve been trying to build that culture for a good 5+ years. Once the features started flopping, I started by doing 2 prototypes - one, based on the PRD from the product team and another, based on my personal research. I had to work 12, sometimes 15 hours a day, but when, instead of showing problems, I was showing solutions, without the “i-told-you-so”s, and when I made it clear that I care about the product’s health alone, that’s when I became the mirror. I reckon it’s not an industry term, but it’s what I like to call it - product presents their idea, you reflect it, and more often than not they do not like what they see. That’s when the real work starts.
I’m with you; I don’t like i-told-you-so, I like solutions.
I wasn’t saying you shouldn’t try, because you obviously should, i was just bitching about the difficulties I have in holding up the mirror.
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”.
That’s a problem, I agree. I feel privileged then, because I actually get to research, and interview, and split test. It was a long battle, I’ve been trying to build that culture for a good 5+ years. Once the features started flopping, I started by doing 2 prototypes - one, based on the PRD from the product team and another, based on my personal research. I had to work 12, sometimes 15 hours a day, but when, instead of showing problems, I was showing solutions, without the “i-told-you-so”s, and when I made it clear that I care about the product’s health alone, that’s when I became the mirror. I reckon it’s not an industry term, but it’s what I like to call it - product presents their idea, you reflect it, and more often than not they do not like what they see. That’s when the real work starts.
I’m with you; I don’t like i-told-you-so, I like solutions. I wasn’t saying you shouldn’t try, because you obviously should, i was just bitching about the difficulties I have in holding up the mirror.
I meant it a more general sense as anyone involved with the software development life cycle, but I see your point, good catch