Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Speaker 1 (00:02):
Welcome to the 4 pm
podcast, where ideas take shape
and strategies find purpose.
I am Mounir Ajam, founder andCEO of Rook Project Management,
and I have a deep-seated passionfor project management and
community development, growingon decades of global experience
(00:24):
across diverse industries androles.
I am here to guide you throughthe transformative power of the
4PMs project program, productand portfolio management and our
focus on business integratedproject management.
Let's explore how integrationunlocks unparalleled value for
you and your organization.
Unparalleled value for you andyour organization.
(00:51):
Good day, welcome back to the4PM Podcast.
I am Munir Ajam, your host.
Thank you for joining me today.
In this episode, we willexplore the realities of leading
mega projects, massiveundertakings that shape
industries, economies andcommunities.
They promise transformativeimpact, but also carry outsized
risks.
Let's dive into the hard truths, bold lessons and the path to
(01:22):
excellence.
Introduction Mega projects arethe titans of the project world.
They are massive undertakingsthat push the boundaries of
engineering, management andhuman collaboration.
They promise transformativeimpact, but they also carry
(01:44):
outsized risks, with budgetsoften exceeding $1 billion and
timelines stretching acrossyears, these projects are not
just technical challenges, butorganizational systems.
This episode explores therealities of leading
megaprojects drawing on twomajor case studies.
Let us call them the USAProject EUP and the Asian
(02:07):
Project AP.
These projects, similar inscope and ambition, diverge
sharply in execution andoutcomes.
Their stories offer amasterclass in what works, what
fails and what leader must dodifferently Understanding
(02:39):
megaprojects, scale, complexityand consequence.
Megaprojects are defined notjust by their size but by their
complexity.
They involve multiplestakeholders with competing
interests, high levels ofuncertainty and risk, long
timelines with shiftingpolitical, economic and
environmental contexts,interdisciplinary coordination
across engineering, procurement,construction and operations.
(03:03):
Both UP and AP were greenfieldfacilities valued at around $2
billion in today's money.
They were executed as jointventures and part of larger
programs.
Despite these similarities,their outcomes were dramatically
different, offering a rareopportunity to dissect the
(03:24):
anatomy of success and failure.
Comparing the foundation doesstructure versus execution.
While UP and AP shared manystructural elements, their
execution strategies diverged.
(03:45):
The USA project UP and Asianproject AP began with similar
ambition but very differentsetups.
Up used a fixed-pricecontracting model with a single
general contractor on an inlandsite managed by a small and
inexperienced client team.
By contrast, ap adopted areimbursable cost-plus model
(04:08):
with multiple contracts, wasbuilt on a reclaimed island with
greater logistical challenges,and was led by an extensive,
integrated and experienced team.
These contrasts shaped riskmanagement, collaboration and,
ultimately, project success,showing that execution maturity,
(04:29):
more than structure, made thedifference.
The USA Project a case study inavoidable failure.
The UP started with a promisebut quickly unraveled.
The issues were not isolated,they were systemic One
(04:51):
undersized and underpreparedTeam.
The client's project managementteam was critically small, just
seven people during engineering.
Project controls were mobilizedlate, at 35% engineering
completion, leaving the teamwithout visibility into cost or
(05:12):
schedule performance.
This lack of early oversightcreated blind spots that would
prove costly.
Two scope volatility and poorchange management.
Major scope changes, includingthe addition of a cogeneration
plant and the removal of anentire process unit, were
(05:34):
introduced after the start ofengineering.
These changes were not wellintegrated into the planning
process, leading to confusion,rework and delays.
3.
Contractor silos and lack oftransparency.
The contractor operated infunctional silos, withholding
(05:54):
critical information.
For example, valvemanufacturing delays were hidden
until they became urgent.
Schedule updates weremanipulated rather than
naturally integrated.
The fixed price modeldiscouraged open communication,
incentivizing the contractor toprotect margins rather than
(06:15):
solve problems collaboratively.
4.
Cultural and organizationalgaps the project suffered from
low project management maturity.
There were no effective earlywarning systems and the team
operated reactively.
Recovery planning became arecurring ritual with temporary
(06:38):
fixes masking deeper issues thefallout.
The consequences were severe,you know 110% over budget,
nine-month delay with a massiveopportunity cost, painful claims
and strained relationships.
Ironically, the same contractorwas awarded a follow-up project
(06:58):
, highlighting a troublingpattern in how organizations
evaluate performance andaccountability.
The Asian project a model ofstrategic excellence.
In contrast, the APdemonstrated how thoughtful
(07:21):
planning, stakeholder alignmentand schedule aligned interest
Team lived together, fosteringrelationship that transcended
contractual boundaries.
This intimacy enabled fasterdecision-making and
(07:51):
problem-solving.
Two best practices embeddedEarly.
The AP team conducted extensiveconstructability reviews,
modularization studies andpre-project planning.
Safety was prioritized from dayone and the project achieved an
excellent safety performance.
These practices weren't justcheckboxes.
(08:15):
They were embedded into theculture and practiced daily by
the management team.
Into the culture and practiceddaily by the management team.
Third, stakeholder engagementand transparency.
Plan managers were involvedfrom the start.
Monthly reports and quarterlyreviews ensured transparency.
(08:35):
The client, contractor andoperation team were aligned in
vision and execution.
Four robust change management,a two-step approval process and
a dedicated change control boardhelped manage scope evolution.
Changes were evaluatedholistically, ensuring they
(09:03):
didn't derail progress.
Months delay, which isconsidered minimal for a project
with this size and complexity.
Epcm contractor earned fullincentives and was awarded a
replicate project.
The AP wasn't just a success.
It was a blueprint for how megaprojects should be led.
(09:30):
Organizational competence, thehidden driver of success.
The divergent outcome of UP andAP reveal a deeper truth.
Project success is oftendetermined long before execution
begins.
Organizational competence,especially project management
maturity, is the hidden driver.
(09:50):
Pm maturity matters.
Studies from the University ofCalifornia, berkeley Independent
Project Analysis and othersshow a direct correlation
between PM maturity andcost-slash-schedule performance.
(10:11):
Ap benefited from a maturesystem with integrated processes
.
Up did not and paid the price.
Front-end planning is crucial.
Most overruns occur later, butdue to factors from the early
stages.
Without formal projectmanagement scope, clarity
suffers, leading to cascadingissues.
(10:32):
Organizations oftenunderestimate the importance of
front-end loading, treating itas a formality rather than a
strategic imperative.
Culture versus system.
In the absence of effectivesystems, culture takes over.
Unfortunately, this often meansblame games, poor leadership,
(10:52):
fragmented teams.
Reactive decision-makingsystems create clarity,
accountability and resilience.
Culture alone cannot compensatefor their absence.
The cycle of doom a pattern ofdysfunction.
(11:14):
A recurring theme in troubledmegaprojects is the cycle of
doom.
Number one delays occur.
Number two root causes aremisunderstood.
Number three recovery planningis initiated.
Number four temporary progressis made.
Number four temporary progressis made.
Number five the cycle repeats.
(11:34):
This pattern reflects deeperorganizational flaws, such as
over-dependence on outsourcing,declining technical capacity,
lack of integration betweenbusiness, technical and project
teams.
Breaking this cycle requiresmore than tactical fixes.
It demands strategictransformation, a call to action
(12:03):
, reclaiming project leadership.
To lead megaprojectssuccessfully or, for that matter
, all types of projects,organizations must 1.
Rebuild competence and capacity.
Invest in internal capabilities.
Train project leaders.
Build multidisciplinary teamsthat understand both technical
(12:26):
and business dimensions.
Technical and businessdimension.
Two treat project as strategicassets.
Projects are not isolatedevents.
They are part of assetmanagement.
Integrate project thinking intolong-term business strategy.
Three adopt and integrate bestpractices.
Don't just benchmark.
(12:47):
Embed best practices into theproject lifecycle.
Use stage gate method to ensureclarity and control.
Four reduce over-reliance onPMCs.
Pmcs can add value, but theyshould not replace internal
leadership.
Reclaim ownership of projectstrategy, execution and
(13:15):
accountability.
Final thoughts Disrupting thestatus quo.
Mega projects succeed notthrough structure alone, but
through leadership, competenceand collaboration.
The lesson is clearOrganization must move beyond
old pattern and lead withmaturity and accountability.
Excellence is possible, butonly if we disrobe the status
(13:38):
quo.
If this episode helped shiftyour perspective, I invite you
to subscribe, leave a review andshare it with your teams.
For more episodes, tools andtemplates, visit urukpmcom or
(14:00):
connect with me directly onLinkedIn.
This is Munir Ajam for the 4PMPodcast.
Until next time, keep learning,keep leading and always deliver
with purpose.