"Upstream Kanban" (2019) extends the kanban-method into the discovery and planning work that occurs before items enter the development workflow — the "upstream" phase that determines what gets built and whether it will meet customer needs.
The upstream problem
The kanban-book (2010) addressed the management of work through a development workflow: items enter the system, flow through stages, and exit as delivered value. It did not systematically address how items get into the system in the first place — how product ideas are generated, evaluated, prioritized, and prepared for development. This upstream phase is where much waste and delay originates: poorly defined work items, options that require rework when they reach development, features that were built but don't meet customer needs.
"Upstream Kanban" applies the kanban-method's core practices — visualize-workflow, limit WIP, manage-flow, make-policies-explicit — to this upstream work. The resulting upstream kanban system manages the flow of options (potential work items) through discovery, exploration, and preparation before they are committed to development.
Connection to fitness criteria
The upstream context is where fitness-criteria (from fit-for-purpose) become operational: it is in the upstream phase that the organization determines what customer purposes need to be served and which options are most likely to serve them. Upstream Kanban thus complements the fitness-for-purpose framing by providing the operational system through which fitness criteria are applied to option selection.
Architectural extension
Together with essential-upstream-kanban (a condensed free guide to the same material), "Upstream Kanban" represents an architectural extension of the Kanban Method. The original method managed the delivery pipeline; upstream kanban manages the discovery pipeline that feeds it. This two-pipeline view — upstream discovery feeding downstream delivery — mirrors the lean thinking about value stream mapping that includes both the information flow (upstream) and the material flow (downstream).
The work reflects the maturity-and-enterprise-era expansion from team-level delivery practice to a complete enterprise service management approach, complementing the kanban-maturity-model's organizational scope with a method-level scope extension.