Posts Tagged ‘vendors’

Dealing With Vendors AFTER You’ve Signed The Deal

Wednesday, February 10th, 2010
Image Credit Getting Married To A Vendor Is Just The Beginning…

Getting Married To A Vendor Is Just The Beginning…

When you become CIO, vendors will enter your life and they just won’t leave. What this means is that they’ll be a constant pain in your neck, always wanting your time and attention. However, on the flip side, they will be a valuable resource that can provide you and your team with information and guidance that you couldn’t get anywhere else. Don’t do what too many new CIOs do and stop talking with vendors after the deal is signed…

What’s In The Relationship For You

CIOs always have the same problem: they are being asked to do more and more with the same amount of resources and funding. The challenge is to do an inventory of what tools and talents you have available to you and then find ways to use those to perform the tasks that the company needs you to do.

One way to do this is to find new ways of using more fully the hardware, software, and services that the firm has already bought. As smart as your IT team is, there is no way that they can know all of the ins and outs of every IT tool that the department is currently using.

Ericka Chickowski over at CIO Insight points out that this is where your vendors come in. Assuming that you didn’t burn your bridges with your vendors during the negotiation process, they can be a fantastic resource for you to draw on. Often new CIOs spend too much time looking only inside of the IT department and don’t take the time to look outside in order to uncover this set of hidden resources.

How To Manage Your IT Vendors For Maximum Benefit

As your company’s CIO, you will ultimately be responsible for controlling how your firm interacts with its IT vendors. You may not be part of every negotiation, but you certainly will end up living with the results. With that in mind, here are six things that you’ll have to do as the CIO in order to get the most out of your IT vendor relationships:

  1. One Cook To Run The Kitchen: those IT vendors are sly guys. They know that when they are dealing with inexperienced CIOs that they can always talk to other parts of the company if they don’t like how things are going with the IT team. You need to step up and put your foot down both inside and outside of the company – let everyone know that you are the one who will ultimately be making the decision and nobody else. This will force your vendors to deal with you.
  2. Banish Confusion: I can’t tell you how many times I’ve seen this issue sink what could have been a great vendor relationship: when the IT department doesn’t know what they really want. This is pretty simple right: if you don’t know what you want, then there is no way that you’re going to be able to tell the vendor what you want to buy. When this happens, the post deal relationship always seems to go poorly because nobody is happy – you’re not happy with what you got and the vendor isn’t happy because you’re not happy.
  3. It’s NOT All About Price: I think that it’s only the government that still sticks to the rule that they’ll always buy from the lowest price vendor. Yes, the up front price of whatever you are buying is important However, the cost of owning or using the product or tool over the lifetime that your company will use it is what really counts. The CIO who can step back and determine what the true cost of a product is can make good negotiating decisions. Once again, choosing wisely will help you to have a good long-term relationship with your vendor.
  4. Boxing Yourself In: One of the popular trends in IT these days is to reduce the number of suppliers that the firm is dealing with. This can have many benefits like being able to get greater discounts because you buy more from one supplier; however, there is also a dark side. You can easily get trapped into having to go along with what a vendor proposes if you’ve become too reliant on them. In order to have a healthy relationship with your vendor after the deal is struck, make sure that you keep your vendor options open.
  5. Forget The Little Guys: Which vendors should you spend your time dealing with – the big guys or the little guys. We generally tend to favor the big guys, they do a slicker job. However, it’s the smaller vendors who can more easily provide the customized services that you’ll need as the CIO and they are the ones who will be willing to work more closely with your team after the deal is done.
  6. The Contract Is Just The Start: CIOs who are just starting out often don’t realize that after all of the effort that went into defining and signing the contract, the real work is only starting after everything has been signed. It’s how you manage the day-to-day relationship with the vendor that you’ve selected that will really control how much value the company gets out of that contract.

What All Of This Means For You

All too often when new CIOs step into their position, they can get caught up in all of the internal issues that are always ongoing. However, if they do this, they may be missing one of the biggest “free” resources that they have available to them – their existing IT vendors.

The vendors know their products better than anyone else on the IT team and they have the experience with other IT departments in understanding how the tools can be used to solve real business problems. You’ll need to be careful how you choose to deal with them, but they are a great resource in these cash strapped times.

Taking the time to realize that selecting a vendor and entering into a contract with them is very much like a marriage is what a new CIO needs to do. Sure the wedding is fun, but you need to realize that you are in it for the long haul and just like every other part of your CIO job, you’re going to have to work at it in order to make it successful…

