Launches: later the better?

One of the main bones of con­ten­tion when it comes to comments on the Nokia blog is product launch dates. Put simply, they are always either too early or too late. Too late because some people want to buy the products as soon as they’re announced, and any launch date there­after is wrong. Too early, because some­times there are bugs and they have to be fixed with firmware updates, both of which are, in some people’s minds, evidence of gross neg­li­gence. I tried to tackle some of the demands for an early release in this piece, which first appeared here.

– –

In the world of the Web, the expres­sion “release early and often” has gained a lot of currency. It refers to the way web com­panies like Google and Yahoo! seem to have a brand new product every week. Smaller com­panies are in on it too. If you read blogs like Mashable and Techcrunch, you’ll find new, often innov­ative web services every single day. They’re labelled ‘beta’ — because they might not work the way you expect. But they’re often free, so nobody can complain too much.

Another way this is some­times put is “fail early, fail often”. The advice makes a lot of sense when it comes to par­tic­ular types of product. Try to do some­thing. Put it out there. If it works, then great, and if it doesn’t, try again. But keep moving quickly so you can retain first-​​mover advantage over your com­pet­i­tion. If your service isn’t evolving, it’s sug­gested, then it is decaying.

This philo­sophy seems to work very well in some markets. It’s probably not great advice when it comes to making phones, though.

When people buy a phone on contract, they’re making a big invest­ment. Currently, 24-​​month con­tracts at £30 a month or more are common for smart­phones in the UK. That’s £720 for your phone. Depending on the model you choose, there might be an addi­tional payment up-​​front.

When you’re making that sort of invest­ment, then you don’t want a product that’s been released early. You want some­thing that works as advert­ised, out of the box. Getting a new phone is a big decision: you want to feel jus­ti­fied that you’ve done the right thing. You want to be able to pat yourself on the back for being so clever, not worry that you may have got it wrong this time.

Then there’s also the fact that phones are made of metal, glass and elec­tronics. If you don’t get those right from the start, then the product is ruined. You can’t download a patch for a wonky catch or a flick­ering screen. Of course, firmware upgrades can upgrade or improve some aspects of your phone — and they’re very welcome — but getting some­thing that doesn’t work right in the first place is a definite no-​​no when it comes to big purchases.

But where this Web 2.0 philo­sophy of con­tinual releases and upgrades does work very well is in extra services. Things you weren’t paying for that you get for free. For example, no-​​one who bought a Nokia smart­phone before January this year expected to be given voice nav­ig­a­tion through Ovi Maps for free. But that’s what many of them got. It’s not only nice to be gifted some­thing valuable by the people who made your phone, it makes you like them more and means that you’re more likely to come back to them when the next contract is due.

So yes, release early and often. But only when it comes to the added extras.

picture credit: Edgar Zuniga Jr.

Share this post:

Digg This
Reddit This
Stumble Now!
Buzz This
Share on Facebook
Bookmark this on Delicious
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Possibly related:

Leave a Reply

  

  

  

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>