3 ms·
Venting out a bit of past frustration, I would rename the title to "why people suck at explaining desired UX to software developer". A kitchen designer won't b
by anticristi 6y ago
Venting out a bit of past frustration, I would rename the title to "why people suck at explaining desired UX to software developer".
A kitchen designer won't be able to guess how you want your kitchen. It's my task as a customer to explain if I want a double sink, how big the induction stove etc. Why do people then expect software developers to magically guess intended UX?
Seriously, I asked people to draw me on paper a few pages of a webapp. It was pointless. I ended up making a bad UX, on purpose, just to get the conversation started.
- AndrewDucker 6y agoA good kitchen designer should be able to ask a few questions to get you started, know what combinations of things go together, etc. The user is not the designer. They don't know what makes good design.
- interestica 6y agoThey'll know what they want but not where or how they want it. It might just be "a sink" and the competent designer will find out about their usage patterns to know number of sinks, size, style, colour, depth, faucet type -- and have it work within the constraints of the space. ...while also aware of the macro organization of the space itself.