By the way, @ChickenLadyLovesLife@lemmy.world, I brought up user stories in particular because they should be initially written or at least verbalized by either the target users or clients like managers. Neither designers nor programmers can know exactly what the target user’s needs are, or they may think they know but be mistaken — because they don’t have what’s called the domain knowledge, i.e. expertise of the target users.

Of course, another major tool in a designer’s workflow is testing with target users before release, including with rough mockups — so any misunderstanding of users’ goals and workflow can be caught in time.

For the context, I’m a dev who mostly does backend. But understanding design is interesting and helpful.