3 ms·

If you are developing a product: at what point do you think you will bring on a UX person? And what would you want that person to do for you/your product?

chadlavi 6y ago
that person should be in the room from the start. Design isn't just putting a pretty façade on it, designers should be part of the deep behavioral decisions from the start.
- meristem 6y ago
  I’m with you. I would like to understand, however, how founders actually think about bringing UX people on board. How early? What scope? Etc.
  - chadlavi 6y ago
    Ah as like, a paid person who is there to do that one thing, you mean? For most startups, it definitely takes a while. The "UX person" is generally one of the hats that one of the first founders needs to wear. I've been in startups where "the design guy" was third into the room after "the inventor/engineer guy" and "the money guy", but I think that's unfortunately rare. As long as _someone_ has their eye on that ball from the start, it usually works out, and that someone who's keeping it in mind will (hopefully) be able to tell when there's a whole person's worth of job to do just on design, and be able to check if there's a whole person's worth of compensation available for it.
- ajhurliman 6y ago
  My sentiment exactly. The only acceptable situation to bring in a UX person on board after the product has already been mostly built is to clean up visual elements (consistent spacing, fixing color creep, choosing a font, etc.). The larger-scale UX should be a consideration from the very beginning: What pages/ views are there, how do these conform to different user flows to minimize actions and intuit next steps, what information is most critical in the visual economics of a view? These questions should be answered before coding anything.

3 ms·

If you are developing a product: at what point do you think you will bring on a UX person? And what would you want that person to do for you/your product?

by meristem 6y ago

chadlavi 6y ago
that person should be in the room from the start. Design isn't just putting a pretty façade on it, designers should be part of the deep behavioral decisions from the start.
- meristem 6y ago
  I’m with you. I would like to understand, however, how founders actually think about bringing UX people on board. How early? What scope? Etc.
  - chadlavi 6y ago
    Ah as like, a paid person who is there to do that one thing, you mean? For most startups, it definitely takes a while. The "UX person" is generally one of the hats that one of the first founders needs to wear. I've been in startups where "the design guy" was third into the room after "the inventor/engineer guy" and "the money guy", but I think that's unfortunately rare. As long as _someone_ has their eye on that ball from the start, it usually works out, and that someone who's keeping it in mind will (hopefully) be able to tell when there's a whole person's worth of job to do just on design, and be able to check if there's a whole person's worth of compensation available for it.
- ajhurliman 6y ago
  My sentiment exactly. The only acceptable situation to bring in a UX person on board after the product has already been mostly built is to clean up visual elements (consistent spacing, fixing color creep, choosing a font, etc.). The larger-scale UX should be a consideration from the very beginning: What pages/ views are there, how do these conform to different user flows to minimize actions and intuit next steps, what information is most critical in the visual economics of a view? These questions should be answered before coding anything.