Sunday 20 April 2008

IT and Your Health

You hear so much bad news about big money and scarce resources being wasted on mega health projects that it's nice to get some good news about IT and your health. It's particularly nice if that good news affects your own life for the good.

To begin with, a good search engine now knows more and can tell you more than your doctor can, with whatever concerns you, either preventive or remedial. You are your own best doctor. So between you, your doctor and the Internet (and it might be a good idea to include God as well), you should be able to optimise your health situation.

And of course, not forgetting a healthy diet and exercise - on which you can also get the best advice through a good search engine. For example, it was on the internet that this writer discovered the amazing health benefits of sprouted seeds. They contain much needed enzymes to keep the stomach and digestion healthy, and are an organic, ever-fresh source of nutrients which are about 40 times more nutritious than ordinary, fresh vegetables.

But getting more specific on technology, if you have ever had to wait interminably for X-rays to be processed, or in some cases having them get lost, then the good news is that old-fashioned photos and use of snail-mail are going out.

Instead, some hospitals are now scanning the image straight into a central radiology database and making it instantly available across and between hospitals and consultants. Not only that, but because the images are available on high-resolution screens, it does make it easier to scrutinise the image and make a diagnosis.

Also, speech recognition is being added for the radiologist, so as to reduce writing, typing and transcription errors, and the time involved.

The x-ray images are input, along with any drawings made by the doctor, consultant or specialist, and get integrated into your electronic patient record.

In addition, with wireless networks, it means that bedside input & output to/from the patient record becomes feasible.

It means no more lost records, more reliable data, and much faster response to patient needs.

At least this is what it means in theory. The other factors, apart from the technology, are the people, process, organisation and management (PPOM) factors. These things, more than the technology itself, are the priority for getting things right in Health Care.

P.S.
Systems Thinking; treating everything as a system, within a system, within a system, is the key to getting PPOM right, and a future article will focus on Systems Thinking.

Wednesday 16 April 2008

Innovation through Customers

About a year ago Dell Computers launched a community site aimed at interactive feedback with customers, for the purpose of improving products and customer service, and responding effectively to customer needs by using this Web 2.0 technology.

The site is called IdeaStorm and, judging by the comments and interactions so far, and especially the rapid response to customers enabled by the site, it seems to be a great success.

The site is powered by SalesForce.com, a SaaS purveyor of Customer Relationship Management Systems (CRM), and is based on their own Ideas Exchange.

Standing back and taking the Big Picture view, what's happening here is improved innovation and product leadership through collaboration with customers through a fairly new technology tool.

It represents innovative synergy between (a) the business organisation, (b) its customers and (c) information & communications technology (ICT). The prediction is that it will benefit the Business in achieving competitive advantage, provided Dell continue to innovate, and tie in its Business Processes with the site.

How did this innovation come about at Dell? Was it a top-down thing, or was it bottom-up? The guess is that it was a bottom-up idea and, if so, it gives an object lesson in using IT and people in achieving competitive advantage.

The people at the bottom, or more correctly at the Coal face, were empowered to innovate, and the people at the top provided the Governance that explicitly or implicitly laid down the principles and set up the organisation structures to make it all happen.

This use of ICT to bring customers into the innovation circle is predicted to grow, according an article in the December, 2007 McKinsey Quarterly.

And it's a good example of what this very blog site is all about.

Tuesday 8 April 2008

T5: Lessons Learned












What actually went wrong in the catastrophic and highly publicised opening of the new Terminal 5 at Heathrow? Was it another systems project failure, but this time a high-profile one?

The impact was first upon people; the passengers whose lives were at the minimum disrupted and at worst seriously blighted.

The impact on British Airways (BA) and British Aiports Authority (BAA), was likewise disastrous, not just in terms of the millions of pounds lost, but in lost reputations as well.

At top-level the cause was reported to be the Baggage Handling System; thousands of pieces of baggage piled up with nowhere to go.

However, reading in and between the lines of Transport Minister Jim Fitzpatrick's 31 March statement in Parliament, the failure was due to a number of things:

  • A glitch in the software.
  • Lack of coordination between BAA and BA.
  • Lack of training.
  • Poor planning.
  • Lack of people integration on the ground.
Of these, web chat sites have blamed lack of training as the biggest reason for the failure.

It's significant that, out of the five reasons, only one was technology.
The others were down to people, organisation and management.

You can learn a lot from blog sites & comments, one such being Joolie Atkins, who specialises in IT training issues, and whose site with its comments gives us further reasons & insights for the T5 Failure:
  • The Big Bang Approach; it should have been phased.
  • Inadequate User Acceptance Testing (UAT).
  • Lack of Systems Thinking; seeing the Big Picture.
  • Lack of senior management involvement.
  • No rehearsals; no process testing.
Again, only one of these had anything to do with Technology, which was the UAT - if this can be considered Technology.

So the T5 disaster appears to have had little to do with IT!

