Browser not supported

Sorry, the InVision Help Center does not support Internet Explorer. Please download Microsoft Edge or another modern browser.


InVision ambassador ambassador
Lala Galindo Lala Galindo Edited

Why is Design QA important and how do you take care of it in your team?

As designs evolve and grow, design debt can get worse and worse. This is every designer's kryptonite. Have you implemented Design QA and how do you do it?

"Design Debt affects the integrity of the user experience. This is what happens when a bunch of incremental changes collect over time and yield a disjointed, inconsistent, and patched-together experience. With each successful experiment, a small amount of Design Debt is incurred as the design moves slightly away from it’s original, cohesive roots." - Design Debt

 

0

comments

sort by


Caitlin Cambron
InVision ambassador Caitlin Cambron , ambassador

Definitely! Design QA is something that's critical to Interapt's process.

Typically the QA process goes:

  1. Developer hands off to QA.
  2. QA passes it back to Developer if there's a defect, if not they pass it to Designer.
  3. Designer completes the task if there are no defects.
  4. Since "no defects" is rare, the Designer passes it back to the Developer with notes. Eventually the Designer completes the task once the defects are corrected.

When Designers actually do the QA work we use a variety of iOS, Android, and computers to test. We go through the designed user flows, UI design details, and check the overall UX, all via notes on Zeplin. Eventually we put our defect notes in JIRA with links to the correct Zeplin designs. Sometimes we'll place a screenshot of the developed product next to designs and point out the differences.

As you mentioned, design debt builds up (even if you have a great process). I try to schedule "Do Not Disturb" days 3x/year where my team can clean up files and update that icon they've had on their list. Just a day to get all the little things done that are low priority.

Lala what different processes have you experienced? What do you feel works and what doesn't?

0

Rob Whiting
InVision ambassador Rob Whiting , ambassador

      > Have you implemented Design QA and how do you do it?

I think this is still an area that needs a lot of work to improve. Despite the great set of Design > Dev tools available (such as InVision with it's 'Inspect' functionality) the QA aspects of how these designs are actually implements still often fall outside of these tools remit.

The most successful process for me still involved an manual review stage by the UX Team before the product update went live.

Research ➡️ Design ➡️ Test ➡️ Handover (to Dev) ➡️ Approve ➡️ Ship

This ⤴️ type of process, but Design items still fell through the cracks. Really interested to know how others approach this tricky area 🙂

0

Kayden Knauss
InVision ambassador Kayden Knauss , ambassador

This is a great topic! I am also curious as to what other teams have set up and how they approach QA.

The design process that I’ve experienced the most is this:

Design > Test (QA) > Handover to Engineering (QA) > Implement

QA has typically happened at different points in many places I’ve been at, which has occasionally has its challenges. I do wonder if there is a “standard” or recommended place for it.

Usually the designers will perform the first round of QA which involves triple checking flows, UI design standards, etc. After the hand off, usually the more technical QA begins but if a design needs to be altered or rethought, the design team will step in and answer to how it can be resolved.

The conversation of QA is definitely an important one! I’d love to hear some more thoughts on it.

0

join the conversation

to comment, sign up or sign in.