Project Management

Please login or join to subscribe to this thread

When should a project manager prioritize securing their own role and authority over “saving” the project in the short term?

linkedin twitter facebook   Leadership  
avatar
Eduard Hernandez
Community Champion
Product Operations Program Manager Barcelona, Cataluña, Spain

In aviation, passengers are instructed to put on their own oxygen mask before helping others. I’ve been reflecting on how this idea applies to project management.

PMs are often expected to absorb ambiguity and keep execution moving despite misalignment or weak decision structures. In the short term, this can stabilize delivery. In the long term, it can lead to burnout or reduced effectiveness.

On that note:

- How do you recognize the point where continuing to “push forward” becomes counterproductive?

- What practical signals tell you it’s time to pause, escalate, or reset expectations to protect both the project and your role?
Sort By:
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Eduard -

In the long term, trusting your gut works well as you'll have built up sufficient brain muscle memory to know when a battle is lost.

Earlier in one's career, it helps to have a trusted unbiased advisor who can look at things with you and help to pull your head out of the sand...

Kiron
avatar
Syed Ashir Riaz
Community Champion
AI-Powered Social Media Strategist
As a marketing strategist, I stop pushing when there is no clear direction or decision-making. If campaigns keep changing and results don’t improve, it’s a sign to pause and speak up. Protecting clarity and authority helps deliver better results in the long run.
avatar
Lissette Indhira Pimentel Sosa
Community Champion
Program Manager| HARPER SRL Santo Domingo / Distrito Nacional, Dominican Republic
It’s time to pause when pushing harder no longer changes the outcome.
If decisions keep getting delayed, authority is unclear, or the same risks are raised and ignored, continuing to “hold things together” starts hurting both the project and the PM. That’s usually the signal to stop absorbing the gaps and reset expectations or escalate.
Protecting your role at that point is not a selfish decision; it’s the only way to create the conditions the project actually needs to move forward.
avatar
Eduard Hernandez
Community Champion
Product Operations Program Manager Barcelona, Cataluña, Spain
Thanks for your contributions to this topic. Discussion outcome can to be summarized as "pick your battles". Which battles to pick come with experience in the battlefield :-)
avatar
Srikana Ray
Community Champion
IT Project Manager
- When stakeholders no longer agree about the purpose, scope or value to be delivered by the project
- When continued project execution increases frustration and tension within the team
- When the risks cannot be effectively managed or mitigated
- When success depends on fixing everything
I think it is time for the project manager to take a step back and explicitly state the facts to the stakeholder and the team, even if that jeopardizes the project or results in failure of the project.
avatar
Imran Afzal Cary, NC, United States
Eduard — I like the oxygen-mask analogy, but I’d reframe the decision slightly.

The question isn’t really when do I protect my role vs. save the project — it’s when has the system shifted responsibility for decisions onto execution.

In my experience, “pushing forward” becomes counterproductive at the moment when progress depends less on delivery effort and more on unresolved authority:

– Decisions are deferred but delivery expectations remain fixed
– Risks are acknowledged repeatedly but never owned
– The PM becomes the integrator of ambiguity rather than the facilitator of choice

At that point, continuing to absorb the gaps doesn’t save the project — it masks the real constraint. Short-term stability is achieved by silently compensating for missing decisions, but long-term damage accumulates in the system.

Securing clarity of role and authority isn’t self-protection for its own sake. It’s an intervention. Escalation, pause, or reset is often the only way to reintroduce decision accountability back into the system.

I’ve found a useful litmus test is this:

If the project can only move forward because the PM is personally absorbing risk that belongs to leadership, it’s time to stop pushing and start reframing the work.

Protecting the role, in that moment, is actually protecting the project’s ability to move forward sustainably.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Great souls have wills; feeble ones have only wishes."

- Chinese Proverb

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters