We want to merge our QA and Customer Support seats because automated AI triage has cut support volume by half, but the Support lead does not know how to run QA. How do we structure this transition?

Question

Tyler Smith · Accepted Answer

When technology reduces the volume of a manual seat, merging departments is a smart way to protect your operating margins. However, you cannot simply force a person into a newly combined seat if they do not pass the GWC™ filter. If your Customer Support lead does not understand QA methodologies, she does not currently GWC™ this combined seat. You must handle this structurally first, then address the person. Start by redefining the combined seat on your Accountability Chart. List the five key roles, ensuring they reflect the new AI-augmented reality, such as monitoring automated ticket accuracy, auditing AI-generated drafts, and managing complex customer escalations. Once the roles are clear, sit down with the Support lead and evaluate her. Does she truly get what QA means in this new context? Does she want to learn it, or is she comfortable just doing traditional support? Finally, does she have the analytical capacity to learn the tools? If she gets it and wants it, but lacks the immediate technical capacity, you can build a defined training plan with a thirty-day or sixty-day milestone to bridge the gap. Set clear, measurable goals for her to achieve capacity. However, if she does not want the technical QA responsibilities or struggles to grasp the logic of automated workflows, you must make a hard right-seat call. You cannot compromise the seat to fit the person. You must find someone who fits the new seat fully, and transition her to an alternative role or part ways.