Great article! We use a similar process when building out new UI.
How do you deal with design bugs that happen as side-effects? For example, sometimes we'll QA and ship a new landing page. Months later, some other team is refactoring some CSS for a different feature and makes a change that causes a design bug in our landing page, as an unintentional side-effect. Our team is no longer working on the landing page, so we don't notice the design bug for some time, and the team that introduced the bug had no idea our landing page was even at risk of breaking from their changes.
Over time, these side-effect bugs really add up, but it's hard to catch them as they happen.
Hey, Weston! That's a great question and it's a situation I've never encountered as I've always worked on pretty small teams. The idea of ownership comes to mind. Specifically assigning pieces of work or pages to a person who can oversee them and check in on them from time-to-time especially as changes are made. Product Managers can do this but I believe designers are better suited for the task given the lens we look at work through. What do you think?
I could see that working. I think PMs would miss a lot of the details, but the designer would catch them. The only downside is that it could be a lot of manual work, depending on how many pages you have to repeatedly do design QA on.
Hey everyone, I wrote about one process method I use to ensure designs get implemented as intended. I would love to hear how you do it and generally your feedback.
Awesome write-up Jess! I've been looking for a phrase like "Design QA" to describe this process, naming something is a key step in making it important. Totally agree that it's a key part of the product development process. In case you're interested, I'm actually a founder at Pastel - our whole thing is we're trying to make Design QA for web products way simpler. Would love to get your thoughts on what we're doing. :)
Hi, Haneef! Thank you! I'm glad you like the phrase "Design QA." I like it as well, especially better than phrases like "Design Review" as it sounds a bit more formal and part of the overall product development process.
I've seen Pastel but haven't used it yet; it looks like a great product! I have used Redpen.io for years now. What's the advantage to using Pastel instead?
Thank you! Agreed that "Design QA" somehow seems more legit than "Design Review". Redpen.io is really awesome, and we're not (currently) direct competitors. Where Redpen is great for doing Design QA on image-based wireframes and mockups, Pastel really shines when doing QA on the actual website.
Here's an example canvas for this DN page: http://usepastel.com/link/d5gd/
Hi! Yeah, OK I see the difference now. It's great; I'll give it a go the next time I'm collecting feedback on a Website. Thanks!
No problem! LMK how you find it, when you give it a try. I'm at email@example.com