Marc Benioff - Salesforce.com - Gartner Symposium

Customer success is number one
SFDC was cloud before cloud was cool
Views himself as a change agent; IT is hard
Looking at how to transform the industry; explode the paradigms
Radical changes are coming to IT
Mobility, iPad, Facebook, ... All major transformations
What is the future of OP?
It's easier for SFDC to enable capabilities in the cloud because of architecture

Companies' datacenters are terribly inefficient
HW and SW upgrades, installs, etc
With SFDC you are always on the latest technology and latest version
- how many customers are on the latest version of their OP systems? Very few

Oracle is buying companies like crazy and consolidating all these acquisitions
SFDC is innovating

Siebel was a failure; people migrated off to SFDC after millions of dollars of failed implementations
Private clouds are not the answer
Sharing is the answer
Mobile and social is accelerating

Ray Ozzie left Microsoft
He created LotusNotes
Microsoft Sharepoint doesn't work
Facebook is winning and is new - how do we learn from that?

Chatter is another example of the way SFDC is building a stronger relationship with customers
300k custom apps built on force.com
Dell is going to 100k users on Chatter
Why? Because doc management is dated

Google? Great job on gmail, docs, tremendous innovation
Mark Zuckerberg? = "the next Bill Gates"

"beware of the false cloud" - if its just another server, it's not a cloud
Oracle is selling HW as cloud but it's not
Do you have to upgrade it? Then its not cloud
Private cloud is just SW and HW

Security is the number one thing to consider

SFDC is looking to partner with CIOs
IT can add value in other ways other than managing HW
Deliver services faster and easier
Help move beyond legacy systems

Comments

Post a Comment

Popular posts from this blog

Enterprise Architecture Inside Salesforce

Image
  Enterprise  Architecture Inside Salesforce Enterprise Architecture — How We Do It Internally The two words, “Enterprise Architecture”, elicit various reactions — everything from “ we tried that and it doesn’t work ” to “ we need that! ” to “ we have an effective EA practice ”. Unfortunately it is possible (even easy) to do Enterprise Architecture  incorrectly , with an approach that is lethargic, technology-first and theoretical — the classic ivory tower. (In Salesforce, the internal IT group reporting into our CIO is called “Business Technology” so you’ll see me use BT to refer to Salesforce IT) I lead the Salesforce Enterprise Architecture team within Business Technology and I’m often asked the following questions: how does Salesforce do Enterprise Architecture? why do you need Enterprise Architecture? how do you shift the conversation to business capabilities? Illuminate — The “How” of Salesforce Enterprise Architecture Let me start with the “HOW” first. Within Sales...
Read more

Illuminate - Business Model Exploration

Image
  Illuminate — Business Model Exploration One of our world-class Salesforce Enterprise Architects, Jonathan Laudicina ( https://www.linkedin.com/in/jonathan-laudicina/  ) has done amazing work on Business Model Exploration. I want to highlight some of his work and I think you’ll find it useful. As a reminder, Illuminate is the Enterprise Architecture Methodology that we use inside Salesforce as well as with our customers. The overall Illuminate methodology is depicted below. You will notice that Business Model Exploration is the first step in Illuminate. Business Model Exploration is the methodology we use with customers to articulate: External Forces pushing on the business Internal Forces pushing on the business Customer specific Business Model Canvas At the heart of Business Model Exploration is the Business Model Canvas. It is the place in which you capture key factors about a company’s specific value proposition, partners, customer segments, cost structure and revenue str...
Read more

5 Key Components of a Successful Enterprise Architecture Function

  5 Key Components of a Successful Enterprise Architecture Function 5 Key Components of a Successful Enterprise Architecture Function Creating and managing a successful Enterprise Architecture function requires a variety of different hard and soft skills. In addition, each company is different and the Enterprise Architecture function needs to calibrate and align itself to the specific company. However, there are five common features of a successful Enterprise Architecture function that are applicable to all companies. 1. Governance Enterprise Architecture (EA) requires governance, however not in the form of complex documents, forms or processes.  Definitely avoid EA being seen as the policy-enforcement team — people will avoid EA if the perception is that EA is a blocker.  The best governance starts with a simple, recurring dialogue across multiple functions facilitated by EA. I am always amazed at how valuable it is just to get cross-functional teams to  talk . Pick...
Read more