IT (Information Technology) projects stall for lots of reasons. They also fail spectacularly. Worse, they don’t fail soon enough and organizations bloat staffing in pursuit of a project that should be killed. It’s also common to see unqualified resources stumbling through what an expert can finish with little effort.
A sense of urgency is often missing in these IT projects. Milestones are missed with regularity and it’s often unclear who is responsible for deliverables. The expectation that a Google search will yield the technical recipe often substitutes for seeking out experienced help.
It’s not uncommon to hear imaginative reasoning for why a project missed a deadline or failed to accomplish the objective. Most of these reasons are fabrications hiding systemic organizational issues. Sometimes the simple steps such as having clear consequences and an immovable deadline are not sufficient to provoke any meaningful results.
Conflicts are avoided while milestones are missed
It’s no secret that most management inherently avoid conflicts. They know what they should do, but inexplicably can not confront the situation before them. Management may not be able to overcome the imaginative technical fabrications in addition to confronting the individuals involved with those fabrications.
Seeking out a peer review of your shop can often begin the process of restoring urgency and accountability in your organization.
What happens next will be the real test of your own leadership.