Brainstorm with the EA: Innovation Zones June 12, 2014

Innovation Zone - working definition for the day

Innovation zones enable users (innovators) to easily step in and try new ideas with a minimum of friction and cost.

Foundation to the Discussion: Gartner Pace Layers 

Gartner, Inc. (http://gartner.com),  uses Pace Layers to describe best practices in managing an enterprise architecture (see Figure 1: Adapted Gartner Pace Layer Diagram).  In Pace Layers, the Systems of Record layer exposes enterprise data, services and capabilities to the layers above.  Gartner defines Systems of Record as systems “that support core transaction processing and manage the organization's critical master data.”   The architectural goal for systems of record is to focus on efficiency and operational reliability while exposing data and services  to the rest of the enterprise in standard ways.  Systems of Record have very slow pace of change.

The Systems of Differentiation layer includes systems where strategic investments are focused and that require continual adaptation.  These systems are critical to keeping the enterprise competitive and aligned with current market changes.  They are linked to the Systems of Record through standardized integration services that expose data, services and processes to the layers above.

Innovation Layer - Opportunity but not Promises

One key idea of the morning's session was that Innovation leads to great ideas and lessons-learned from failures not new things in production by some due date.   If you say, "I want to do this innovation thing and I need to have it up and in production by July 1" then you are not doing innovation, you are doing an implementation project for either a System of Record or a System of Differentiation.

Innovation is an opportunity to explore and try out ideas.   It is a way of failing fast and learning along the way.  If you have a successful innovation cycle, then you may leave with a great idea for a System of Record or Differentiation.  The next step is to write a business case or proposal to move your great idea into one of the other layers.

Innovation is an opportunity to try out your ideas and see what works and what doesn't work.  Innovation is not a promise that they thing you create will be deployed in the enterprise.   

Innovation Zones - Outcomes of the Discussion

Core Needs for Innovation and Innovation Zones

• There needs to be an active program to change the culture towards one of innovation where time spent innovating is seen as valuable and failure is an accepted outcome.
• Each Innovation Zone needs a Sponsor (someone who owns the zone and manages the selection, funding, operation processes) and a Champion (someone who sells the value of engaging with the zone).
• Innovation Zones need Innovation Brokers who help you get started and navigate the processes.
• Innovation Zones need to be able to easily connect with domain experts 
• There needs to be collaboration support for each zone (between innovators, the process, domain and subject matter experts, support people, etc).
• There needs to be clear user evaluation, review and acceptance criteria and processes.
• Expectations must be very clearly defined
• Release time and unstructured time are needed for innovation cycles
• A cost structure and payback notion for engaging and using innovation resources needs to be established
• We will need a recognition system for innovators and those who support them
• There will need to be seed resources and a clear proposal processes to help people engage with the zones.

Next Steps

• Build a framework that describes how Sponsors and Innovators will run and engage with the innovation zones.  Get buy-in on the framework.
• Do outreach with the University at large to get buy-in and align resources.
• Work with business and campus leaders to socialize the idea and framework
• Develop a system to capture outcomes and lessons-learned from all the various innovation efforts.   (Possibly use User-Voice or IdeaScale as a starting point)
• Categorize our existing projects into the Pace Layers.  Correct those that are in the wrong layer.
• Look for external case studies to see how to scale "this" (ed: effort ,the zones?)
• Form a group to work on developing Innovation Zones at UW.  Set SMART Goals etc.
• Clarify the existing decision making structures and governance processes in relationship to this effort.  Align these efforts especially around resources and approval processes.