CDW Talk on Enterprise 2.0 Technologies

of 18/18
ENTERPRISE 2.0: NAVIGATING THE SEA OF OPTIONS Business Technology Expo (BTEX) Phil Simon May 14, 2013
  • date post

  • Category


  • view

  • download


Embed Size (px)

Transcript of CDW Talk on Enterprise 2.0 Technologies


Enterprise 2.0:Navigating the Sea of optionsBusiness Technology Expo (BTEX)Phil SimonMay 14, 2013

Hello. My name is Phil Simon. Today Ill be talking about the arrival of Enterprise 2.0. Ill be talking about cloud computing, SaaS, Big Data, mobility, and a whole host of other topics.Ill be referencing my second book, The Next Wave of Technologies.Transition whos this guy? Offer prize/book to winner.


The future aint what it used to be. Yogi Berra

Enterprise 2.0, # 2

Yogi Berra was a former American Major League Baseball catcher, outfielder, and manager. He played almost his entire 19-year baseball career (19461965) for the New York Yankees. As a general comment on baseball: "90% of the game is half mental. when you come to a fork in the road, take it.LETS GO BACK 15 YEARS TO A MUCH SIMPLER TIME WITH RESPECT TO IT.


enterprise 1.0 (1995 2005)Deployment of COTS ERP and CRM applicationsOrganizations moved from mainframes to relational databasesThe introduction of e-mail, ecommerce, and relatively simple websitesFar too often, data silos hamstrung organizations and their employeesEnterprise 2.0, # 3

4 bullets1. Mention Why New Systems Fail2. Oracle, IBM & SQL server3. Email has remained the killer app4. Emphasis was on the application, not the enterprise. Transition: IN THE LATE 2000s, we began to hear the term Enterprise 2.0.3

Enterprise 2.0: Whats the point?Increase communication and collaboration among employeesIncrease quality ofand access toenterprise dataChange the focus: Move from department or application to organizationEnterprise 2.0, # 4

3 BULLETS this is not a definitive listDEFINE E2.0: Technologies include Cloud computing, MOBILITY, MDM, SaaS, open source, SOA, web services1. Move beyond email and intranets; unleash power of information in organization2. Data is very powerful, but only if people can access itand its quality isnt suspect.3. Remove focus from department, group, and division; begin to think enterprise- or company-wideTRANSITION: Now lets compare enterprise 1.0 and 2.0 across a number of different dimensions


access to the best technologyEnterprise 1.0With few exceptions, only large companies could afford best-of-breed technologies.

Enterprise 2.0Companies of all sizes can afford best-of-breed technologies.

Enterprise 2.0, # 5

Table 1Hedge funds

Table 2QUESTION: ASK PERSON IN FRONT HOW MANY EMPLOYEES WORK AT YOUR COMPANY. You can use the same services as Netflix a $12B company-> Even a small business can use AWS, just like multi-billion dollar Netflix.Mention the new small


Vendor landscapeEnterprise 1.0Organizations had to evaluate relatively few technology vendors and solutions.

Enterprise 2.0The number of options available to organizations is downright dizzying.

Enterprise 2.0, # 6

Table 1 MOST COMPANIES RAN WINDOWS, OFFICE, ETC. Many small businesses ran their own MS exchange serversTable 2And if you cant find what you want, just build it. The number and variety of APIs, SDKs, ISVs, and robust development platforms has exploded.


data storageEnterprise 1.0Extremely expensive.

Storage requirements needed to be anticipated.

Enterprise 2.0Very cheap; a commodity.

Storage needs can be adjusted on the fly.

Organizations can pay for only what they consume.

Enterprise 2.0, # 7

Table 1 Childrens Place ExampleTable 2Mention Kryders lawMinimize waste; more company-friendly pricing models


dataEnterprise 1.0Small Data

Relational, structured, transactional, table-friendly, and orderly.

Enterprise 2.0Big Data

Non-relational, unstructured, not table-friendly, and messy.

Enterprise 2.0, # 8




mobilityEnterprise 1.0IT provisioned BlackBerrys for a few key executives.

Few proper apps existed for cell phones

Enterprise 2.0Just about every employee is carrying a smartphone, tablet, or both.

BYOD has arrived.

Apps have exploded.

Enterprise 2.0, # 9

Table 1Early innings of mobility

Table 2Define BYODApple more than 50 billion app downloads


applications Enterprise 1.0Hosted on-premise or via ASP.

Enterprise 2.0An array of options exists: On-premiseDifferent types of clouds

Enterprise 2.0, # 10

Id like to talk a little about about the cloud and dispel a few myths.10

Myths of The CloudThere is one cloudYou have to go all in with the cloudThe cloud is a panacea

Enterprise 2.0, # 11

3 bullets1. Not true. Public cloud, private cloud, semi-private cloud2. Many organizations have migrated slowly, one application at a time.3. It doesnt fix bad data, dysfunctional business practices, etc.11

primary deployment methodEnterprise 1.0Almost always Waterfall-based.


Enterprise 2.0A hybrid. Both agile and Waterfall methods are used.

Enterprise app stores allow for near-instant deployment.

Often organic and bottom-up.

Enterprise 2.0, # 12

Table 1:Mention long implementation times (often a number of years). Very expensive projects. Consultants parked on site.Table 2: Much shorter implementation timesTalk about Yammer 1.2BTRANSITION AGAINST THIS INCREASINGLY CHAOTIC BACKDROP, WHAT SHOULD THE ROLE OF IT BE?12

The role of the it department:THREE PHILOSOPHIESHands OnBig BrotherObstructionistHands OffThe EnablerEnterprise 2.0, # 13

So, with the consumerization of IT and the explosion in technologies, what should be the role of IT? Here are three schools of thought1. Hands on a. IT is omniscient and omnipotentb. if left to their own devices, end users will cause the organizationand ITquite a few headaches2. Laissez faire IT cant and shouldnt contribute3. IT should give the business what it needsand occasionally step in as needed.


Tips and best practicesKnow your organizations limitations from the get-goGet a little bit pregnant with the cloudBridge the IT-Business Divide

Enterprise 2.0, # 14

1. If you dont have internal expertise developing apps, dont try. Use Merck systems analogy. Would IBM make its own aspirin?2. Its not a binary3. As I write in Why New Systems Fail, this kills many projects. Involve key players early on. 14

Tips and best practicesEnterprise 2.0, # 15

What is this?15

Tips and best practicesPrepare for sudden, unexpected growthEmbrace uncertaintyConsider the developer ecosystem, not just the platformEnterprise 2.0, # 16

1. Always better to have excess capacity and not need it than vice-versa2. Predicting the future is futile.3. Interoperability is essential; dont build new silos. Remember the infamous words of Peter Drucker16

Culture eats strategy for lunch. Peter Drucker

Enterprise 2.0, # 17

No matter what the technology or strategy, beware of bad culture or employees.17



Enterprise 2.0, # 18