How to Drive Transformative Change with Portfolio Management
About this recording
Dr Al Zeitoun argues that transformative change depends on more than sound projects and well-run processes. In conversation with Stuart Easton, he connects organisational culture, executive ownership, learning and enterprise portfolio management, drawing on engagements where the formal work was completed but the change itself fell short.
Shape culture through the way change is led
Al treats culture as something practitioners can influence, even if they do not control the whole organisation. It matters because culture determines whether their work receives sponsorship and practical support. Al argues that practitioners have responsibility for connecting strategy, culture, leadership and ways of working. The language they use, the behaviour they encourage and the way they involve people all affect whether teams understand the purpose of change and feel able to contribute to it. His ambition is an experience-driven culture that learns through experimentation, adapts quickly and makes room for challenge rather than merely following instructions.
That also changes how methods should be used. Al rejects arguments about whether Agile, waterfall or a particular PMO framework is the universally correct answer. Standards should guide judgement; the approach must fit the organisation and the change. From innovation work at Siemens, he recalls recommendations that looked promising but proved difficult to implement because they demanded a greater appetite for experimentation and risk than the organisation could readily sustain. A method can be attractive on paper without the conditions needed to put it into practice.
Find the real change problem before delivering the brief
Al gives two candid examples of getting this wrong. In a European consulting engagement, his team completed a portfolio assessment and work connected to a shared IT system. The client accepted the deliverables, but a follow-up meeting months later revealed deep dissatisfaction. The organisation had needed help overcoming resistance from influential executives and stakeholders to the intended change, and the consulting team had not addressed it. Delivering the statement of work had not meant delivering what the customer needed.
He recalls an early PMO assignment in a manufacturing business that likewise concentrated on processes, templates and meetings without first establishing what value that business needed the PMO to create. Stuart makes the distinction through his duck-and-egg analogy: the business cares about the value it receives, not the management machinery used to produce it. The practical question is therefore not only whether the requested work was delivered, but whether the underlying organisational problem was understood and changed.
Build executive ownership, not just compliance
Asked how a PMO can win C-suite support, Al distinguishes change that leaders genuinely want from change they feel forced to make. External pressure may trigger action, but he worries that compliance-led change can come late or fail to last. He prefers to help leaders develop and own an inspiring view of the future. In his experience of enterprise change in the UAE, a CEO's commitment to a more project-oriented organisation gave the work a starting point, but difficult organisational boundaries and board-level practices still had to be confronted. In practice, Al advises practitioners to speak to executives about industry growth and returns rather than PMO mechanics, and to build momentum by sharing successes. Change needs continuity beyond the initial mandate.
Al urges practitioners to move from the immediate activity to the wider organisational view, using the image of stepping onto the balcony rather than remaining on the dance floor. He calls for connecting the head, heart and hand: clear strategic thinking, human commitment and the action needed to deliver change. Stuart adds that a case for changing a PMO should begin with the business problems leadership wants solved, not the PMO's preferred methodology or qualifications.
Make the PMO a learning engine
For Al, the future PMO is a learning engine: a function that helps the organisation develop shared language, build capabilities, connect strategy with execution and keep adapting. He sees it as an agent of business change rather than a centre devoted mainly to reporting and administration. He would put that function directly with the executive team; its mission and ability to challenge assumptions matter more than whether it is called a PMO, a strategy office or a value office. His wider point is that learning, leadership and portfolio decisions cannot be treated as separate activities when the organisation is trying to transform.
Connect the North Star to real portfolio choices
Al describes a transformation roadmap built around an inspiring North Star, an honest understanding of the present and initiatives expressed in terms of the value they are intended to create. He questions letting fixed quarterly or six-month planning cycles define the transformation: nearer horizons can contain more specific commitments, while more distant horizons allow greater uncertainty and adjustment. The destination must answer the so what? question rather than merely describe a more mature PMO or a collection of projects.
That purpose has to affect decisions. Al argues for enterprise portfolio management as a capability connecting strategy, investment, shared resources and value across the organisation, not just administering a product or R&D portfolio. He wants discussion elevated from ranking initiatives to the strategic choices and alternative directions available to leadership.
Stuart illustrates the distinction with objectives such as reducing carbon emissions and improving profit: having an objective or key result for each does not determine how scarce resources should be divided between them. Portfolio decisions require an explicit judgement about competing forms of value. Al agrees that good OKRs have a role, but says their quality and connection to the portfolio matter. Stuart adds that value is subjective: executives tend to think in returns and strategic impact, while a local community may care about jobs or a cleaned-up site. Without a structured way to prioritise, groups can fight for the projects that fit their own view, and the loudest voice may win. A sound framework lets leaders compare priorities alongside resources and capacity so they do not overcommit. Stuart cites Michael Hannan's deliberately provocative suggestion to stop half the projects to relieve overload. Al agrees with the need to act but warns that it is easier said than done: it takes courage, empathy and negotiation, not just data.
Keep technology connected to people
Al's human digital thread brings his argument together. Data, AI and digital tools can support faster learning and adaptation, but they operate within relationships that depend on empathy, trust and human judgement. Technology does not, by itself, create the willingness to experiment, the shared understanding of value or the executive commitment needed for transformation. The continuing task is to connect those human conditions with the organisation's changing portfolio choices.
Research in context
Engagement beyond the executive team. Al argues that the way practitioners involve people helps teams understand the purpose of change and feel able to contribute. In McKinsey's 2016 Global Survey, 94% of respondents reporting successful transformations rated the CEO as very or somewhat visibly engaged, compared with 83% of other respondents. The differences were larger for line managers (82% versus 57%) and frontline employees (73% versus 46%). The comparison draws on 1,487 respondents who had participated in a transformation in the preceding five years. These are reported associations, not measures of whether people willingly owned the change.
The PMO as a learning and change function. Al describes the future PMO as a learning engine and an agent of business change, rather than a centre devoted mainly to reporting and administration. In the same 2016 survey, the PMO or transformation-office leader practices most closely linked to reported transformation success were identifying barriers to change and circulating transformation knowledge and best practices. A separate McKinsey survey, fielded in November 2014, found no clear link between simply having a PMO or central transformation team and reported transformation success.
How this connects to TransparentChoice
In the recording, Stuart argues that value is subjective: different stakeholders naturally push for the initiatives that fit their own view, creating a risk that prioritisation becomes a contest won by the loudest voice. TransparentChoice makes those competing judgements explicit, then tests them against what the organisation can actually support.
- See where judgements differ. Each leader can weigh what matters independently, using pairwise comparison, including competing forms of value such as financial return and community impact. Their resulting weightings can be compared side by side, so leaders can see and discuss where they differ before resources are committed.
- Test the choice against real constraints. Available funding, capacity and other material constraints can be represented alongside value so leadership can compare feasible portfolio choices rather than rely on priorities or rankings alone. If priorities, assumptions or constraints change, the portfolio can be recomputed to test whether the previous choice still holds.
TransparentChoice supports the analysis; leadership decides what to fund, continue, change, defer or stop. See how the software works.
Learn more
How can a PMO earn executive support for change?
Laura Barnard and Stuart Easton explore how a PMO can build credibility by addressing the business problems executives care about rather than leading with PMO processes. Laura also describes 90-day delivery cycles with 30-day checkpoints for showing progress, learning and adjusting. Explore Laura Barnard's PMO framework
How do you decide what starts, stops or waits?
Strategic goals help express what matters, but do not settle which initiatives fit available funding and capacity. The project prioritization guide explains how to assess competing work against leadership priorities and constraints, compare feasible portfolio choices and decide what starts, stops or waits. Explore the project prioritization guide
What makes difficult project-stopping decisions defensible?
Sunk costs, sponsor interests and perceived failure can keep work alive even when priorities no longer justify it. Stuart Easton examines how shared priorities, structured comparison and facilitated leadership trade-offs can make stopping decisions easier to explain and support. Read What We've Learned from Weeding Project Portfolios
Speakers in this recording
Al Zeitoun is a global leader in strategy execution and programme management, with expertise in operational excellence, organisational development, and sustainable transformations. A PMI Fellow and trusted strategic advisor, he has supported Fortune 500 companies, government agencies, and global enterprises in delivering complex transformations. He is also an author, keynote speaker, and executive coach recognised for helping organisations achieve lasting impact.
Stuart Easton is Founder & CEO of TransparentChoice. He works with leaders and portfolio teams on decisions about which investments and initiatives to fund, continue, change, defer or stop when priorities compete for limited funding and capacity. His work combines structured decision-making with practical portfolio choices.