This blog is a summary of thought from a CIO group that I have the privilege of moderating. They are the top CIOs in the Bay Area – so this is relevant. Not sure I agree with everything, but it is thought provoking.

Why Reboot IT? There are many reasons – here are a few:

• Outsourcing is broken. It doesn’t reduce cost much, but does reduce flexibility, innovation and accountability.
• Integration and customization = huge complexity, and you can’t introduce cool new stuff to meet the business needs because you are in the land of Lilliput.
• Waterfall methodologies are arcane.  Slow, costly, etc.
• It’s really hard to measure value.  Conversations around IT are often directed toward cost-saving, whereas they should include deep discussions around revenue generation as well – see my IT Benchmarking blog (published 9/13/13).

So – what’s a CIO to do?

The simple answer is that the IT department must be just like a technology company with products.  The head of development is like the VP Engineering, and should be supported by Product Managers who are responsible for the various offerings (Think as if you are Workday, Salesforce, etc., building commercial products – for internal use).

Technology Choices:

Build with the Cloud in mind, Web scale resilient apps, open source, embrace mobility (the form factor of a PDA screen requires a different development approach to apps delivered on PC and Mac/iPad), build everything scalable, and embrace choice.

How should you run IT?

• Agile, self-directed project teams of 6 – 12 including product, technical and iteration management and developers.
• Create product and service lines.
  • E.g., a product could be a CRM platform that would be charged to the business and handled like any other product.
  • Help desk would be a service – measured by cost and value (customer satisfaction).
  • Follow agile and/or scrum-based software development methodology for both custom and off- the-shelf development.
  • Follow product lifecycle – eliminate less used products.

 IT Department – Principals

• Flat hierarchy: 8 – 15 directs with teams being self-directed.
• Hire engineers capable of building products for commercial use.
• Managers should have a combination of skills: leadership, business, and Technical.

What should an IT organization look like?

1. Shared services group comprising IT:  infrastructure, security.
2. Office of the CIO: focus on metrics, portfolio management, communication, finance.
3. IT Operations: Problem, Change, Incident and Release management. First and second level support, NOC, Help Desk.
4. Product Management. Strong business relationships, understand customer demand and translate into features/initiatives.
5. IT Development. Services-based platform development of the products tied to capabilities, continuous delivery and deployment, modern tools, develop in-house capability (muscle memory).

What should you measure?

• In a word – everything, with the objective of tying business capability enabled, to the benefits realized.
• Build a big data store and capture logs, telemetry, capacity data, metrics, adoption data, incident management data, financials, etc.
• Build BI on top so decisions are increasingly based on data, e.g., – products should have telemetry and adoption logging so you can see which features are being used and how.
• Business pays for products and services delivered by IT on a usage/consumption based model. If product is not used, reduce support and then scrap.  This forces IT to be cost and value conscious so it can compete with SaaS products.