Section 6 Solutions

These are the answers to the Section 6 Review's Knowledge Check. If you haven't attempted the four scenarios yet, do that first.

Scenario 1: The Checklist Rejection

Correct answer: The hiring process should assess judgment and reasoning through scenario-based exercises, not a checklist of specific tools, per Hiring and Interviewing Test Engineers.

Explanation: This is the module's own opening scenario restated — specific tool knowledge can be taught quickly, but sound underlying reasoning transfers across tools and is what actually predicts on-the-job success.

Alternative approaches considered: Simply expanding the checklist to cover more tools doesn't fix the underlying issue — the format itself, checklist versus scenario-based reasoning, is the actual problem.

Real-world reasoning: Tests whether "assess transferable judgment, not memorized or tool-specific knowledge" was understood as the fix, not just "the checklist needs more items."

Scenario 2: The Reconstructed Review

Correct answer: A running, specific record kept throughout the year is missing, per Career Development and Performance Reviews — reviews should synthesize ongoing attention, not be reconstructed from memory shortly before they're due.

Explanation: This is that module's own opening scenario restated — a review based on vague, recent impressions misses most of a year's actual work.

Alternative approaches considered: Simply spending more time writing the review right before it's due doesn't fix the underlying gap — the missing piece is ongoing tracking throughout the year, not more effort at review time.

Real-world reasoning: Tests whether "ongoing record-keeping, not better annual writing" was understood as the fix.

Scenario 3: The Six-Month Delay

Correct answer: The cost is a specific, avoidable pattern repeating unaddressed for months, and feedback losing its specificity and impact by the time it's finally delivered, per Giving Feedback.

Explanation: This is that module's own opening scenario restated — feedback given close to the relevant moment is far more actionable than feedback delayed until a formal review.

Alternative approaches considered: Assuming the eventual September feedback is just as effective as timely feedback, only later, misses the actual cost — both the delay itself and the loss of specificity matter.

Real-world reasoning: Tests whether "proximity to the instance is what makes feedback actionable" was understood as the core lesson, not just "feedback should eventually be given."

Scenario 4: The Forgotten Goal

Correct answer: Structured, regular coaching check-ins explicitly revisiting the stated goal, per Coaching — a goal mentioned once and never structurally revisited effectively goes nowhere.

Explanation: This is that module's own opening scenario restated — coaching requires ongoing, deliberate attention to a stated goal, not a single conversation.

Alternative approaches considered: Assuming the team member should simply raise it again themselves if it matters to them shifts responsibility away from the leader's own coaching practice — the fix is a structural check-in habit, not waiting for the report to re-raise it.

Real-world reasoning: Tests whether "coaching requires ongoing, structured revisiting of a stated goal" was understood as the fix, not just "have more conversations eventually."

Section 6 Complete

Across four modules, this section built the core team-management skills every QA leadership track eventually needs: hiring for real, transferable judgment, making performance reviews genuinely reflect ongoing attention, giving feedback specific and timely enough to actually change behavior, and coaching people toward goals they've defined themselves. From here, continue to Section 7 — Cross-Functional Leadership, starting with Working with Product and Developers.