HKSM

A disciplined way of questioning and testing the underlying values and assumptions behind actions to uncover true root causes and craft better countermeasures, rather than treating only the symptoms.

Key Points

• Goes beyond quick fixes by examining the beliefs, rules, and policies that drive behavior.
• Used in retrospectives and postmortems to reach root causes and design systemic changes.
• Requires psychological safety so team members can challenge assumptions without blame.
• Often results in updates to workflows, definitions of done, policies, and decision criteria.

Example

During a sprint retrospective, a team keeps missing integration targets. Instead of adding more buffer or extra testing (a surface fix), they question their working agreements and Definition of Done. They discover that integrating only at the end of the sprint and having separate code branches are core assumptions causing the delays. The team changes policy to integrate daily, adopts trunk-based development, and pairs on merge conflicts. The misses drop significantly in the next release.

PMP Example Question

A Scrum team repeatedly experiences production defects. The Scrum Master proposes challenging the teams Definition of Done, testing strategy, and release policy to uncover root causes before choosing fixes. What approach is the Scrum Master using?

1. Single-loop learning focused on quick corrective actions
2. Double loop learning that questions underlying assumptions and policies
3. Updating the lessons learned register only
4. Issuing a change request to add more testers

Correct Answer: B — re-examining underlying assumptions to fix root causes

Explanation: Double loop learning explicitly challenges governing values and assumptions to identify and address systemic causes, not just symptoms.