When Product Rollouts Go Bad: Learning from Firefox & Verizon
Writing by Darrin Dickey on Friday, 27 of June , 2008 at 2:09 pm
Image via Wikipedia
Image via Wikipedia
Over the past two weeks I’ve witnessed two product rollouts (from the consumer side) and learned a lot from them - especially how many things can go wrong. The most unfortunate part of it is that a lot, if not most, of the problems could have been avoided… or at least contained. You may be wondering what this has to do with history. Every day, across the globe, people are rolling out new history books, movies, music and artwork. Historic houses, museum and organizations are rolling out plans for events and products. Maybe these experiences will help you prepare for a more successful rollout.
Firefox is a popular web browser and users across the globe have been anticipating the release of version 3 of the software. Someone came up with the great idea of feeding & building that passionate community. They set a goal to enter the Guinness Book of World Records for the most downloads in a 24 hour period. They declared June 17th as Download Day. A nice website was built that hosted community forums, featured event promoters who were the most active, collected commitments for downloads from hundreds of thousands of people and featured a world map that showed how many people had committed to the download from each country. People around the world were planning download parties and the Spread Firefox site was the central planning place. This was great work on their part and when midnight came and June 16th slid into June 17th, the Firefox world was full of… really ticked off people. And lots of them.
You see, the globe has time zones and while the Download Day folks did announce the time it would start (10am Pacific Time), they didn’t do it very prominently. Most people just saw the date, June 17th, which was featured and promoted heavily. And June 17th in Tokyo, Japan and June 17th in Mountain View, California, USA are not the same. Potential downloaders stayed up till all hours of the night and early morning waiting for the promised Download Day and then trying to figure out what went wrong when it didn’t materialize. To make matters worse, when 10am Central time came, the Firefox download page changed to “Download Firefox 3 Now” buttons. But when you clicked the button, it took you to a page to download the old version of Firefox 2. In fact, this error wasn’t corrected for at least a couple of hours. Downloaders were mad all over again. At last, the problems were ironed out, download links were corrected and more than 8 million downloads of Firefox took place in that 24 hour period. But how many angry people just decided to download the software another day?
The second rollout was Verizon’s introduction of the new LG Dare. It’s a strong contender against Apple’s iPHone (Verizon’s strongest yet) and Verizon customers were already excited about it, even though Verizon didn’t appear to be and kept it hush-hush. In my opinion, Verizon had already made a mistake by not organizing and feeding the growing community of people looking forward to the phone. Despite LG and Verizon being very mum on the subject, photos and reports on the Dare leaked out and each lead ratcheted up the excitement. Verizon could have done a lot to really build this excitement, but they pretty much ignored it, only releasing (as far as I could find) one vague press release about the phone. In fact, it’s on sale date wasn’t even announced until June 25th, the day before the phone went on sale in Verizon’s online store. It won’t be in physical stores until early July. To complicate things, Verizon didn’t even inform their own staff very well about the phone. The answers customers got on when the phone would be released and the price varied wildly from Verizon employee to Verizon employee.
Figuring the online store would add the phone around 12:01 am on June 26th, hundreds, if not thousands, of Verizon customers stayed up hitting refresh on their computers to make sure they got their order in. I was one of those people. 11:30 - refresh (just in case they were early). 12:00 - refresh. 12:01 - refresh. 12:05 - refresh. 12:10 - Refresh! 12:15 - REFRESH!! 12:30 - Argh! It still wasn’t showing up in my phone upgrade options online. I went to a forum dedicated to the LG Dare and, to my horror, I was a post that said the Dare was available online… and had been for nearly an hour! What?!?! I completely logged otu and then back into the store. There it was. I went to the upgrade page and… no Dare. I attempted to call customer service, but they had closed an hour before the phone went online and wouldn’t open again until 6am. (Note that the website doesn’t tell you what time zone. And they have offices across the US.) I tried the online sales consultant, only to receive a terse stock notice that said the live online sales area had closed for the day and I would need to try back tomorrow. About 1:30 am I finally gave up and resolved to call customer service the next day.
The next morning, too early and grumpy from the lack of sleep, I called customer service only to be told that their system hadn’t updated yet and the phone wasn’t actually for sale yet online (despite my having seen it). They told me I would have to try again later or go to a store. (Huh?! A store? This customer service rep told me the phones woud be in store this same day.) Eureka! I decided to just go to my local Verizon store and buy one. Too bad that info was wrong. Good thing I checked before hopping in the car and wasting my lunch hour chasing down the phone. I called customer service again and was told that they were updating their system now and I should be able to buy the phone soon. This was crazy. I then contacted their online live customer service. They told me that they were having technical problems that were preventing exisitng Verizon customers from buying this phone and they hoped to have them resolved soon. How soon? We don’t know. I was so frustrated. This had now been going on for more than 12 hours. As a last desperate attempt, I connected with the online customer service again and got someone else. I asked if they were having technical difficulty with people upgrading their phone online. (I wasn’t sure I believed the story.) I finally got someone with a brain who said, yes, there was a problem. But if I would call telesales, they would process my upgrade order right away, with full online discounts. Thank goodness. Someone was finally implementing a work around solution! I finally got my phone ordered, but I know from online communities that many others were still stymied throughout the day.
So, what is there to learn?
1. Plan for things to go wrong. They will.
2. Pay attention to the details, like time and date. They matter.
3. Communicate with your audience! A lot of the frustration and anger experienced by Firefox and Verizon customers could have been alleviated by posting simple situational updates and solutions.
4. Make sure a problem-solver is around. Verizon closing customer service an hour before the rollout was a really, REALLY bad idea.
5. Find a solution or workaround for the problem as quickly as possible. Verizon should have had the alternative ordering method going within an hour, if not minutes, of the problem coming up. It was a simple workaround until the problem was resolved. If you have a problem, fix it. If you customer has a problem, fix it FAST!
Category: Lessons Learned, Marketing 101, Personal Observations
- Add this post to
- Del.icio.us -
- Meneame -
- Digg
Pingback by When Product Rollouts Go Bad: Learning from Firefox & Verizon
Made Friday, 27 of June , 2008 at 3:12 pm
[...] Michael wrote an interesting post today onHere’s a quick excerptIt’sa strong contender against Apple’s iPHone (Verizon’s strongest yet) and Verizon customers were already excited about it, even though Verizon didn’t appear to be and kept it hush-hush. In my opinion, Verizon had already made a … [...]
Pingback by Books and Magazines Blog » Archive » When Product Rollouts Go Bad: Learning from Firefox & Verizon
Made Friday, 27 of June , 2008 at 4:04 pm
[...] Original post by BrandingFire Blog [...]
