A project can be green right up until the moment it isn't
Leadership

A project can be green right up until the moment it isn't

A project can be green right up until the moment it isn't.
There's often pressure, particularly with large migrations or transformation programmes, to provide certainty.

-            When will it be finished?
-            Are we on track?
-            Will we hit the deadline?

Of course, leadership needs answers to those questions. But sometimes the most useful answer is:

"We don't know yet, and here's what we need to find out."

I've always preferred being open about risks and uncertainty early. If we don't fully understand a dependency, say so. If a date relies on an assumption we haven't validated yet, make that visible. If something outside the team's control could affect delivery, don't wait until it actually does. That isn't being negative about a programme. It gives you options.

You might change the sequence of work, bring in additional expertise, reduce scope, test an assumption earlier or simply make sure the right people understand the potential impact. The alternative is a project that stays green for months, suddenly turns red, and everyone wonders what happened.

Usually, the risk didn't appear overnight. We just didn't make it visible soon enough. I also think there's an important distinction between reporting a problem and simply handing it upwards. When I raise a risk, I try to include what we know, what we don't know, the likely impact and what I think we should do next. Senior leaders don't need false certainty. They need enough information to make good decisions while there is still time to make them.

A risk reported early is still manageable. A risk reported when it becomes an issue gives you far fewer choices.

Share this post

Paul White

Senior Technology Executive · Cloud, DevOps, Security & AI specialist with 25+ years in enterprise technology leadership.