Posts Tagged ‘it’

The four stages of IT architecture maturity

Thursday, December 15th, 2011

The MIT Sloan Center for Information Systems Research developed a capability maturity model that defines four stages of architecture maturity. Each stage involves organisational learning about how to apply IT and business process discipline as strategic capabilities.

As companies move through each stage they can realise benefits rangin from reduced IT operating costs to greater strategic agility.

Stage 1: Business silos

In this stage companies focus IT investments on delivering solutions for local business unit or functional needs and have do not utilise technology standards. The role of IT in this stage is to automate or facilitate specific business processes.

  • One off solutions
  • Bottom-up. IT led by local business units
  • Poor integration with other IT systems
  • Poor server utilisation
  • Little shared data

Stage 2: Standardised technology

This stage means moving some IT investments  from local applications to shared infrastructure. Technology standards are now established intended to increase reliability and decrease the number of technology platforms to manage.  Fewer platforms means lower cost (around 15% less) but also less choice, however companies are willing to accept this tradeoff.

  • Rationalisation, standardisation, and consolidation of the IT infrastructure
  • Achieving a reliable, cost-effective IT infrastructure shared services model
  • Focus on quick wins

Stage 3: Optimised core

The next move is from a local view of data and applications to an enterprise view. IT staff eliminate data redundancy by extracting transaction data from individual applications and making it available to all processes. In this stage companies are also standardising business processes and It applications.

  • Standardising core business processes
  • Local managers and units lose control over discretion over processes and IT
  • Consolidating redundant applications into a single global instance of ERP and CRM
  • Rationalisation of processes and applications with the objective of standardising processes and consolidating applications.
  • Build re-usable data and business process platforms
  • Top-down. Business processes and IT investments are made by central IT department

Stage 4: Business modularity

This stage allows strategic agility through customised or reusable modules.  The objective is to create reusable modules that business units can join together a standard interface such as web services.

  • Move from local flexibility to global flexibility

The five common pitfalls of IT implementation

Friday, February 4th, 2011

Andrew McAfee in his article titled “When too much IT knowledge is a dangerous thing” details five common pitfalls in IT implementation.

1. Inertia

Inertia comes from not enough progress over time even when everyone agrees that it is the right project to do. Inertia is usually caused if a project is too complicated or not given the right priority or support in the business.

2. Resistance

Resistance occurs when people’s motives are not aligned and there is disagreement about the project. It has the same manifestations as inertia (i.e. a lack of progress over time) but there will be more arguments and more political manoeuvring around the project.

3. Misspecification

Again this is caused by complexity, scale or too much change at once across too many business units or systems.

4. Misuse

This can be intentional misuse or unintentional. Users who are not technology savvy or have not had enough training may not use the new system correctly after it has been implemented.

5. Non-use

If the new system is not mandatory then it may suffer from people not using it. Recent research shows that as much as 70% of new IT systems are not used once they have been implemented.

What is the difference between a CIO and IT director?

Friday, January 28th, 2011

A CIO is a business leader with a responsibility for IT.

Where as…

An IT director is an IT leader who delivers to the business.

A subtle but very important difference.

In IT It Pays To Follow Not Lead

Wednesday, December 8th, 2010

Just a quick thought today. I listened to a talk where the case was made to follow not lead when it comes to technology. The speaker gave the following reasons:

  • Technology competitive advantage is usually temporary
  • Delayed IT investments decrease your risk of buying-flawed or soon to be obsolete applications
  • Following the leaders means you are more likely to invest in standards and best practice