3 ms·

If you have concerns about UX I'd have thought you should be commenting at the design level rather than leaving it until things have got to the stage where they

If you have concerns about UX I'd have thought you should be commenting at the design level rather than leaving it until things have got to the stage where they've been developed to the point where there's HTML to talk about.

tosbourn 4y ago
The "U" part is hard to talk about without actual users using it though. Which is hard to do pre-html.
ChrisMarshallNY 4y ago
In my experience, this doesn’t work. It’s always in everyone’s “In a perfect world” plans, but no one ever seems to have much to say, in the beginning. Even technically-proficient major stakeholders (for example, managers and testers) seldom offer much in the way of feedback, early in the project. I have learned to write my applications in a manner that affords “hands-on” testing, as early as possible, and I use techniques that allow a lot of pivoting. I wrote the following comment, in an earlier thread[0] where I discuss this approach. [0] https://news.ycombinator.com/item?id=32153234 https://news.ycombinator.com/item?id=32153234
- onion2k 4y ago
  I have learned to write my applications in a manner that affords “hands-on” testing, as early as possible I think we agree in principle. I prefer using design tools that offer 'interactive' previews like Figma, but the idea is the same - get feedback from stakeholders as early as possible.
solardev 4y ago
Nobody really knows this stuff. If you're at huge companies, you have the luxury of having several rounds of UX testing. But it's still largely trial and error. At smaller outfits you just have ramshackle processes that sometimes include user feedback, sometimes not. The stakeholders rarely know all the applicable personas and journeys and such right off the bat, especially for greenfield features... Not disagreeing with you, since that would be really nice, just never really seen it in practice. Every org I've ever worked for had made UX a low priority.

tosbourn 4y ago

The "U" part is hard to talk about without actual users using it though. Which is hard to do pre-html.

ChrisMarshallNY 4y ago

In my experience, this doesn’t work. It’s always in everyone’s “In a perfect world” plans, but no one ever seems to have much to say, in the beginning. Even technically-proficient major stakeholders (for example, managers and testers) seldom offer much in the way of feedback, early in the project. I have learned to write my applications in a manner that affords “hands-on” testing, as early as possible, and I use techniques that allow a lot of pivoting. I wrote the following comment, in an earlier thread[0] where I discuss this approach. [0] https://news.ycombinator.com/item?id=32153234 https://news.ycombinator.com/item?id=32153234

onion2k 4y ago
I have learned to write my applications in a manner that affords “hands-on” testing, as early as possible I think we agree in principle. I prefer using design tools that offer 'interactive' previews like Figma, but the idea is the same - get feedback from stakeholders as early as possible.

solardev 4y ago

Nobody really knows this stuff. If you're at huge companies, you have the luxury of having several rounds of UX testing. But it's still largely trial and error. At smaller outfits you just have ramshackle processes that sometimes include user feedback, sometimes not. The stakeholders rarely know all the applicable personas and journeys and such right off the bat, especially for greenfield features... Not disagreeing with you, since that would be really nice, just never really seen it in practice. Every org I've ever worked for had made UX a low priority.