Mobility In India – Reminds Me of A BoneyM Song Bahama Mama


Last time I went to India was in May of this year. And I came back totally convinced that Mobility and Cloud have tremendous potential there. As I am flying back home to Phoenix now, after a whirlwind trip to India, I have a better perspective of opportunities and challenges.

I know BoneyM might not be popular with some of the readers – so check this video out. When I think of mobility in India , the lyrics of the song that goes “…6 beautiful roses, and no body to pluck them..” come to mind.

First, some observations from last week when I was in India.

Internet speed in India has increased by leaps and bounds, but hotels surely have ways to go in terms of bandwidth they provide their guests. I spoke to the staff at both Windsor and Leela Palace in Bangalore, both amazing hotels – and was told I will be pleasantly surprised if I visit a year from now. I will take them for their word since I know first hand over the years that they take customer service more seriously than almost any other hotel I have stayed in.

Mobile phone bandwidth on the other hand is a different story. I had poor up-time even with international roaming for data and voice. Voice surely was better than data by a long margin.

Device diversity is probably bigger in India than in US – and I found everything from iPhones, iPads, Androids of all form factors, Nokia phones and several blackberry PDAs. Email and Facebook are probably the most used apps from what I could see.
But almost every person I met is an expert in SMS messages. India runs on SMS (and missed calls – no voicemails, people just leave a “missed” call as an indication that they expect a call back).

Mobile banking continues to be a big hit with even the “tech averse” older generation taking an active interest now. I was pleasantly surprised to see many elderly folks take internet connections to just read news on internet, and do internet banking and save trips to the bank.

Mobile users in India seem to have lower expectations of functionality and performance than those in US and Western Europe. However, they do expect extreme simplicity. Given a choice, they would like to live in a world of SMS alone.

With these observations, I have to believe there is tremendous opportunity for someone to take that market by storm. Volume is not a problem in India – there are a billion people, and vast majority seem to have a mobile device of some sort. However – I think a mobile solution for India should have some common aspects to succeed.

1. It should be inexpensive

India needs a volume pricing – and buyers are price concious. And this would mean whatever solution is put in place needs a solid platform to go with it that gives economies of scale.

2. It should work in any device

There is no one favorite device.  It is a gadget friendly nation

3. Wherever possible, use SMS

The country practically runs on SMS. It will take time to change to something else. But if SMS can solve an issue today, there will be lot of people who will buy. This is also good from a multilanguage support point of view. It will be an expensive undertaking to build apps for each Indian language.

4. Offline capabilities is a must

Given high availablity of bandwidth is a pipe dream in several parts of India, some offline capability is a must for any mobile app

5. Government, banks, construction and transportation are easy pickings

Forget your political leanings – India is all about big government, and people look at government for all kinds of things. Vendors should embrace this and not fight it. On bright side, there is plenty of interest from government to IT enable everything. Banks are already on forefront of mobility initiatives, but the opportunity is huge. Construction is probably where the biggest bang for the buck is – there is a high rise coming up anywhere you look. And I am yet to see engineers use a mobile device to do their work in those. Public and private transportation companies are used by everyone, yet hardly make use of mobility. These are the no-brainer type opportunities. I can think of another two dozen or so avenues for mobility initiatives

6. India needs local talent to develop and sell mobile solutions

This is applicable not for just mobile – but ANY solution really. It is a unique place, that many from outside India will find hard to figure out at a level needed to succeed in business. It is not a big deal for vendors since India has amazing talent locally, and a large expat community that can bridge any gaps. It will be a very strategic investment to utilize this talent pool and invest in it now.

7. Extensibility, multi language support can wait a bit

On first impression – it looks like several users in India can live for some time with out of the box functionality. From a good design perspective, of course it is better to build things with extensibility and multi-language support in mind. But it can wait for a bit – I think a profitable business model can be built for short to mid-term without needing a lot of enhancements and multi-language support. Of course I will gladly stand corrected if people who live in India point me in another direction. I am basing this on my short visits, and I am fully aware that I might not have picked up on the nuances.

The question in my mind is – who will seize the first mover advantage in India? Will it be SAP? IBM? Startups? By first mover – I mean the first to try to solve the problem in large scale. I am well aware that this is happening already in a low scale fragmented mode. I must admit I am quite tempted to give it a go myself.

Can Enterprise Software Innovation Be Industrialized ?


Every enterprise software vendor I know of touts innovation in every message they share with their ecosystem. It has many flavors – open innovation, inclusive innovation and so on. Yet, there are very few products that come out that customers cheer as innovative.

That shows a couple things clearly, in my opinion
1. There is more thought leadership and marketing about innovation, and less actual innovation
2. Innovation does not scale

More Talk, Less Action

This is not a surprise, since generally talk precedes action in software circles ( as proven by hype cycles of SOA, social business, big data etc in last 5 years alone).  SOA by now is well accepted, and real projects use it. When it first was talked about and evangelized, very few projects used it. Social business and Big data will most probably follow that same trend.

But unlike with SOA, I see a disturbing trend with newer topics. People who talked up SOA had a good proportion of folks who knew what they were talking about. They could articulate the value proposition, and answer criticism logically and explain the pitfalls. Even then, it took several years for actual projects to use SOA at scale.

That is not true for currently hyped stuff like cloud, big data, social business etc.  There is an absolute minority of people who can sound credible when they talk about these topics. That scares me.  A lot of evangelists of cloud, for example, have never seen a data center, worked closely with an IT organization , been involved with a CAPEX/OPEX decision in their life at big scale, or negotiated a software contract to know how lock in happens in on-demand and on-premises world. Yet, they have no problems advising CIOs (at least allegedly advising) on what they should do about cloud.  And they are the loudest – so I always worry some CIO will inadvertently fall for it and make a bad decision.  A lot of reasonable voices on cloud just drown unnoticed because of the loud evangelizing of the people who are unreasonable.

