One responsibility that seems to be growing for IT directors is keeping good people engaged.
A few years ago, retention was largely viewed as an HR concern.
IT directors certainly played a role, but the day-to-day focus was usually on projects, service delivery, budgets and technology decisions.
Today, I think the picture looks a little different.
Finding skilled people is difficult enough.
Replacing them once they’ve left can be even harder.
The impact isn’t limited to recruitment costs or the time it takes to fill a vacancy.
Every experienced member of an IT team carries knowledge that doesn’t appear in documentation.
They understand the history behind certain decisions. They know which systems require special attention. They remember previous incidents, supplier issues and lessons learned from projects that happened years ago.
When somebody leaves, that knowledge leaves with them.
You may have experienced this at some point.
A key team member moves on and suddenly a project slows down, a support issue takes longer to resolve or a system nobody has thought about for months becomes far more important than anyone realized.
That’s one reason retention has become closely connected to operational performance.
What I’ve found interesting is that people rarely leave because of a single issue. It’s usually an accumulation of small frustrations.
- Projects keep being delayed because operational work takes priority
- Training budgets become difficult to justify
- The same people end up carrying responsibility for the most demanding work
- Opportunities to learn new skills get pushed back because there isn’t enough time available
I’ve spoken with IT directors who genuinely want to invest more in their teams but find themselves trapped by competing priorities.
- A major infrastructure project arrives
- A security initiative needs attention
- The service desk becomes busier than expected
- Development plans get postponed because operational demands feel more urgent
The difficult part is that these decisions are usually reasonable.
The immediate business need takes priority.
Yet every decision to delay development, mentoring or project involvement has a cumulative effect on the experience of the team.
This becomes particularly noticeable in smaller IT departments.
When capacity is limited, there are fewer opportunities to rotate responsibilities, involve people in strategic work or create space for professional development.
Talented individuals can spend large portions of their time responding to operational demands rather than expanding their skills or contributing to longer-term initiatives.
It’s simply what happens when workloads continue increasing while team capacity remains unchanged.
I’ve also noticed that retention becomes easier when people can see progress.
That doesn’t necessarily mean promotions or new job titles.
It might mean involvement in an interesting project or exposure to a new technology. Greater responsibility in an area they care about or time to improve a process that’s been frustrating them for months.
Those opportunities require capacity.
Without capacity, operational work fills every available space.
It’s one reason IT directors are looking at co-managed support.
They’re trying to create enough breathing room for their existing team to focus on higher-value work, participate in projects and continue developing professionally.
The immediate benefit may be additional operational support.
The longer-term benefit is a stronger, more engaged IT function.
If you’re finding that operational demands are making it harder to invest in your team, let’s talk. Get in touch.
