Imagine you’re leading a rescue mission to save a sinking ship. You wouldn’t send the divers to patch the hull weeks after the engineers arrive to assess the damage, right? You need a coordinated effort, with all hands on deck at the right time.

The same principle applies to project recovery, especially when technical issues are at the heart of the problem. Bringing in a technical review team is like sending in those expert divers. But timing is everything.

Here’s why it’s crucial to synchronise the technical review with your arrival as the Program Recovery Manager:

Minimising Downtime:

If technical problems are the culprit, your first priority is to stop the bleeding. This means putting a temporary halt to any further development or changes to the system. Think of it as stabilizing the patient before performing surgery.

However, this “pause” can create a perception of inactivity, especially in the client’s eyes. They might start to wonder, “Why isn’t anything happening? Is the team just sitting around?”

That’s why it’s crucial to have the technical review team on-site as soon as possible. Their presence sends a clear message: “We’re not just twiddling our thumbs; we’re actively investigating the problem.”

Demonstrating Progress:

Furthermore, having the technical team alongside you allows you to showcase progress in real-time. As they uncover issues and identify solutions, you can relay these findings to the client, demonstrating that you’re taking concrete steps to address the situation.

This transparency builds confidence and reassures the client that you’re in control. It also helps to manage expectations and avoid the dreaded “IBM is doing nothing” perception.

Tailoring the Technical Approach:

The technical review isn’t a one-size-fits-all solution. It needs to be tailored to the specific needs of the project. This means adjusting the project plan to reflect the actual activities involved.

For instance, your plan might include tasks like:

• Kick-off meeting: Bringing the technical team up to speed on the project’s history and challenges.
• Architecture overview: Analysing the system’s design and identifying potential weaknesses.
• Detailed technical interviews: Gathering insights from the development team and other stakeholders.
• Monitoring and communication activities: Tracking the team’s progress and keeping the client informed.

Don’t Forget the PM Review:

In addition to the technical review, it’s crucial to assess the project management processes themselves. Often, poor project management practices contribute to, or even exacerbate, technical issues.

Bringing in a Testing Expert:

Another common weak point in troubled projects is the testing environment. Consider bringing in a testing expert to assess the current testing practices and implement improvements. This can significantly enhance the quality of the solution and prevent future issues.

By synchronising the technical review with your arrival, tailoring the approach to the project’s specific needs, and addressing project management and testing practices, you can create a powerful and coordinated effort to rescue the project and set it on a path to success.