As organisations take on more change, they create roles above and around project management: program managers to coordinate related projects, portfolio managers to choose and balance investments, project management offices to support and oversee delivery, and strategic procurement managers to bring in external capability. These roles are often filled by promoting the most successful project manager, or created by renaming an existing function. Sometimes that works. Often it produces a larger version of the old job, while the new questions the role exists to answer go unasked.
The difference matters because each role works on a different kind of decision. A project manager protects an agreed objective. A program manager integrates several projects and the business changes needed to produce benefits. A portfolio manager keeps testing whether the set of investments still fits strategy and capacity, and recommends what to stop. A strategic project management office improves the information and capability that leaders use to steer. A strategic procurement manager connects market capability, project needs, governance and commercial reality. Staffing these roles well means understanding those differences.
This article explains what distinguishes each role, the common mistakes organisations make when creating and filling them, how they fit together, and how to assess and develop the people in them. It is general information for executives, managers and professionals in larger businesses and public organisations, with notes on how smaller businesses can apply the same ideas.
Projects, programs and portfolios
- A project is a temporary effort to deliver a defined output, such as a new system, facility or product, within agreed scope, time and cost.
- A program is a group of related projects and change activities managed together to achieve outcomes and benefits that the projects could not achieve separately, such as a business transformation.
- A portfolio is the collection of programs, projects and other work an organisation invests in, managed to achieve strategic objectives within limited capacity and funds.
These are different decision systems. Project management asks how to deliver what has been authorised. Program management asks how to coordinate interdependent work and organisational change to produce benefits. Portfolio management asks what should be authorised, prioritised, paused or stopped.
The program manager
The promotion from project manager to program manager is not simply a bigger span of control. It is a change in what must be noticed, judged and influenced. Program managers still need delivery credibility, but they spend more time on:
- Strategic intent and whether the program is still aimed at the right outcomes.
- Interdependencies between projects, and negotiating changes to plans across them.
- Business change: the new processes, roles and behaviours without which outputs produce no benefits.
- Stakeholders and politics: many people whose cooperation is needed are not under the program manager’s authority.
- Benefits: working with the business owners who must change how they work to realise value.
Research by Sergio Pellegrinelli and colleagues found that where programs bridge projects and organisational strategy, program management takes on the character of strategic change management and organisational development, and that real programs are politically influenced and continually adapted.
Common mistakes:
- Treating program management as senior project management, promoting on schedule control and technical delivery alone.
- Solving uncertainty with more detail. Some program uncertainty comes from strategy, markets and stakeholder interests and cannot be planned away. Excessive detail creates an illusion of control.
- Relying on hierarchy. Program managers rarely control everyone whose behaviour matters, so influence is essential.
- Treating politics as failure. In significant change, competing interests are normal and must be worked with openly.
- Taking over struggling projects instead of fixing the conditions that made them struggle.
Benefits depend on the people who must use the outputs. The sponsors who can stop the work and owners who must make it pay article covers the sponsor and benefit owner roles that program managers rely on.
The portfolio manager
Portfolio management operates one level above authorised investments. The portfolio manager asks:
- Does the portfolio still reflect strategy?
- Which initiatives compete for the same people, money or attention?
- Where is risk concentrated?
- Which initiatives should be accelerated, paused, merged or stopped?
- How should executives respond when priorities conflict?
A project manager protects an authorised objective. A portfolio manager continually tests the set of authorised objectives. That requires strategic judgement, analytical skill, and the standing to challenge powerful sponsors.
Research by Mark Young and Kieran Conboy on an Australian performance-based competency standard for project portfolio management treated the portfolio manager as a distinct role, defining competence by what practitioners must be able to do rather than what they know.
Common mistakes:
- Promoting the best project controller and expecting the role to scale naturally.
- Making the portfolio manager a reporting coordinator, collecting data without converting it into options and recommendations.
- Giving accountability for balance without influence over resources, while business units can start work and move people freely.
- Expecting neutrality without executive sponsorship. Portfolio decisions create winners and losers, and the role needs legitimacy to make them stick.
- Equating framework knowledge with competence.
The project management office
Project management offices take many forms: support offices that help project teams with planning and reporting, program offices that serve a single program, enterprise offices that oversee the whole portfolio, and centres of excellence that develop methods and people.
Organisations often rename their office as “strategic” or “enterprise” and move its reporting line closer to the executive. Nothing changes if it still spends most of its effort collecting status, policing templates and reporting activity. A project management office becomes strategic only when it improves enterprise decisions and capability. A useful test covers four areas:
| Area | Question |
|---|---|
| Investment intelligence | Does it help leaders judge whether initiatives remain aligned, valuable and feasible? |
| Execution intelligence | Does it identify forward-looking risks, dependencies and exceptions that need intervention? |
| Enterprise coordination | Does it expose resource conflicts, sequencing problems and cross-functional effects? |
| Organisational capability | Does it improve skills, methods, learning and leadership for delivering change? |
Common mistakes include expanding the mandate without expanding capability, equating strategy with reporting, and making the office accountable for business change that operating leaders still control. The office should enable and inform; business leaders remain accountable for change in their areas. Processes should be proportionate: the standardise the routine, not the thinking article covers how much process is enough.
The strategic procurement manager
Procurement is often seen as purchasing: obtaining quotes, running tenders, signing contracts and chasing orders. At a strategic level, the procurement manager is an integrator of external capability, connecting five systems:
- Governance: policies, delegations, probity, compliance and defensible decisions.
- Market: supplier capability, competition, capacity, pricing and trends.
- Project: scope, schedule, dependencies, technical requirements and benefits.
- Contract: obligations, risk allocation, performance, changes and claims.
- Relationship: communication, negotiation, trust, escalation and supplier development.
Weakness in any one undermines the others. Governance without commercial judgement produces process without value. Negotiation skill cannot rescue an unclear requirement or the wrong contract model. Procurement engaged only after scope and delivery strategy are fixed is being used transactionally; its strategic value appears earlier, when market capability, packaging and sourcing options can still shape the project. Procurement leaders do not need to be the deepest technical experts, but they need enough understanding to ask good questions and know when specialist advice is required.
How the roles fit together
| Decision | Usually decided by | Supported by |
|---|---|---|
| Which investments to start, continue or stop | Executive or portfolio board | Portfolio manager, project management office |
| Program outcomes, scope and benefits | Program sponsor | Program manager, benefit owners |
| Project delivery within agreed scope | Project manager, within delegations | Project team, project management office |
| Sourcing strategy and contract model | Project or program leadership with procurement | Strategic procurement manager |
| Methods, standards and capability | Executive owner of delivery capability | Project management office |
Clear decision rights prevent the roles from duplicating or undermining each other. The decision rights before meetings article explains how to make them explicit.
Assessing and developing people for these roles
Competence in these roles shows in what people do, not just in their certificates. Useful questions when selecting or developing people include:
- Program roles: can the person describe a time they changed a plan across several projects through negotiation rather than authority? How did they secure business change and benefits?
- Portfolio roles: has the person recommended stopping or reshaping significant work, with analysis that persuaded senior leaders?
- Project management office roles: can the person turn data into forward-looking insight that changed a decision?
- Procurement roles: has the person shaped a sourcing strategy early enough to influence the project, and managed a supplier relationship through difficulty?
Development paths should include supervised exposure to these decisions, coaching from experienced practitioners, and deliberate practice in influence, commercial judgement and strategic thinking. Recognised frameworks and qualifications help but do not replace demonstrated performance.
Signs each role is working
Simple observable signs show whether the roles are adding value:
- Program management: business owners can explain the changes they are making and the benefits they expect, and cross-project conflicts are resolved before they become delays.
- Portfolio management: work is regularly stopped, paused or reshaped, and the reasons are recorded; scarce specialists are not split across too many initiatives.
- Project management office: executives use its information to make decisions they would not otherwise have made, and project teams find its methods helpful rather than burdensome.
- Strategic procurement: sourcing strategies are set before scope is fixed, competition is genuine, and supplier problems are raised early.
If these signs are absent, look first at mandate, authority and capability before blaming the people in the roles.
In smaller businesses
Smaller businesses rarely have separate portfolio managers or project offices. The same people wear several hats: the owner acts as the portfolio board, a senior manager coordinates related projects, and someone handles purchasing. The ideas still apply. Keep the questions separate: regularly ask which work should continue or stop, who is coordinating related changes and benefits, what information leaders need, and how external suppliers are being chosen and managed.
A worked example
This is an illustrative example. An engineering services business with about 150 staff runs around 40 initiatives at once, including client-funded projects, a new business system and several internal improvements. Its most successful project manager is promoted to head a renamed “strategic project office”. Within a year, reporting has grown, but resource conflicts persist, nothing is stopped and the business system project is late, with users resisting the new processes.
Diagnosis. The executive team reviews the roles. The office is collecting more status reports but rarely gives forward-looking advice. Nobody is responsible for recommending which work to stop. The business system is run as a technical project, with no one leading the process and role changes it requires. Procurement is engaged only to issue purchase orders after suppliers are chosen.
Changes.
- A monthly portfolio review is introduced, with the head of the office acting as portfolio manager and expected to recommend what to stop or reshape.
- The office’s reporting is simplified to forward-looking exceptions, resource conflicts and decisions needed.
- The business system becomes a program, with a program manager focused on process change, training and benefits, working with named benefit owners in each department.
- The procurement lead joins major initiatives at concept stage to shape sourcing and contract models.
- Decision rights for each role are written down and shared.
Result. Within six months, nine initiatives are stopped or merged, freeing key engineers for the most valuable work. Time spent preparing status reports falls by about half. Adoption of the business system improves as departments take ownership of their process changes.
Applying this in an Australian organisation
- Define each role by the decisions it serves, not by seniority.
- Promote on demonstrated capability for the new role, not success in the old one.
- Give portfolio managers sponsorship and influence over resources.
- Test the project management office on the decisions and capability it improves.
- Engage procurement early in significant initiatives.
- Write down decision rights across the roles.
- Develop people through exposure and coaching, not just courses.
- In small businesses, separate the questions even when one person asks them.
Where these roles go wrong
- Promoting the best project manager into a role needing different skills.
- Renaming the office without changing what it does.
- Portfolio managers who report but never recommend stopping work.
- Program managers who manage detail instead of change and benefits.
- Procurement engaged only to process orders.
- Unclear decision rights between roles.
- Certificates treated as proof of competence.
Questions for leaders
- What decisions does each of these roles exist to improve?
- When did our portfolio process last stop something significant?
- Does our project office change decisions, or just report on them?
- Who leads the business change in our major programs?
- When does procurement first see a significant initiative?
- How do we assess people for these roles?
Bringing it together
Program, portfolio, project office and strategic procurement roles each answer different questions. Program managers integrate projects and business change to produce benefits. Portfolio managers keep testing which investments deserve the organisation’s limited capacity and recommend what to stop. Project management offices become strategic only by improving decisions and capability. Strategic procurement managers connect markets, projects, governance, contracts and relationships, and add most value early. Define roles by the decisions they serve, give them the authority and sponsorship they need, staff them on demonstrated capability and make decision rights clear. The result is an organisation that chooses its work well and delivers it.
Source: KEVOS editorial notes, drawing on earlier KEVOS corporate articles on program management, portfolio management, strategic project management offices and strategic procurement roles. Research referred to includes work by Sergio Pellegrinelli and colleagues on program management and by Mark Young and Kieran Conboy on an Australian competency standard for project portfolio management. The worked example is illustrative.
