Setting up an open beta program and questions
We’re setting up an open beta program. What does this mean? We’re not really sure because we just made it up.
Here is what we think. We’re working on a beta version of our first service. Keeping a closed beta program is very typical (wherein beta testers are privy to versions of the software prior to anyone else and as such are asked not to share this information with anyone), however we’ll be setting up an open beta program where our beta testers will be free to share the details of our service with whomever they want. They can blog about the problems with our service (as long as they let us know about the problems first) - they can let people know what we’re doing - pretty much anything. We feel that not only will this help us on marketing the product, but perhaps we will be able to collect the perspectives of people outside of our beta program - even if they are not directly in contact with us or the service during beta.
Has anyone ever heard of doing something like this? Do you have any tips regarding setting up a solid beta program? How to solicit good beta testers? How to get a wide-spectrum of testers? Do you setup a reward system for providing valuable feedback?
If you are interested in being part of this program - send me an email and we’ll get you setup - beta is coming soon.
Email sent. I’m quite curious about the service.
As for rewards, I don’t think it’s necessarily something you have to plan out at this point. Rewards are a nice “Thank you” at the successful completion of a beta stage, but don’t necessarily attract the best beta testers if they’re offered up front.
December 12th, 2006
Jeff Smith: Glad you brought that up. I’m all for giving people some sort of benefit though for being good beta testers. Say - a free pro account of the service or whatever. But I agree with you on not setting up a system prior but merely reward the outstanding testers
Thanks for the feedback and thanks for signing up to the beta.
December 12th, 2006