The Community Building Era spans the years from the first Lean Kanban conference (May 2009) through approximately 2015 — the period in which Anderson shifted from developing the Kanban Method to building the institutional infrastructure for a global community of practice. The kanban-book-publication in May 2010 marks the era's central milestone, but the defining activity is the creation of the conference series, the training organization, and the shared vocabulary that transformed the Kanban Method from Anderson's personal framework into a community-owned intellectual tradition.
The first Lean Kanban conference (2009)
The first-lean-kanban-conference in Miami, FL (May 6-8, 2009) preceded the book publication by a year. With 66 attendees and keynotes from Anderson, Dean Leffingwell, and Alan Shalloway, it demonstrated a community of practitioners already engaged with kanban ideas. The conference was organized after discussions on the kanbandev mailing list between Anderson, Chris Matts, and Joshua Kerievsky — establishing the internet discussion community as the social substrate from which the face-to-face conference grew.
The Kanban book and community growth (2010-2012)
The kanban-book-publication in May 2010 gave the community a canonical reference. The book's success — 40,000+ copies, 8 languages — both reflected and accelerated community growth. It validated the method's intellectual substance to practitioners, trainers, and organizational decision-makers who needed a credible reference before adopting the approach.
The first-kanban-leadership-retreat in Reykjavik, Iceland (June 2011) established the retreat format that allowed core practitioners to deliberate on the method's evolution outside the conference context. The kanban-university-founding at Utrecht in February 2012 institutionalized the training and accreditation function.
STATIK
The Systems Thinking Approach to Introducing Kanban (statik) emerged during this period as the canonical methodology for designing and implementing Kanban systems. STATIK provides a structured process for analyzing a service, understanding its sources of dissatisfaction, designing appropriate WIP limits and workflow structures, and socializing the design with stakeholders. It represented a methodological advance over ad hoc kanban implementations — a reproducible design process rather than an intuitive one.
Evolutionary change as community doctrine
The evolutionary-change principle — start with what you do now, agree to pursue incremental improvement, respect current processes and roles — became the central community doctrine during this era, distinguishing the Kanban approach from the "throw away your current process" prescriptions of Scrum and other Agile methods. The community building effort was partly about communicating this distinction to a practitioner audience already saturated with Agile frameworks.