Explicit Policies and Visualization

Definition

Explicit policies and visualization is one of the Kanban Method's six core practices and becomes foundational in Scrumban. It means making three categories of information visible: (1) the workflow itself—what states work passes through, visualized as columns on a board; (2) the work items and their current state, displayed as cards; and (3) the policies that govern how work is handled—written agreements about when to pull new work, what "done" means, how ad hoc requests are prioritized, what happens when capacity is exceeded. The practice acknowledges that implicit policies create confusion and enable different team members to operate under different assumptions about the same work.

In the Book

Reddy details the specific policies teams should make explicit: Which individuals manage the ready buffer and replenish it? When and how? Who manages completed work and forwards it downstream? How should ad hoc requests be managed? When should work be pulled from the ready buffer? What is the definition of ready (pull criteria) and definition of done for each work type or lane? The book also addresses what not to visualize—administrative activities or 5-to-10-minute ad hoc requests may clutter the board unless teams discover they constitute significant hidden demand. Visualization policies for work items themselves include due dates, size estimates, start dates, and end dates, chosen not as a prescriptive set but as a starting point teams can evolve.

Importantly, the book distinguishes explicit policies from static processes: these policies are continuously visible and therefore continuously available for challenge and improvement. Jason Yip's GIFTS framework (Good start, Improvement focus, Focus on moving work, Team collaboration, Status communication) shows how an explicit policy for daily stand-ups shifts the meeting from status reporting to collaborative problem-solving.

Why It Matters

Explicit policies eliminate ambiguity that otherwise fragments team effort. When "done" is ambiguous, one team member calls a task complete while another assumes more work is needed; visualizing the definition of done prevents rework and debate. When ad hoc work arrival is undiscussed, it invisibly disrupts planned work; making the policy explicit (e.g., "ad hoc requests queue in a separate lane with 30% capacity reserved") lets teams see and manage the impact. This also enables evidence-based improvement: teams can discuss whether a policy is working by observing its effects on the board, not by guessing or blaming individuals. Finally, explicit policies are easier to remember, teach to new team members, and share across teams—they become part of the organization's shared language.