Monday, 10 March 2008

Frictionless IT

I spend most of my time in board rooms helping management teams to develop an understanding of their customer value and golden threads that will focus the energy of their enterprise towards its success. Through a series of workshops I work with leaders to reach a small number of objectives and key performance indicators that will form the basis of a sustainable method of managing performance.

When the time comes to try to find the data to populate these KPIs, it is at this moment for management teams that the challenges of getting information the last mile really start to hit.

So we have a meeting with IT. They tell us that some of the information exists but it has never been brought together in that way before so it might ‘be difficult’. They say that for some of the newer KPIs the data has never been gathered before. Then one of the department heads says that he has some of the information on a spreadsheet. Another department head says the same. Then as we finally reach the end of the list we find that there is a requirement for new information systems to capture the data that doesn’t exist at the moment.

By the time we get to the end of the sheet our timescales for the change programme are in tatters. We are facing a serious risk of all the momentum of the strategy communications programme, the energy and vibrancy that we started with on the first day spent with the management team plotting to take on the world with their great customer offer, all of that ebbing away.

I should like to introduce to you a new paradigm called ‘Frictionless IT’.

Frictionless IT describes a theoretical information management environment where all costs and restraints associated with aligning information systems to emerging business needs are non-existent.

Let me recap and describe precisely what I mean: I’m talking about a situation where people networks – collaborative groups of information workers who share a common goal or outcome - are able to train their information systems to always fit their changing information requirements.

In the next 5 years we will see Frictionless IT become a reality. But for Frictionless IT to happen you need what I call ‘Rubber-Walled IT’.

In our management meetings we used to use the term rubber-walled building to describe our requirement for office space which, as a fast growing business, always needed to be sufficient for the people that we employ but not excessive so that we were paying for space that we don’t need.

Unfortunately, most buildings don’t have rubber walls so the choice for tenants is to estimate the size of office space they think they will need over the next 3 to 5 years and hope that they guess right.

We’ve come to apply the same terminology to describe the needs of organizations for their information systems. Rubber walled IT is the ability of an information management system to always fit the needs of the organizations. It describes an information management platform that expands and contracts in a similar way to our rubber-walled building.

The technology to power rubber-walled IT exists today. Technology that enables your key workers to serve themselves with the information they need without having to make do with inappropriate tools like Excel and Word to use as information management tools?

What I’m talking about is what people are now calling situational applications. (You see the difficulty with new technologies is knowing how to describe them! Thankfully IBM did a great job in providing terminology to something that we’ve being doing for a few years now but never really managed to explain it. Thank you IBM!)

As organizations experience change, small groups of users find themselves requiring new information management needs. Products like ENCANVAS – our own software – exist to create these applications as new requirements emerge.

Situational applications typically have a short life span, and can be created within the group where they are used, sometimes by the users themselves. As the requirements of a small team using the application change, the situational application continues to evolve to accommodate changes. Any significant changes in requirements might lead to abandonment of the application altogether as with agile software tools it’s often easier to develop a new one

The fact is, most IT service providers and internal IT departments have a truck-load of small IT project requests to deal with that are either too difficult to justify so they sit on the shelf, or they don’t have time to action; so there is a huge pent up demand for situational applications.

The ultimate outcome of situational applications software like ENCANVAS is the creation of a rubber-walled information management platforms that deliver Frictionless IT.

1 comment:

  1. Il semble que vous soyez un expert dans ce domaine, vos remarques sont tres interessantes, merci.

    - Daniel

    ReplyDelete