Keystones and Rivets

IT (still) exists for one reason

The Pebble groaned.  “Another big 2.0 conference is coming up...I’ll be reading about it for weeks.” 

My non-tecchie colleague, who freely admits that the average pebble possesses more IT knowledge than he does, spends a few hours each day trawling various media for news and information of interest to our company.

Something he hates is anything ‘2.0’.  “Who comes up with this junk...is the pen the pencil 2.0?”, is a rant I’ve heard on more than one occasion.

The other day he was scanning a few blogs and I could tell he was going he let rip once again.  It was like watching and listening to a volcano in the hours leading up to an eruption. 

“All the usual rubbish”...‘uber’...‘paradigm shift’...‘3.0’...“THREE point oh?!! - you have to be kidding me!”  At this point various items of stationery went into orbit.

After I’d stopped laughing and he’d calmed down he said, “Why don’t we set up a 2.0 Skeptic blog?”

“One blog is enough to be getting on with, thank you very much” I replied.  But I could see his point. 

The name The Pebble chose for his proposed blog was inspired by the blog of the IT Skeptic.

Governance and Government

We weren’t sure whose chin hit the floor first.

“He did say 25 million, didn’t he?” asked The Pebble.

“Yip”, I replied.

We had just begun watching a news broadcast about the latest data security breach by a British government department, Her Majesty’s Revenue and Customs (HMRC).

25 million personal records, including the banking information for every family in the UK with a child under the age of 16, had been written with only password protection onto two CDs which were subsequently “lost in transit”.

The UK Prime Minister, Gordon Brown, said that the security breach was down to “Failure in implementing the proper procedures.”

He went on to explain that:

1. “Only authorised staff should have access to protectively marked information”
2. “Information must not be removed without appropriate authorisation”
3. “Encryption should be used whenever information is being sent”

Trying to cross No Man's Land

The Pebble and I work well together.

But he is an Arts graduate, so I have to humour him from time to time.

This entails having to listen every so often to one of his “stories” about history or politics. 

Today, for some reason, he decided to explain why the Red Army initially collapsed during the German invasion of Russia during 1941. 

“Barbarossa”, “Lebensraum”, “OKW”,  “Timoshenko”, “Smolensk”, “Stavka”…

The Pebble often talks about interesting things but occasionally he uses too much terminology.  As is sometimes the case, after a few minutes I felt my eyes glazing over.  My mind started to drift into that strange state where you feel conscious and unconscious at the same time.  The lights were on, but there was definitely nobody home.   

His talk about matters military must have had some impact though.  Through the haze I began asking myself - when did IT last go into battle with a genuine understanding of what the business was trying to do?

When did Business and IT last plan together strategically, agree tactics, and march together with clear objectives?

How about ten years ago...?

Rolling Rocks and Landing the Catch

A couple of years ago we were invited to visit a few companies in Silicon Valley to chat about what we were up to.  It was a great trip and one of the perks was being taken to some fantastic seafood restaurants.

During one meal there was a long discussion about the problems companies have with project prioritisation in complex environments. 

One humorous comment that stuck with me was, "I don't mind rolling the rock up the hill and getting near the top only to see it roll all the way back down again.  It's rolling the rock up the hill, getting half way and having to just hold it steady that I can't stand - an occasional change of scenery would be good."

Working in IT, we’re all rolling the rock up the hill.  It tends to be the nature of the industry to load IT staff with lots of work, all of which needs to be completed in a hurry. 

It could be that we’re involved in a couple of projects, busy with procurement, testing parts of a system, fielding user queries, fault fixing, or trying to catch up on the often neglected paperwork to keep either the change board or auditors off our backs.

When it comes to scheduling our work, we could all come up with differing priorities for new tasks depending on our current workload, or how we perceive a task’s relevance.

So if a problem or failure occurs, how can we ensure that it is given the correct priority from an enterprise perspective?  If we leave it to the individual to decide the priority we cannot guarantee that we get a consistent approach to IT delivery across the enterprise. So what can be done?