4.5Handling "Why Is QA Taking So Long?"

This question is rarely about curiosity. It is about frustration. The executive asking it feels that QA is a bottleneck. Your response must address both the explicit question and the underlying concern.

Bad Responses

• "Testing takes time." (Dismissive. Does not explain why.)
• "We found a lot of bugs." (Implies the developers are bad.)
• "We need more resources." (Sounds like an excuse.)

Good Responses

When the delay is justified:

"We discovered 3 critical issues in the payment flow during testing. Fixing and re-verifying them added 2 days. Without this testing, those bugs would have reached 10,000+ customers. I can share the specific issues and their potential impact if that would be helpful."

When the delay is due to external factors:

"Testing was blocked for 2 days because the staging environment was down. We have resumed and will complete by Thursday. I have already coordinated with DevOps to prevent this from recurring."

When the delay reveals a systemic problem:

"The current testing cycle takes 5 days because we are running 80% of tests manually. I have a proposal to automate the top 50 regression scenarios, which would reduce the cycle to 2 days. The investment is approximately 3 sprints of automation work, and the break-even is 4 releases."

The Key Principle

Always pair the explanation with a path forward. Executives do not want to hear why something is slow. They want to know what you are doing about it.