Do you think that your vendors would be willing to work more closely with you if you asked them to?

Click here to get automatic updates when The Accidental Successful CIO Blog is updated.

What We’ll Be Talking About Next Time

You and I both know that a well run IT department is what can make one company more successful than its competitors. That must mean that the IT department is important, and therefore the CIO must also be important, right? If that’s true, then why are some of the really big companies like News Corp, Harrah’s, ConocoPhillips, etc. getting rid of their CIO and then choosing to not replace him / her? What are they thinking?

CIO’s In The Wild: A Field Report

Wednesday, December 9th, 2009
Image CreditCIO Lindsey Jarrell Was Observed Doing What CIOs Do

CIO Lindsey Jarrell Was Observed Doing What CIOs Do

One of life’s great mysteries is “just exactly what do CIOs do” I’m pretty sure that we all think that we know what they do, but do we REALLY know? In order to prepare you for your future job as a CIO, I have undertaken a dangerous field study in order to observe the wild CIO in their natural habitat and I’m now prepared to make my report back to you. Listen and learn.

The Subject

Our subject in this case was Mr. Lindsey Jarrell who is currently the CIO of BayCare Health System. BayCare is a community-based health care system in the Tampa Bay, Florida, area. They connect patients to a complete range of services through their not-for-profit hospitals, outpatient and imaging facilities, and other regional services that reach beyond the Bay area.

These observations were made as part of my attending a healthcare conference that was being held in the Tampa area. Lindsey had been invited to give a talk about how BayCare has been using IT as a part of its operations.

Overall Knowledge

In order to judge how a CIO is doing his job, you have to take a careful look at just what he says. This is truly a case where words may speak even louder than actions.

Lindsey showed that a CIO needs to know about more than just IT issues. The key to being a successful CIO appears to have a good understanding of where the company is trying to go and how the IT department can help it get there:

  • IT Vision: The goal of BayCare’s IT department is to understand how physicians think.
  • Relationships: The CIO has to have a good relationship with the Chief Medical Information Officer (CMIO). This required Lindsey to get over his need to always be in control.
  • Extra Knowledge: Things that the BayCare CIO needs to know about that are not IT related include how doctors work and a lot about vendor contracts.
  • Who Owns Quality?: A company’s quality project is not an IT project, instead it is a company-wide transformation project.
  • Deep Knowledge: Lindsey was able to quote off the top of his head the incoming call volume that his help desk was currently fielding.

IT Projects

IT is all about projects: we start them, we run them, and hopefully the company is made better by them in the end. It was clear that Lindsey had spent a lot of time trying to find the best way to do IT projects and here’s what he had to say about that:

  • Where?: Lindsey was able to admit some of the functionality of the large-scale project did not have to be located in the IT department.
  • Keeping The Right Focus: He believes that his project teams needed to be out in the field in front of the doctors. One of the reasons for this is that inside of BayCare they have a completely different focus: they deal with an in-patient environment whereas doctors are focused on people who come to their offices (out-patient care).
  • Dates: He believes that for large IT projects you need to avoid announcing a “go live” date until AFTER you are either weeks or months into the project and have a good understanding of what it’s really going to take.
  • Project Management: The CIO came to understand that vendors really only care about getting to “live” (which is when they get paid). Realizing this, Lindsey hired his own project manager who is responsible for keeping track of the “big picture” for his projects.

What All Of This Means For You

This kind of observation of a real, live CIO is exactly the kind of information that you need to be considering as your career moves you closer and closer to the day that you’ll be named CIO. Hopefully my field notes have provided you with some insights into what a CIO really does.

Of special note should be the fact that Lindsey didn’t spend any time talking about servers, operating systems, development tools, networking, or security issues. These are all part-and-parcel of what an IT department deals with on a daily basis, but Lindsey realized that these are internal issues that nobody else cares about. CIO’s need to focus on what the rest of the business wants and keep the IT stuff inside the IT department.

Do you agree that IT vocabulary and IT specific issues should be kept inside of the IT department or should we share them with other departments?

Click here to get automatic updates when The Accidental Successful CIO Blog is updated.

What We’ll Be Talking About Next Time

When you become CIO, almost instantly everything that you know will quickly start to become out-of-date. Just to make things even worse, as the CIO one of your jobs is going to be to accurately predict the future. Just how are you going to go about doing this? It turns out that when you need insights into what the future of IT is going to look like, it helps to sit down and have a talk with the guys who are busy creating it