Any problem requires us to… 1.State the problem 2.Specify the problem 3.Develop possible causes from knowledge and experience or distinctions and changes 4.Test Possible causes against the specification 5.Determine the most probable cause 6.Verify assumptions, observe, experiment, or try a fix and monitor
The issue definition describes the 4 aspects of any problem; 1. What it is 2. Where it occurs 3. When it occurred 4. To what magnitude did it occur This results in an easily understood statement such as; The email system crashed after the midnight shift engineer applied a hot fix ABC to Exchange server named XYZ only We can use this information for the next step… Issue Definition A poor definition of a problem would be the server crashed. A better issue definition should include more information.
ISCould be but IS NOTDifferencesChanges What Where When Magnitude The Matrix 17
ISCould be but IS NOTDifferencesChanges What System Failure Similar systems/situations not failed Where Failure location Other locations that did not fail When Failure time Other times where failure did not occur Magnitude Other failed systems Other systems without failure The Matrix 18
ISCould be but IS NOTDifferencesChanges What Exchange server XYZ crashed upon application of hot fix ABC Other exchange servers getting hot fix ABC Different shifts applied the hot fix New patch procedure from vendor Where 1 st Floor server room (unsupport ed by vendor) Anywhere else that has vendor support External vendor support New procedure, 1 st time the midnight to 6am shift applied hot fixes When 2.25am 12/03/13 Any other time or location None noted Magnitude Any other 1 st floor server Other 1 st floor servers 19
Understand the Issue Gather info: listen & check Checklist to hand Ask Questions Listen Check Understanding