The Best Project Managers Don't Simply Report Risk. They Identify It Early.
One of the most common responsibilities associated with project management is reporting status.
- • Schedules are updated.
- • Metrics are reviewed.
- • Risks are documented.
- • Progress is communicated.
And all of those activities are important, but over the course of more than 30 years managing complex industrial projects, I've come to understand that the most valuable project managers do something more.
They identify risk before it becomes status.
That distinction may seem subtle, but it can have a significant impact on project outcomes.
Most Risks Aren't Hidden
When a project encounters significant cost growth, schedule delays, quality issues, operational challenges, or safety concerns, people often search for the event that caused the problem.
In reality, many of the warning signs were present long before the issue became visible.
The challenge is that they didn't look like major problems at the time.
They looked like:
- • A schedule assumption nobody challenged.
- • A resource constraint everyone knew about but nobody owned.
- • A turnover plan that worked perfectly on paper and nowhere else.
- • A dependency that seemed manageable until multiple activities began competing for the same resources.
- • A critical path that existed largely because people had convinced themselves it existed.
Individually, these conditions may not appear particularly concerning.
Collectively, they can create significant project vulnerability.
The warning signs are often visible, the question is whether or not anyone is paying attention to them.
Why Smart Organizations Still Drift
A common misconception I've encountered is that project problems occur because organizations lack capable people, but truthfully, that’s rarely the case.
Most large projects are staffed by intelligent, experienced professionals who genuinely want the project to succeed.
The challenge is something different.
As projects become larger and more complex, people naturally focus on their area of responsibility.
- • Engineering focuses on engineering.
- • Construction focuses on construction.
- • Scheduling focuses on schedules.
- • Operations focuses on operations.
- • Procurement focuses on procurement.
Each group is managing its portion of the work - The risk emerges when nobody is consistently challenging the assumptions connecting those pieces together.
That's where projects begin to drift, not because of a catastrophic failure or because people stop caring, but because dozens of small risks gradually become accepted as normal. (This is a key element and I discuss “normalization of deviance” in detail in a separate insight article).
- • A schedule assumption goes unchallenged.
- • A coordination issue remains unresolved.
- • A workaround becomes permanent.
- • A resource conflict is deferred.
- • An emerging risk is acknowledged but not addressed.
Over time, these conditions accumulate until the project begins experiencing impacts that seem sudden but have actually been developing for quite some time.
The Difference Between Reporting and Oversight
Traditional reporting is often focused on describing what has already occurred.
Oversight should focus on identifying what may occur next, and that requires a different perspective.
Instead of asking:
What happened?
Effective oversight asks:
What assumptions are we making?
What conditions are changing?
Where are the emerging stress points?
What are we becoming comfortable with that we shouldn't be?
What risks are being accepted without fully understanding the consequences?
These conversations are often more valuable than reviewing historical performance metrics because they focus attention on future outcomes rather than past events.
The Highest-Value Conversations Happen Early
A key lesson that’s remained consistent throughout my career is that the highest-value conversations usually happen before there is a problem.
- • Before the schedule slips.
- • Before the cost increases.
- • Before the rework occurs.
- • Before the safety event.
- • Before recovery becomes expensive.
At that stage, options still exist and the organization still has flexibility.
Adjustments are relatively inexpensive, and decisions can still influence outcomes.
But once a problem becomes visible in reports, many of those options have already disappeared.
The discussion shifts from prevention to recovery.
And recovery is almost always more expensive than prevention.
Why Experience Matters
I've always joked that experience is the thing you get immediately after you needed it most.
Experience is often misunderstood as simply having spent a long time doing something.
In reality, one of the greatest benefits of experience is pattern recognition.
Experienced professionals have seen projects struggle, recover, succeed, and fail.
They begin to recognize familiar conditions long before others see them as risks.
They're not necessarily smarter than everyone else, they're simply noticing patterns that resemble situations they've encountered before.
That perspective allows them to ask questions others may not think to ask.
And sometimes those questions prevent problems that never appear in a status report.
Final Thoughts
Anyone can explain why a project failed after the fact, because the lessons are usually obvious once the outcome is known.
Far fewer people can identify the failure while it is still preventable.
That's where experienced project leadership and effective oversight create the greatest value.
Not by reporting the fire - But by smelling the smoke.
Not by documenting the problem - But by recognizing the conditions that allow the problem to develop.
Because the most effective project managers don't simply report status.
They identify risk before it becomes status.
And in complex projects, that difference can determine whether a project remains on track or spends the rest of its life trying to recover.