Jul 29 2008
Beta Testers for the Bold, MPC 5000
Who’s testing your product?
Blackberry is sending out Bold’s to users. Real users. People who are trying to sync their phones to their Macs, their Windows XP machines, and maybe even an Ubuntu machine. They’re using them in real world environments.
I’m sure if there’s a problem, someone at the home office is going to hear about it.
What happens when you’re not beta testing properly? You get super-fans and power-users going on 2700 word diatribes about how awful your product is. [For those not in the know, the author of this blog post is Just Blaze who's put in his work. Warning: Video below is for super-nerds.]
How can you tell if you’re beta testing properly?
1) What controls are you using? Are they the same controls you’re going to be using at launch?
2) What is the profile of your beta tester? Is it exactly like the profile of your user?
3) What will you do if something big is found out to be wrong. Like, not just big, but BIGG. Two G’s. Are you going to be able to fix it? If not, you’re not beta testing. You’re a little bit further into your release than you thought. (Delta launch?)
4) If there aren’t any known bugs in your beta release, it’s not a beta release.
5) If you’re working with software, are the improvements to the full release going to be substantial enough that you can fight back (the right way) against piracy?
For the comments, what makes your beta releases worth the effort you put into them? How do you get your feedback?



salesman, write a book about sales. This is not the first thing you should attempt, but it will help you sell your other products later by giving you credibility. The best thing you can do is find a niche and be the authority on it.
"I'm an artist, and if you give me a tuba, I'll bring you something out of it." (c) John Lennon 


