Context: I’m a pipeline program manager. I joined the company 1.5 years ago at a time when the business moved from siloed development to a cross-functional working model having strong growth ambitions. Until now, my line manager was the Head of PMO and I had a dotted‑line program lead. My line manager was recently laid off, and I will be directly reporting into the program lead, who has no PMO experience and did not collaborate with PMO before joining the program. I'm managing four complex and high-stakes programs under the same asset.
Unfortunately, I have been facing many gaps in this role, which I believe undermine program delivery and may put me at personal risk for failures I cannot control.
1. My responsibilities (scope, timelines, budget, resources, outcome, benefit management) only partially match the access to information that I actually have e.g. resource information is missing, and program budget management was not done prior to my arrival. Now, I'm partially involved in the program budget. Resource allocations are still made by separate departments without my input.
2. Lack of transparency & overpromising
There is a lack of transparency about constraints, operational risks, and real capacity. One department with most deliverables on the critical path is pressured by their departmental head. To signal ambition, unrealistic promises become rewarded. Although I challenge these promises, colleagues keep holding onto them. Roadblocks are not openly shared by this department until too late, so minor issues become problems.
3. Escalation breakdown
When I flagged risks to both dotted line and my line manager e.g. early warnings or decisions not being respected by cross-functional team members, it did not lead to action on their end. Later, when issues materialized e.g. slipped milestones, executive leadership asks for “early warning,” despite me having raised these risks earlier.
4. Many stakeholders, many meetings
The original intent was: two core cross‑functional meetings and one single point of contact per function across the programs (four programs are running under the same asset). Now, there are on average three contact points per function, many parallel meetings, often set up by others, with overlapping topics (I was presented with the same content in three different meetings) and unclear decision rights. Decisions are sometimes revisited or ignored afterwards. Dotted line keeps adding more stakeholders to regular meetings.
5. Inefficient information flows
Despite the many team meetings, it is highly difficult and inefficient to get timely and accurate PgM information.
6. Culture
Some colleagues in the cross-functional team are favored, and decisions are not enforced consistently. Although there has been senior sponsorship for the new cross-functional model, it was not active/engaged. There was no change management covering all functions and levels affected by the change. Resistance towards PMO by one middle manager and micro‑aggressions/stress dumping toward the PM role occur by this manager. Generally, there is resistance towards processes in the company.
7. Program lead (previous dotted line) is very visionary, energetic and ambitious, but lacks planning realism and openly dislikes roles and responsibilities, PM methodologies, standards and structure. He frequently launches new workstreams, creates and circulates strategic docs (budget, milestones), and sets up cross‑functional meetings without involving me as PgM.
The entire situation left me exhausted.
My line manager recently got fired, the PMO department was dissolved, however I and my colleagues keep our pipeline program management roles, now reporting into the program leads and our reporting line continues into the department which is pressured to overpromise.
I'd really value your input:
How do you see this situation overall ?
If you were in my position, what would you do in the next 3–6 months to protect delivery and your own role?
At what point would you decide, “this setup is not fixable for me,” and how would you act on that (e.g., push for a formal reset, change role, or leave)?
What would you do differently from what I’m doing now, and what “red flags” or “green flags” would you watch to decide whether to keep investing in change here?
I'd really appreciate your thoughts. Thank you! Saving Changes...
Sort By:
Anonymous
This situation isn’t a challenge—it’s a warning sign of systemic failure. If I were in your position, I’d stop pretending delivery can be “protected” in a structure that rewards chaos and punishes accountability. In the next 3–6 months, I’d document everything, create my own truth, and make it public—even if it embarrasses leadership—because survival beats loyalty. The point where this setup becomes unfixable? The moment decisions turn performative and governance becomes theater, which is usually now. At that stage, pushing for a reset is just optics; the real move is planning your exit before burnout becomes your legacy. What would I do differently? Stop investing in change unless leadership commits to radical transparency. Red flags? Overpromising celebrated, dashboards multiplying, and silence on accountability. Green flags? None—because in environments like this, “green” is just a color they paint over cracks. Saving Changes...
Sripranav Charan R GProject Management| infinite computer solutionsErode, TN, India
The formal role of a program manager is strategic and integrative—owning multiple related projects, aligning them to business goals, and acting as the glue between executives, project managers, and delivery teams. Role vs. reality
span class="ql-ui" contenteditable="false"/spanOn paper, program managers focus on strategy, roadmaps, benefits realization, cross‑project risk/issue management, and stakeholder alignment, while individual project managers handle day‑to‑day execution.
span class="ql-ui" contenteditable="false"/spanIn reality, many program managers get pulled into firefighting, detailed project tracking, escalations, and even hands‑on delivery, because organizations under‑staff PMs, blur responsibilities, or treat the role as a “super project manager.”
How to handle the gap
span class="ql-ui" contenteditable="false"/spanClarify expectations: Agree with your sponsor on what success looks like at program level (outcomes, KPIs, decision rights) and document responsibilities for you vs. project managers vs. functional leads.
span class="ql-ui" contenteditable="false"/spanProtect your altitude: Delegate task‑level tracking to project managers and leads; keep your own focus on interdependencies, risks, benefits, and stakeholder management, stepping into details only for critical issues.
span class="ql-ui" contenteditable="false"/spanCommunicate relentlessly: Run a consistent cadence of steering forums, cross‑project syncs, and risk/decision logs so stakeholders see you as the owner of alignment and trade‑offs, not just another status reporter.
span class="ql-ui" contenteditable="false"/spanManage overload and scope creep: When you’re being used as both program and project manager, surface the impact (on risks, timelines, benefits) and propose options—additional PMs, deprioritization, or reduced scope—rather than silently absorbing the extra work.
Personal positioning
span class="ql-ui" contenteditable="false"/spanPosition yourself as the person who turns strategy into executable programs: talk in terms of outcomes, value, and portfolio trade‑offs, not just timelines and tasks.
span class="ql-ui" contenteditable="false"/spanBuild a small “core team” (architect, lead PM, ops/finance partner) that shares ownership of planning, governance, and reporting, so the program doesn’t depend on you doing everything yourself.
These are symptoms of low organizational PM maturity and a broken system. You have no way of fixing the fundamental gaps which are causing these issues. As such, make sure you are continuing to be diligent about formally identifying and communicating delivery risks including recommended responses to their owners, get decision records documented for any critical decisions, especially those which will impact delivery success, and start your job search.
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
This is extremely tough, and what you’re describing goes far beyond a single role, it’s a systemic maturity problem. When responsibilities don’t match access, escalation loops break, and overpromising is rewarded, even the strongest PgM can’t create stability alone. In the next few months, the best protection is clarity: document risks, decisions, and constraints, and share them in the right forums so your accountability is visible. At the same time, watch for signs that leadership is willing to reset expectations and bring structure back into the model. The setup becomes “unfixable” when transparency is discouraged and decisions keep bypassing governance. If you see no movement toward realistic planning, it may be time to consider other options for your own well-being. You’re not the problem here, but the environment is. Your priority is protecting your role, your boundaries, and your energy while you assess whether change is actually possible. Saving Changes...
From my view point, it's an opportunity to adopt a real program manager role. As everything is chaos, that's where an orchestration and integration is badly needed. Having said and done, it's certainly not an easy task however If I were in your position, I will align with leadership team and obtain their support first. Have an open discussions and take things in control. Articulate and highlight the risks and challenges to each stakeholder such as project managers, cross functional teams and make them responsible for any slippages in communications. The more clear and candid your communication is, the best way to gain the control back. I handled similar situation where everything is chaos and by taking ownership, being firm in every communication helped to gain the control back. Hope this helps !! Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
This situation reflects a classic governance breakdown: you are accountable for outcomes without authority, visibility, or structural support. That is not a program-management issue, it is an organizational design and leadership issue.
Cross-functional delivery was launched without defining decision rights, escalation paths, role boundaries, or change management.
No program manager can deliver predictably when resource control, budget ownership, and risk transparency are structurally outside their reach.
Even if you worked harder, raised more risks, or attended every meeting, the system would still produce overpromising, hidden constraints, and late escalations, because the underlying incentives reward the wrong behaviours.
Treat the next 3–6 months as a diagnostic window, not a performance window. Your job is to test whether leadership is willing to restore governance, not to compensate for its absence.
Shift all escalations and dependencies to written, visible, traceable channels. This protects delivery and protects you.
Build a minimal “single source of truth” (milestones, risks, dependencies, decision log) and request written clarification of what you own vs. what you influence.
If the system continues rewarding overpromising, bypassing your role, and ignoring escalations, the setup is structurally unfixable without executive reset.
Red flag threshold:
When your accountability > authority for more than 2–3 months and leadership shows no intention to rebalance it.
If green flags appear (clarity, transparency, acted escalations), invest. If not, protect your credibility and consider a transition.
You’re not failing.
You’re navigating a system that hasn’t been designed for success, yet.
Your situation shows a structural gap between responsibility and authority. As a PM, you’re accountable but not given information, decision rights, or real sponsorship. For the next months, document risks, set a clear operating rhythm, and protect what you can influence. If transparency and support don’t improve, that’s a red flag to consider a reset or a role change. Saving Changes...
Community Champion
