Google IO 2012: Project Glass

Let's say I was developing a product with huge potential for privacy concerns and that my company was already under constant scrutiny for privacy issues, in part because the success of my business is dependent on stripping as much personal information from my users as possible. Maybe I would be worried about releasing that product and possible repercussions.

I think I might try doing a soft launch, call it a beta. I would do it to a small number of people, preferably fans of my company, who are highly enthusiastic, dedicated and talented. I would give those people the tools to play with it and come up with their own ideas for its use.

If bad things happen, if anyone takes issue with the product or the uses it's put to, I can take some cover behind its beta status. I can also claim that any privacy intrusive uses or life threatening results were not the fault of my company, rather it was the tragic result of a few rogue beta testers and developers. I can gauge overall public reaction by watching how many issues arise, how often the product is banned from use in certain venues, what percentage of people complain when they see the product used in their vicinity. I can prepare for issues before they arise in a full product launch.

"No senator, it was never our intention that this product would be used in that manner."

I might even model my entire approach to the beta after Google's Project Glass introduction at Google IO 2012.