CoIT: An IT Nightmare?

the screamFor the average worker, it might seem like a dream come true. However, I suspect that some information technology folks consider it a nightmare. What’s the issue? The advent of the consumerization of IT; something Scott Finnie calls “CoIT.” Dion Hinchcliffe describes the elements of  CoIT in the following way:

1) businesses taking more local control for IT, 2) workers using their own preferred computing devices and apps, and … 3) manageable processes for rapid uptake of enterprise apps, mashups, and devices matched with IT support processes that scale to match.

While this may not seem an ideal scenario for the traditional IT department, it most likely is within the limits of what can be tolerated.  However, what happens when the business gets “carried away” and starts driving IT initiatives? Here’s Dion Hinchcliffe’s explanation:

The overall trend towards ad hoc adoption of personal and cloud technology at work seems to be inexorable. More and more IT is moving out from under the CIOs budget, just over 30% by some estimates. Perhaps most disruptive of all, however, is the sudden appearance of extremely stiff competition for IT services. While the move to self-service IT in general has been a steady trend for a decade — and which is starting to be called CoIT — it’s the outright diversion of business budgets directly to external IT providers, whether they are the newer SaaS vendors and app developers or the more traditional IT consulting firms and VARs. In short, the business likes the selection and service it’s getting elsewhere, and routing around IT in many cases. [emphasis added]

Suddenly, we have a situation in which the IT department no longer is in complete control and may well have trouble imposing a locked down computing environment.  Now, if you’re working in the financial or legal services industries, consider what happens when you couple the move to CoIT and external IT providers with growing incursions by hackers. According to a recent report in Bloomberg News, there’s been disturbing hacker activity directed towards law firms lately:

Over a few months beginning in September 2010, the hackers rifled one secure computer network after the next, eventually hitting seven different law firms as well as Canada’s Finance Ministry and theTreasury Board, according to Daniel Tobok, president of Toronto-based Digital Wyzdom. His cyber security company was hired by the law firms to assist in the probe.


`As financial institutions in New York City and the world become stronger, a hacker can hit a law firm and it’s a much, much easier quarry,’ said Mary Galligan, head of the cyber division in the New York City office of the U.S. Federal Bureau of Investigation.

Galligan’s unit convened a meeting with the top 200 law firms in New York City last November to deal with the rising number of law firm intrusions. Over snacks in a large meeting room, the FBI issued a warning to the lawyers: Hackers see attorneys as a back door to the valuable data of their corporate clients.

To be honest, I don’t envy law firm IT directors.  They are faced with the difficult task of imposing stringent security measures even as they watch their internal clients scurry out the door, exercising their right to choose their own IT tools and chasing self-service IT as a means to get out from under the control of their organization’s IT department.  While security concerns have often trumped other considerations in the past, it will be interesting to see if the newly emboldened  IT consumers will insist on using their preferred devices and self-service IT despite heightened security concerns.

It’s a nightmare scenario, coming to an IT department near you — soon.

[Photo Credit: Terry Freedman]


My Mistake

I made a mistake yesterday. Although I started with the best of intentions, my error was apparent within minutes. In fact, as soon as my first mouthful hit my digestive track, it was obvious that I had eaten food that was on the verge of spoiling. Unfortunately, by the time my brain processed the bad news, I was a few mouthfuls into my gastric disaster.  I’ve been paying for my error ever since.

Usually, nature provides an excellent early warning system to keep us away from spoiled food.  Bad smells and visual signs of spoilage are clear indicators that we should give up on that food and try something else.  In my case, the food looked fine and didn’t smell bad.  Consequently, I didn’t realize that I was on the road to pain and should turn around immediately.

We’re regularly told that fail fast and often are key to successful Enterprise 2.0 deployments.  Those of us who are trying to do it right look earnestly for signs that our current effort may be in danger of riding off the rails.  We check usage, we seek out anecdotal evidence, we read the tea leaves.  But what if we can’t tell if we need to quit?  What if the signs are ambiguous or, in the case of my bad meal, misleading?

Dion Hinchcliffe, Peter Kretzman and Michael Krigsman have been thinking about the role of failure in IT projects generally and Enterprise 2.0 deployments specifically.  I’ve provided links below to some of their writing, as an amuse-bouche.  However, I’d encourage you to dive into their blogs.  You’ll find lots of learning there.

In the meantime, I’ll leave you with the following observations from Peter Kretzman’s blog post, The IT project failure dilemma:  how to get early warnings:

One of the problems, as I’ve pointed out before, is that it can actually be surprisingly difficult to tell, even from the inside, how well a project is going.  Project management documents can be appearing reliably,  milestones met, etc.  Everything looks smooth. Yet, it may be that the project is at increasingly large risk of failure, because you can’t address problems you haven’t identified.  This is particularly so because the umbrella concept of “failure” includes those situations where the system simply won’t be adopted and used by the target group, due to various cultural or communication factors that have little or nothing to do with technology or with those interim project milestones.

Moreover, every project has dark moments, times when things aren’t going well. People get good at shrugging those off, sometimes too good.  Since people involved in a project generally want to succeed, they unintentionally start ignoring warning signs, writing those signs off as normal, insignificant, or misleading.


Further Reading:

[Photo Credit: stevendepolo]