This kinda depends. User stories document the typical goals and workflow of the users with the app, and thus should come from the target users or at least the client like a manager. The designer is not qualified to make the user stories since they don’t know the business domain, as it’s called. But they know how to organize the UI for any particular goals.
Yes, but it is also important to understand that not having a Design Document does not equate to not having a Design.
There was 1 project where the users of the UI I was making were not nearby (in most cases my direct senior was also the user) and most of the UI/UX expectation were passed on verbally. I then made a basic model and then iterated over it with repeated feedback from the target users.
So the point is that anyone putting a design document on a pedestal (like an interviewer at one of my past applications) is most probably spewing garbage.
This kinda depends. User stories document the typical goals and workflow of the users with the app, and thus should come from the target users or at least the client like a manager. The designer is not qualified to make the user stories since they don’t know the business domain, as it’s called. But they know how to organize the UI for any particular goals.
Yes, but it is also important to understand that not having a Design Document does not equate to not having a Design.
There was 1 project where the users of the UI I was making were not nearby (in most cases my direct senior was also the user) and most of the UI/UX expectation were passed on verbally. I then made a basic model and then iterated over it with repeated feedback from the target users.
So the point is that anyone putting a design document on a pedestal (like an interviewer at one of my past applications) is most probably spewing garbage.