Section 3 Solutions

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

Scenario 1: The Unaddressed Process Gap

Correct answer: Propose a small, provable fix and pilot it on their own work first, then present evidence framed around a shared goal, per Leading Without Authority — not wait for a formal title.

Explanation: This is the module's own opening scenario restated — most real influence happens without formal authority, and waiting for a title delays solving a visible, fixable problem for no real benefit.

Alternative approaches considered: Escalating the concern loudly without any evidence or small-scale proof is far less persuasive than a demonstrated, small fix.

Real-world reasoning: Tests whether the specific mechanism (small proof, evidence, shared-goal framing) was understood as the actual path to change, not just "speak up more."

Scenario 2: The Inconsistent Team

Correct answer: Explicit, deliberate structure — a stated work-allocation method and purposeful rituals, per Running QA Teams.

Explanation: This is the module's own opening scenario restated — ad hoc, case-by-case decisions feel flexible but compound into inconsistency and imbalanced workload over time.

Alternative approaches considered: Assuming the team simply needs more meetings or more oversight misses the actual gap — what's missing is explicit, consistent structure, not more managerial attention.

Real-world reasoning: Tests whether "explicit structure prevents compounding inconsistency" was understood as the core lesson, not just "the Lead needs to try harder."

Scenario 3: The Repeated Question

Correct answer: Switch from giving direct answers to guided questioning — asking what the junior tester thinks and why, per Mentoring Engineers.

Explanation: This is the module's own opening scenario restated — direct answers, even correct ones, don't build the underlying reasoning process, so the same type of question resurfaces.

Alternative approaches considered: Simply explaining the answer again, more clearly or in more detail, doesn't address the actual gap — the issue is process, not clarity of explanation.

Real-world reasoning: Tests whether "mentoring should build judgment, not just transfer answers" was understood as the fix, not just "explain better."

Scenario 4: The Centralized Bottleneck

Correct answer: The cost is a bottleneck and stalled team growth, per Delegation and Decision Making — routine, low-risk decisions should be delegated, reserving personal review for decisions with major, hard-to-reverse consequences.

Explanation: This connects directly to that module's delegate-versus-keep framework — over-centralizing decisions with small, recoverable consequences produces exactly this cost.

Alternative approaches considered: Concluding the Lead simply needs to review faster misses the actual fix — the issue is what's being centralized, not the speed of review.

Real-world reasoning: Tests whether the consequence-based delegation framework was understood as the fix, not just "the Lead is a bottleneck, so work faster."

Scenario 5: The Side-Picking Resolution

Correct answer: The Lead resolved the conflict at the position level rather than the interest level, per Conflict Resolution — the underlying interests behind each position were never surfaced or addressed.

Explanation: This is the module's own opening scenario restated — picking a side settles immediate friction but leaves the underlying disagreement to resurface in a new form.

Alternative approaches considered: Assuming a stricter or faster decision process would fix this misses the actual gap — the problem is that interests were never surfaced, not that the decision was slow.

Real-world reasoning: Tests whether the positions-versus-interests distinction was understood as the actual mechanism, not just "make a firmer decision next time."

Section 3 Complete

Across five modules, this section built the core people-leadership skills every QA leadership track eventually depends on: influencing change without formal power, running a team with deliberate structure, mentoring in a way that builds real judgment, deciding what to delegate versus decide personally, and resolving conflict at the level of underlying interests rather than surface positions. From here, continue to Section 4 — Engineering Excellence, starting with Shift Left at Scale.