Shuhari: Rules, Detachment, Fluency

Definition

Borrowed from Japanese martial arts, shuhari names three stages of learning. In shu ("protect" or "obey"), a learner needs simple, unambiguous rules ("meet every day and answer these three questions") because they have no basis yet for judging what matters. In ha ("detach" or "break"), practice with the rules has built enough understanding that the learner starts internalizing the principles the rules were protecting, and gets the real gains — beyond mere better-than-not-doing-it results — from genuinely grasping why the rules exist. In ri ("separate"), the learner is fluent enough that they no longer need the rules, or even the methodology's name, to do the right thing: "you don't really care if it's Scrum, XP, Kanban, waterfall... it doesn't matter."

In the Book

Chapter 10 uses shuhari to explain why coaching the same team member the same way is a mistake — a person still at the shu stage wants an unambiguous rule (stickies or index cards on the task board?) because they have no way yet to judge whether the choice is trivial or critical, while an "agile zealot" who never progresses past shu insists there is exactly one correct way to do everything. The chapter walks through a concrete coaching moment: a developer discovers mid-sprint that a feature won't be done done, and the Product Owner wants him to cut corners to include it anyway. The shu-level answer is simply to invoke the rule — incomplete work can't be demoed, it moves to next sprint — but a good coach also uses the moment as a ha-level teaching opportunity, helping the Product Owner see the developer's fractured perspective on technical debt. The book also uses shuhari to justify why some rules (a WIP limit in Kanban, for instance) must never be changed no matter how far along a team has progressed: a coach needs a "ha-level" understanding of which parts of a methodology are its "supporting beams," because a shu-level coach might let a load-bearing rule get negotiated away just to preserve superficial harmony.

Why It Matters

Shuhari gives a coach or mentor a way to match the level of explanation to the learner's actual stage, instead of over-explaining abstractions to a beginner who just needs a rule, or under-explaining to an advanced practitioner who is ready to understand — and eventually discard — the rule. It also draws a line between rules that are scaffolding (safe to relax once understood) and rules that are load-bearing (must hold regardless of stage), a distinction relevant to teaching any skill, discipline, or system of practice, not just agile methods.