Why Your IT Team's Performance Problems Are Not a Training Problem

IT organisations are among the most heavily trained workforces in any sector. Technical skills, certifications, agile frameworks, leadership programmes. And yet the same problems keep surfacing . the investment is significant and ongoing.

Delivery delays that nobody can fully explain. Escalations that reach senior leadership when they should have been resolved two levels down. Business units and IT teams that sit in the same meetings but seem to be operating from completely different playbooks. Talented technical people who were promoted into management and are now quietly struggling - not because they are not capable, but because nobody ever defined what leading in this organisation actually looks like.

This is execution friction. In most IT environments it is not caused by a lack of skill. It is caused by a lack of alignment, clarity, and consistent leadership and no amount of training will fix those things if they are not identified first.

The three most common execution friction points in IT

01 The promoted technical expert who was never set up to lead This is the most common and least-discussed problem in IT management. A skilled developer, architect, or analyst gets promoted because they are excellent at what they do. They are now responsible for a team, stakeholder relationships, performance conversations, and cross-functional communication. Nobody sits down with them and defines what good leadership looks like in this organisation. No shared framework exists. So they lead the way it feels natural which may be nothing like the manager down the hall, or the expectations their team actually has. The result is inconsistency. And inconsistency creates friction that shows up as a performance problem.

► Before investing in leadership development for this group, ask one question: do these managers have a clear, shared picture of what good leadership looks like here or is everyone interpreting it differently? If the answer is the latter, start there. Content before clarity will not land.

02 IT and the business are misaligned This is the friction that lives in the gap between what IT delivers and what the business thought it asked for. It shows up as rework, missed requirements, frustrated stakeholders, and project timelines that keep slipping. It is almost never a communication skills problem. It is almost always a structural problem no agreed language for priorities, no clear ownership of decisions at the handoff points, no consistent process for how requirements move from business need to technical brief. Training a team in stakeholder communication will not fix a broken handoff process.

► Map the handoff first. Find where the information breaks down. Fix the structure before you address the behaviour.

03 Agile is running. Delivery is not improving. Most IT teams have adopted agile in some form. Standups happen. Sprints are planned. Retrospectives are scheduled. And yet delivery is still inconsistent, priorities keep shifting mid-sprint, and the ceremonies feel like overhead rather than progress. This is the most misdiagnosed problem in IT. The instinct is to improve the agile practice more training, better facilitation, stricter process. But in most cases the problem is upstream of the methodology entirely. Agile cannot compensate for unclear priorities from leadership. It cannot fix a culture where mid-sprint scope changes go unchallenged. And it cannot create accountability where none has been established.

► Before investing in agile coaching, ask whether the people setting priorities are aligned on what matters most and whether the team has the authority to protect committed work. If the answer is no, the methodology is not the problem.