Member-only story
Team collaboration optimization: How to use Notion for Design QA and Issue Tracking Management
This article mainly shares the implementation of Design QA using the tool Notion — how to conduct Design QA, how to write QA content, track and manage this stage, and briefly discuss other tools (such as Google Doc, Dropbox paper, Jira, Trello, inVision, Figma) to share experience and help designers carry out a smoother Design QA stage.
At the end of the article, the reference URL of the mentioned Notion application is attached. You can try it out and copy and adjust it to a format suitable for the team or yourself.
Design QA often becomes chaotic without realizing it
As a designer, when there are many release projects, you may have experienced… After the design stage is over, you hope that the engineer will send the testing link someday. After one or two weeks, you finally receive a link, open the test website, and start cross-checking with the design draft. At the same time, you also discover many problems that were not considered during the design process…
Spend a lot of time creating Issues, but not sure which Issues have been fixed
After communicating with the engineer for an hour, looking at the test site, it seems that this problem was mentioned just now, but I am not sure if I have checked it all; and after a few days, when I look back at the test site, I can’t remember how some Issues were found?
The engineer seems to have said that some places cannot be fixed due to restrictions, but which side did he say? Why does it seem to be discussing the same problem repeatedly?
Initially, a QA document was opened to list the Issues, but as the number of problems increased, it began to become difficult to find out which Issues have not been fixed.
Unable to grasp the status of the Issue, not sure where Design QA is going, and not sure if the previously discovered Issues have been fixed.
