One of the most difficult realities of program management is that you may be accountable for an outcome without directly managing everyone responsible for delivering it.
You may own the roadmap, the timeline, the risk, the executive updates, and the overall success of the program. But the engineers, analysts, vendors, business owners, legal partners, compliance teams, finance representatives, and operational leaders involved may report to someone else. You cannot simply instruct everyone to prioritize your work. You have to earn alignment.
That is why one of the most important skills a program manager can develop is the ability to influence without authority. This does not mean manipulating people, playing organizational politics without integrity, or trying to become the most persuasive person in every room. It means understanding how to build trust, communicate value, clarify ownership, navigate competing priorities, and help people see how their work connects to a shared outcome.
Program managers do not succeed because they control everyone involved. They succeed because they create the conditions that allow people to move together.
Accountability without direct control
Traditional management structures often rely on positional authority. A manager assigns work, sets expectations, evaluates performance, and has formal responsibility for the people on the team. Program management frequently works differently.
A program manager may coordinate people across multiple departments, vendors, geographic locations, leadership levels, and technical domains. Each group has its own priorities, deadlines, leadership, incentives, risks, constraints, and definition of success. The program manager is responsible for connecting those different realities into one coordinated delivery model. That requires more than project plans and meeting invitations. It requires influence.
Influence begins with understanding
A common mistake is assuming that people resist a program because they do not understand its importance. Sometimes they understand it perfectly. They may simply be protecting something else.
An engineering team may be concerned about technical debt. A business leader may be focused on operational disruption. Finance may be protecting the budget. Legal may be considering contractual exposure. Compliance may be concerned about auditability. An executive may be weighing the program against several other strategic priorities.
Strong program managers do not immediately interpret every objection as unwillingness, incompetence, or lack of commitment. They learn to ask what this stakeholder is responsible for protecting, what competing priorities are affecting their decision, what risk they see that the program manager may not see, what information they need, and what tradeoff is being asked of them.
Influence starts with understanding the world from the other person's position. That does not mean abandoning the program's needs. It means developing a recommendation that reflects organizational reality rather than only the program's own timeline.
Build relationships before the escalation
The worst time to begin building a stakeholder relationship is when you already need that person to approve, prioritize, fund, or rescue something. Trust built only during an escalation often feels transactional.
Strong program managers develop relationships before the program reaches a crisis. They learn who the key decision-makers are, but they also identify the informal influencers — the people whose opinions shape decisions even when they do not hold the highest title. They ask questions before making requests. They communicate consistently. They follow through on commitments. They give credit. They share context. They do not contact stakeholders only when something is wrong.
Relationships create the social infrastructure through which difficult work becomes possible. When trust already exists, stakeholders are more likely to raise risks early, provide honest feedback, and work collaboratively through challenges.
Translate the program into their language
A program manager may understand why an initiative matters, but that does not mean every stakeholder will interpret its value the same way. Different audiences require different framing.
An executive may need strategic impact, financial exposure, enterprise risk, and tradeoffs. An engineering team may need technical requirements, dependencies, and architecture implications. An operational team may need process changes, downtime expectations, and support models. A compliance partner may need control mappings, evidence requirements, and audit implications.
The message should remain truthful and consistent, but the emphasis must change based on the audience. That is not inauthentic. It is translation. Strong program managers do not simply repeat the same presentation to every group. They connect the program to what each audience is responsible for understanding and protecting.
Stop reporting activity and start enabling decisions
Program managers often become trapped in status reporting. They collect updates, create slides, schedule meetings, and report what happened. Those activities may be necessary, but they are not the highest form of program leadership.
Influence grows when the program manager moves from reporting activity to enabling decisions. Instead of saying "the integration remains delayed," a stronger update might say:
"The integration is two weeks behind because the current design requires additional security testing. We have three options: reduce the initial scope, add temporary resources, or move the launch date. My recommendation is to reduce the initial scope because it protects the critical control objective without increasing cost."
The second version does more than communicate a problem. It gives leaders context, options, tradeoffs, a recommendation, and a decision to make. Program managers increase their influence when stakeholders trust them to bring clarity rather than simply surface complexity.
Create shared ownership
People are more likely to support what they helped shape. That does not mean every decision should be made by committee. It means key stakeholders should have meaningful opportunities to contribute before the direction is finalized.
Strong program managers involve people early enough to influence the approach — not after every major decision has already been made. This creates better plans, but it also creates ownership. There is a significant difference between "the program team decided this is what you need to do" and "we worked through the constraints together, and this is the approach we agreed gives us the strongest path forward." The second creates commitment rather than mere compliance.
Clarify ownership without becoming controlling
Influence without authority does not mean avoiding accountability. Program managers still need to establish who owns each deliverable, what completion means, when it is due, what dependencies exist, who can make which decisions, and when an issue must be escalated.
Ambiguity weakens influence because it creates space for assumptions, missed expectations, and conflicting interpretations. Clarity strengthens influence. The goal is not to control every detail. The goal is to make responsibilities visible enough that people can coordinate effectively. A mature program manager knows the difference between oversight and micromanagement. Oversight creates visibility, removes obstacles, and supports accountability. Micromanagement takes ownership away from the people responsible for doing the work.
Learn how to make a clear ask
Many program-management conversations fail because the request is buried beneath too much background information. A strong ask makes four things clear: what is needed, who needs to provide it, when it is needed, and why it matters.
Instead of "we have been discussing access requirements for several weeks and are becoming concerned about the timeline," say: "We need the final access requirements approved by Thursday to preserve the testing window. Sarah owns the approval. Without it, the launch moves by at least two weeks."
Clarity is a form of respect. It allows people to understand what is being requested and decide how to respond.
Use escalation as governance, not punishment
Some program managers avoid escalation because they fear damaging relationships. Others escalate too quickly because they view escalation as a way to force action. Both approaches can weaken trust.
Escalation should be a governance mechanism, used when a decision exceeds the team's authority, competing priorities require leadership intervention, a significant risk cannot be resolved at the working level, ownership remains unclear, or a deadline or control objective is materially threatened. A responsible escalation includes the issue, the impact, the actions already taken, the unresolved decision, the available options, and the recommended path.
Escalation should not surprise people unnecessarily. Whenever possible, the affected stakeholders should know that an issue is being raised and understand why. The goal is not to embarrass someone. The goal is to obtain the decision or support the program cannot secure at its current level.
Develop credibility through consistency
Influence is rarely created through one impressive meeting. It develops through repeated evidence that the program manager is reliable. Do you follow through? Do you communicate early? Do you distinguish facts from assumptions? Do you acknowledge uncertainty? Do you give credit to the people doing the work? Do you remain calm when the program is under pressure?
Consistency builds credibility. Credibility creates influence. Influence makes coordinated execution possible.
Mission over ego
Influencing without authority requires humility. A program manager cannot be committed only to being right, appearing competent, or receiving recognition. The mission has to remain larger than the individual.
Sometimes another person will have the better idea. Sometimes a stakeholder's objection will reveal a weakness in the plan. Sometimes the program manager will need to change the approach, repair a relationship, or acknowledge that the original recommendation was incomplete. That is not a loss of authority. It is evidence of judgment.
The strongest program managers do not need to be the smartest person in every conversation. They need to make it easier for the collective intelligence of the program to produce a strong outcome.
The real work of program leadership
Program management is often described through schedules, budgets, risks, dependencies, and deliverables. Those disciplines matter. But as programs become larger and more complex, the work becomes increasingly human.
The program manager must help people with different priorities, incentives, communication styles, and responsibilities move toward a shared objective. That requires trust, clarity, translation, judgment, relationship-building, accountability, adaptability, and ethical influence.
You may not have direct authority over every person involved. But you can create direction. You can build alignment. You can clarify decisions. You can strengthen relationships. You can connect people to the mission. And you can develop the credibility that causes people to trust your leadership, even when they do not report to you.
That is the difference between coordinating work and leading a program.