2.3Asking the Right Questions

The most valuable QA contribution to any technical discussion is asking questions that nobody else thought to ask. Two question patterns are particularly powerful.

"What Happens When..."

This question pattern explores failure modes, edge cases, and unexpected states:

• "What happens when the database connection pool is exhausted?"
• "What happens when two users edit the same record simultaneously?"
• "What happens when the third-party API changes its response format?"
• "What happens when the user's session expires during a multi-page form submission?"
• "What happens when the file upload is interrupted at 99%?"

Each of these questions forces the team to think about scenarios they may not have considered. Many of the most severe production incidents come from "what happens when" scenarios that nobody asked about during design.

"How Do We Test..."

This question pattern ensures testability is considered from the start:

• "How do we test the email notification flow without sending real emails?"
• "How do we test the payment integration without charging real cards?"
• "How do we test the recommendation engine with deterministic data?"
• "How do we test the migration script without risking production data?"
• "How do we test the cron job that runs once a month?"

If the answer to "How do we test this?" is "We can't" or "We'll test it manually in production," that is a design problem that should be addressed before development begins.