Great article, Mike. One thing I would add to it is to emphasize in the IT world is that documentation should be occuring throughout the troubleshooting effort. Record what you're doing. Record what the results were. That way if you have to rollback, you know exactly what you did and in what order you did it. In the scenario you've described I'm sure there is documentation continuously going on. When you check vitals, etc., you're probably recording some info, just like you probably did with initial information. A lot of times in troubleshooting what frustrates me is when I get brought on to help find out what is wrong and I ask the folks that have already been working the problem, "What have you done to this point?" and they can't give me a good breakdown of what has already been tried and what they saw when those things were tried.