How to Apply ELSE: Difference between revisions

From go-ELSE
Jump to navigation Jump to search
VisualWikitext
No edit summary
No edit summary
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
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:
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. 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.


# Engage people and create the safety to surface issues and try experiments
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.
# Collaboratively map the current context
# Use the ELSE Scaling Principles to analyse the context for gaps
# Identify improvement options and prioritise
# Shape, run and support experiments
# Review, adapt and learn from the experiments
# Emerge practice
# Broaden and evolve
# Repeat


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|Defining Products Principles]] provide the background knowledge to inform your experiments.


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!
[[File:ELSE - Align to end-to-end Products.png|frameless|800x800px]]


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.


[[File:ELSE - Align to end-to-end Products.png|frameless|800x800px]]


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.
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:
&nbsp;                                                                                                                                                                                                                                                                                         
# Engage people and create the safety to surface issues and try experiments
 
# Collaboratively map the current context
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:
# Use the ELSE Scaling Principles to analyse the context for gaps
 
# Identify improvement options and prioritise
[[File:ELSE Change Journey.png|frameless|800x800px]]
# Shape, run and support experiments
 
# Review, adapt and learn from the experiments
 
# Emerge practice
 
# Broaden and evolve
 
# Repeat
 
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.

Latest revision as of 13:06, 30 January 2024

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.

  1. ↑ http://www.gurteen.com/gurteen/gurteen.nsf/id/to-turn-on-a-dime-for-a-dime
Retrieved from ‘https://go-else.org:443/index.php?title=How_to_Apply_ELSE&oldid=484’