One commentator pointed to the re-opening of St Pancras Station (a beautiful example of Victorian architecture in London), and the Eurostar Service to the Continent, which was opened by H.M. The Queen, and went without a hitch. So it can be done, even when you have no option but to use the Big Bang Approach.

So what, as Transport Minister Jim Fitzpatrick asked in his statement before Parliament, are the Lessons To Be Learned?

There is only the space to summarise - what to do next time:
  1. Senior management governance & involvement.
  2. Join up Business and IT.
  3. See the Big Picture.
  4. Assure & test the end-to-end business process.
  5. Provide quality & early (not tacked-on at the last-minute) training, and on what people need to do the job well.

Sunday 6 April 2008

Winning the Email Battle


The first thing to do in winning the email battle is to decide to do something about it; to decide to win.

That done, you'll invest a bit of time in winning the battle.

In fact you had better do something about it now, because:
The amount of information is increasing exponentially year by year!
What will happen if you don't do something about it?

Your productivity & performance will continually worsen,
and your increasing stress level will make you ill & angry!


Here's what needs to be done:

  1. Use the Software
    Make sure you have the best system for email overload.
    Turn off the Alert.
    Use the Spam Filter.
  2. Get Training
    Get quality training on how to effectively use your email software, and get more general training for yourself and colleagues (the people from whom you're likely to receive emails), on how to use email effectively.
  3. Make Sure it's Relevant
    Work out your:
    - Explicit Goals & Objective (EGOs).
    - Critical Success Factors (CSFs).
    - Critical Current Issues (CCIs).
    - Knowledge & Competency Areas (KCAs)
    - Underlying Aims & Interests (UAIs)
    Although subject to change, this is your Relevance Base.
    It's only these things in which you're interested.
    Delete everything else.
  4. Be a Good Sender/Giver
    - Is it relevant for and needed by the target recipient,
    and those copied?
    - Avoid sending a Victorian Novel!
    - Have a succinct, pithy, stand-alone, action-oriented heading.
    - Not more than five paragraphs, and keep them short.
    - Use good English. Make it easy to read & understand
    - Review for logical sequence and errors before sending.
    - Never send anything angry, impolite, confrontational or insensitive.
    - Action orientation: what do you want the recipient to do?
    - Minimise "For Your Interest".
    - Put yourself in the target recipient's shoes.
  5. Use Information Net-Value
    Use Info Net-Value and evaluate each email; what's the cost v. benefit of receiving it?
    What's the cost v. benefit for the recipient of those you send?
    What's the cost v. benefit of social chat and news groups?
  6. Manage the In-Box
    Manage your In-Box through the following:
    - Look at emails not more than four times per day.
    - Review for urgent and/or easy-to-deal-with according to the subject heading or sender.
    - If urgent and/or easy to handle, do now.
    - If not urgent or easy to do look at later, and handle all of these in chunks - not one at a time.
    - By end of day should not have more than ten open items, and these not because of delay but because of needing further information before replying or actioning.
    - All the rest should be deleted, filed or archived.
  7. Assure Security and Regulatory Needs
    Delete anything from unknown sources unless you're sure it's
    (a) relevant, and (b) not malware, spam or phishing.
    Don't open an attachment unless you're sure it's
    (a) legitimate, and (b) needed.
    Don't delete anything that may be needed later on for regulatory reasons.
Lastly, don't be over-reliant on e-mail. It's a double-edged sword. People like the personal touch, and it may be a lot more effective if not enjoyable. Use the phone, or go and see, or write an old-fashioned note.

Tuesday 25 March 2008

Not Just the CIO's Responsibility

It's not just the CIO that's responsible for the effective use of IT.

A recent survey by Gartner indicated that Chief Information Officers (CIOs) now need to have non-IT business unit management experience if they wish to pursue new CIO opportunities.

In many organisations, particularly governmental, the CIO still does not have direct report to the CEO, and does not therefore sit at the boardroom table.

Part of the reason for this is the lack of non-IT management experience, so that the CIO is still seen as a "techie", rather than a business manager.

It's a a chicken-and-egg situation: the best way of getting general management experience is for the CIO to sit at the boardroom table, and yet the CIO is often prevented from gaining general management experience by being barred from the boardroom table.

It's a fundamental block in the effective use of IT, and aligning IT with Business needs.

An even more fundamental block is the implicit assumption that the effective use of IT is the job of the CIO and the CIO alone.

Even that most excellent of magazines CIO, both the USA and UK versions, appears to have the underlying assumption that everything connected with IT is the job of the CIO.

If this were the case, then the effective use of people would be the job of the HR Director alone.

And the effective use of Money & Finance would be the job of the Chief Financial Officer (CFO) alone.

Responsibilities like these, IT, HR, Money & Finance, and other key resources - are the job of every manager.

In fact an implication in IT Governance (see the Weill & Ross book), is that although the CIO is obviously at the forefront, the ultimate responsibility for the effective use of IT rests with the whole senior management team.

Education and experience therefore cuts both ways. If business is to get full value with IT then business managers need education and experience in IT.

That is, while it is true that general management experience will help the CIO, it is equally true that appropriate IT education & experience of senior management - and of every non-IT manager - will enable more effective use of IT, and alignment of IT with Business needs.

The HR function has a vital role to play in all of this, because it doesn't just come down to education and training in Business-with-IT. There is also the issue of changed mental models and business change programmes, so as to get Business and IT in a Partnership Paradigm, rather than the Us v. Them Paradigm that frequently prevails.

P.S.
We're not talking education in point-and-click. By appropriate education we mean MBA-type IT education - of a practical and integrated nature.

And by IT experience we mean nitty-gritty experience like business process mapping, preparation of development testing and use cases, and side-by-side collaboration with IT people.

Wednesday 19 March 2008

Easter Greetings in Irish

If you go to the Aran Islands at this time of year, and if you greet an Aran Islander with:
Ta Criost eirithel!

- they will respond with:
Go deimhin, ta se eirithel!

It's the Irish for
Christ is risen!
and He is risen indeed!

The Aran Islands were made famous by John Millington Synge who, after studying Irish and Hebrew at Trinity College, Dublin, spent several summers there perfecting his knowledge of Irish and absorbing the culture.

This led to his masterpiece The Playboy of the Western World, which caused riots when it was first performed at the Abbey Theatre in Dublin, in 1907. It's a quirky comedy about Christy Mahon, a young man whose claim to fame is that he has killed his father by bashing him over the head with a garden spade.

It's the way he tells his story (and who are better story-tellers than the Irish?), that makes the women fall in love with him.

Unfortunately for Christy, his supposedly dead father comes back from the dead, albeit a bit worse for wear, and Christy loses the respect and love of his admirers.

So in a way, Playboy of the Western World has a parallel with Easter, when we celebrate the resurrection of Jesus Christ.

In this case however, it's an event that is either the biggest myth and con-trick ever perpetrated, or is the miraculous, non-fiction, actual happening which historians at the time reported it to be.

One of these Historians was Luke, a physician, who "carefully investigated everything from the beginning" in order to write his history for a new Christian by the name of Theophilus, who must have been a very important person for Luke to go to all this trouble; a bit like having your own Alpha Course.

Incidentally, the Aran Isands are/were the home of Father Ted, another quirky if not hilarious Irish comedy about Fr. Ted (himself), his zany young side-kick Fr. Dougal, the drunken priest Fr. Jack, and Mrs Doyle, who would NOT take no for an answer ("ah go on!"), in offering you that cup of tea!

May the joy and gladness of Easter be with us all at this time of year.


Caisc shona duit! Happy Easter!

Wednesday 12 March 2008

PRINCE2 Cost v. Benefit

Prince2 is a Project Mgt. method used internationally.

But what's the cost v. benefit? It's mandated in UK govt. projects, but this has not prevented some recent, classsic failures.

Which of these statements do you lean toward?

  • Prince2 assures the discipline, governance, quality & risk control, alignment with business goals, documentation and guaranteed deliverables needed in an IT project, without which there would be anarchy and failure.

  • Prince2 is a fat, heavy-handed method that goes back to the 1970s, before the world became the fast-changing global village, Internet-enabled place that it is today, and it is a source of competitive disadvantage in preventing IT from meeting customer business needs in the time needed, and getting product & service to market.
The primary advantage of Prince2 is the Business Case, and the business analysis and IT governance that goes with it. It seeks to ensure that the project is rigorously aligned with business aims, and is likely to add value to the business.

The rest of Prince2 is all about the management & control of each stage of the project so as bring about expected deliverables and benefits, as promised in the Business Case.

The issue is that you don't necessarily need Prince2 - and perhaps the bureaucracy that goes with it - to have a good Business Case.

So Prince2 is a double-edged sword; required rigour on the one hand, and bestial bureaucracy on the other.

For example, there is a great deal of documentation, formal approvals, inspections and co-ordination needed in a Prince2 project. Is all of this really needed? Will the documentation actually serve any real purpose?

Arguably, this all adds time to the project. And yet, IT customers may be needing the deliverables - or at least the core component of them - sooner than later; much sooner, owing to business environment and/or competitive pressures.

A second issue is the old chestnut of paralysis by analysis which, arguably, a Prince2 culture fosters. When you have to allow for your business and systems analysis being subjected to severe scrutiny, with no errors allowed, you tend to make sure that it's iron-clad.

Whereas, supposing IT were working in a closer, more iterative, less formal, ego-less mode with its customers, what would happen then?

A third issue is that Prince2 virtually assumes no change, whereas this is one thing you can depend on: change. Consequently, one of the major problems in systems development and its project management is Requirements Creep. After all, it's often impossible for IT customers to know up front what's really needed.

A fourth issue is that Prince2 arguably dis-empowers IT people, and controls rather than trusts. What would happen if IT people became much more in the business picture, really and truly part of it, and were empowered with the (1) business knowledge, (2) tools, (3) business guidelines, and (4) trust as to what's needed and when, albeit with frequent interaction between customers and IT?

In other words, would it be possible to have our cake and eat it?

Might we adhere to Prince2 as a model,
and use its principles as guidelines,
while avoiding the bureaucracy?

Monday 3 March 2008

Making Mobile Working Work

Mobile working
is accelerating
.

It's a priority item on the agendas of many CIOs, and is an example of advances in ICT being used for competitive advantage - or just catching up.

Achieving competitive advantage with mobile working, and the information & communication technologies behind it, depends on:

  • Being an early adopter on the New Technology Adoption Curve.
  • Doing it right.
And doing it right depends on taking a systemic approach. In other words, it's not just a technology project, and not just a business project. It's a technology & business & people project. It has a big sociological content.

So, first of all, why is mobile working accelerating?
  1. It's being greatly enabled by the advances in telecommunication and human-computer interface (HCI) technologies.
  2. It enables a more cost-effective organisation.
  3. It facilitates quicker & easier networking.
  4. Given the need for business organisations to be increasingly agile, flexible and responsive, it enables better use of the three paramount resources of the Information Age: People, Time and Information.
  5. It means that people on the go in this Global Village can stay in touch and keep the pot boiling.
  6. It makes it possible for people to have a better quality of life in being able to work at home and telecommute - thus avoiding the need to drive/train/bus commute into the business centre every day. We can live a rural life if we want to (see photo).
  7. Green Thinking and the cost of fuel. We're trying to reduce global warming and minimise carbon emissions and pollution from electrical & electronic devices, and car/plane/train use. Besides, the prices are going up and up at the pumps!
So it's evident that mobile working represents a sea-change; a tectonic movement; a paradigm shift in the use of ICT & HCI, in the way people work and live, in business & organisation models that we've been used to, in cost structures, in the ways that customer service & value might be delivered, and even in society itself.

What can be done, therefore, in approaching mobile working in a way that is not techno-centric, but rather takes a broader, systemic approach? How can we do it right?

The first thing to do would be to:
  • Flag mobile working as the bigger issue that it is
  • Establish a senior-level Mobile Work Group
    of business and IT executives
- to address the opportunities and challenges in mobile working.

The group should (a) seek the big picture, (b) brainstorm, (c) evaluate, and (d) govern & guide. The goal would be to put the organisation on the right footing, in harnessing mobile working and its enabling technologies, so that it works for the business, its people, and its customers.

Here are some ideas for the Group:
  • Look at the impact of mobile working on work practices, and evaluate where we are now.
  • Consider how present work practices, routines and processes might be guided for added value, better payback and people satisfaction through mobile working technology.
  • Take a big-picture look at all the technologies impacting mobile working, including video-conferencing, WiMax, 3G and Bluetooth, and the ones coming down the road, such as flexible screens, the Windows Mobile 7 operating system and high speed uplink packet access, with the objective of standardising the mobile infrastructure and avoid infrastructure anarchy.
  • Evaluate the technologies for innovative ways in which mobile working might be used to deliver better service and value to customers.
  • Ditto for cost savings and time savings.
  • Identify those areas where selective outsourcing might be considered, so as to delegate infrastructure management to specialists in these areas.
  • Make explicit the business goals & objectives that need to drive mobile working.
  • Get IT people out into the field and/or operating at the coal-face, to get first-hand experience of mobile working by internal customers, collaborating to make it more effective.
  • Look at how mobile working might be used in optimising quality of life for people as, for example, with flexible working, shared jobs and home-working.
  • Assess the risk aspects with mobile working such as malware & viruses, identity theft, data loss, regulatory compliance and social networking.
  • Consider the Green Issues and impact.
No doubt the Mobile Work Group could come up with other if not better ideas as to how the mobile working should be approached in a systemic manner. The above gives us a start.

Tuesday 26 February 2008

Firefox & Mitchell Baker

The soon-to-be-released V3.0
of the Firefox open-source browser will make mobile working easier.

What's more interesting is the useful lessons to be learned from The Firefox Way - of doing business.

It is, after all, a consumer product facing tough competition. In fact the company is a giant-killer - with Microsoft & Internet Explorer being the giant.

Starting with one employee in 2002, the company now has 150 - not counting the thousands of volunteers around the world.

The first lesson to be learned from Firefox is that achieving competitive advantage with IT can just as easily come from the bottom as from the top.

When Mozilla 1.0 came out it was a suite of Internet applications that included a browser. It was a flop, and it could have been the end. But two developers, Blake Ross and David Hyatt, had been working on a lean & secure version of the browser module. They were (a) motivated and (b) empowered. As a result, this bottom-up initiative became Firefox business strategy.

This leads to the second lesson; self-organising teams. You don't need layer upon layer of managers, giving a tall pyramid, which does not make for effective organisation in today's rapid-change environment. What you need is motivated and empowered people who, being guided and coached by their managers, with simple rules to keep them in sync with business aims, can do the business themselves.

Firefox has pushed the boundaries on this one, enabling and facilitating its thousands of volunteer programmers around the world to self-organise themselves into such teams.

The third lesson to be learned is that you don't need to be a Computer Science graduate - to succeed with IT. CEO Mitchell Baker (see photo) studied Asian Studies @ undergraduate, then went to Law School and practised as as a corporate lawer. She worked for Netscape then AOL, got fired in a round of layoffs, got involved in the Open Source Applications Foundation, and then started up the Mozilla Foundation.

She is also a skilled trapeze artist, flying several times a week, speaks Mandarin Chinese, and is married with one son. Now that's a well-rounded life!

The fourth lesson: CEO Mitchell has a simple yet powerful Vision for Firefox: safe & simple browsing. As it says in the book of Proverbs, Where there is no vision, we perish (29: 18). With Vision, Mitchell has the direction, ability and passion to lead and motivate others in the Firefox story. So Leadership & Vision is another lesson we can learn.

The fifth lesson is collaborative management style. It's quite evident that Mitchell is a Theory Y Manager. See also the Mozilla School of Management Simple Secrets of Successful Management.

In fact, a lesson in itself is that Mitchell uses a blog site, which gives output on what she's thinking and gets input on what others think.

It's not a bad idea; using blogs, wikis and other Web 2.0 technologies to optimise communication, collaboration, meeting of minds and team-working.

The sixth lesson is that concerning motivation @ work. What motivates people? How does Mozilla motivate its thousands of volunteers around the globe? How might this apply to the more conventional working environment?

The simple answer is treat people like volunteers, who work because they want to, who are motivated not so much by money or position but by (a) the work itself, and the satisfaction that comes from doing a good job, (b) mutual recognition & respect from working colleagues, and (c) the camaraderie that comes from team-working with others in a shared vision.

Senior Management Guidance & Suport - is the seventh and final lesson. Mozilla has a Steering Committee which undertakes the top-management role of proactively carrying out the following:

  • Overall guidance.
  • Empowering people
  • Setting & monitoring progress for business goals
  • Tracking overall progress
  • Allocation & provision of resources
  • Overall co-ordination of activities
  • Spotting opportunities
  • Addressing strategic problem areas
  • Providing Leadership
  • Seeing the big picture
As Mitchell Baker says, senior management's job is to guide and support, then get out of the way and enable people to do theirs.


P.S.
CJB had occasion to visit the main hospital in Oxford recently, the John Radcliffe, and had a look at the application icons on the nurse's computer screens. The browser they were using was Mozilla Firefox.

Thursday 21 February 2008

Information Governance: I

The big fuss in parliament over the lost DNA disc is about the risk to the UK public, as a result of vital information on criminal activities having been ignored.

It's the latest episode in a series of lost information catastrophes in government departments.

And there is a blame-game going on that may or may not get to the root of the problem: the need for effective Information Governance.

In this latest case, last year the Dutch Police sent a disc with 2,000 DNA profiles from crime scenes to the Crown Prosecution Service, to be checked against the UK's database. But the checks did not start until this month - and so far 15 matches have already been found. The Police are now urgently looking for the matching individuals suspected of serious and violent crimes.

What was the systemic reason for the failure? Is it true that the information was left in the desk of an official away on sick leave?

There is a parallel here with lost information in Financial Services, resulting in heavy fines and/or significant financial risk - and also financial losses for the UK public.

Even though every case involves Information Systems & Technology (IST), this is not about IST as such. It's about the overall system, the organisation, and the management of information; in fact it's about Information Governance.

Unfortunately, Information Governance in current parlance has a restricted meaning, in referring to the security & compliance issues. But this is only a sub-set (albeit a critical one), of a deeper need - the management of Information Itself in business organisations (as opposed to the library setting). This is what real Information Governance in business organisations is about!

It's similar to COBIT (Control Objectives for Information Technology), being wrongly described as IT Governance. It's not. Or at least, it's a restricted, security & compliance view of IT Governance (for a book on real IT Governance see Peter Weill & Jeanne Ross).

This is a fundamental problem with IST - too many misnomers!
It's a bit like Humpty Dumpty, who said "When I use a word . . . it means just what I choose it to mean". But getting back to Information Governance:

  • Is Information Itself a strategic resource?
  • Does it need to be managed as a strategic resource?
  • Would this make a difference to the type of losses mentioned?
  • What are the principles of Genuine Information Governance?
And so , in this first article on the subject, let's try to put down some Principles of Genuine Information Governance:
  1. Information is a strategic resource - and it needs to be managed as such.
  2. There needs to be a specific responsibility for managing Information Itself.
  3. The responsibility for managing Information Itself must include that of managing Information Overload - InfoLoad - and its consequence of vital information lost & buried.
  4. Information relevance is the paramount need for managers and organisations - and the primary goal in all information.
  5. Information quality is dependent on the data from which it is formed - data quality.
  6. Data quality - and security - is largely dependent, first, on the business process (has it been mapped collaboratively end-to-end to make it rapid & reliable?), and second, on the IST that supports the process.
  7. Effective business process has seamless linkages both internally and externally to the organisation.
  8. Optimising Information Net-Value (the value of information less its real & total cost), is the basic aim, in conjunction with information relevance, of Information Governance.
  9. An Information Architecture, defining & describing (a) the main elements or entities of information, (b) their linkages across the organisation, (c) where the information elements reside and where used, and (d) the external interfaces, is mapped out and managed.
  10. Security-sensitive and critical information needs to be tagged as such, in some form.
However, Genuine Information Governance is not about technology, as such. It's about governance, i.e. the overall management of Information Itself. So it might, for example, concern itself with collaboratively developing principles & policies concerning email practices, but not the detailed technology of alternatives such as wikis and blogs.

And it might be concerned with Information Lifecycle Management, Business Process Management and Customer Relationship Management in terms of principles & policies, but not the detailed technology or practice. Again it's governance, rather than management.

Any comments?



Sunday 17 February 2008

Senior Management Education

The photo is about the Lloyds TSB card scheme at the 2012 Olympics. It was the lead story in the 14 Feb. Computing.

A letter from CJB was also printed about management education, in response to an article which had the key phrase:

There are no longer IT decisions; only business decisions.

In other words, IT is normal management. For example, HR and Finance are specialised functions, but every manager is still responsible for people and money - and IT. It can't be a separate hand-off. IT is normal business.

Getting back to the letter, it was interesting that the letter printed was quite different from the letter submitted - not that there would be much disagreement with the letter as printed - here it is:

~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

Tom Young's article Business must see IT as everyday task, is highly relevant to a core problem in Business with Information Systems & Technology (IST).

The initial issue is that people too often lack relevant information, have limited opportunity for knowledge sharing, are kept in pigeon-holes, are penalised for initiative, and are greatly under-used.

Secondly, IST is itself, also, greatly under-used.

Consequently, there is limited synergy between people & IST.

The place to start in addressing the core problem could well be to follow the philosophy presented in the editorial:

- Start with appropriate education for senior management people.

~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

What was omitted from the letter as submitted was that, if there are no longer IT decisions only business decisions, then every single manager needs to be Business-IT savvy.

This does not mean the point-and-click skills that Bill Gates talks about. What it means is - - that kind of wisdom which comes from a big-picture, integrated view of Business & IT.

And how would this savvy & wisdom come about? Well for starters, and what could make all the difference, would be the right kind of Business-IT education for senior management people!

However, and notwithstanding the omission, the editor of Computing came up with a better letter!

Any comments?
What do you think?



Monday 4 February 2008

Information Overload Help: II

It was recently announced that Intel has produced a microprocessor, that can contain two billion transistors; so Moore's Law continues.

Moore's Law says the number of transistors on a microchip doubles every two years.

So far, so good, for the computer scientists at Intel. But what are the implications for Information Overload and the users of business information?

Last month's first article on Information Overload, or InfoLoad, identified the main causes of the Information Tsunami breaking over the shores of business organisations, and into the Read & Do Baskets of already-overloaded business information users.

Now, with Intel's announcement and the implication that it will soon be more feasible to increase the deluge of information coming at us, seems a good time to address the second part of the InfoLoad issue - namely the Effects & Business Consequences of InfoLoad:

  1. InfoLoad can have a hyper-stress effect on the InfoUser.
    The sense of the stress is captured in Richard Wurman's book Information Anxiety. Literally & physically, InfoLoad can make you ill, impair your performance, (for example in decision-making and in reaction time), and shorten your life.

  2. If there is one thing that we cannot waste today, it is time. In fact it can be a source of competitive advantage - or disadvantage. But that's what InfoLoad leads to; wasted time, because there is so much filtering, sorting and reading to do, and much of the InfoLoad is marginally useful information.

  3. And Bacon's Law: bad information drives out good. That is, the really relevant and critical information gets buried and lost. You're in a meeting and have to acknowledge you weren't aware of a key piece of information - it got lost in the pile. Or that vital information needed for complying with regulatory requirements - it somehow got lost in the shuffle.

  4. It makes us lose focus and stray from what's important.
    We get mesmerised and, in trying to stay abreast and catch up with the pile of information, we lose sight of key goals & objectives.

  5. Lastly, InfoLoad wastes money. January's article on InfoLoad made the point that one of the causes is the assumption that information is a free good. But it isn't!

    One of the latest trends in computer operations is virtualisation of servers and memory which, through clever software sitting above the operating system, frees up a lot of the space currently used. But this, and any other technology, is only putting off the day of reckoning, because storage volume requirements are at least doubling every three years.

    There is so much information clogging up hardware resources that organisations are running out of space and money to store all this information, having to buy more and more hardware.

    And yet, hardware is only the tip of the ice berg. The real waste is in the waste of human resouces in producing and maintaining the less-than-useful information that makes up much of the InfoLoad Mountain.

Next month we'll start looking at key remedies
for addressing InfoLoad.


In the meantime, do you have any war stories concerning Information Overload, or do you have ideas that might possibly help?



Tuesday 22 January 2008

Share Prices & IT

As share prices and the stock market head south, and as companies hunker down to survive the down cycle, there may be few that realise the impact that corporate IT can have on share price and survival.

In the short term, financial markets are largely driven by emotion. But in the medium to long term they are driven by fundamentals such as profitability & growth, which is where IT comes in.

Take Standard Life, for example, the Edinburgh based life & pensions company.

Last year, in 2007, Operating profit shot up by 71% and new business grew by 31%, after the company started to focus seriously (a couple of years ago), on achieving the promise & potential in IT.

Another example is British Airways (BA) whose return to financial health is largely due to its corporate IT, and particularly its customer-reaching e-ticketing and e-check-in sysem

But Standard Life and BA are not isolated cases. There are other examples of business organisations ramping up performance through IT. MIT's Centre for Information Systems Research, for example, has a number of studies showing the connection between IT performance and business performance.

The main point is this:
If the promise & potential of IT were achieved in business organisations it would (ceteris paribus), have a significant impact on satisfacion, value and purpose, with this impact being shown @ the bottom line in profitability, growth, and shareholder returns.

In the case of Standard life, the company turnaround came largely through the following.

  1. A change of mental models, as for example in the 'traditional' separation between Business on the one hand, and IT on the other. Everyone started speaking the same language.
  2. Close collaboration & synergy between IT specialists and Business client/users. In fact IT people got out into the business areas and worked alongside their client/users, with the third party in the equation being the customer - what might be referred to as Synergy Circles.
  3. Business process re-design (BPR), which has a lot to do with total quality management (TQM), to squeeze out the parts that add cost and take time, and optimise the parts that add customer value and cut time.
  4. Lean/agile development, which is the IT version of BPR, re-designing the development & support processes so as to be lean & mean and rapidly responsive.
  5. A flexible/integrated IT architecture, which enabled rapid response to business needs.
But the secret ingredient as it were, in all of this, in any organisation that wishes to fulfil the promise and potential of IT, is senior management if not Board active involvement & support.

After all, if IT really does have the promise and potential to significantly impact profitability and growth, then the need for senior management if not Board active involvement & support, is evident.

Do you have experience with IT making a difference
to business performanc?

What, in your view, were the key things that made it happen?



Sunday 13 January 2008

Change & Rapid Response

Martin Fowler is one of those rare people who combine deep knowledge of information technology with the ability to write lucid articles about Business with IT.

His article The New Methodology, posted on his web site, which is about Agile Computing, is for anyone seeking an easy read on new ways of responding rapidly to changing business needs.

In today's rapidly changing and Black Swan environment, a Critical Success Factor (CSF), is how to get rapid IT response in the real world of changing Business-Client needs - which is often driven by changes in the external, competitive, sociological and regulatory environment.

That is, in addition to pro-active changes for innovation through IT.

The interesting thing is that rapid response is not (apart from a flexible/integrated enterprise architecture), about technology.

Rapid response is about people synergy. In other words, the key to meeting the Business-IT CSF of rapid response is effective collaboration between business managers and IT people.

Yet it's unlikely you'll get this without Theory Y management (which is much simpler than it sounds), as described in one of the most important books on management, and is a must-read book:
The Human Side of Enterprise, by the late Douglas McGregor.

What's needed is a Theory Y Culture, both in IT and in the organisation as a whole, if there is to be rapid IT response to business change.

This is demonstrated by another lucid writer on Businesss with IT, Alistair Cockburn, who says (in a highly interesting article), that project success depends on people characteristics, that is, more than methodology or project discipline.

For example, minimalist documentation works best (especially if you have self-documenting code), because heavy documentation is a burden and a chore, and slows down the project, even causing it to fail. Besides, it won't be used, because people don't trust it and prefer to "look around".

Finally the Client/User, notwithstanding business responsibilities, may need to embrace a role as Business Information Systems (BIS) Designer, not just Specifier. This, instead of getting more point-and-click skills, is more likely to add value for the Client/User, and the business.

P.S.
In coal-face systems, it may be well to bring the external customer into the equation as well, to form a Synergy Circle.

What are your experience & thoughts on this?
What are the issues in getting rapid,
if not pro-active & innovative response, to business change?


Monday 7 January 2008

Competitive Advantage & IT

Paul Otelellini, head of Intel, says that more powerful mobile devices with Wimax connection will deliver a more personal internet within five years.

And Bill Gates, head of Microsoft, says that the human-computer interface (HCI), or the way people interact with computers will change dramatically, and within five years the keyboard and mouse will become obsolete.

Not only that, but so will the desk-top become redundant, as we all migrate to more mobile working & computing.

Perhaps no surprises with any of this, but what has it to do with
Competitive Advantage & IT?

One of the big debates in Business with Information Systems & Technology is this: Should (a) innovative applications of IT be used to achieve competitive advantage, or (b) business strategy be supported by innovative applications of IT?

For example, suppose you are a CIO, a Project Manager, or other IT Manager, seeking to exceed client/user expectations. Should you be looking for innovative ways (e.g. XML and the Asus Eee PC) of using IT for reduced cost, added value or customer benefit?

Or suppose you are a business manager or executive, pursuing a new or improved product, service or business process. Should you be turning to your IT advisors for advice on how best to achieve this with innovative ways of using IT?

In other words, from which direction should the initiative come; from Business or from IT? This is what the debate is about:
Achieving competitive advantage with IT - whose job is it?

Perhaps there is no debate. Perhaps innovation & initiative with and through IT should come pro-actively & collaboratively from both directions. Therefore, what are the organisation structures, culture and development processes like; do they encourage this collaboration?

But there's a third party ; present or prospective external customers; how are they brought into into the picture? Case studies in the use of IT for competitive advantage tell us that collaboration with and through this third party, the external customer, can be vital.

Getting back to (a) better work-mobility through & with IT, and (b) better Human Computer Interface/Interaction, should the seemingly inevitable changes be seen and used pro-actively for competitive advantage, and if so, by whom and how?

We have new/improved information & communications technology (ICT) coming down the road; how might we put it to good use? We're developing this new/improved product, service or business process; how might we use ICT innovatively for competitive advantage?

The changes forecasted by Paul Otellini and Bill Gates may not be surprising, and therefore not leading and especially not bleeding edge technology. But they do provide opportunities for achieving competitive advantage with IT/ICT, and achieving this depends on the good use of people, organisation and management.

The bottom line is this:
Competitive advantage with IT is not necessarily achieved through the use of leading or bleeding edge technology.
It is often achieved
- through innovative ideas for existing technology,
and this is down to synergy in people, organisation and management.

Nonetheless, knowing what new technology is coming down the road
- and knowing how you are going to use it before it becomes available, can give serious competitive advantage.


What's your experience of using IT innovatively?
What's your opinion?



Friday 4 January 2008

Information OverLoad Help: I

This year, 2008, may be
The Year of Information Overload,
rather than new technology.

Because, in this competitive, global-village, information-based, IT-enabled economy in which we work, organisations are Information Factories, giving, grinding and getting more and more information.

It seems to be increasing at a geometric rate, and we're not just talking about information available via the Web.

What are the real costs of Information Overload or InfoLoad where, for example, we have hundreds of incoming emails arriving daily, with every probability that this will increase in 2008?

It would be one thing if all this information were relevant, reliable and rapid, but a large part of it is not, and lacking in real value.

It's not what this Part 1 on Information Overload Help is about, but what might be needed is an Information Resource & Knowledge Manager, who would, as a key responsibility, act to cut InfoLoad. Such an overall responsibility may happen when InfoLoad reaches a tipping point, when the high cost of irrelevant and poor quality information is uncovered.

Until then, there are things that might be done, starting with a recognition of the Five General Causes of InfoLoad:

1. The View of Information as a Free Good
When you give or get an email, telephone call, written report or letter, or have a meeting, it's costing you and the other person(s) time and therefore money. It's not free, so is it relevant & required? What's the purpose? Can it be made shorter, or more structured, so as to be easier to process? In fact, is it needed?

For example, do you ever give or get something along the lines of "you might find this interesting", or turgid, complex, Victorian Novel type of letters that need to be read three times? What can you do about this?

2. Ritualistic & Indiscriminate Information-Giving
Does this happen in your organisation; the organisational version of Junk Mail? Can you influence it? What about your external and internal customers; does the information you give and they get provide net value both ways? Is there a need to audit the Information Net-Value
of routine internal & external information flows?

3. Lack of Explicit Goals & Objectives (EGOs)
There should be a purpose, goal, or objective in getting and giving information, and the more explicit it is, the better. It's likely that, of those hundreds of emails you send/receive, many have questionable value. Is there a need for a short course and/or dialogue on Giving & Getting Email?

However, it's also business information systems and business processes where the real, ingrained InfoLoad is lurking, and where explicit goals & objectives (EGOs) in information may need to be assessed. For every information flow that you receive and send, you may need to ask: what purpose is served; what's the added value?

4. Everything but the Kitchen Sink
Often, we get and give much more information than is really needed. This is because the Information System has the functionality to give it to us, and so we're given everything but the kitchen sink. That is, everything we need, and then some. The user/client might have a need for this information, so let's give it them. The Technology Tail is wagging the Business Dog.

The evidence is that giving 'em the kitchen sink, and thus bringing about InfoLoad, has a negative impact on decision making quality.
So again, we might consider Information Net-Value.

5. Ineffective Organisation
This asks whether:

  1. The individual knowledge worker, manager and executive
    is effectively organised.
  2. The business organisation itself is effective and fit for purpose in its structure and culture.
  3. Business Information systems are aligned & integrated.
  4. Business processes avoid duplication and make-work.
  5. Data is integrated, administered and managed effectively.
As examples of evident remedies, InfoLoad is much less of a problem if you're personaly organised. And the organisation is effective and fit for purpose if bureaucracy is minimised.

In Part 2 we'll look at the Effects of InfoLoad,
and in Parts 3 & 4 we shall take a better look at Remedies.

In the meantime:
What's your experience with InfoLoad?
What are the big causes of it for you?