You Don't Run Your IT Department. Your Leadership Team Does.

I walked into a leadership team meeting many years ago and immediately felt the tension. My Infrastructure Manager and Applications Manager were debating a server migration timeline, but it wasn't a productive debate. It was territorial. Each was defending their turf, neither was listening, and the rest of the team was watching the show.

This wasn't an isolated incident. It was the pattern. My leadership team operated as a collection of individuals managing their own silos, not as a cohesive team leading a shared mission.

And that was my fault.

I'd been so focused on building individual relationships with each of my direct reports that I'd neglected to build them as a team. I'd been delegating work downward through separate channels, holding one-on-ones, giving guidance — all the things you're supposed to do. But I'd missed the most important thing: forging those individuals into a unit that could lead the organization together.

The result? Friction at every boundary. Duplicated effort. Dropped balls when work crossed domains. Staff confusion because their managers were sending different signals about priorities. That moment became a turning point. I realized that if I wanted to build a high-performing IT organization, I had to start by building a high-performing leadership team.

After 25 years leading IT in local government, I'm convinced this is the single highest-leverage investment a CIO can make.

The Insight That Changed Everything

Here's what took me too long to understand: as a CIO, you don't actually run the IT department. Your leadership team does.

You set direction. You establish vision. You build relationships with executives and elected officials. But the daily reality of how your department operates, how decisions get made, how problems get solved, how people experience their work environment — that's all shaped by your leadership team.

If they're dysfunctional, siloed, or misaligned, it doesn't matter how brilliant your strategy is. The organization will reflect their dysfunction, not your vision.

This is especially true in mid-sized local government, where you likely have three to eight direct reports who each manage a functional area. There are no layers of middle management to buffer the impact. Those leaders are the management layer. If you're not investing in building them as a team, you're fundamentally limiting what your organization can achieve.

Why Individual Relationships Aren't Enough

Most CIOs fall into the same trap I did. You hold regular one-on-ones. You understand each person's challenges. You provide coaching and support. You think you're building a strong leadership team because you have strong relationships with each member.

But a collection of strong individual leaders does not automatically become a strong leadership team. In fact, strong leaders without team cohesion often create more organizational problems than weak ones. They optimize for their own area at the expense of the whole. They compete for resources instead of collaborating. They build empires instead of bridges.

Your job as CIO is not just to develop individual leaders. It's to forge them into a team that operates with shared purpose, mutual accountability, and genuine trust. That requires intentional work. It doesn't happen by accident.

The Distinction That Changes Team Dynamics

The most powerful concept I've applied to my leadership team is the difference between agreement and alignment.

Many leaders pursue consensus. They want everyone on board before moving forward. This sounds noble but creates paralysis. With a diverse leadership team — different personalities, experiences, roles, and perspectives — unanimous agreement on tough decisions is nearly impossible.

And honestly, you shouldn't want it. If everyone always agrees with you, either you're not making hard decisions or people aren't being honest.

What you need instead is alignment: every team member commits to supporting and executing a decision, even if they personally disagree with it. They communicate it as "our decision," not "the boss's decision that I didn't support." They execute with full effort, not passive resistance.

I learned this the hard way when a manager consistently telegraphed her disagreement to her staff. She'd say things like "I don't agree with this direction, but we have to do it." Technically compliant. Organizationally devastating. Her team absorbed her resistance and reflected it back tenfold.

When I addressed it, she said she was doing what I asked. And I told her that's not alignment. Alignment means owning the decision as yours, publicly and privately. She chose to get in alignment — and once she did, everything in her area improved.

Building the Team That Builds the Organization

So how do you actually build this? A few practices that have made the biggest difference for me:

Be explicit about expectations. Don't assume your leaders understand that you expect them to operate as a team, not just as individual managers. Tell them directly. You expect proactive information sharing. You expect them to hold each other accountable, not just report problems up to you. You expect full commitment after decisions are made. Say it, revisit it, reinforce it.

Transform your team meetings. Stop running status updates. Use leadership team time for strategic conversations, collective problem-solving, and real decision-making. If your meetings feel administrative, you're wasting the most valuable hour on your calendar.

Delegate and trust. If you went on vacation for two weeks, would your IT department operate effectively? If not, you haven't built the team you need. Give people real authority. Let them own outcomes. Your job is to build a team capable of running IT without you, not to be the indispensable decision-maker.

Coach, don't solve. When a leader brings you a problem, resist the urge to fix it. Ask what they think. Help them develop their own judgment. The goal is building their capacity, not demonstrating yours.

The Multiplier Effect

When your leadership team is strong — aligned, trusting, mutually accountable — everything multiplies. Strategy gets executed. Culture gets built. Problems get solved before they escalate. People across the organization feel the difference because leadership isn't just happening at the top. It's cascading through every level.

That's not luck. That's the result of a CIO who understood that their real job isn't to run IT. It's to build the leadership team that runs IT.

Are you doing that? Really doing it?

If not, that's where to start.