←back to thread

324 points bilsbie | 1 comments | | HN request time: 0.2s | source
Show context
dcastonguay ◴[] No.44974574[source]
> At the end of it, they were sketching a completely different architecture without my "PMing". Because they finally understood who was actually using our product.

I cannot help but read this whole experience as: “We forced an engineer to take sales calls and we found out that the issue was that our PMs are doing a terrible job communicating between customer and engineering, and our DevOps engineer is more capable/actionable at turning customer needs into working solutions.”

replies(41): >>44974602 #>>44974635 #>>44974655 #>>44974660 #>>44974676 #>>44974814 #>>44974873 #>>44975042 #>>44975156 #>>44975182 #>>44975196 #>>44975269 #>>44975293 #>>44975666 #>>44975685 #>>44975856 #>>44975925 #>>44975972 #>>44976091 #>>44976207 #>>44976426 #>>44976440 #>>44976835 #>>44976924 #>>44977035 #>>44977052 #>>44977553 #>>44978517 #>>44978620 #>>44978689 #>>44979587 #>>44979694 #>>44979713 #>>44980051 #>>44980093 #>>44980149 #>>44980874 #>>44981249 #>>44981402 #>>44982096 #>>44982636 #
general1726 ◴[] No.44975856[source]
Or engineers are little bit full of themselves and know better how user should experience the product. If user is "holding the product wrong" it is a problem of a user and not a problem of stupid design, created by a person who knows in which order these buttons should be pressed. People around Desktop Linux could write a complete book about dismissing user's complaints.

The moment you have stubborn engineer who knows better than PM and user, it is really difficult to get anywhere. However if you will put such engineer into line of fire from a users that's suddenly not engineer's friendly PM trying to tell the engineer that this is wrong, these are frustrated people who would like to skin engineer alive as a punishment for using his "awesome" creations! That induces fear, but absolutely also crushes his ego, because somebody is berating product of engineer's genius like it would be a retarded hamster.

From my perspective, it is not about showing that PM is an idiot, it is about humbling your engineers. Their ego will grow again and this exercise will need to be repeated.

replies(11): >>44975950 #>>44976195 #>>44976313 #>>44976852 #>>44977055 #>>44979138 #>>44979256 #>>44980815 #>>44983195 #>>44985200 #>>44985785 #
sillywabbit ◴[] No.44976195[source]
God forbid an engineer should have an opinion on UI/UX.
replies(4): >>44976263 #>>44976505 #>>44978993 #>>44980155 #
neilalexander ◴[] No.44978993[source]
I have long believed that the biggest issue here is that engineers and power users generally have a much higher “pain threshold” when it comes to poor or complex UI/UX. They are not always the best people to judge how or if less experienced users will tolerate or adapt to those patterns. It’s fine to have opinions but they must be prepared for them to be challenged. Even better if they can invite others to challenge them, which is essentially what talking to your users achieves.
replies(2): >>44979274 #>>44979898 #
1. slipperydippery ◴[] No.44979898[source]
The two biggest causes of major UI problems I see are:

1) Exactly what you wrote: power users don’t even realize they clicked through five things in ten seconds any one of which would have derailed a weaker user, because they’re so used to bad UI that it’s almost invisible to them.

2) Zero care given to what’s most natural for the platform, for cost of development & maintenance, or what’s easiest for the user, when (bad) designers and (bad) “product folks” get involved and are way too into the wrong kinds of “consistency”, especially brand and cross-platform consistency (yo, I’m not sure it’s worth spending extra money fucking up contrast and platform norms on your inputs so your fucking radio buttons are “on brand” or whatever, like, I’m deeply skeptical of the actual business value of that kind of thing, though I can see the PowerPoint presentation value… and that’s why it happens)