New answers tagged

0

Your business analysts are currently doing the product design by proxy. Use cases are supposed to be a way for the business side to identify and communicate the product's business requirements to the design side, who then does the actual product design to meet those requirements. Use cases are not supposed to be a point-by-point description of the product ...


0

Nobody should be coming up with just one idea that becomes the design. Ideally you should be exploring multiple ideas (as many as you can think off) before deciding on the design direction, and perhaps even running with 2 final ideas that you progress via A/B testing to see which one is best. So just treat their suggestion as just one idea and see how many ...


0

A good design is to help users accomplish their goals. Everyone has their own opinions about how things should be designed, but how do we know what's the best for users? It will be inappropriate to take someone's design as a tempalte guide without futher discussion or validation. You may discuss with the analyst about his design concept and see why he thinks ...


0

I think it should be a collaborative task, the analyst has a depth knowledge about the requeriments and the UX team has a depth knowledge about the user and user interactions, so create the wireframes take in account both opinions. If the analyst has already created some wireframes, take these as reference, it could be very useful to understand what they ...



Top 50 recent answers are included