This is from my experience and it hasn't failed me yet. It actually saved me in more ways that I can count:
- Stay away from Dev modules(mod), unless you want to be part of the user testing.
- Create a backup before you add the mod. Using Direct Admin works best for me.
- Add the mod in the correct folder. " ........../domains/yourdomain.asu.edu/public_html/sites/all/modules" is recommended for Drupal 5+.
- Read the readme.txt file that is with every mod to study changes and what it does to your install. (You will need to extract the compressed folder to read it.)
- Also check the ReadMe.txt if the mod has any dependencies such as CCK, Views, or core modules.
- When you login with your admin account, check "User Management >> Access Control" to see if you need to add mod use permissions.
- Don't install any other module to monitor conflicts for at least a week. It is VERY hard to find a problem in Drupal with so many multiple variables.
- If you don't like it, disable it first, then delete the folder in direct admin.
- Check you see if their is another way, most likely someone created something else that works better for your needs.
- If you find a mod that work great for you, tell us about it.

Installing contributed moduleshttp://drupal.org/node/70151