Archive for January, 2014

Let’s talk about the CDO- again!

    I got roped into another “the time has come” debate about the Chief Data Officer. I maintain that IMHO the CDataO is pure hype. Here’s how the roles of the existing C-suite play out:

    CEO: What we need to do
    CMO: How can we use it or apply it to better our product/image/business
    CIO/CTO: What tech strategy do we need to adopt to get there and subsequently maintain/scale
    COO: How can we implement these changes while maintaining normal business operations?

    There’s really no room or need for a data officer- because it is close to impossible for one individual to determine all the combinations in which data can be useful to the people in the company. Will creating a new CDO position magically fix data governance, reliability and accessibility issues let alone make it more meaningful all of a sudden? No way! It’s all about understanding that these issues exist and need to be addressed & fixed.

    The reality though is that I get angry and sad to see hype like this gaining momentum- it almost makes the real promise of big data seem illegitimate. I was pleasantly encouraged when Jim Stikeleather from (CIO- Dell/Perot) concurred with this remark:

    “Sharda is spot on. There should be a lead data scientist under the CInfoO, and a lead enterprise architect, and a lead security analyst, etc. The issue IMHO is that CInfraOs are neither strategic or knowledgeable enough to lead those other roles. The CMO should have the analysts (mathematical and marketing) who are supported by the data scientist. Business units / COO / etc should have their own domain experts supported by the lead enterprise architect (including enabling the orchestration and choreography among enterprise and SaaS applications). A good CInfoO understanda they are an enabler and facilitator, not an owner (or a prohibitor – which is what CInfraO tend to be).”


, , , , , , , ,

Leave a comment

DOs and DONTs of working with remote or outsourced teams

    As I was browsing discussions on LinkedIn, I came across a question from Natalia Ostraverkha – COO at Mobidev. She was asking about communication between teams on both sides of an outsourcing project (here). I had to chip in! This is a close-to-my-heart topic. Read on for my comments and let me know if you agree or not!

    In my past experience working with overseas teams (outsourcing partners) I found the following things to be very useful:

  • DO Be patient: When working with teams for whom English is a second language- it can be frustrating to have to repeat every sentence. However- put yourself in their shoes and remember you’d be struggling if you had to do business in Chinese, Hindi, Russian etc.

  • DO Be part of *their* team: You can get a lot from even a mediocre team (and the team I was interfacing with was definitely mediocre) if they recognize that you are part of their team. Words like “We”, “our goals”, “our progress”, “our accomplishments”, “our missed deadlines” vs you, “your ” create a team-spirit that is palpable across even a phone line.

  • DON’T be funny: I remember attending a seminar years ago where a senior engineer from IBM was talking to us about working with overseas teams. She said that nothing could bomb on an inter-cultural team meeting like humor. Humor does NOT transcend boundaries as much as we’d like it to. Get to know the team you are working with and over time, you can inject humor to lighten the mood.

  • DO be diligent: It’s very important to understand that in Asia- people really respect knowledge (and yes titles). They also assume you are stupid unless proven to be smart (if you have a good title- then you are given a little more room for errors). So be smart. Be intelligent. Don’t fake it. Do your homework. Earn their respect. Only then can you give orders and expect them to be followed.

  • DO know the goals of the project: Whether you chart the course from the very beginning or make adjustments along the way, have a good feel for what your working strategy is going to be. Be candid with the team about it up front. (If you expect changes to be made- tell them- so they can expect it too). Also- make sure you have a good understanding of what will define a successful project (technical, business, process wise etc). It will influence the energy and performance of the team you are working with greatly.

  • and finally

  • DO be honest: If you are unsure about something, please be honest with the team about it. If the deadline is creeping up and you are feeling the pressure- share it.

  • Working with a remote team is as much about psychology as it is about technology. Also, it was incredibly challenging when I was doing it but in retrospect, very rewarding as well.

1 Comment

It’s trendy to use #BigData @ #CES2014

Recently, I was involved in a discussion on LinkedIn on whether or not Big Data was enabling better customer service. I think the trend at the 2014 International Consumer Electronics Show (CES) indicates that Big Data is actually enabling better customer experience. If you are a more established provider of similar services and products, then you will be compelled to sit up, take notice and make changes to keep up with these leaner, smaller and providing service-in-real-time competitors. That is, if you haven’t already started to do so.

According to Forbes (read article here), the biggest disruptive trends include the use of MEMS (microelectromechanical sensors) in everything from your household appliances to wearable clothing to self-driving cars. Look past the coolness factors of these products and you cannot miss the incredible behemothian force of big data technology driving them.

The data points collected by the sensors can broadly be classified under the umbrella of semi-structured data. This gets stored in either a private or commercial public cloud based store. The product/service provider generally offers some out of the box apps. In addition, they offer authentication and access APIs for users and developers to consume freely to create their own apps (and most likely, contribute them back to the provider’s eco-system). This is the evolution of the B2C big data ecosystem. All this ties back to improved customer service if and only if the product or service provider makes an attempt to track consumer behavior, actual apps created by their customer base, user feedback, customer reviews, competitive trends. Extend this to measure the impact of all these intangible factors on company revenue, profitability and product planing- now you’ve just made the case for an enterprise big data analytics solution.

See to learn how the qLSocial and Genie products can help your enterprise attain the goal of improved customer service and better business insights.

Leave a comment

Gimme more data strategy!

Gimme more data strategy!

I found this article on with an incredibly provocative suggestion- the CDO’s time has arrived! I had to stop and think about that for a bit. My first reaction was “I have to agree- this is a valid point”. Then I read the article and found that I had to reverse my position after all. Here’s my response to the author: 

“A CIO who understands the need for a proper big data strategy- technology, infrastructure, scalability, governance, accessibility- will do more for an enterprise than a new CxO title. The reality is that data is most powerful when everyone has access to it for their needs. What organizations require is for the data, information and knowledge to be available to the right people as and when they need it- without waiting on data specialists. Such an enabling-focused strategy will benefit any business in the long-term.”

, , , , , ,

1 Comment

%d bloggers like this: