↵

How do you give feedback on design implementation to developers?

almost 5 years ago from Ahmed Sulaiman, Designer + Developer + Harmonica Player, Make of crosspatch.io

  • Nimrod Gavish, almost 5 years ago

    We are creating a google spreadsheet with all the issues we found. Each issue gets few columns to be filled:

    • Area in the product - our features are usually affecting few places in the product, sometimes these places are owned by different developers so this arrangement is more effective.

    • Priority (P1, P2, P3) - very important in order to be able to release without finishing everything

    • Description - explaining the issue, current behavior, expected behavior, explaining how to recreate the issue.

    • Screenshot of the issue / Video in case it’s a flow that needs to be fixed (we paste links we capture with marker.io / loom)

    • Type - Server side / Front end (When its not clear I leave blank for the Dev team to fill)

    • Status - Open, In progress, Ready for QA

    For the columns of area, priority, type and status I add the predefined values as drop down options so it will be possible to filter the list (all open issues, all issues in server etc)

    When all blockers (P1s) and P2s are fixed we usually release and all the leftovers, the P3 we move to JIRA issues.

    We find this workflow good and efficient for the whole team. Sometimes few designers are involved in the UX QA process, in this case we also add a column for the name of the designers who reported the issue in case a developer needs a further info.

    Hope that helps :)

    4 points
    • Ahmed Sulaiman, almost 5 years ago

      Wow! Thank you so much for such a detailed overview of the process. It really helps a lot.

      You've mentioned that you're using market.io but just for capturing videos/screenshots.

      It seems like they have the ability to create issue/card/etc directly within the tools the team is using (like Trello, Asana etc.). But you prefer to make everything in google spreadsheet if I understood correctly.

      Do you think it's less flexible to us the automatic creation of these issues or it's just a process that you have in your team?

      1 point