Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
blog:how_do_we_improve_our_improvement_process [2017/03/21 09:50]
Hans Samios
blog:how_do_we_improve_our_improvement_process [2018/12/03 19:30]
Hans Samios Added todo note
Line 1: Line 1:
 ====== How Do We Improve Our Improvement Process? ====== ====== How Do We Improve Our Improvement Process? ======
 +
 +<WRAP todo>​Work in progress</​WRAP>​
  
 One thing we talk about with agile is the idea of continuous or relentless improvement. Most organizations want to improve, but like a lot of things it is sometimes hard to feel good about the improvements you are making. Further it is hard to establish a continuous practice where the whole organization is doing these improvements and feeling good about it. One thing we talk about with agile is the idea of continuous or relentless improvement. Most organizations want to improve, but like a lot of things it is sometimes hard to feel good about the improvements you are making. Further it is hard to establish a continuous practice where the whole organization is doing these improvements and feeling good about it.
  
-One tool that I've seen helps organizations is to treat improvements as experiments and talk about them this way including a good definition of what the experiment ​is, what the expected result is, what the result actually turned out to be, what we learned, and what we will do as a result. And I would then maintain a list of experiments we have run somewhere in order allow others to learn from our experience.+One tool that I've seen helps organizations is to treat improvements as experiments and talk about them this way. The traditional approach to capturing improvement ​is to set up SMART goals. The problem I have with this approach is that we are treating the improvement ​as a conclusion (it will result ​in the improvement we expect - its deterministic) rather than recognizing that the new approach might in fact result in no improvement. And when this happens the thinking is that you have "​failed"​ because you did not meet your goal.
  
-In other words instead of talking about a change or an improvement we set up an experiment. ​+Learning is not failure. And to capture this instead of talking about a change or an improvement we set up an experiment.
    
 +To define a good experiment we need a definition of what the experiment is, what the expected result is, what the result actually turned out to be, what we learned, and what we will do as a result. This is the scientific method. ​
 +
 +And I would then maintain a list of experiments we have run somewhere in order allow others to learn from our experience.
 +
 So, for example, during a transformation to agile, we might want to understand whether the idea of a "True Team" (see [[:​why_do_we_form_teams_when_we_transition_to_agile|Why Do We Form Teams When We Transition To Agile?]]) actually is a concept that works in our organization. We could setup and experiment as follows: So, for example, during a transformation to agile, we might want to understand whether the idea of a "True Team" (see [[:​why_do_we_form_teams_when_we_transition_to_agile|Why Do We Form Teams When We Transition To Agile?]]) actually is a concept that works in our organization. We could setup and experiment as follows:
  
Line 17: Line 23:
   * Timing: Do survey 4 (say – need to set up in time for rollout) weeks after team kick off, analyze results and provide feedback one week after that   * Timing: Do survey 4 (say – need to set up in time for rollout) weeks after team kick off, analyze results and provide feedback one week after that
   * What Did We Learn?: TBD   * What Did We Learn?: TBD
 +
 +Then, when the time box is finished, we collect the result, and determine what we learned and what we do next. (Hopefully in this case you got the expected, positive result:-))
 +
 +Experiments can be done at all levels. Teams can set them up as part of a retrospective. Transformation coalitions can set them up as a result of their retrospectives. If you are doing SAFe experiments would be generated as part of a the Inspect and Adapt. And so on.
  
 Using this approach at whatever level you operate at helps you become a "​learning organization"​ where experiments are seen as a normal part of the work you do. The vocabulary will help and assists by making change less threatening (more "try it and see" and less "you will do it this way"). In particular we want to treat new understanding as a “success” (and publish it as a “win”) to aid the momentum. It also like to encourages a spirit of experimentation beyond just “lets try it!” (said in giggly tone). Experiments should be aimed at generating useful knowledge. Using this approach at whatever level you operate at helps you become a "​learning organization"​ where experiments are seen as a normal part of the work you do. The vocabulary will help and assists by making change less threatening (more "try it and see" and less "you will do it this way"). In particular we want to treat new understanding as a “success” (and publish it as a “win”) to aid the momentum. It also like to encourages a spirit of experimentation beyond just “lets try it!” (said in giggly tone). Experiments should be aimed at generating useful knowledge.
Line 22: Line 32:
 {{tag>​BlogEntry FAQ ToDo Experiment Improvement}} {{tag>​BlogEntry FAQ ToDo Experiment Improvement}}
  
-~~LINKBACK~~ 
-~~DISCUSSION~~ 
  • /home/hpsamios/hanssamios.com/dokuwiki/data/pages/blog/how_do_we_improve_our_improvement_process.txt
  • Last modified: 2018/12/03 19:30
  • by Hans Samios