Running IT like a Start-Up - Gartner Symposium

Running IT like a start-up - Leigh McMullen

New Rules – The Game Changed in the Front Office
  • drive differentiation
  • Don’t follow Lead
  • Hunt in Packs
  • Don’t fight Shadow IT – cultivate for innovation
  • Its okay to be IT again
New Practices
  • mine the front office for ideas
  • Focus on capabilities
What we need is a start-up inside our IT organization. Fundamentally different – in all ways.

Case studies – Janet is CIO of boutique retailer.
Phil – CIO of established govt agency with ww offices. Local agility with global scale.

Exploring opportunities is vexing
  • Need to understand biz problems at the "do-er" level
  • Start with understanding; how does biz make money
  • Create power map to determine relationships and politics
  • Identify the moments of truth; get your people next to the right people
Don’t ask "How can I help" - indicated you are not aware of business challenges.
Technology's role in the front office is to enable better outcomes for Moments of Truth – business moments.

Use the business model framework to get an overall view of where Moments of Truth can be found. Understand where we should explore. Gartner Business Value Model – understand how we can identify KPIs.

Take the mega-processes and then overlay the Gartner Business Value Model to identify opportunities.
Eg – what if pricing models change? Understand those moments of truth – do they benefit from speed, accuracy, etc? Describe tolerances of error. Define an innovation perimeter to describe where we want to explore.

Find the right people - 
Innovation requires experimentation which requires tolerance for failure. Startup team needs to act like detectives. Detectives follow leads that don't always pan out. Cases are based on a testable hypothesis. 

Your users are not professional sw designers. We take their opinion as truth. 


Startup mentality requires a top-down and bottom-up change in mentality.

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