Washington Mutual: How NOT to Launch a Web Site

Ian Lurie Aug 3 2006

wamuglitchKudos to WaMu for demonstrating, graphically, how not to launch new features on a web site. A story on CNET points out that their online bill payment and banking system has been down since last Saturday.

In the mean time, they apparently didn’t really admit to anyone that there was a problem.

And Gary Kishner’s excuse doesn’t wash, either.

Here’s what happened:

1. WaMu launches new features on site.
2. Site fails.
3. WaMu tells customers it’s ‘routine maintenance’ (!!!).
4. Almost a week later, they admit it’s not routine maintenance.

Here’s how launching new features on a web site should work:

1. Test what you did.
2. Launch it.
3. If it fails, roll back to the old version.

My company is hardly perfect. We’ve had some real forehead-slappers. But leave an entire chunk of a site totally nonfunctional? For days?

Lessons:

A good quality assurance regime is critical to internet marketing.

When things go wrong, be honest with customers.

Always have a backup plan.

tags : conversation marketing

3 Comments

  1. I have a huge website launch coming up in a month. Well that is anticipated launch. I say anticipated because I am going to test everything! I would rather be a bit late then do what WaMu did.

  2. Update: Wama as of 8/16 still not functioning at par.
    As a customer for 4 years at Wamu, I’m extremely frustrated as I do all my billing etc online.
    Seriously considering switching banks.
    Test before launch!

  3. Christofle

    Christofle

    As a tech person in the trade and a customer I am apalled by the utter lack of technical and professional abilities exhibited by the people at wamu.com. Can you say ‘integration testing’? Can you say ‘regression testing’? Does no one know how to test and debug anymore? Just drop the code straight in to production and yippee!!! here we goooooooo. Yup. Poof! gone can’t wait to see how many people just decide to split. Duh.

Comments are closed.