What is a CIO? | Tech Talk - YouTube

Channel: unknown

[3]
Hi, there. Thanks again for joining us on another Tech Talk.
[5]
I'm Nick, and I'm joined again by Chad Hiatt.
[8]
He's our chief information officer here at Aldridge.
[10]
Today we're going to be talking about our CIOs that we provide to our clients.
[15]
Chad, go ahead and describe for us what a CIO is.
[19]
A chief information officer within an organization
[21]
within Aldridge or even in overall delivery
[25]
is really tasked with strategically aligning IT
[28]
to what the business's objectives are.
[30]
The CIO is normally part of the executive leadership team of the organization.
[33]
Whereas the CEO, is going to define the vision
[36]
and the mandate and the direction of the organization.
[39]
The CEO will say, "We're going to accomplish this in the next year
[42]
or the next two years or the next three years.
[44]
Here are our goals. Here's what we're trying to do."
[46]
The CIO then internalizes that and says, "Okay. Within my teams,
[50]
within technology, and what technology does within the organization,
[53]
here's how we are going to either accomplish
[56]
or support the other teams and those initiatives.
[58]
Here's what we're bringing to the table to make that happen
[61]
and make sure that as an organization we achieve that."
[63]
What are some of the key benefits that our CIO is bringing to our clients?
[66]
Most of our clients in the small- to medium-sized business level
[70]
while they can certainly benefit from the strategy that a CIO brings
[74]
and the IT Knowledge that a CIO brings
[76]
often it's not economically appropriate for clients
[78]
of that scale to have a full-time CIO role.
[81]
It makes sense for them to be able
[84]
to leverage the expertise of what Aldridge brings to them
[87]
much like they leverage our expertise
[88]
for our services desk and network operations and implementation teams.
[92]
The CIO role is actually part of our overall service delivery to our clients
[96]
so that the CIO can participate in the leadership meetings
[99]
and strategize with the client and say,
[101]
"Well, let's really talk about what we're trying to do
[103]
over the next 12 months or 24 months or 36 months
[105]
so that we understand what we're trying to build the solution to support."
[110]
It's not just a matter of going in and saying this is the right product
[113]
and here's the thing that's new and this is exciting.
[116]
It's like, no, house is really going
[117]
to generate more revenue or reduce costs in the client environment
[120]
to help them achieve what they're really trying to do as an organization.
[123]
In fact, the best relationships that we've got with some of our clients
[125]
that are at a very high level of maturity
[128]
we are always planning ahead.
[130]
Usually, those conversations are occurring 12 to 18 months down the road.
[135]
We know what's going to be happening.
[136]
That information, that part of that strategy
[140]
part of what we're doing from an IT architectural perspective
[143]
gets fed back into our service teams, into our network operations teams,
[146]
so that they understand what our client organizations are trying to accomplish.
[150]
Everything that we're doing as an organization for IT is in context
[154]
and that's usually led by the CIO.
[156]
Where does the CIO fit in the framework that we have for successful IT?
[160]
The CIO sits at the strategy level the framework.
[163]
They often also participate in the architectural or the management components of it.
[167]
When you're designing IT
[169]
there's a very large part of the design
[172]
that has to be driven by the strategy of the organization.
[175]
They're really participating in those top levels.
[177]
There are also times where the CIO will come
[180]
into the conversation even from a support or a management perspective.
[182]
If someone has an issue within the client organization
[186]
and someone within the IT group is saying, "Wait, I can solve that."
[190]
Oftentimes, they'll know the right direction to go
[193]
but the loop that passed the CIO to say,
[195]
"Is this consistent with what we're trying to do for an overall strategy?
[197]
I don't want to go in a direction that's not consistent
[200]
with what the leadership is trying to achieve."
[201]
What makes a good CIO? What sort of skills do they bring to the table?
[204]
-Speaking for Aldridge
[206]
the CIOs have technical backgrounds
[209]
but also management executive backgrounds.
[211]
A typical CIO; we're talking in an IT Industry overall
[216]
has usually gone through a support role.
[218]
They've usually gone into a manager role
[220]
managing other people providing support.
[221]
Sometimes they've progressed up to a director role
[223]
but usually, they have that executive level experience.
[225]
These are people that are comfortable participating
[228]
at the table with a CEO or president, or a business owner,
[231]
the principals of the organization, and having high-level conversations
[236]
at that tier without getting stuck down in the weeds
[238]
of the individual technical implementations.
[240]
They then take that information, synthesize it
[243]
and turn it into the actual strategies, designs and architectures
[247]
that make the organization move forward.
[248]
What would be some differences
[250]
between our CIO offering versus maybe other CIOs
[253]
or internal CIOs at large companies?
[255]
Internal CIOs at large companies are great
[258]
for the companies that have that economic scale and that makes sense.
[261]
For companies that are smaller
[263]
where maybe they don't have that role dedicated inside
[266]
but they feel like they're getting that or some similar name service
[269]
from another provider, at least what I've seen in conversations
[272]
is that it's rare to see the level of engagement
[275]
that we really bring to the table with that
[276]
to really understand what we're trying to accomplish.
[279]
It's not about products. It's not about technology solutions.
[283]
If the conversation shifts to products or technology solutions
[286]
it's the wrong conversation.
[287]
It's not a CIO conversation at that point.
[289]
It's really about what is the business trying to achieve?
[291]
What is the business trying to accomplish?
[293]
What are the things that the business is trying to overcome?
[295]
Then applying our expertise and our knowledge
[299]
at that executive level to be able to say, "I think we can solve that
[302]
if we did this, this and this. Let's consider this."
[304]
Nick: Thanks for joining us again for another Tech Talk.
[307]
This has been a great discussion.
[308]
Hopefully, you've learned a little bit about the CIO offering that Aldridge has.
[311]
If you want more information, feel free to reach out to us at www.aldridge.com.
[316]
We'll see you on the next Tech Talk.