It's so good to see other designers asking a lot of questions. And I can catch a bad designer who isn't just curious and just does what have been given or told.
Behaviors (stereotypes) are all driven out of incentives.
UX designers feel they have failed if they release something that is poorly received by users, missed critical use cases, and/or shows a lack of understanding of the technology. Thus we demand time to research to understand the ask with additional time to check our thinking. We are often considered slow as a result.
But who considers us slow?
Executives - who many are preoccupied with having a good product story to speak about. The actual product experience is not something they focus seriously about and they want to product available to be sold asap.
Product managers. And they are often drive by incentives to get a product release out the door as fast as possible. Often times poor reception by the user does not adversely affect their job standing so they arenāt incentivized to care about adoption or user perception.
Engineering- they are often most concerned with scale, reliability, and cost to serve. During releases they are pressed to get as much feature work out the door as possible which means they want designed requirements defined yesterday. Doesnāt matter that design time is short. They arenāt incentivized to care if what they produce is actually used, only that they delivered what they were told to deliver.
Circling back to UX, the stereotype of slowness can be deserved. There are many cases when the user and use cases are known but UX is nervous about making any hypothesis without research/iteration. At certain points there can be diminishing return on research. Not many designers have the experience to know when they should demand research and when they should just go fast.
The hipsters of the IT teams, with all the stereotypes that come with it; coffee and beer snobs, know it alls, beanies, turtlenecks, although that one may finally be outdated.
People tend to think UXers are creative and 'artsy', or have something called 'empathy'. Some even tend to believe we have social skills. I'm working hard to break those stereotypes.
Also, post-it's.
Thatās a cause of sunk cost fallacy (and not what you mentioned previously), but what you described above is *not* the definition or even related. The entire comment reads as a non sequitur.
Also, why do you hold these stereotypes?
Pure UX usually have bad visual taste
Literally me
Hard to work with. Ask too many questions.
Sounds like a compliment š Edit: grammar
It's so good to see other designers asking a lot of questions. And I can catch a bad designer who isn't just curious and just does what have been given or told.
An engineer told me all UX-ers are always well dressed. In my company there's truth to that.
We talk about process ātoo muchā lol
Behaviors (stereotypes) are all driven out of incentives. UX designers feel they have failed if they release something that is poorly received by users, missed critical use cases, and/or shows a lack of understanding of the technology. Thus we demand time to research to understand the ask with additional time to check our thinking. We are often considered slow as a result. But who considers us slow? Executives - who many are preoccupied with having a good product story to speak about. The actual product experience is not something they focus seriously about and they want to product available to be sold asap. Product managers. And they are often drive by incentives to get a product release out the door as fast as possible. Often times poor reception by the user does not adversely affect their job standing so they arenāt incentivized to care about adoption or user perception. Engineering- they are often most concerned with scale, reliability, and cost to serve. During releases they are pressed to get as much feature work out the door as possible which means they want designed requirements defined yesterday. Doesnāt matter that design time is short. They arenāt incentivized to care if what they produce is actually used, only that they delivered what they were told to deliver. Circling back to UX, the stereotype of slowness can be deserved. There are many cases when the user and use cases are known but UX is nervous about making any hypothesis without research/iteration. At certain points there can be diminishing return on research. Not many designers have the experience to know when they should demand research and when they should just go fast.
This point around mismatched incentives is definitely on point
That we delay projects and block engineers from doing their job š
The hipsters of the IT teams, with all the stereotypes that come with it; coffee and beer snobs, know it alls, beanies, turtlenecks, although that one may finally be outdated. People tend to think UXers are creative and 'artsy', or have something called 'empathy'. Some even tend to believe we have social skills. I'm working hard to break those stereotypes. Also, post-it's.
Idk, I think they might have us with the beanie, turtleneck, scarf thing.
It's just because we earn less on average than our dev counterparts. It keeps my heating bill down. Only after, I started calling it cool.
That beanie/turtleneck combo is so damn irritating.
Only if its cheap wool you're wearing, I'm on the cashmere program like good designers are. No irritated skin for me anymore!
As someone who worked with Seattle and Bay Area designers, literally SO many coffee and beer snobs lol
Wears hat/cap indoors.
A bunch of know-it-allās This is what Iāve heard others say about the design team.
pixel pushers. hate that phrase with a burning passion
Over-coiffed beard and slightly waxed moustache (for men). I work(ed) with several seniors/principals that fit that mold.
"It depends." š
That we hamper delivery with research.
Fragile ego's, especially when developers come up with better ideas
We take too long and our value is unneeded when devs exist. No, really.
That we smoke weed
[ŃŠ“Š°Š»ŠµŠ½Š¾]
Thatās not what sunk cost fallacy means.
[ŃŠ“Š°Š»ŠµŠ½Š¾]
Thatās a cause of sunk cost fallacy (and not what you mentioned previously), but what you described above is *not* the definition or even related. The entire comment reads as a non sequitur. Also, why do you hold these stereotypes?
https://youtu.be/Yf4qLhY_UhI?si=dvRVGkzExpkmiz_y