The Kanban Values

Kanban has nine values that guide behavior. Unlike the practices (which are actions), values are ways of thinking. They help you make decisions when the practices don't give a clear answer.

These values emerged from the Kanban community over years of practice. They're not arbitrary—they reflect what makes Kanban implementations succeed or fail.

Sharing information openly improves the flow of value.

Transparency means making work, policies, and problems visible to everyone. It means not hiding bad news. It means data over opinions.

A transparent Kanban system shows:

• All work in progress (no hidden backlogs)
• Who's working on what
• Where bottlenecks are forming
• What policies govern the work

The opposite: Hidden work queues, optimistic status reports, information hoarding.

Different aspects, viewpoints, and abilities must be balanced for effectiveness.

Balance shows up in many forms:

• Balancing demand against capacity
• Balancing speed against quality
• Balancing individual focus against team collaboration
• Balancing planned work against emergent needs

Imbalance causes problems. Too much demand creates overload. Too much focus on speed sacrifices quality. Too much planning kills responsiveness.

Kanban's WIP limits are fundamentally about balance—matching work-in-progress to capacity.

Working together for mutual benefit and value creation.

Kanban boards are collaboration tools, not surveillance tools. The goal is for people to help each other, not to track who's "behind."

Collaboration in Kanban means:

• Swarming on blocked items
• Cross-training to reduce silos
• Pair working on complex items
• Shared ownership of flow, not just individual tasks

The opposite: "That's not my job," finger-pointing when things go wrong, optimizing individual metrics at team expense.

Keep the focus on what the customer needs and values.

It's easy to get caught up in internal process optimization and forget why you're doing it. The point isn't a beautiful board or impressive metrics—it's delivering value to customers.

Customer focus means:

• Measuring lead time from customer request to delivery
• Prioritizing based on customer impact
• Reducing wait times that frustrate customers
• Understanding what "value" means to your customer

The opposite: Optimizing for internal convenience, celebrating velocity without connecting to outcomes, long queues of "almost done" work.

Work should flow smoothly and continuously.

This is the central operational concern of Kanban. Flow means work moves steadily through the system without long waits, large batches, or frequent interruptions.

Good flow feels like a calm, productive rhythm. Bad flow feels like chaos—bursts of activity followed by waiting, constant context switching, heroic efforts to meet deadlines.

Kanban practices (WIP limits, explicit policies, managing blockers) all serve the goal of smooth flow.

The ability to inspire others to action through example, words, and reflection.

Leadership isn't a position—it's a behavior. In a healthy Kanban system, anyone can exercise leadership by:

• Raising problems they see in the flow
• Proposing experiments to try
• Helping unblock colleagues
• Modeling the values

This requires psychological safety. If pointing out problems gets you punished, leadership becomes impossible.

Know yourself and your organization to guide improvement.

Improvement requires understanding your current state. This means:

• Understanding your actual process (not the documented one)
• Understanding what customers really value
• Understanding where time is actually spent
• Understanding why problems recur

Systems thinking matters here. Individual problems often have systemic causes. A developer who's "slow" might be handling too many interrupts. A bottleneck in testing might stem from unclear requirements upstream.

Shared commitment to goals and rules.

Kanban's explicit policies only work if people agree to follow them. This doesn't mean top-down mandates—it means genuine buy-in.

Getting agreement means:

• Involving people in creating policies
• Explaining the "why" behind rules
• Revising policies when they don't work
• Respecting agreements once made

The opposite: Policies that exist on paper but are routinely ignored, decisions made without input, agreements that weren't really agreed to.

Valuing, understanding, and showing consideration for people.

Respect is foundational. Without it, everything else falls apart.

Respect means:

• Listening to concerns before dismissing them
• Assuming good intent
• Valuing diverse perspectives
• Recognizing the expertise people bring

When people feel respected, they engage. They raise problems. They propose solutions. They collaborate. When they don't feel respected, they comply minimally and disengage.