Implement and Propagate the Fix

If you have multiple systems or if you're dealing with a product, roll out the tested fixes to your other sites. Make sure that any code changes are placed into your source code control system and into any archives that you use to prepare and stage your software for distribution. There's nothing more embarrassing than having to fix the same problem again because subsequent software releases lost the changes you've made. If you're really unlucky, this will happen a year after the first fix, and the person who made the first fix is gone Then you'll actually have to go through the process again. If you are not using source code control, start using it!

Document All Changes

In addition to placing changes into your source code control system and making sure that these changes get propagated to other or later systems, always come up with some sort of a written document that explains exactly what you have done and why you have done it. This will be of immense help later if you are trying to work through someone else's fixes, if someone is trying to figure out your fixes, or even if you are trying to figure out why you did something yourself a year ago. These changes should also be reflected in your system and application logs.