- 1. Include Your Employees in your 5-year Plan
- 2. Utilize Consultants Sparingly
- 3. Choose Your Advisors Carefully
- 4. Learn From Outages Together
- 5. Guide the Ship
Congratulations on your new role as CIO! As the CIO, your job is to remove roadblocks, provide a vision, and enable your business partners without spending more than is required to do so. Here are 5 tips that I have gathered as an employee watching multiple CIO transitions.
1. Include Your Employees in your 5-year Plan
Every new CIO wants to create a vision, but one of the biggest mistakes that a new CIO can make is relying too much on external consultants or upper management to lay out this vision. Unfortunately, this type of top-down leadership strategy tends to lead to low adoption rates. While it is a great way to create a bold vision and great slide-deck, the resulting plan typically lacks adoption and leads to bland execution.
If you want buy-in to your vision, make sure you listen and absorb as you enter the new landscape and involve your employees when creating an execution plan. Finding a way to blend your 5-year plan with an execution roadmap that will get to that point is what will separate a great CIO from an average CIO. Give your staff a vision and operating rules and let them help you get to the end-state. Your job is to eliminate any roadblocks in the way of your vision and to make sure that everything that is being done today is in line with where you are trying to get to.
2. Utilize Consultants Sparingly
Consultants are often used as scapegoats when a project or initiative isn’t on track, but consultants can be a great resource for an organization when utilized properly. The key with utilizing consultants is to make sure you are getting the experience that consultants can bring with them. Ask yourself and your team if the value being provided is worth the money being paid and also consider the technical debt that is being added by using a consultant. Always ensure that a full-time employee is paired with the consultant to learn from them and to take over the project before a consultant leaves. Any work done by consultants must include meaningful documentation and meaningful tests. Consultants can also be utilized to spin up an environment, but make sure an internal resource is involved as well because once the environment is up, you don’t want to rely on a consultant to handle ongoing support.
3. Choose Your Advisors Carefully
Along with eliminating roadblocks, another role as a new CIO is to identify who you listen to around the organization. Identifying people you should take advice from can be daunting task but it is the only way to effectively guide the organization. One way to help identify who you should take advice from in an organization is to engage in brainstorming sessions. The idea behind these sessions is to help develop a vision that everybody buys into and to get everybody talking in the same conversations. Not everybody is comfortable with the same medium so it is a good idea to follow up on these brainstorming sessions with output items as well based on the conversations. This is a great way to figure out who is going to execute at a high level. Another important thing to keep in mind with this group of advisors is that they have to be willing to tell you their true opinion even if it’s not popular. You should be encouraging this to the entire staff, but really emphasize it with your advisor team.
Once these projects start to gain traction, go out of your way to recognize members of your team and solicit advice from them. Ask them specifically what is working well, what isn’t working well, and see if they have any ideas to help improve things going forward. Focus on the areas that they talk about and ask follow-up questions. Identify the strengths and weaknesses of yourself and your advisors.
4. Learn From Outages Together
Issues can appear in many forms: missed SLAs, unresponsive servers, hanging jobs. Unplanned issues and outages should be viewed at as a huge opportunity to get your team a better understanding of how the overall technical landscape works at your company. Any time a member of your team is spending time fixing systems or chasing down issues, they aren’t working on the problems that are guiding the organization towards the 5-year vision. Understanding why system issues occur, how the issue was detected, how the solution was identified, and what can be done to reduce issues in the future either in severity or detection time are the key areas that should be focused on in this type of post-mortem. Be mindful that this doesn’t turn into a blame game. This is a collaborative team-building exercise and everybody should be growing from it. This is a great exercise that can help you understand how different pieces of the puzzle fit together and get everybody on the same page.
5. Guide the Ship
As the CIO, you are responsible for crafting a draft of your organization’s roadmap and guiding your team. There will be times when you have to make changes to the 5-year vision, but it’s important to keep it in mind as you make decisions and enable your team to make decisions. Make yourself intentionally available to your organization. Keep an open door policy and advertise it. If you solicit advice and nobody responds, you probably need to re-consider how you are reaching out to your staff. Try meeting with small group, virtual suggestion boxes, or even one-on-one discussions until you find a medium that connects. Your actions will play a big part in setting the tone of the entire organization.