A major tenet of Kanban is that you should have explicit policies that define your workflow. Team learning occurs because team members actively discuss how they should be doing their work on a regular basis. Teams manage the amount of Work in Process so that they can stay focused and avoid creating new work caused by delays between the stages of work.

Moreover, Kanban includes management. Visibility in Kanban changes the relationship between management and their teams. It also allows managers to provide coaching and leadership to the team when necessary. While management respects that the team is doing their best but understands that sometimes teams don’t see all the things they need to do.

Resources related to kanban

Contrasting the Daily Scrum with Kanban's Daily Retrospective (Article)
Designing the Kanban Board (Article)
Iteration 0 - Facilitate (Article)
Lean-Agile Team Checklists (Article)
Meetings for Lean-Agile (Article)
Metrics (Article)
Product Demonstration and Review - Facilitate (Article)
Product Demonstration and Review - Plan (Article)
Product Planning and Review - Conduct (Article)
Resistance is Not to Change (Article)
Starting With Kanban (Article)
Types of Tests for Code (Article)
What Framework / Method / Approach Are We Using? (Article)
What Should Team Process(es) Be: Scrum, Kanban, Leanban? (Article)
Writing Explicit Policies (Article)
Writing Tasks (Article)