Pick the process improvement process you prefer and there will always be an analysis phase specified before deciding what to improve.
For this entry, I am going to focus on the postmortem or 'lessons learned' which should be done after any project or iteration and the interesting reasons why the analysis rarely leads to any change.
When gathering the good, the bad and the ugly, there seems to be a natural propensity to state the symptom and not the problem. Gather the symptoms and spend the time analyzing which are just symptoms and spending the time doing the analysis to uncover the problem. Some symptoms do need to be addressed, but once they are do not ignore them especially when they are an indication of a problem.
Avoiding the analysis ( the hard part) rarely leads to any meaningful improvement so focus on uncovering,understanding and addressing the problem and do not just list and address the symptom.
Aspirin is wonderful for a headache but not very effective if the problem is a brain tumor !
For this entry, I am going to focus on the postmortem or 'lessons learned' which should be done after any project or iteration and the interesting reasons why the analysis rarely leads to any change.
When gathering the good, the bad and the ugly, there seems to be a natural propensity to state the symptom and not the problem. Gather the symptoms and spend the time analyzing which are just symptoms and spending the time doing the analysis to uncover the problem. Some symptoms do need to be addressed, but once they are do not ignore them especially when they are an indication of a problem.
Avoiding the analysis ( the hard part) rarely leads to any meaningful improvement so focus on uncovering,understanding and addressing the problem and do not just list and address the symptom.
Aspirin is wonderful for a headache but not very effective if the problem is a brain tumor !
RSS Feed