• [object Object]@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    9 hours ago

    By the way, @[email protected], 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.

    • ChickenLadyLovesLife@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 hours ago

      another major tool in a designer’s workflow is testing with target users before release

      Lol you should have seen this UX dude’s face when I suggested doing exactly this. It’s hard to imagine an actual live human being saying “users don’t know what they want” but that is exactly what he said. It should be no surprise that this company routinely produced one-star apps, and also no surprise that the company was a routine winner of the Worst Company of the Year contest.