There is a simple reason I worry about this topic.  I get paid for actual execution of projects. When unrealistic expectations are set for my clients, my job gets harder because a lot of my time will be spent in convincing people to let go of fantasies and get realistic. That is time that I should have spent in executing the project.  I also get criticized by many friends that I have no incentive as a consultant to promote cloud, since it reduces consulting effort. Actually nothing is farther from truth. Cloud needs a lot of change management, integration and migration work . I ( and others like me) will earn a living doing that work instead of on-premises work. So – no , I do not worry for a second about my work disappearing.

Does Innovation Scale ?

I used to think till very recently that innovation scales. I was wrong – it does not scale. I need to live with it. Innovation – and the associated disruption – is not every ones cup of tea. In fact most people cannot live with innovation in their work life. The same people usually love innovation as a consumer of someone else’s work.

 

To begin with – it is very difficult for two people to agree on definition of innovation.  For example, SAP promotes design thinking a lot. It is a simple philosophy, but if you ask 3 people in SAP to explain it to you – you will rarely get any consistency in their responses. That is not a bad thing really. If two smart teams are given a problem to solve – and they both follow design thinking approach – there is practically no possibility that the two teams will come out with same solution. We all have our biases – formed by our life experiences. That decides what questions we ask, and you only get responses for questions you ask. And the solution you design depends on those answers. Ergo – design thinking is not a magic bullet that helps industrialize innovation.  It does help provide a structure – and that is pretty much it.

We all know what happens when design happens by committee. And if Jobs and Ive tried to ask customers on how to get requirements for Apple products, how would that have worked for them ? So, essentially true innovation needs special people, who by definition are small in number in any population. And even those people can only come out with so many new ideas. Look at Apple – they have shifted to an incremental improvement model now. May be something truly innovative will come again from them in future, but it is a good point for rest of us to know how mass innovation does not happen.

I am still on the fence on effect of inclusion on innovation. That is what I am planning to think through in the next 36 hours or so that it will take for me to reach India.

SAP Teched 2012, Las Vegas Recap – The Customer Is Always Right


This is the first blog post by my buddy Nathan Oyler, and I am honored that I got to host this. Nathan is an Enterprise Architect at SAP, and works in Oliver Bussman’s organization . He specializes in Hana.

I met Nathan on twitter last year, and we have been friends since. We both enjoy Indian food, and technology – and hence most of our techie chats are done at our favorite Indian Restaurant, Chutneys, at Tempe, AZ.

You can follow Nathan on twitter as @nathanoyler

—————————————————————————————————————————————————-

Teched 2012 was the first Teched I’ve attended, and it was as an SAP Employee working at the SAP runs SAP booth. SAP runs SAP is a project developed by our CIO Oliver Bussmann to ensure that SAP is always a first customer of products that we create. I work as an enterprise architect at SAP running the internal implementations of ERP on HANA, CRM on HANA, HANA as a side by side accelerator, and many other internal projects. I spent several months preparing innovative demos to present at Teched.

I approached each customer the same way asking what they were interested in before considering whether showing the demos fulfilled their needs. What I learned quickly was that customers loved the story of SAP runs SAP, and were very pleased to hear about the different systems we run internally, but it didn’t fit their immediate concerns. Innovative demos are nice, but they wanted real advice on how to implement BW on HANA today in their current environment.

I was blown away, and decided to do the only rational thing. I became an architect for each customer that visited our booth. I asked each customer about their environment to understand what sort of challenges they experience. I listened intently before I spoke and tailored everything I said to the direct specifics of their situation.

It couldn’t have went better. Over and over again I worked hard to consider ideas from the customers as if I was an architect working for them. There were configurations I had never even considered before. There were older versions of our products that I didn’t know customers ran! It was fascinating hearing about their challenges and considering options to improve their situations.

And they listened. The fact that it was IT talking to them as opposed to a sales guy really made a difference in my opinion. I wasn’t trying to sell them on anything, but really made an honest effort to determine what I would do. In some cases I even suggested holding off on HANA, and instead focusing on other topics that were very specific to their business. Most of the time I thought BW on HANA was the right fit, and helped many customers make improved business cases for themselves.

It was tremendously difficult to deal with the range of questions people had, and there is no way I could have done it without the teammates at the SAP runs SAP booth, Dirk Pluschke, David Poisson, Oguzhan Genis, Bjoern Brencher, Martin Lang, Paul Rostagno, and Eileen Butler. They allowed me to roam a bit while providing wonderful Demos on Business Objects, SAP applications for Windows 8, Mobile Applications designed by SAP IT, and providing many talks as well. It was a tremendous effort from everyone, and I’m really proud of SAP IT being a leader in helping shape customer decisions.

Overall I thought this year’s Teched was a huge success. Many of our customers came into it unsure if HANA was right for them, and walked away with a clear understanding of the choices, rewards, and challenges related to upgrading to BW on HANA. Several customers were looking for a HANA Architect to employ in their company, which shows the demand for HANA, and the need for skilled architects to help these customers add HANA into their environments.

It was a rewarding and frankly awesome time. I would encourage us to be in front of customers more often in an open Q&A Clinic where we can field any specific concerns they have. The most common thing I heard from customers was,

“My boss came here to have me get the answer to a question, and I can’t find anyone to help me. Can you?”

My job may have been to give innovative demos, however when a customer gives me a compelling challenge like that, I have to react. As we know, the customer is always right.