iPhone

Is success best measured by tickboxes or delight?

Product owners get hung up on the features, a shopping list of requirements rather than considering what is actually important to their customers.

Imagine it is 2007, there is no Apple, you are a new entrant developing a product that will go head to head with Nokia’s flagship phone the N95. You are the product manager who is responsible for the success of the product. You are focused upon beating Nokia; you’ve made it your business to intimately know the N95, you can recite the list of features it has from memory. You have a meeting with your design team and they break the news. They tell you the spec they have come up with.

“Let me get this straight” you say. “You are telling me that the phone you are proposing we take to market will have no Card slot, no 3G, no Bluetooth (headset support only), no decent camera, no MMS, no video, no cut and paste, no secondary video camera, no radio, no GPS, no Java…”

“Yup” the team say.

How do you feel?

Ditch the feature list that you’ve fixated upon in your quest to beat your competitors flagship product?

Only the brave would avoid the tick box mentality and strive for feature parity as a minimum requirement. Would you really throw out 3G, GPS and a decent camera; the real innovations in the market place?

The first generation of iPhone was released in June 2007, three months after Nokia’s flagship handset the N95. On paper, when you compare the phone features side by side, it is a sorry looking list. As a product manager would you rather have the iPhone or the N95 on your resume?

Below and here [SlideShare] is the story in pictures.

Dinosaur thinking

When Autotrader developed their cool and innovative iPhone app, they presumedly never paused to think what the DVLA would think.

Let’s say you are waiting at the traffic lights and you see a car you like and you think to yourself ‘I’d like one of those’ With the Autrotrader app all you need do was take a photo of the reg plate.  From that, details of the make and model would appear and similar cars for sale close to you your current proximity would be displayed.  Sadly, this functionality has been canned.  Autotrader say:

The DVLA has requested that Auto Trader remove the image recognition element of the iPhone application. Although the app in no way infringes data privacy regulations, the ‘snap’ function conflicts with the DVLA’s code of ethics, as it allows consumers to capture images of vehicle license plates.

This is the same government agency with ethics that enables it to sell drivers details.  That’s an aside.  Perhaps the DVLA’s  is more concerned with avoiding the trouble they got over Castrol using number plate recognition for interactive advertising.

With localisation being championed as one of the hottest topics of 2010 combined with the ubiquitous use of camera phones, it is clear that technology and the opportunities that it brings are moving at a faster pace than the ‘public opinion’ (read Daily Mail Opinion) that the DVLC is clearly running scared of.
So what?

So when you are envisioning and playing innovation games, have a session where you play devils advocate and tease out what angry from Tunbridge wells would think.  Kill your idea as many ways as you can.  Can you identify risks you’d otherwise missed (such as DVLA’s dinosaur thinking), or does it uncover new ideas or alternative ways of doing things (to bring out a cheesy quote from Benjamin Franklin “out of adversity comes opportunity”).  There is of course always another alternative,  to leave the innovation to others, for others to face the wrath of Government quangos and follow fast.  But that is a blog post for another time.

Make something consumers love

Bubblegum generation presents a compelling model for Apple’s iPhone strategy:

1) Pick an industry which sucks (ie, imposes significant nuisance costs/menu costs/externalities on consumers)
2) Redress the imbalance by making something consumers love
3) …Which disrupts the long-standing industry equilibrium, and shifts market power
4) Use said market power to redesign (a hyperefficient) value chain

Don’t think that organisations in industries that suck don’t aspire to “do an iPod”. Go to any proposition development or product strategy workshop and it won’t be long before someone is mentioning Apple products. Yet all too often they fail to do anything truly revolutionary; they end up doing something different rather than “Redress(ing) the imbalance by making something consumers love”.

Do customers want something that is different or something that is just better?

Interestingly, little functionally in the iPhone is new. Like every other phone on the market it makes phone calls, sends messages, receives emails, takes photos and allows users to listen to music. Nothing different or new there… other than being better than every other phone on the market.

What Steve Jobs espouses is the experience of the phone. He says “So, we’re going to reinvent the phone. Now, we’re going to start with a revolutionary user interface… Now, what’s the killer app? The killer app is making calls! It’s amazing, it’s amazing how hard it is to make calls on most phones.”

He’s not looked to do anything radically different, rather do it radically better.

So how do you bring revolution to your product set? Rather than trying to be different, why not try to better. Make something that consumers love?

Take a leaf from the Apple book and focus upon the experience. Design and attention to detail are critical. Moving beyond purely functional and satisfying products to crafting experiences that engage the emotions. In agile product development it is often easy to focus upon delivering functionality that is perceived to deliver business benefit, yet end up with a mediocre product that has little resemblance to the original idea it was meant to become. Incremental delivery is a key feature of agile; it means you get stuff out there early and often. The challenge is to identify what that stuff is. To make something that consumers love using the agile approach, in addition to great developers and focussed project management, you need three people;

1. A passionate sponsor who has a dream and a vision and can articulate that to the team, banishing mediocrity from the outset
2. A business analyst who will help the team slice the functionality according to consumer needs and desires; that take the consumer of the journey they want to travel, not a predefined route that constrained to picking those features that eventually will deliver greatest value.
3. A customer experience architect, interaction designer or graphically minded usability dude who can champion the product aesthetic and usability.

Get them on your side and maybe you might be taking the first step on developing a better gizmo that your consumers will love, and sleep outside your retail outlet for hours to buy one.