One thing I've found when documenting any of my projects -- if it is too hard to explain clearly, then something is probably wrong with the interface. So what

One thing I've found when documenting any of my projects -- if it is too hard to explain clearly, then something is probably wrong with the interface. So what I end up doing is writing a document that makes sense, then I go back and re-write parts of the app in order to fit the documentation. Then, before tagging a release and announcing it, get a few other people to look it over first, just to make sure that everything matches. Oh, and having an automated test suite that at least checks all common cases and various edge cases will make sure that you don't have to hurry up and push a .01 followed by a .02, .03, etc. release. Now, that being, said, what is the best way to get a good group of pre-release testers? So far I haven't had too many people bite.