I would not give a fig for the simplicity this side of complexity, but I would give my life for the simplicity on the other side of complexity. – Oliver Wendell Holmes, Jr.
I remember attending Mobile Money Monday sometime in November, 2010 for a session on Mobile Web Trends. At that time, I was still thinking about how the whole service delivery platform had changed from SMS to USSD and MMS to GPRS and mobile applications. However, In his talk about the Mobile Web, Shwetank Dixit from Opera made a very interesting comment about the mobile explosion in Kenya and its impact: It was based purely on existing technologies such as SMS and USSD. In fact, the entire mobile money service of m-Pesa is completely based on USSD. The thing is if services can be delivered efficiently on existing technology platforms, then why use more advanced platforms as what is happening in the mobile industry ?
One obvious reason is the UX. Basically, mobile OS’es such as Android, the Apple iOS and Symbian allow developers to build pretty GUIs and define how text and graphics should be displayed rather than just a string of text. But I think there is a more important reason than that. It’s about transferring complexity from the development stage to the deployment platform.
I know I know. Too many multi-syllable words in that previous sentence. So here goes. If you had to develop an application using a normal non-OS solution, you would basically have to learn how USSD text works, how the network would deliver it and basically how to build an USSD-based product which does not typically work on C++ or Java or some other well-known OOP language. Secondly, design-wise you would barely get any flexibility. SMS limits you to 140 characters. Too many messages and it jams up the inbox (without any way to delete old messages automatically). Only text. The business model requires extensive network tie-up, etc. Basically, at the developer end you get badly killed. So it’s simple. Build it on an Android or/and an iOS platform and deploy.
However, what happens is that the complexity of building the app is not killed. It is transferred. It is transferred to the customer who has to replace his existing barely-feature-rich handset to a fully loaded Apple iPhone to enjoy the product. It probably requires a GPS-enabled handset to locate a joint. It requires MMS capabilities to send across the required data. This is all fine in the USA but in countries like India and African countries, people first demand proof-of-concept before any adoption takes place. That’s why handsets with radio facilities exploded in Mumbai. The concept of radio and its entertainment value was already tested and proven. Apps and GPRS-based services, however are an entirely different story. So was interactive TV which failed because people refused to adopt it without any proof of concept. So we end up missing a whole section of people who hold back from moving up the value chain because they don’t perceive value in moving.
I’m not writing this post from a developer’s point of view to increase adoptibility. I’m viewing it from the customer’s point of view. My biggest frustration is that a lot of people don’t have access to critical services and information because the complexity of the operation is transferred to them. It’s not that it cannot be done on a simple technology. It’s just that it requires a lot more (a LOT LOT more) effort from the development team along with certain UX and feature compromises to deploy the basic information on a plain-vanilla platform. And this kills adoption by people who could really use and benefit from the service: whether it is the rural poor unable to access financial services because they don’t have proof of identity (designing a process that requires documentation to open accounts is easy; deploying a product like UIUD across the country from scratch for people with absolutely no documentation of existence is difficult. (In the first scenario, the complexity is transferred to the customer – the responsibility to run from pillar to post to get the required documentaiton, in the second, it is transferred to the provider which simplifies the subsequent processes for the poor) or the humongous number of brands and sub-brands we face every time we go to make a purchase (tweaking a few options and launching them as multiple sub-brands is easy which transfers the complexity of making the choice to the customer).
The second example reminds me of Apple. When Steve Jobs (hesitatingly) accepted the role of interim CEO, his first action was to do a in-depth review of all of Apple’s products . There were around 50 of them. Basically, customers had to choose among 50 of Apple’s products alone, forget about what HP, Compaq and Dell were launching. The complexity of choosing products to launch was transferred to the customer as products to choose from. As Steve himself said during WWDC 1998,
What I found when I got here was a zillion and one products. [...] It was amazing. And I started to ask people, why would I recommend a 3400 over a 4400? Or when should somebody jump up to a 6500, but not a 7300? And after three weeks, I couldn’t figure this out! And I figured if I can’t figure it out working inside Apple with all these experts telling me into it, how are our customers going to figure this out?
Steve decided to simplify. Legend says (and so does Icon
) that he went up to a white board and drew a 2 X 2 matrix. The rows were “Types of computers” i.e. Desktop or notebook and the columns were “Types of users” i.e. Professional andConsumer (as per the picture below). That’s it. 4 products. Simple. And with that, he conquered the world.
I think the basic point of what I’m trying to say is this: It’s that not all complexity can be killed. Those are few and very obvious instances where it can actually be removed from the process and the product. The problem is the complexities which get transferred. It’s when we can’t deploy services on simple platforms that middlemen arise. It’s the problem of standing in line for railway tickets that travel agents for trains arose. Online booking have reduced that complexity somewhat, but not without setting up its own complexities of requiring internet access and owning credit cards and bank accounts. It’s when there was a difficulty in getting a driver’s license (demanding repeat visits to the RTO) because the list of documents required was not updated that agencies who help you obtain driving licenses arose. It’s the complexity of choosing across multiple (and only slightly different) products that personal shoppers arose. Unscrupulous moneylenders make unheard of profits because of the complexity of opening a bank account or getting crop insurance.These intermediaries take on the complexity and put in the effort required to resolve that complexity. To be fair, some of these middlemen obviously also provide a lot of other services to help the customer through fair and legitimate results but their jobs exist because of this complexity. Complexity which should not have been handed over to the consumer in the first place.
Telecom products and VAS are still at their infancy. In my opinion, this is the first infrastructure sector that is actually a carrier of knowledge rather than crude oil or power. It is, in fact, as I optimistically believe, the answer to the wide-spread problems of rural illiteracy, ignorance, lack of participation on vital issues and influence of propoganda . However, if these products / information are halted at the gates of customer complexities, it’s akin to the bureaucracy which refuses to let life-saving medicines into the city through octroi because the papers are not in adequate order. In fact, I have to re-iterate that. Customer complexity is like a bureaucratic government corporation – a bureaucracy that prevents information from reaching its rightful owner. The owner shouldn’t have to run from pillar to post sorting out the mess. It should be the producer who takes on the responsibility to deliver the information to the consumer’s footstep no matter where he is. It’s easy to demand that the customer accept some of the complexities to better their own lives. It’s a fallacy to expect it. It’s only when the consumer adequately believes in the proof-of-concept in his existing state of being, that he is ready to be hand-held into the more advanced nuances of your service/ product.
Bonus link: When strength becomes weakness. Dave Trott may be an advertiser but I swear, each one of his posts is worth printing and pinning to the wall !
Bonus talk: One of my favorites Barry Schwartz on the paradox of choice (based on the example of too many brands to choose from)
Update: Found another couple of videos on the topic from TED which I forgot to add
Sheena Iyengar on the art of choosing:
A slightly different one on choice which actually supports choice up to a point: Malcolm Gladwell on spaghetti sauce







