Good Morning!

I agree that it is a huge mistake to over document. I have a Developer's Mantra that I try to have my entire development team repeat to the customers/clients/users: "Don't tell me your solutions! Tell me your problems!" We developers are in the business of solving problems. While I am always interested in hearing how the user would approach the solution, until I know what the problem actually is, I can't really be anything more than a coder.

Same for Disaster Recovery. If the server farm explodes, the problem is that I need live_Database_X up ASAP. I then need devel_Database_X up within a week. The folks doing the Disaster Recovery should have enough information to know how to rebuild a working SQL Server box and reload database from backups. (Or backup backups.)

So document enough so they know WHAT they are doing. Don't bother telling them HOW to do it.

Nik Hughes