• Chris KeithChris Keith, over 4 years ago

    Our team manages everything in Trello. I always, always include annotated screenshots for UI fixes. I’ll use Sketch or Skitch to mark them up and provide context. If the fix is motion or animation-related I’ll include a gif or mp4.

    In both instances I’ll show the “current” and “desired” states side by side with highly specific directives that are actionable (this is key): “increase this margin by 8pt.” Or “this element should be vertically centered between these two elements.”

    The devs I work with consistently thank me for being painfully specific and including annotated visuals, even for simple fixes. The slight bit of extra time I spend to create more detailed tickets saves a ton of time overall because the engineers have all the detail they need without any further back and forth.

    10 points
    • Scott ThomasScott Thomas, over 4 years ago

      how do you break your tickets down?

      1. Overall Summary what needs changed
      2. Reference page
      3. Design Reference
      4. Templates/models that are effected as well
      5. Task list with detailed changes like (Increase the padding on .class to 1em)
      6. Annotated Screenshot
      0 points
      • Chris KeithChris Keith, over 4 years ago

        That's about right. Love that you called out the "templates/models" point. Many times a UI fix affects a component that is used system-wide, so it's super important that communicate that.

        0 points