The promotion from project manager to program manager is not simply a larger span of control; it is a change in what must be noticed, judged and influenced.
A high-performing project manager is often an obvious candidate to lead a program. They understand delivery discipline, planning, risk, cost, teams and accountability. Those strengths remain valuable.
They can also become a constraint if the new leader tries to manage a transformation as though it were one large project.
Program leadership requires a different altitude. The manager still needs delivery credibility, but must spend more time on strategic intent, cross-project consequences, organisational politics, stakeholder power, operating-model change, commercial exposure and the conditions required for benefits to emerge.
The difficult part is that many of the behaviours rewarded in project management need to be supplemented, and sometimes deliberately restrained.
The Strategic Context
The supplied practitioner sources describe the program manager as coordinating projects, budgets, resources, risks, issues, stakeholders and interdependencies rather than directly managing every project. IBM's historical 2004 discussion makes the distinction more sharply: program managers spend comparatively more effort on integration, negotiating changes in plans and communicating across organisational levels.
The deeper evidence comes from Sergio Pellegrinelli's research. His 2002 paper argues that where programs bridge projects and organisational strategy, program management starts to take on the characteristics of strategic change management and organisational development. In a consultancy case used to develop program-management competencies, experienced project managers had to broaden their focus from technical and project concerns toward business drivers, politics, culture, commercial awareness and ambiguous organisational conditions.
Pellegrinelli and colleagues' later six-programme study found a similar reality in practice. Program management was organisationally embedded, politically influenced and continually adapted. That environment is fundamentally different from a project setting in which success can often be framed around a more bounded objective.
Related article: The Portfolio Manager Is an Enterprise Integrator, Not a Senior Project Manager
What Leaders Commonly Misread
The first misread is that program management is senior project management. This leads organisations to promote people based primarily on schedule control, technical competence or successful delivery of a large project. Those are useful foundations, but they do not demonstrate the ability to lead interdependent strategic change.
The second misread is that the program manager should solve problems by increasing detail. A project manager confronted by uncertainty may correctly seek clearer requirements, tighter plans or more direct accountability. At program level, some uncertainty cannot be removed because it originates in strategy, stakeholder interests, market change or organisational politics. Excessive detail can create an illusion of control while the real uncertainty remains untouched.
The third misread is that program leadership is mainly hierarchical. Many program managers do not control all the people, resources, suppliers or business units whose behaviour determines the outcome. Influence therefore matters as much as authority.
The fourth misread is that politics is a management failure. In major change, different executives and functions can hold legitimate but conflicting interests. Pretending those interests do not exist does not make the program apolitical; it simply makes the program manager less prepared.
Reframing the Issue
The shift from project to program management can be understood as a change from controlling a bounded delivery system to shaping an organisational change system.
At project level, the leader asks:
- What must be delivered?
- By when?
- With what resources?
- Against which requirements?
- What risks threaten the plan?
At program level, those questions remain, but they are joined by harder ones:
- Which combination of capabilities will create the desired business outcome?
- How must the projects change as strategy or evidence changes?
- Which stakeholder interests can block or reshape the program?
- Where are the unresolved dependencies between technology, process, people and operations?
- What must the receiving organisation do differently for the benefits to exist?
- Which decisions should be escalated, negotiated or deliberately left open?
That is a different management problem.
Strategic Analysis: The Five Altitude Shifts
1. From deliverables to enterprise outcomes
A project manager can succeed by delivering an approved output. A program manager has to ask whether the output contributes to the combined outcome and whether that outcome is still valuable.
A system implementation completed on time is not sufficient if business processes, data governance, workforce capability and adoption are not ready. The program leader must protect the outcome from local project optimisation.
2. From direct control to influence
Program managers often work across business units, suppliers, functional executives, regulators and operations. The decisive resource may belong to someone who does not report to the program.
Influence therefore becomes operational capability. Pellegrinelli's case material highlights understanding power bases, communicating confidently at senior levels, handling third parties and creating alignment across organisational and cultural boundaries.
This does not justify manipulation without ethics or governance. It means program leaders must understand how decisions are actually made and how stakeholder interests shape behaviour.
3. From certainty to managed ambiguity
The project instinct is to reduce ambiguity. The program leader must know when ambiguity is information that has not yet matured.
Early in a transformation, leadership may know the strategic problem and desired future capability without knowing every project required to get there. Forcing premature certainty can lock the program into an architecture that evidence later proves wrong.
The program manager must therefore combine disciplined planning with the ability to keep options open.
4. From technical problem solving to organisational diagnosis
Major programs change systems of work. A technical solution can fail because incentives, roles, culture, process ownership or operating capacity prevent adoption.
Program leaders need enough systems thinking to distinguish a technical defect from an organisational constraint. They must ask which system is producing the resistance rather than assuming resistance is a communication problem.
5. From project leadership to commercial and strategic judgement
Programs can carry substantial capital, supplier and reputation exposure. IBM's practitioner paper emphasises broader program financial management; Pellegrinelli's case work includes commercial awareness and understanding the client's wider business. The program manager therefore needs to understand not only whether work is progressing but whether the economic logic remains sound.
Decision Framework: The Program-Leadership Readiness Test
Before appointing or developing a program manager, assess capability in six dimensions.
| Dimension | Project-level strength | Program-level requirement |
|---|---|---|
| Delivery | Plans, scope, cost, risk | Integrate multiple delivery systems without micromanaging them |
| Strategy | Understand project business case | Interpret changing strategic intent and protect outcome alignment |
| Influence | Lead a defined team | Mobilise executives, functions, suppliers and operations without full authority |
| Context | Manage project stakeholders | Read politics, culture, incentives and external forces |
| Change | Deliver outputs | Shape adoption, operating capability and behavioural transition |
| Judgement | Resolve defined problems | Make decisions with incomplete, conflicting or evolving information |
A candidate does not need perfection in every dimension. But a serious gap should trigger development, additional leadership support or a different appointment decision.
From Strategy to Execution
Immediate action is to change the program-manager job description. If it reads like a project-manager description with larger numbers, the organisation is selecting for the wrong role. Add explicit accountability for integration, benefits, organisational change, stakeholder influence and strategic adaptation.
Medium-term capability building should use experiences that cannot be learned from methodology training alone. Give emerging program leaders exposure to executive decision forums, commercial negotiations, operating-model design, cross-functional conflict and post-delivery benefit reviews. Coaching should address judgement and influence, not only tools.
Long-term strategic positioning means building a separate program-leadership pipeline. Some exceptional project managers will become exceptional program managers. Others may create more enterprise value by remaining technical or delivery specialists. Career progression should not force every strong practitioner toward a role requiring a fundamentally different cognitive and behavioural profile.
Related article: Project Manager Career Paths Are Capability Architecture, Not HR Administration
Signals to Monitor
Watch for program managers who spend most of their time reviewing project schedules, personally resolving issues that should remain with project managers, or demanding more detail when the strategic problem is unclear. Other warning signs include weak relationships with operations, benefits that have no credible owner, repeated escalation because stakeholders will not align, and a program plan that remains stable while the organisation around it changes.
Positive signals look different: project managers retain delivery authority, cross-component conflicts are resolved at the right level, operating leaders are involved before transition, the program can explain how its design has changed in response to evidence, and executives receive decisions rather than aggregated status.
References
- Pellegrinelli, S. 2002, 'Shaping context: the role and challenge for programmes', International Journal of Project Management, vol. 20, pp. 229-233.
- Pellegrinelli, S., Partington, D., Hemingway, C., Mohdzain, Z. & Shah, M. 2007, 'The importance of context in programme management: An empirical review of programme practices', International Journal of Project Management, vol. 25, no. 1, pp. 41-55.
- Hanford, M.F. 2004, 'Program management: Different from project management', IBM developerWorks.
- Bridges, J. 2018, 'Program Manager Responsibilities', ProjectManager.com.
- Harrin, E. 2019, '10 Things Every New Program Manager Should Know', The Balance Careers.
Questions for the Leadership Team
- Are we selecting program managers because they delivered large projects, or because they can lead strategic change?
- Which decisions in our programs require influence rather than formal authority?
- Where are our program leaders still operating at project-detail level because the organisation has not given them the right support?
- Do our development pathways teach commercial judgement, organisational politics and change leadership as deliberately as planning and control?
- Which high-performing project managers would actually create more value by remaining specialist project leaders?
- What evidence tells us that a program manager can tolerate ambiguity without becoming vague or indecisive?
Closing Perspective
The best program manager is not the person who can manage the most project detail. It is the leader who can hold enough detail to understand consequences while staying high enough to integrate strategy, stakeholders, capability and change. The transition from project to program leadership succeeds when the manager stops proving they can control everything and starts creating the conditions in which the whole system can succeed.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.