Have you developed a “sixth sense” as a leader to identify when an IT project is truly stalled versus experiencing normal delays? What’s your thought process?

1.6k viewscircle icon1 Upvotecircle icon3 Comments
Sort by:
Chief Information Technology Officer in IT Services9 months ago

Empowering team members with autonomy enhances their commitment and accountability, as they take ownership of their tasks without micromanagement. Leading by example, I demonstrate a proactive and dedicated approach, inspiring similar behaviors among the team. In terms of communication strategies, I have found that a combination of regular team meetings, concise progress reports, and one-on-one check-ins fosters clarity and cohesion. Utilizing collaborative tools and platforms ensures that information is accessible and that team members remain connected, especially in hybrid work environments. By implementing these approaches, I strive to cultivate a motivated and agile team capable of overcoming delays and driving projects to successful completion.

Chief Information Technology Officer in IT Services9 months ago

As the Director of Information Technology, I've developed an intuitive sense for distinguishing between typical project delays and situations where a project is genuinely stalled. This insight stems from years of experience and close observation of project dynamics. When I notice consistent missed deadlines without clear reasons, a lack of regular progress updates, or a decline in team morale, I recognize these as red flags indicating potential stagnation. In such cases, I engage directly with project leads and team members to uncover underlying issues, assess resource allocation, and review project documentation to identify discrepancies. This proactive approach enables me to determine the project's status accurately and implement necessary interventions to realign it with our organizational objectives.

Head of Transformation in Government9 months ago

Yes, it's based on heuristics, or "gut" after so many projects.

But I also lean on a technical approach. Earned Value analysis "light," by calculating a very basic EV model based on percentage complete as a proxy. That way I can track any project, even if they don't apply PM methodology. The actual EV doesn't matter. It's the evolution over time. And related to that is "Earned Time". Basically, any project out of it's line by 10-20% better have a good explanation or I conclude it's doomed. 

I also like DICE from BCG. It's a very accurate tool.

And finally, any time I here 95% to 99% complete from a project board.... more than once about 5% to 1% from the planned end date.... That's it. That project is stalled and there is no way to claw back without a major intervention.

Lightbulb on1

Content you might like

Invest more in eCommerce34%

Maintain the current investment in eCommerce60%

Invest less in eCommerce4%

View Results

0-3 months6%

4-6 months43%

6-12 months29%

Longer than 1 year8%

Have not seen a return on our test automation investment7%

Don't know3%

View Results