CompuServe Messages

I've beta tested a couple of products for a company, and I've helped influence what went into the final design of both. The particular developer I work with really likes getting comments from the beta testers, but frequently doesn't get *any* sort of feedback at all. A lot of people who want to test either want to have the "status" of being a beta tester, or are merely looking for a tool that they need for something they're working on (ie, they need a specific tool, and the only way they can get it is by getting a beta version). You'd be surprised how often that occurs. Anyway, in the end it's up to the developer to decide what advice to take, and what advice to ignore. Developers should really listen to what the testers are saying, because it's more than likely that other people will have the same opinions when the product is finally released. That time management software you talked about is a good example. If that package makes (made?) it to market, they'd be ripped to shreads in the market place, and it would be their own fault because they didn't listen to a tester who worked with things like that before. Which brings up another point…The beta testers better know a bit about what the program is trying to do. I've turned down offers to beta test software because I didn't know a thing about that particular type of product (like business or music software). I've done that because I believe that it wouldn't be to the author's benefit to have me as a tester. All in all, it's worked out pretty well. Beta testing is tough work, if you do it right. 🙂 Steve