{"id":6849,"date":"2013-09-10T09:28:03","date_gmt":"2013-09-10T14:28:03","guid":{"rendered":"http:\/\/www.mrc-productivity.com\/blog\/?p=6849"},"modified":"2022-11-22T10:57:01","modified_gmt":"2022-11-22T16:57:01","slug":"7-things-experienced-cios-and-it-leaders-wish-they-knew-earlier","status":"publish","type":"post","link":"https:\/\/www.mrc-productivity.com\/blog\/2013\/09\/7-things-experienced-cios-and-it-leaders-wish-they-knew-earlier\/","title":{"rendered":"7 things experienced CIOs and IT leaders wish they knew earlier"},"content":{"rendered":"

\"Education\"A couple of weeks back, I put together an article entitled, \u201c7 things experienced web developers wish they knew earlier<\/span><\/a>.\u201d It was filled with great advice from long-time developers, who shared some of the most important lessons they learned over the years.<\/p>\n

That got me thinking. What about other professions? In any job, you\u2019re bound to know more today than you knew starting out. There must be at least one important lesson that you wish you knew earlier. <\/p>\n

Today, I\u2019d like to approach this topic from a CIO and IT leader perspective. If you\u2019re an experienced CIO or IT leader, what do you know now that you wish you knew when you started your career? If you were to have a conversation with a younger version of yourself, what advice would you give? <\/p>\n

We asked those questions to experienced CIOs and IT leaders, and received some great input. I\u2019ve compiled their advice below, but–as always–feel free to contribute your thoughts in the comments. Here are 7 things experienced CIOs and IT leaders wish they knew earlier:
\n<\/a><\/p>\n

1. Understand your user\u2019s problems<\/h3>\n

\n\u201cWhen I first started in IT I was enamored with the technology and what new thing it could do,\u201d explains Michael Clapperton, CIO of George Little Management<\/span>. \u201cMany \u2018C Level’s\u2019 don’t care about what the latest and greatest is, they just want to solve a business problem. Stick with the problem, then if technology can fix it then convey that in SHORT CONCISE language that they can understand.\u201d\n<\/p><\/blockquote>\n

It\u2019s a lesson that applies to nearly anyone: Understand your users and the problems they want to solve. For instance, if company executives ask for mobile apps, dig a little deeper before running off and building a solution. What problems are they trying to solve? What are they hoping to accomplish with a mobile app? <\/p>\n

2. Assume the best<\/h3>\n

\n\u201cEarlier in my career, I was impatient and sometimes hot headed and I did not assume that everyone’s intentions were good,\u201d says Joe Fuller, CIO of Dominion Enterprises<\/span><\/a>. \u201cI have found later in my career that almost everyone is motivated to do the right things and when something goes wrong, it’s usually due to an unfortunate set of circumstances rather than a person’s incompetence or lack of dedication. Once I learned to assume the best in people, my relationships got better and our results got better. When people who are intelligent and dedicated don’t do well, the people in charge need to reflect on how well they are defining or not defining the mission.\u201d\n<\/p><\/blockquote>\n

This is fantastic advice for CIOs (as well as leaders in general), and is more important than most people realize. When leaders address mistakes with judgement or anger, they inadvertently create a fear of failure among their employees. Why is that a problem? As outlined in this article<\/span><\/a>, a fear of failure is the #1 creativity-killer.<\/p>\n

3. When conflict arises, talk about it (don\u2019t email)<\/h3>\n

On a related note, how should an IT leader or CIO deal with conflict when it inevitably arises? As Fuller explains, the answer is simple: Talk about it (but not over email). Most likely, it\u2019s simply a misunderstanding.<\/p>\n

\u201cAnother piece of advice I would give my earlier self is when there’s a conflict, pick up the phone or go visit the person,\u201d explains Fuller. \u201cI wasted too much time and positive energy crafting biting emails when there was almost always a misunderstanding or grounds for compromise that can only be discovered through a verbal exchange. Again, this mature approach comes from assuming the best in people. My rule today is that email is for positive or neutral communication only and I ask that everyone in my group follow that rule.\u201d\n<\/p><\/blockquote>\n

4. Under-promise and over-deliver<\/h3>\n

\n\u201cWhatever you do, be sure to under-promise and over-deliver,\u201d says Frank Petersmark, a former CIO and current CIO Advocate at X by 2<\/span><\/a>. \u201cThe last mistake you want to make as a new leader is promising more than you and your team can deliver \u2013 even if the pressure is on to do so while you\u2019re sitting at the board table, or in a room full of customers. It\u2019ll take some courage and intestinal fortitude to say \u2018no,\u2019 or at least \u2018not now,\u2019 but in the long run you\u2019ll be building trust and credibility \u2013 things not easily regained once lost.\u201d\n<\/p><\/blockquote>\n

I believe this is important advice, and should be followed by all IT leaders. However…be careful. While you can\u2019t over-promise, or agree to projects that your staff can\u2019t handle, some make the mistake of taking this too far. How so? Many IT departments fall into a \u201cculture of no,\u201d where they regularly deny user requests. As explained in this article<\/span><\/a>, this approach often contributes to a \u201cShadow IT\u201d problem. <\/p>\n

How can you avoid this trap? Always remember the first point: Understand your user\u2019s problems. Rather than simply saying \u201cno\u201d, try to understand what they\u2019re trying to solve. You may not be able to solve it in the way they\u2019re asking, but maybe you could suggest an alternate approach.<\/p>\n

5. Focus more on the people and the business <\/h3>\n
\"photo
photo credit: lumaxart<\/a> via photopin<\/a> cc<\/a><\/figcaption><\/figure>\n

\n\u201cWhile technology is always evolving and IT paradigms shift frequently in the information age, my 22 years as a CIO has taught me that there are some core critical skills for IT leaders which remain constant,\u201d says Brian Kelley, CIO of Portage County<\/span><\/a>. \u201cWe must be technology enablers, visionaries, and we definitely must be more focused on the PEOPLE than the technology within our organizations. Focusing on people involves aligning IT with the business, delivering superior customer service and IT support to end users, working with management to decrease costs, and increase efficiencies, and successfully interfacing people with technology. If you\u2019re just focused on technology, you are missing the mark as a CIO and IT leader in the 21st century and you may want to consider updating your resume!\u201d\n<\/p><\/blockquote>\n

\nGyutae Park, Head of IT at Money Crashers<\/span><\/a> shares that sentiment: \u201cI wish I knew that gravitating out of my comfort zone and working to bridge the gap between IT and business operations would have a much bigger effect on my success than simply solely focusing on how I ran the IT department in and of itself. It took me a long time to come to that realization.\u201d\n<\/p><\/blockquote>\n

I couldn\u2019t agree more. Aligning the IT department with the business is one of the most important responsibilities of CIOs and IT leaders. However, it\u2019s not easy. What gets in the way? Here\u2019s a list of 5 major IT\/business alignment stumbling blocks, and how to avoid each one<\/span><\/a>.<\/p>\n

6. Find a trusted sounding board<\/h3>\n

As a CIO or IT leader, you\u2019ll be hit with choices from all sides. You must choose the company\u2019s technology direction. You must choose which products to buy. You must choose which projects to tackle. It\u2019s not easy doing this alone. <\/p>\n

\n\u201cFind someone that you can trust and use him\/her as a sounding board,\u201d says Te Wu, an experienced IT Leader and CEO of PMOAdvisory, LLC<\/span><\/a>. \u201cPreferably, he\/she can also help you “do” versus just giving advice which has little consequences. Too often as a business executive, we are bombarded with choices. All vendors are trying to pitch their solutions and services (including me), most internal colleagues have their own agenda… How many of them put your interest before theirs and how many of them can actually help you do something versus just giving advice?\u201d\n<\/p><\/blockquote>\n

7. Treat your vendors well<\/h3>\n

Some people take the \u201ccustomer is always right\u201d mentality, and use that as an excuse to mistreat their vendors. The problem is, if the vendor wants their business bad enough, they\u2019ll put up with it. This is a mistake. Not only is it just wrong, you could be alienating a key resource.<\/p>\n

\n\u201cTreat your vendors well,\u201d says JJ DiGeronimo<\/span><\/a>, a Technology Executive, Author, Entrepreneur & STEM Advocate. \u201cThey can help you as you help them. They often are well networked and aware of key resources that can help you in a bind, job change or new project.\u201d\n<\/p><\/blockquote>\n

Your thoughts?<\/h3>\n

What do you think? If you\u2019re an IT Leader or CIO, would you add anything to that list? If so, I\u2019d love to hear it in the comments.<\/p>\n","protected":false},"excerpt":{"rendered":"

A couple of weeks back, I put together an article entitled, \u201c7 things experienced web developers wish they knew earlier.\u201d It was filled with great advice from long-time developers, who shared some of the most important lessons they learned over the years. That got me thinking. What about other professions? In any job, you\u2019re bound …<\/p>\n

7 things experienced CIOs and IT leaders wish they knew earlier<\/span> Read More »<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"default","ast-global-header-display":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","slim_seo":{"title":"7 things experienced CIOs and IT leaders wish they knew earlier - mrc's Cup of Joe Blog","description":"A couple of weeks back, I put together an article entitled, \u201c 7 things experienced web developers wish they knew earlier .\u201d It was filled with great advice from"},"footnotes":""},"categories":[8],"tags":[81],"class_list":["post-6849","post","type-post","status-publish","format-standard","hentry","category-education","tag-cio-challenges"],"_links":{"self":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/6849","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/comments?post=6849"}],"version-history":[{"count":20,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/6849\/revisions"}],"predecessor-version":[{"id":13867,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/6849\/revisions\/13867"}],"wp:attachment":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/media?parent=6849"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/categories?post=6849"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/tags?post=6849"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}