Explicit Policies: Making Work Rules Visible and Collectively Owned

Definition

In any organization, countless implicit decisions are made daily about how work is organized—when to pull new work, what "done" means, how to handle urgent items, who decides what. Kanban requires these implicit policies to be made explicit: written down, visible (ideally displayed near the Kanban board), collectively agreed upon, and openly changeable. Explicit policies include pull criteria, WIP limits, service classes, meeting times, and collaboration agreements. They are not work instructions but enablers of self-organization—they create boundaries within which teams decide how to work.

In the Book

The Official Kanban Guide dedicates a full section to explicit policies: "Every day, countless decisions are made about the organization of work, either by individuals or between groups of people. Imagine a new employee starting in your area. Ideally, she will quickly understand how work is organized through explicit policies."

The guide lists what makes a policy explicit: "Policies such as replenishing the board (when, how much, by whom), Definition of when a work activity is completed and the work item can move on ('pull criteria'), WIP Limits, Policies for handling work items of different classes of service, Meeting times and content, Other principles and collaboration agreements. All of these policies should be agreed to jointly between all parties involved including customers, stakeholders, and employees responsible for work on the board."

Critically, explicit policies are not rigid: "The policies should be placed in a clearly noticeable area, preferably right next to the board...Like all other building blocks of the system, it is necessary to check and adapt these regularly...policies are not like work instructions freeing people from the burden to make meaningful decisions. Rather, policies should enable self-organization within the group of people running a Kanban system." Effective policies are "sparse, simple, well-defined, visible, always applied, readily changeable by those providing the service."

Why It Matters

Implicit policies breed silent conflict. One person thinks "urgent means you interrupt what you're doing"; another thinks "nothing is truly urgent until planned." One thinks "done means it ships"; another thinks "done means code review." When a new decision is needed, each person invokes their own implicit model. With explicit policies, decisions are transparent—and disagreement surfaces as policy disagreement, which can be debated and changed. The guide's emphasis on making policies changeable by those doing the work (not handed down from management) means policies are living documents, not rules imposed from above. In any system where people must coordinate without constant direction, explicit policies are the difference between anarchy and self-organization.