Gartner Symposium - Master Innovators


Masters of Innovation – What CIO's can Learn from the World's Best Innovators
Pete Goss – 4 trans-atlantic and 2 round-the-world yacht races
  • new learnings about sleep patterns, new clothing, new designs, eating patterns
  • Always leads with clear values
4 key success factors in innovation (Master Innovators)
  1. Focus – focus on single driver; figure out the next step as you go
  2. Encourage ambiguity in the process but not in the purpose
  3. Time – spend more time on understanding the components of the problem; less time on designing the solution
  4. Starting point- start with "What do we want to achieve?"; start with outcome; don’t start with "Here's what we've got"
Master Innovators
  • exhibit behaviors that all can adopt
  • In hindsight, it may look like master innovators had unusual advantages; in actuality they leverage their advantages to drive to success
  • Many of the master innovator behaviors are learnable
Common CIO Advantages
  • constraints drive creativity; guard-rails
  • CIOs understand the overall value change
Additional messages
  1. Manage your distance from the mother-ship
  2. Great innovators are often flawed operator
  3. Understand and choose your core strengths and moral purpose
  4. Engage people based on their "why" more than their "what". Look for motivation and style
  5. Spend time to sink into the problem and understand it's facets.
  6. Keep the innovation process light and innovate the innovation process. Avoid over-processing.
  7. Get inspiration by looking at challenge from different directions.

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