As a junior project manager, you may identify risks, track blockers, and follow up on pending decisions, but progress can still stall when senior project managers or decision-makers don't respond in a timely manner.
When these delays start affecting project timelines, how do you handle the situation without overstepping your authority or damaging working relationships?
- How do you escalate unresolved risks and decisions effectively?
- How do you create accountability when follow-ups go unanswered?
- How do you protect project timelines when decisions are outside your control?
I would like to hear how experienced project managers have handled this situation, especially when they were responsible for delivery but lacked the authority to make the final call.
That’s a really good question, and it’s something many junior project managers face: when you are responsible for delivery but not the final decision-maker, the best approach is to stay professional, structured, and focused on impact rather than frustration.
If senior PMs or stakeholders are slow to respond, I would document the pending decision, the deadline, and the impact on timeline, then follow up in a way that makes the risk visible without sounding accusatory. If there’s still no response, I would raise it through the proper channels, such as status reports or project meetings, so it becomes a shared and visible project risk rather than a private chase.
To create accountability, use action logs, decision trackers, and named owners with due dates, which helps keep things transparent. And to protect timelines, highlight possible scenarios, recommend temporary assumptions or alternative paths where possible, and make sure leadership understands the trade-offs of delay.
In my experience, this kind of calm, documented, and impact-based escalation helps move things forward while preserving working relationships and staying within your authority.
...
1 reply by Srikana Ray
Oct 26, 2026 11:08 AM
Srikana Ray
...
Thank you for sharing the valuable insights. Having a well documented and structured approach to handling escalations, while maintaining positive working relationships is essential for continue successful delivery of projects.
This is a great question, and I think we all face it, whatever our seniority. PMs may deal with it more than most, but it's a very typical challenge.
In my experience, the first thing is to be structured and organized. I identify the bottlenecks, but I also think through how to move forward, not just flag the problem. Two things help me most. The first is having a clear escalation route defined upfront, so I never have to figure out how to escalate each time. Everyone knows the path, which also keeps it from feeling personal or like I'm overstepping.
The second is giving context. Often people don't realize how big the issue is, and I'm asking them to expedite something without showing the full picture or explaining the rush. So instead of saying "there's a delay, please respond ASAP," I explain what's at stake: if we don't get an answer by a specific date, we risk missing the market launch, which could cause a shortage and affect patients. That's very typical in pharma. I also put a dollar figure on it, because it helps people grasp the scope and severity of the delay.
Making sure people understand the whole picture is definitely the PM's job. When they understand what happens if the timeline slips, follow-ups get answered much faster.
...
1 reply by Srikana Ray
Oct 26, 2026 11:10 AM
Srikana Ray
...
Thank you for sharing your experience and practical advice. I agree that providing clear context, highlighting the impact and having a defined escalation path are key to driving timely decisions and successful project delivery.
Senior IS Project Manager| Baycare Health SystemsClearwater, Fl, United States
I think as project managers one of our main responsibilities is to remove blockers from the team and then get out of the way.
Therefore it is critical to follow-up with the team members who are able to correct the situation, and if time is critical their leadership should be included shortly there after.
This is not a one and done, you must continue to follow-up, using different contact methods, until the issues are resolved.
Keeping a detailed issues list is also important Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Usually you do not have the authority to solve issues and risk. The key thing is to make impacts visible mainly to the steer committee. Saving Changes...
That’s a really good question, and it’s something many junior project managers face: when you are responsible for delivery but not the final decision-maker, the best approach is to stay professional, structured, and focused on impact rather than frustration.
If senior PMs or stakeholders are slow to respond, I would document the pending decision, the deadline, and the impact on timeline, then follow up in a way that makes the risk visible without sounding accusatory. If there’s still no response, I would raise it through the proper channels, such as status reports or project meetings, so it becomes a shared and visible project risk rather than a private chase.
To create accountability, use action logs, decision trackers, and named owners with due dates, which helps keep things transparent. And to protect timelines, highlight possible scenarios, recommend temporary assumptions or alternative paths where possible, and make sure leadership understands the trade-offs of delay.
In my experience, this kind of calm, documented, and impact-based escalation helps move things forward while preserving working relationships and staying within your authority.
Thank you for sharing the valuable insights. Having a well documented and structured approach to handling escalations, while maintaining positive working relationships is essential for continue successful delivery of projects. Saving Changes...
This is a great question, and I think we all face it, whatever our seniority. PMs may deal with it more than most, but it's a very typical challenge.
In my experience, the first thing is to be structured and organized. I identify the bottlenecks, but I also think through how to move forward, not just flag the problem. Two things help me most. The first is having a clear escalation route defined upfront, so I never have to figure out how to escalate each time. Everyone knows the path, which also keeps it from feeling personal or like I'm overstepping.
The second is giving context. Often people don't realize how big the issue is, and I'm asking them to expedite something without showing the full picture or explaining the rush. So instead of saying "there's a delay, please respond ASAP," I explain what's at stake: if we don't get an answer by a specific date, we risk missing the market launch, which could cause a shortage and affect patients. That's very typical in pharma. I also put a dollar figure on it, because it helps people grasp the scope and severity of the delay.
Making sure people understand the whole picture is definitely the PM's job. When they understand what happens if the timeline slips, follow-ups get answered much faster.
Thank you for sharing your experience and practical advice. I agree that providing clear context, highlighting the impact and having a defined escalation path are key to driving timely decisions and successful project delivery. Saving Changes...
Anonymous
You will encounter similar situations in projects regardless of your level of experience, and how you handle them will strongly influence the project’s outcome. It’s important to conduct a stakeholder analysis and understand each stakeholder’s working style and preferred method of communication. Some respond well to email, while others may prefer phone calls or regular meetings to stay aligned.As a project manager, you must present the true status of the project, clearly call out risks that require immediate attention, and highlight blockers that could impact the timeline. Don’t hesitate to escalate issues through the appropriate channels before they escalate further. Saving Changes...
Adrian BearManaging Director| ThorAppsGawler, Australia
Thanks Srikana. A pending decision is easiest to deal with when you turn it into a task like any other. "Decide X" gets the decision-maker as its owner, a due date, and the impact if it slips. Then an unanswered follow-up isn't you chasing someone. It's an overdue task with their name on it, visible to everyone in the status report. The hard part is that senior people often don't like their delays being that visible. I'm interested to hear how others get sponsors to agree to that kind of tracking up front, before it gets awkward. Saving Changes...
Project Manager| AWR Development (BD) Ltd. Cox's Bazer , Bangladesh
Hi Srikana, brilliant question! Managing responsibility without authority is one of the toughest challenges in project management. I've found that framing follow-ups around clear impact works best—showing decision-makers exactly what happens to the schedule or budget if a choice isn't made by Date X. Keeping these risks visible in the risk register creates gentle accountability without feeling confrontational!
Hi Srikana, brilliant question! Managing responsibility without authority is one of the toughest challenges in project management. I've found that framing follow-ups around clear impact works best—showing decision-makers exactly what happens to the schedule or budget if a choice isn't made by Date X. Keeping these risks visible in the risk register creates gentle accountability without feeling confrontational!
Thank you for the valuable insight! Saving Changes...