Free Newsletters

   All InfoWorld Newsletters
Advice Line | Bob Lewis » Making the case with central IT

August 12, 2007 | Comments: (0)

Making the case with central IT

Dear Bob ...

We are a small group of dedicated people working for a public safety unit under a large agency. We have accomplished the impossible and have worked in an environment of hostility towards the public safety department by other support units. There is central IT at six of the agencies and we fall under the HQ agency. Our relationship with HQ IT has always been difficult as our needs do not always fall under their standards for business operations. We are a 24/7 operation and require vertical applications and processes that relate to law enforcement.

Our staff is well versed in the specification, implementation, and support of these unique systems and we have been successful over the past seven years. At this time, we're undertaking a migration to an entirely new system that will replace most of our bread and butter applications, move from Nortel networking to Cisco, from Novell and GroupWise to Windows and Exchange, and introduce modern law enforcement systems. The training will be considerable and our group has been working on this project for three years.

We have requested that our staff be increased – finally – to best support the new systems and to accommodate new staff that has doubled since 2001. The HQ C-level staff has determined that the HQ IT staff should be directly responsible for all of our systems and the process has started with knowledge transfer and giving up our projects. This group has not been involved with the project, has limited knowledge of law enforcement systems but the CIO insists that with "good" SLAs, anything can be accomplished. With seven years of historically bad support, it's difficult to accept this change.

The HQ culture and work ethic is very different from what we've developed in our department. There is a strong case to grow our technical unit and to continue our future support. My questions are "how can I best develop a case and objective study to demonstrate that our department's needs are best met with dedicated staff?" and how can I influence the C-level managers to consider this case? Hiring a consultant to perform this on our behalf will be thwarted by central IT so that is a distant option. Any comments would be helpful.

- Case builder

Dear Casey ...

I don't think you're going to like my answer.

First, give up on the notion of winning the debate by making a strong business case. This issue isn't being decided by evidence and logic. From what you describe, at least, the chain of argument goes like this: "Here's what I want the answer to be" -> "Here's a plausible sounding statement that rationalizes the decision for me, and is good enough to shut off the argument from anyone else" -> "Stop arguing - I've made my decision and it's final."

You have two avenues to explore that I can see. One is to present an alternative that sounds a lot like what the HQ CIO has planned but gets you what you really need. It might go something like this:

* After everyone agrees to an SLA, it's still true that the more users you have to support, the more people you'll need to support them. The two questions are, how many additional support staff are we talking about and where will they sit?"

* We already have the local infrastructure set up and know the territory. Why don't you plan on seating however many you're planning to hire in our area?

It's a long shot but it might work.

The other alternative I can think of is to match clout for clout. Surely, the thought of having HQ's IT staff providing local support is making the top managers in your area nervous. If you have a good relationship with them, explain your concerns, let them know you don't have any influence over the decision, and suggest that it's up to them to make the case for local support if that's what they prefer.

There is, of course, a third alternative, and it isn't all that bad: Let things play out. If you're right, one day there will be a blow-up. When it happens, your hands will be clean and the HQ CIO's fingerprints will be all over the crime scene.

Then you can make your case to whoever is in a position to recommend a change of course.

- Bob

Powered by ScribeFire.

Posted by Bob Lewis on August 12, 2007 09:45 PM


RATE THIS ARTICLE:





 

  •  
  • COMMENTS




I would add one caveat to the third possible course of action. Yes, your hands will be clean, but will the people who need to, know that? Let's face it, scapegoating is not an uncommon tactic. Protect yourself by documenting the situation. Make sure that there is a paper / email trail that documents your concerns - and that you communicated them to appropriate people.

Posted by: Kayza Kleinman at August 13, 2007 09:57 AM

I have to agree with Kayza, and more so. Not only document your concerns, and document that you appropriately shared them (Another good reason for at least giving option 2 a try even if there is limited chance of success) do this documentation in a manner where it can't be erased or "modified" or "corrected" by the HQ IT. I have seen the waste material hit the rotating object, and immediately the IT department which dispatched the waste material immediately send people to "fix" the machines of the people who had issued warnings. So paper documentation is a great idea.

Years ago I kept my self out of jail on such a situation in that as soon as the mess was found my machine was "detected to have a virus" and reformated. Also all of my project files grabbed. Interesting how it took four file boxes to removed them, and one hanging folder to return them. ;-) They were claiming that I had engaged in fraud and were trying to place all of the blame on me. Interesting how the investigation stopped as soon as I pointed out that the documents I had not "properly and legally filed in the project files" existed as copies in a number of other files.

Especially where public safety is involved I would make sure you have plenty of protection. In this day and age of thumb drives I might put all of the files on one and then lose it down the back of a file drawer.

Posted by: Ray Stevens at August 15, 2007 11:39 AM

Working for an incumbent telco that supports PSAPs (Public Safety Access Points, which are the various local 911 call centers), I understand all too well what CaseBuilder is going through.

There is a downside on your "3rd alternative" Bob, and that is that the failure to to at least try to derail the CIO's takeover bid will result in many nights of complete lack of sleep upon the realization that this reorganization will cost the life of a LEO (law enforcement officer), and quite probably many tax payers along the way.

A good working process that is outdated and requires updating in order to be current *should* be done, but in a slow and careful process that takes failure into account by providing redundancy for processing, and the ability to build everything back "the way it was" if the failure is catastrophic.

Best for the CIO to take over CaseBuilders group and charge them with the responsibility of completing the conversion themselves, since they have a viable game-plan that they have been working on implementing for the last 3 years.

Best to keep the experts involved, especially in areas concerning Public Safety...

Posted by: Elrendhel at August 15, 2007 02:20 PM

Three books. Three ways to change the world, your life, or at least Bob Lewis' bank account.

Leading IT: The Toughest Job in the World distills the world of IT leadership into eight learnable skills and gives you concrete, practical techniques for each one of them.

Bare Bones Project Management: What you can't not do makes project management manageable, even for first-time project managers with no formal training in the discipline.

ManagementSpeak: What managers say/What they mean … well, it won't help your career, and won't make you a better manager. Mostly, it will make you chuckle, guffaw, and maybe even chortle. Make friends - it's the perfect gift for anyone who has ever suffered through one of those meetings.

Order your copies today!





Technology White Papers

 

InfoWorld Technology Marketplace

» Technology White Papers Library

Technology White Papers by Topic

Technology White Papers E-mail Alert

Find out when the latest white paper is available:
 
 
» BUY A LINK NOW

Sponsored Technology Links