Speaking with managers.

Early in my career as an IT professional, I realized some things...

WOW...  management speaks a language that I do not understand and, as much I thought I controlled the IT environment for my enterprise...  Management really controlled the IT environment.

So, I set out to figure out a way to address those things.

Management controls the money.  Money is generated by the business units. And, business units usually see IT as a necessary evil. Hence the language I did not understand.

I was (and still am) excited about the latest and greatest. I wanted to roll out new technologies because I thought it would help the business and also maybe because I thought it would be fun. But getting management to give me the budget and the cycles to accomplish that was excruciatingly painful. Why?? We were not speaking the same language “The business makes money, not IT” language.

As an example, I remember getting excited about a technology to train users about the new version of Office through self-learning online module. I decided to pitch it to my management. So, I get ready, make a slide deck, write a document with the description of the technology, how we can implement it the tracking module, etc....

Friday comes I manage to get 20 minutes on the agenda of the CIO's monthly meeting. I walk in, and start the pitch. The following is what my management heard:

"Hello, I wanted to present a project to you regarding deploying an online training technology that uses blah blah blah blah blah blah blah blah  ......"

The CIO stops me....  and asks

"How much will it cost?"

"$65,000.00 for a complete site license" I replied.

He paused, and ended the conversation with "get out!”

The realization that we're not speaking the same language, in fact addresses both issues I mentioned above. Let me explain… If I could figure out a way to speak the same language as the management, I could then drive my points and agendas, therefore exercising more influence over the IT management decisions and increase my “control”. Simple, right?

Well, not simple, but achievable. Think of it this way. Don’t lead in the conversation with the technology. Start by talking to management and the business units to identify the pain point, define the problem and the impact. And make sure to tie-in the money impact. Then through collaboration with management and the business units identify what the solution would look like. YOU”RE STILL NOT TALKING ABOUT TECHNOLOGY…. You’re setting the vision of what the solution would look like, what the end state would be and how it would benefit the business units by either saving money, or avoid losing money.

Once management and the BU have agreed that the end state is desirable and beneficial to the bottom line, and then you can bring up a product that will fill the need, meet the requirements. And in my experience, the budgeting and resource allocation discussions become much much simpler.

Let me go back to the previous example, this is the way it should have played out.

"Hello, I realized that a quarter of our 800 users are going out to training facilities to get training once a year.  The average cost of those classes is around $1,500. Not counting the productivity loss by having someone out of the office for a week. That really means that we are spending approximately $365 per user for training

What if we could lower that cost below $100 and keep the employees in the office where they can be reached.  Would you agree that this is a desirable?"

To that he would have said "YES!"

"Great! it so happens that I have been researching this and I found a solution that will meet our requirements to lower the training budget, and allow us to train not a quarter, but all our employees for approximately 80$"

He would have certainly replied

"Where do I sign?"

Not only it's a completely different conversation.... it's also a completely different mindset.

Don’t get me wrong, this is not an easy thing to achieve. It’s a mindset shift that needs to occur and it takes time to train your brain to think in those terms. There are a few articles and books that you should read to gain a greater understanding of how management thinks about IT. I suggest you get your hands on at least 2 of them that I have found to be a great way to clarify that kind of thinking.

The first is an article that I believe we should all, as IT Pros, be aware of and understand. It really put things into perspective. “IT doesn’t matter” by Nicholas G. Carr published in the Harvard Business Review in June 2003.

The second is “In Search of Business Value: Ensuring a Return on Your Technology Investment” by Robert L. McDowell, William L. Simon, and Jeff Raikes (Jan 2005).

So, hopefully this can help you speak the management language and empower you to be an influencer and a trusted business contributor in your own enterprise.  This is the tip of the iceberg...  I'm still learning and striving to find strategies to talk to different audiences. It never ends, people change and the way you connect with will change as well. All we can do is to adapt.

If you have thoughts or comment on this post, please let me know. We can only learn and grow by keeping an opened mind.

Cheers!