How to Apply ELSE: Difference between revisions

From go-ELSE
Jump to navigation Jump to search
No edit summary
No edit summary
Line 13: Line 13:




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 for a dime"<ref>http://www.gurteen.com/gurteen/gurteen.nsf/id/to-turn-on-a-dime-for-a-dime</ref>, i.e. optimising for adaptability in product development. One characteristic of many companies is to have a huge [[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. It does not make any sense to build great Teams if the value stream they work in is inherently flawed!
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"<ref>http://www.gurteen.com/gurteen/gurteen.nsf/id/to-turn-on-a-dime-for-a-dime</ref>, i.e. optimising for adaptability in product development. One characteristic of many companies is to have a huge [[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. It does not make any sense to build great Teams if the value stream they work in is inherently flawed!


So we suggest considering how your value stream is organised in order to deliver your product and work to reduce the Accidental Complexity of that value stream. To understand the best way to do it, [[The Product Perspective]] as well as the [[Defining Products|Defining Products Principles]] provide the basic knowledge to inform your experiments.
So we suggest considering how your value stream is organised in order to deliver your product and work to reduce the Accidental Complexity of that value stream. To understand the best way to do it, [[The Product Perspective]] as well as the [[Defining Products|Defining Products Principles]] provide the basic knowledge to inform your experiments.

Revision as of 16:16, 29 January 2024

The Perspectives discuss the background thinking behind the Principles. The Change Perspective includes a detailed discussion of the process for applying the ELSE Scaling Principles. In summary, the list below outlines the major activities and suggested order:

  1. Engage people and create the safety to surface issues and try experiments
  2. Collaboratively map the current context
  3. Use the ELSE Scaling Principles to analyse the context for gaps
  4. Identify improvement options and prioritise
  5. Shape, run and support experiments
  6. Review, adapt and learn from the experiments
  7. Emerge practice
  8. Broaden and evolve
  9. Repeat


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. One characteristic of many companies is to have a huge 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. It does not make any sense to build great Teams if the value stream they work in is inherently flawed!

So we suggest considering how your value stream is organised in order to deliver your product and work to reduce the Accidental Complexity of that value stream. To understand the best way to do it, The Product Perspective as well as the Defining Products Principles provide the basic knowledge to inform your experiments.

While the evolution of the definition of product is going to inform the main direction for the change, The Leadership Perspective, The Teams' Perspective and The Coaching Perspective and all the Principles will help in the design of experiments that shape the organisational environment that will support the evolution of the definition of product.

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:

  1. Engage people and create the safety to surface issues and try experiments
  2. Collaboratively map the current context
  3. Use the ELSE Scaling Principles to analyse the context for gaps
  4. Identify improvement options and prioritise
  5. Shape, run and support experiments
  6. Review, adapt and learn from the experiments
  7. Emerge practice
  8. Broaden and evolve
  9. Repeat