How to Apply ELSE

From go-ELSE
Revision as of 12:02, 30 January 2024 by Cbird (talk | contribs)
Jump to navigation Jump to search

ELSE proposes that change is an emergent and evolutionary approach. As such, at the core, it's about designing experiments that drive the change in a useful direction. But... what is this direction? Agility is about value delivery and the capability of "turning on a dime for a dime"[1], i.e. optimising for adaptability in product development. A common characteristic of many companies is to have a high level of Accidental Complexity in the way they have organised their product development. As such, how products and value streams are set up is a key element to inform change.

We noticed that often the improvement work on Teams, Product Ownership and Leadership to create a more agile ecosystem is severely constrained within the limits of how the value stream is structured.

Given streamlining the value stream and achieving a more end-to-end product can open up greater opportunities for improvement, it makes sense to start improvement iterations from this perspective.

To understand the best way to do it, The Product Perspective and the Defining Products Principles provide the background knowledge to inform your experiments.


As the definition of Product evolves and makes new improvement opportunities possible, The Teams' Perspective and The Coaching Perspective and all the Principles will help in the design of experiments that help reshape the organisational environment.

To help you in the implementation of these experiments, The Change Perspective describes how to create the needed emergent evolutionary culture in your organisation based on the ELSE actionable principles, which can be summarised as follows:



The catalyst of this work is, of course, Leadership! In order to support this work, leaders lead by example and take themselves through a change process that involves learning to work as an end-to-end leadership team, rather than focusing on their individual silos.