Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Fritz Nelson

Fritz Nelson

Vice President, Editorial Director InformationWeek Business Technology Network

Google's CIO Dilemma

CIOs are torn between wanting to back a company that represents the future and needing predictability. Google execs must now ask CIOs the right questions--and be prepared for stubborn answers.

Google thinks that it could earn $10 billion in enterprise revenue some day. Michael Lock, Google Enterprise VP, speaking at the InformationWeek 500 conference along with Clay Bavor, Google Enterprise head of product management, said that there are 5 million businesses on Google Apps, and 40 million users. (You can watch the entire discussion in the video embedded at the end of this article.)

But Lock and Bavor also said that almost every part of Google's enterprise business will simply follow the company's success in the consumer space. The enterprise business, Lock said, will "stand on the shoulders of the giants at Google." The strategy, he said, is to "bring the consumer goodness to the enterprise."

For CIOs, this must be a difficult dilemma. On the one hand, Google represents the future. Its products--from Gmail to real-time collaborative apps to Google Drive to Android--are the embodiment of the consumerization of IT era. CIOs dismiss Google at their own peril.

The typical customer Google wins is sometimes simply making a statement about how that company aims to do things differently, Lock asserted. It signifies an internal cultural shift, Bavor added. "When I talk to CIOs about products, they ask about Google Glass, about self-driving cars . . . there is almost this philosophical approach: I want to transform the way my employees think, to be more collaborative."

In many environments, Google comes to stand for something that's new and fresh and different.

On the other hand, Google has to come to terms with an enterprise mentality that demands a strategy, a roadmap, a commitment to some measure of predictability. Lock admitted that changing the perception of Google as "the search company" is hard. I pointed out the perception among many CIOs that the enterprise seems often to be an afterthought at Google, challenging Lock and Bavor to name a Google product that started out life as enterprise only. Bavor named Google Vault, an archival and e-discovery system.

Global CIO
Global CIOs: A Site Just For You
Visit InformationWeek's Global CIO -- our online community and information resource for CIOs operating in the global economy.

No, I hadn't really heard of it either. But to be fair, there is also Google App Engine and Google Compute Engine. Bavor also said that when Google first began working on Google +, the company's management team saw Hangouts (video chat) as an enterprise product.

Regardless, Lock made it very clear that Google is "not sitting around thinking: let's go disrupt this marketplace." Specifically, he mentioned customer requests that Google tackle CRM, and Lock thinks Salesforce.com is doing just fine. He said Google Chairman Eric Schmidt told him: "Be careful not to become what you're here to replace."

This is precisely where Google has its challenge. For some organizations, this consumer-first focus has come through too loudly, too clearly. Many CIOs complain about Google's support, for example. I asked Lock and Bavor what grade they would give themselves for enterprise support. They didn't, but Lock said that Google's enterprise customer satisfaction scores were above the industry average. Most CIOs I talk to have found Google's enterprise support wanting.

Some CIOs are willing to live with it, maybe even embrace it. Others run away just as fast. There seems to be no in between.

Two of CIOs addressed both sides of this Google-in-the-enterprise dichotomy on these pages. John McGreavy said, simply: Google Enterprise, I'm Not Impressed, whereas Jonathan Feldman wrote: Why MBAs Hate Google--And You Shouldn't. The title was a reference to Lock's quip: "A lot of MBAs at Google are frustrated because they want the five-year roadmap, and we're just not that way." To which an audience member with an MBA said: "When I'm going to commit hundreds of millions of dollars, I really do want the five-year roadmap."

Many readers--other IT decision makers--responded to the columns these two CIOs wrote. Those responses were typical of the divide Google elicits:

-- Joe Tierney wrote: "Workers shouldn't be marginalized. Why don't you poll them and see if they like Outlook or Gmail better? You might be surprised." In other words, don't dismiss the power of your user base.

-- But MrCynical responded (to a few responders) with vigor: "Your responses don't come with an enterprise mindset--and that's a shame. There is much more to getting the latest 'innovation' the end-users [want] than a 3 to 6 month roll out. How about support? How about maintenance? How about upgrades? Oh wait, we don't have to care because Google says so. Google is SaaS? Upgrades are seamless and issue free to the end user? Right. Again, Google says so … Having a 3-5 year roadmap is essential. Having our business units and users work with us is essential. While I can't predict what the world is going to look like in that time, I can dang well provide a direction. Road maps are not written in stone, they are a guide for the entire organization to reach the goals of the business. For the Jonathan Feldmans of the world who think that we should just take every latest fad and run with it to prove we are 'agile IT', good luck to you."

-- And then there was Dianejhuff: "As a company that moved to Google to replace our customer portal collaboration (email, shared media, meeting spaces) after two years, we are happily returning to an Exchange infrastructure. Although Google truly believes that it is enterprise worthy, I can assure you, it is not. Google lacks the collaborative and support infrastructure to maintain a large enterprise group. They worked well with a small group of users and, as a consumer product, they are second to none. But for our customers, their 'collaboration' features were poor, their support was weak, and their shared spaces rolled to three different names and products in the three years we were customers. I love my Android phone, but I'll stick with Microsoft for my enterprise services."

If Google believes its advantaged by leveraging the development work it does in the consumer space, then it should continue to pursue that strategy, and while doing so its executives should embed themselves with enterprise IT: Make it their mission to ask the right questions--the ones they need to hear, not the ones they want to hear, and to be prepared for the stubborn answers CIOs will provide. And then do what Google does best: adapt.

Informationweek.com run-of-site player, used to publish article embedded videos via DCT. The same ads will be served on this player regardless of embed location.



Related Reading


More Insights




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.