As a Program Manager; How to manage a delayed project from a PM from a different area/department

In these situations I first build trust by asking the PM what support would remove pressure, not add to it. A short daily sync and a simple recovery view of risks, milestones and blockers helps us get aligned fast. Once they feel you are helping to clear the path, the information flow improves and the schedule recovery becomes a shared effort.

Francisco,
You are approaching this with the right mindset. In delayed projects, posture matters as much as process.
If the PM is firefighting, your role is not additional oversight but structural relief.

Focus on three levers.
First, ask what friction you can remove at program level.
Trust builds when you reduce pressure instead of increasing reporting.

Second, clarify decision rights and escalation paths.
Significant delays across departments are often governance and prioritization issues, not execution failure.

Third, protect the PM’s cognitive bandwidth.
Form an initial view from available artifacts and use short validation conversations instead of heavy onboarding sessions.

At program level, your value is systemic: restore clarity of decisions, align trade-offs with strategic intent and stabilize interdependencies.
When you become the architect of coherence rather than another control layer, you accelerate recovery without becoming a burden.

In these situations I first build trust by asking the PM what support would remove pressure, not add to it. A short daily sync and a simple recovery view of risks, milestones and blockers helps us get aligned fast. Once they feel you are helping to clear the path, the information flow improves and the schedule recovery becomes a shared effort.

I’d position myself as support, not oversight.
Ask what’s blocking recovery and remove friction at program level.
Build context from existing artifacts, validate quickly, and focus on clarifying priorities and escalation paths.

I agree with Pavan, this is best way to proceed.