specialist-publisher: # Quality assurance
As mentioned in the Automated tests section, we introduced a QA process to plug the holes in testing journeys through the application. We started by asking a product manager to go through the old Specialist Publisher application and to write down all of the "critical journeys" they could find. We then worked with them to consolidate this into a QA worksheet that has evolved over time.
You can see that worksheet here.
We make it a mandatory step that when going live with a new format, at least two people must run through this QA process. Later, we extended this invitation to people outside the team to help with this burden. I would not recommend this process to other teams looking to migrate. I think it would be better to look at RFC 50 and try to solve that, instead.