All knowledge work requires a delicate and continuously shifting balance between delivery – exploiting existing knowledge – and discovery – exploring new knowledge. This need to balance discovery and delivery can be found across the entire innovation cycle: from technology innovation over performance and sustaining innovation to disruptive innovation. It has been a driving concern for specific approaches such as Lean Product and Process Development as well as The Kanban Method, as exemplified in examples such as: developing a new product that requires novel features (discovery) while at the same time managing the overall risk that is involved in developing those features (delivery); improving agility and predictability of an organization that may require substantial change (discovery) while at the same time keeping resistance to change under control (delivery); a startup that requires an initial focus on finding problem/solution fit or product market fit (discovery) but then needs to develop the organization to delivery at scale (delivery); etc. In each of the examples above, too much emphasis on discovery may result in a disconnection with the past leading to resistance to change, increasing delivery risk, and non-adoption of innovation. Too little emphasis on discovery (and consequently too much emphasis on delivery) may lead to not being prepared for the future resulting in stagnation and the risk of being disrupted. Discovery Kanban systems are Kanban systems that help to balance discovery and delivery while moving from a mindset of episodic (one-off) innovation and change towards a culture of continuous innovation and change. Discovery Kanban systems work across the entire discovery cycle starting from pre-hypothesis moving into hypothesis validation and ending in post-hypothesis. In this presentation, we will discuss the different elements of Discovery Kanban, examples and underlying principles.