The Major Project Big Ideas

The $80M overlay

Ep 001 · Grant Stead

The P6 schedule is a time-scaled, detailed estimate that says when each discipline is needed and in what numbers; the committed resource plan is what the purchase orders actually buy: headcount by contractor by day, often leveled flat with no ramp. Both looked right in isolation, but nobody put them on top of each other until a week before execution: the schedule demanded 80 welders and 20 showed up. Overlaying them months early exposes the idle-crew/missing-crew mismatch that cost $80M.

From Grant's BP war story, ~35:00–39:00 · schedule demanded 80 welders; 20 showed up

See it in contextFrom ep 001 · Grant SteadAlso filed under Materials / Resources

The schedule–map handshake

Ep 002 · Jovita Stander

Every green asset on the program (mosque plantings, road segments, parks and wadi parcels) carries a shared location code that lives in both ArcGIS and Primavera P6, with costs attached. That common key makes scope, schedule and money reconcile at street level in either direction: a scope change ripples through both databases, and at handover every tree maps back to GIS.

From the conversation, ~25:28–31:20 · the Friday-mosque scope change is the worked example

See it in contextFrom ep 002 · Jovita StanderAlso filed under Data & AI

Trust, but audit

Ep 005 · Tarun Gohel

The contractor's schedule (finish date constrained, green every month, P10/P50/P90 never offered) and the owner's realistic schedule describe the same project, and a quarterly project-controls audit - a contractual right, exercised with notice - is the bridge that reconciles them. The owner rebuilds reality from deliverable, procurement and quantity registers, matching every deliverable ID to its P6 activity and cross-checking vendor lead-times, before the gap becomes a surprise.

From Chapter 04 (~21:50–30:10)

See it in contextFrom ep 005 · Tarun GohelAlso filed under Governance / Reporting

The dimension stack is an on-ramp, not a ladder

Ep 009 · Omar Habib

The BIM dimension stack (3D geometry, 4D time, 5D cost, 6D sustainability) is usually drawn as a ladder, but real projects set budgets before models exist, so teams enter the stack from either end. The value is not the sequence but the linking: model, schedule and cost feeding one simulation that gives engineers and executives a shared language, with what-if questions answered live in the room.

From the Lego-house explainer (~11:30) and the 5D-before-3D exchange (~15:45–17:00)

See it in contextFrom ep 009 · Omar HabibAlso filed under Cost

The vital four

Ep 013 · Travis Arlitt

Travis's deterministic forecast reduces the whole progress picture to four numbers: a rolling average of the pace the field is actually producing, the pace required to hit the committed date, the compression factor (required divided by actual), and the impact if the end date floats to match real pace. There is no plan variance anywhere in it - just measured pace against demanded pace, and the honest finish date the gap implies.

From the conversation, ~11:10–13:30 · “that’s what we call now the vital four.”

See it in contextFrom ep 013 · Travis ArlittAlso filed under Field / Progress

The bow wave

Ep 013 · Travis Arlitt

Slipped work never disappears - missed early starts, optimistic re-plans, and progress claimed ahead of the field pile up as hidden compression in front of the finish date, invisible to a report that still shows the original plan. Ignored, the bow wave compounds into a two-or-three-x endgame blowout; measured honestly, it becomes an early, cheaper decision.

From the conversation · “if your average pace is less than what’s required, you’re pushing a bow wave” (~12:45); “early starts matter” (~1:17:30).

See it in contextFrom ep 013 · Travis ArlittAlso filed under Field / Progress

From plan variance to forward control

Ep 013 · Travis Arlitt

The episode's central pivot: stop grading the project against a static day-one baseline and start forecasting from what the field is actually producing. Forward redistribution - the Day1Model, where every status state is a fresh day one - turns rear-view variance explanations into forecasts from real pace, decisions made three to nine months earlier, and direct, action-based conversations.

From the conversation · “the plan is now a date and a set of progress that’s required to meet that date” (~12:35); “you’re gaining minimum three months, probably six to nine months, on those key decisions” (~24:40).

See it in contextFrom ep 013 · Travis ArlittAlso filed under Governance / Reporting

Two ways up in project controls

Ep 002 · Jovita Stander

There are two winning career strategies in project controls: go deep as the subject-matter expert everyone calls, or move horizontally across scheduling, risk, cost and commercial, widening the base before each climb. The trap is stepping into the director's hub seat still in love with one discipline: the hub role deliberately trades expertise for a wide view and knowing what to ask.

From the conversation, ~55:08–1:03:30 · including Orion’s orchestra-conductor question

See it in contextFrom ep 002 · Jovita StanderAlso filed under Leadership

The talent gauntlet

Ep 011 · Ahmed AbdelSalam

A project-controls hire only happens when every gate passes at once: the candidate has built this kind of project before, the client will pay the rate, the location or remote arrangement works, and they are authorized to work. Even with every box checked, the market can still take the candidate at the finish line with a better offer, so speed and a compelling career story win, not just rate.

From the talent discussion, ~18:10–23:10

See it in contextFrom ep 011 · Ahmed AbdelSalam

Career growth beats compensation

Ep 011 · Ahmed AbdelSalam

Staffing plans optimize rate against budget, immediate availability and onsite presence, but Ahmed's PhD research found candidates are weighing something else entirely: what happens after the project, whether they will grow, and whether the job is secure. The bridge between the two is a visible career path: the thing that actually retains people through closeout.

From the PhD finding (~1:07) and the closeout-attrition warning (~15:30)

See it in contextFrom ep 011 · Ahmed AbdelSalamAlso filed under Leadership

The remote-work matrix

Ep 012 · Live Panel

The panel never picks a remote-vs-office winner because the answer is a 2x2: what the work is (analysis vs field) crossed with where you are in your career. Experienced analysts can work remote and grab an SME anywhere in the world; field work stays hybrid at best because impacts must be seen contemporaneously. For people starting out, remote is a career risk: out of sight is out of mind, and presence is how judgment and mentorship get built.

From the remote-work chapter · Nosbisch, Darley, Caddell & Bennink

See it in contextFrom ep 012 · Live PanelAlso filed under Field / Progress

The Four Drivers

Ep 015 · Christina Robinson

The next generation has four non-negotiables before it will choose project controls: easier workflows, flexibility, pay, and autonomy. Miss any one quadrant and there is no new workforce to replace the people aging out -- manual data entry reads as a first-week resignation letter, and rigid five-day mandates only work if you're still the only game in town.

From Christina’s answer at ~10:20 and the driver-by-driver walk through ~23:45

See it in contextFrom ep 015 · Christina RobinsonAlso filed under Leadership

The Broken Ladder: a mutual de-risking

Ep 015 · Christina Robinson

Both sides of the employment contract quietly withdrew their long-term commitments: corporations pulled retirement programs, real performance bonuses, and the 5-10-year 'good run,' while workers pulled their long-term time investment, their patience for 'where I sit in 20 years' pitches, and their tolerance for control. The new social contract that bridges the gap is offering something now -- recruiting pitches built on 'later' no longer land.

From the exchange at ~31:30–33:55 · Orion’s de-risking frame, Christina’s moving-goalposts answer

See it in contextFrom ep 015 · Christina RobinsonAlso filed under Leadership

Go to Them First

Ep 015 · Christina Robinson

Christina's leadership playbook for rebuilding the talent pipeline, scaled up from the BP x TSU partnership that recruited her: go to the next generation first through university partnerships, professional organizations, and real conversations at their level. Ask instead of guessing, then run rotational pilot programs, measure, and implement slowly -- carried top-down from the C-suite with the human element first.

From ~27:45–31:00 · and from her own start at ~0:55

See it in contextFrom ep 015 · Christina RobinsonAlso filed under Leadership

Every risk needs a trigger, and an owner

Ep 005 · Tarun Gohel

A risk register only works as a control when each risk carries both a defined trigger (when do we act?) and an assigned mitigation owner (who acts?). With only one of the two, action either arrives after the delay is already fact or is nobody's job; with neither, the register is wallpaper - defined, quantified, reviewed, and never acted on.

Sketched from Tarun’s trigger framework (~17:00–21:30): “Every risk must have a trigger… every mitigation trigger must have a mitigation owner assigned.”

See it in contextFrom ep 005 · Tarun Gohel

Four things you can do about any risk

Ep 010 · Kim Essendrup

Kim teaches the four classic responses to any risk (mitigate, avoid, transfer, accept) through one running example: materials shipped from overseas that might arrive late. Mitigate reduces the probability or the impact (expedite, dual-source, build slack); avoid removes the risk entirely by finding a local supplier; transfer keeps the risk yours but puts responsibility and financial impact on a third party via a fixed-fee contract or insurance; accept means deciding now what you'd do and holding contingency just in case.

From the conversation at ~9:15–10:20 · the same example later flips into an opportunity at ~15:30

See it in contextFrom ep 010 · Kim Essendrup

The RAID log is the run tool

Ep 010 · Kim Essendrup

Risk inputs scattered across the contract/SOW, charter and initiation documents, team risk workshops, and past registers converge into one managed table: the RAID log (Risks, Actions, Issues, Decisions). It is not the plan, the schedule, or the budget; it is the run tool that keeps those plans honest, spots drift when it starts, and lets you course-correct while it's still cheap.

From the conversation at ~6:00–7:45 (sources) and ~16:35–18:30 (the run tool)

See it in contextFrom ep 010 · Kim EssendrupAlso filed under Governance / Reporting

Change one word, change the meeting

Ep 010 · Kim Essendrup

A tactical culture fix Kim credits to Dr. Josh Ramirez: asking "what are the risks?" feels hypothetical and invites the lightning-strike shrug, while asking "what are the obstacles between us and success?" feels tangible and invites a plan. Changing one word turns risk identification into an action-oriented conversation (no PMI certification required) even in organizations without psychological safety.

From the conversation at ~12:50–14:20

See it in contextFrom ep 010 · Kim EssendrupAlso filed under Communication & Stakeholders

Two registers, one project

Ep 016 · Matt Mitchell

Leviathan's risk load was too big for one list, so the team ran two registers with the boundary drawn at FID: a commercial register (gas sales and offtake, geopolitics and markets, pipelines beyond the fence) managed separately above the project, and an execution register (schedule and cost impacts, engineering and delivery risk, what the team can actually mitigate) reviewed monthly with the project. The fix wasn't a bigger list; it was a boundary drawn at what the project team can control, so the overlap can't muddy the water and the team stays pointed at execution.

From the conversation, ~8:20–9:40 · “we just really wanted to focus on project execution.”

See it in contextFrom ep 016 · Matt MitchellAlso filed under Governance / Reporting

The valve test

Ep 016 · Matt Mitchell

Gut likelihoods arrive miscalibrated from both ends of the spectrum: one voice says the valves are extremely high risk and going to fail, another says it'll never happen, and someone wants 12 extra valves ordered just in case. One reframing question (out of 100, how many actually fail?) converts feelings into frequencies before they hit the register: "probably three" gets logged very low, the whole room believes the number, and the fix arrives as a conversation instead of an argument.

From the conversation, ~14:20–15:20 · “it’s about having that conversation and talking them through.”

See it in contextFrom ep 016 · Matt MitchellAlso filed under Communication & Stakeholders

The lessons-learned loop

Ep 016 · Matt Mitchell

Matt's single takeaway, drawn as the cycle it is: lessons learned captured no-blame, old registers closed out rather than deleted, and similar projects' risks all seed the next project's opening register, so it never starts as a blank screen. That register is closed out in its turn and becomes the next lessons file, which means no register is ever really finished, and none should ever start blank: the loop closes on every project.

From the conversation · “a lesson learned is a risk on a future project” (~1:01:40); “change is the mother of all risk” is the loop’s trigger condition (~1:02:30).

See it in contextFrom ep 016 · Matt MitchellAlso filed under Front-End Planning

The three I's

Ep 001 · Grant Stead

A ladder for executive reporting: raw information (estimates, timesheets, quantities) rolls up into insights like 'your PF is a 0.8,' but each rung is worthless to a leader without the one above it. The top rung is interventions: concrete options such as holding $90M by cutting scope versus accepting $100M. Intervention is the only rung that makes money; it is a decision framework, not a chart.

Credited on air (~47:00–52:00) to a mutual friend now at Cenovus Energy

See it in contextFrom ep 001 · Grant SteadAlso filed under Leadership

Basics before the dashboards

Ep 002 · Jovita Stander

Get the boring layer right first: one project calendar, common cutoff dates, sense-checked week-over-week deltas, and a golden thread that lets a monthly report deconstruct cleanly into its weeks. Only then layer on the shiny stuff (PMIS platforms, dashboards, S-curves and AI), because those tools amplify whatever sits beneath them: garbage in, garbage out.

From the conversation, ~45:28–54:00 · “start with the basics… then go for the dashboards”

See it in contextFrom ep 002 · Jovita StanderAlso filed under Data & AI

Project success = PM success + product success

Ep 008 · Akin Oni

The iron triangle (on scope, on schedule, on cost) only measures project management success: the operation was successful. Product success asks whether the patient is alive: value delivered and benefits realized. True project success requires both, the equation at the heart of Akin's 2006 paper that Ed Merrow circulated across IPA.

From the episode, ~45:45–47:30 · and his 2006 paper, circulated by Ed Merrow across IPA

See it in contextFrom ep 008 · Akin OniAlso filed under Reference

The three shapes of a PMO

Ep 011 · Ahmed AbdelSalam

Ahmed sorts PMOs into three types along one axis: how involved the office is and who answers for delivery. Advisory PMOs push reports and templates from outside the work and usually fail; supporting PMOs (his preferred shape) embed cost, schedule, risk and procurement experts alongside a project manager who stays accountable. Controlling PMOs take full accountability as the client's single answerable team, which works only if the leaders have the experience to carry it.

From the PMO chapter, ~34:50–41:00

See it in contextFrom ep 011 · Ahmed AbdelSalamAlso filed under Leadership

The misdiagnosis loop: it’s never just the people

Ep 014 · Ellie Moradinezhad

When integration fails, every faction blames a different single cause (the people, the old system, the procedures) because blaming others is the simplest move. Ellie's ERP case study runs those complaints through real root-cause analysis (interviews, workshops, private conversations, data) and lands on fixing the combination instead: training, procedures, and system configuration together, which gives much better results.

From the ERP case study (~25:30–29:10) and the buy-in discussion (~29:30–33:45)

See it in contextFrom ep 014 · Ellie MoradinezhadAlso filed under Leadership

An approval system and a decision-making system are not the same building

Ep 017 · Iwona Wilson

Two organizations can hold identical stage-gate documentation and be doing completely different things with it. An approval system asks 'can we pass?' through templates, checklists, and deliverable status; a decision-making system asks 'is this a good decision?' by thinking through uncertainty, framing opportunities before they're projects, aligning stakeholders, and challenging assumptions. The span between the two is capability, the thing almost nobody buys, teaches, or measures.

From Iwona’s answer at ~1:33–1:35 · “having a process in place is not the same as having capabilities”

See it in contextFrom ep 017 · Iwona WilsonAlso filed under Careers & Talent

The stage gate becomes a stream

Ep 003 · James Wiseman

Energy's traditional stage-gate model - plan, scope, engineer a 100% design package, then buy and build - was built for certainty, and the current demand wave punishes it. Wiseman's replacement is a continuous 'stream of activities' where the gates blur: engineering is sequenced to keep materials flowing, the operative question becomes 'what can we do - and buy - right now?', and the first-mover prize outweighs a perfectly cost-controlled plan.

From the conversation, ~3:45–12:00 · stage gates, Tesla’s lithium refinery, and the first-mover prize

See it in contextFrom ep 003 · James WisemanAlso filed under Schedule

Flipping the Table: Construction Sets the Sequence

Ep 006 · Geoff Ryan

The old silo model optimized engineering and procurement to their own budgets and schedules, so drawings and materials arrived out of sequence and construction (half of any project's cost) paid the price. AWP flips the table with a path-of-construction workshop ('imagine construction in heaven'): construction names its ideal sequence first and engineering and procurement sequence to match it. In data centers, procurement drives the schedule, so you plan around when the parts arrive.

From the conversation, ~9:10–10:20 and ~35:50

See it in contextFrom ep 006 · Geoff RyanAlso filed under Interface Management

The Exponential Front End

Ep 007 · Roger Farish

Front-end discipline doesn't guarantee a successful project - it multiplies the odds, while skipping steps divides them just as hard. Plotted as a 2x2 of front-end discipline against execution quality, the only quadrant worth aiming for is disciplined front end times strong execution; execution matters, but it can only cash the cheque the front end wrote.

From Roger’s exponential framing (~9:00) and Orion’s cannonball close (~61:10)

See it in contextFrom ep 007 · Roger FarishAlso filed under Risk

Anatomy of a Stage Gate

Ep 007 · Roger Farish

Every FEL stage funnels the same deliverables - scope definition, cost estimate, schedule and risk analysis, project economics - into a gate review built on a checklist, an economic analysis, a request of funds, and a recommendation. The machine is allowed to say no: outcomes are Go, Hold, or Recycle, and exit ramps are the point, not a failure.

From the FEL 101 segment, ~10:30–12:15

See it in contextFrom ep 007 · Roger FarishAlso filed under Governance / Reporting

“Can we?” is the wrong question

Ep 008 · Akin Oni

Feasibility only answers whether a project can be built, and 'yes' is almost always available at a price. The real decision is the evaluation, where courage meets clarity: should we build it now, here, with these assumptions and at this risk, weighing markets, supply chains, regulation, community, talent, geopolitics, and the true cost of capital.

From the episode, ~19:20 · the heart of Megaproject Development & Decision Making

See it in contextFrom ep 008 · Akin OniAlso filed under Portfolio & Capital Strategy

All decisions are equally important. Not all carry the same consequences.

Ep 017 · Iwona Wilson

A 2x2 of the project lifecycle against cost-to-change and organizational attention: attention follows the money, so it arrives in Execute exactly when changing your mind has become near-irreversible. The highest leverage sits in Assess and Concept/Select, where changes are cheapest and nobody is watching, and where options quietly get locked before FID makes the commitment emotional, political, and financial.

From Iwona at ~32:15 and ~33:40 · and the title of her book, Where Projects Are Won or Lost

See it in contextFrom ep 017 · Iwona WilsonAlso filed under Portfolio & Capital Strategy

One source of truth

Ep 004 · Leanne Allgaier

A major project generates documents from every direction (engineering, contractors, vendors and suppliers, regulators, and operations/field changes), and document control is the one function standing between that firehose and the people betting billions, and lives, on the contents. Done right, it delivers the most updated information to the correct audience at any moment, from one agreed-upon single source of truth, protecting cost, schedule, quality, and safety.

From Leanne's definition of document control (~4:05) and the P&ID lifecycle walk-through that follows.

See it in contextFrom ep 004 · Leanne AllgaierAlso filed under Data & AI

The shoe doesn't make the runner

Ep 004 · Leanne Allgaier

Every serious project buys a document platform (Documentum/OpenText, Aconex, PIMS, M-Files, Omega 365, SharePoint), but the tool only supplies the repository, automated workflows, search, and audit trail. Defined lifecycles, version and revision integrity, written-and-trained procedures, and a single source of truth people trust come only from operating discipline. As the episode's metaphor puts it, the shoe doesn't make the runner: the tool is only as good as the discipline of its operators.

From the systems exchange, ~14:50–16:30 · Orion's metaphor, Leanne's operator rule.

See it in contextFrom ep 004 · Leanne AllgaierAlso filed under Governance / Reporting

The four levers of doc-control ROI

Ep 004 · Leanne Allgaier

Treating document control as admin cost is the wrong frame: it directly moves four levers: cost, schedule, quality, and risk/safety. Building from a superseded revision means paying twice for the same work and falling behind schedule, while version control is quality control, ensuring the field builds exactly what engineering last approved. At the extreme, an outdated drawing can lead to equipment failure, injury, or death.

From the ROI segment, ~20:20–21:45.

See it in contextFrom ep 004 · Leanne AllgaierAlso filed under Cost

The noise ladder

Ep 004 · Leanne Allgaier

Document control health is audible: the quieter the project, the healthier the information, and each rung up the ladder is a louder, costlier signal. Level 0 is quiet (information reaches the correct audience with little fuss); Level 1 is 'can't find it' (search, hierarchy, and metadata problems); Level 2 is 'can't reach it' (access misalignment amplified by contractor churn); Level 3 is building from the wrong revision: rework, cost, and schedule pain the project director will notice.

From the good-vs-bad diagnosis, ~26:30–29:40.

See it in contextFrom ep 004 · Leanne AllgaierAlso filed under Governance / Reporting

Culture is cadence

Ep 001 · Grant Stead

On a 4,000-person turnaround, culture is not a value statement: it is the byproduct of planning deep enough that every hand is handed a task, every shift. Line-by-line scope validation, a 70–100k-activity schedule, and an early resource overlay are what let you tell 400 welders exactly where to put their stick on day one. The output is a calm, safe, productive site; incidents live where people don't know what to do.

From the episode, ~7:15–10:30 · the hill Grant dies on

See it in contextFrom ep 001 · Grant SteadAlso filed under Schedule

Right plan × right people = project culture

Ep 003 · James Wiseman

Wiseman's first principles for scaling, drawn as a 2x2: the plan on one axis, the people on the other. Only the right-plan-plus-right-people quadrant produces the project culture that survives the full 'eight seconds' - a good plan can't execute itself, talented people burn down fighting a bad plan, and wrong-plus-wrong means the bull wins.

Sketched from “you have to have the right plan and the right people,” ~4:45–12:00

See it in contextFrom ep 003 · James WisemanAlso filed under Front-End Planning

The bridge from technical expert to industry leader

Ep 012 · Live Panel

All four presidents entered project controls by accident, but none of them became an industry leader by accident. The bridge from the technical base (estimates, schedules, knowing your stuff) to the leadership seat is built from three deliberate planks: credentials in the bank, soft skills that let you influence people, and giving time back through contribution. On the far side, the work shifts from analysis to recommendations, servant leadership and reputation that compounds.

From the next-generation and big-chair chapters · Darley, Nosbisch, Caddell & Bennink

See it in contextFrom ep 012 · Live PanelAlso filed under Careers & Talent

From the lab bench to the giga picture

Ep 014 · Ellie Moradinezhad

Systems thinking is the bridge from the specialist view (your discipline, your deliverable, your slice of the schedule) to the giga picture: functions in interaction, the personalities leading them, and finance, politics, communities, and the environment as forces on the project. It is a mindset before it is a method: openness to contradictory information rather than loyalty to one methodology or one media diet.

From the mentor story (~6:45–8:10) and the closing takeaway (~1:22:40–1:29:00)

See it in contextFrom ep 014 · Ellie MoradinezhadAlso filed under Careers & Talent

When AI multiplies you, and when it makes you a menace

Ep 009 · Omar Habib

Orion's knowledge quadrant, endorsed by Omar: AI's value depends on whether you can verify what it gives you. When you know what you know (or know what you don't know), AI is an accelerant, and every AI win in the episode ends with a verification step. When you don't know what you don't know, there is no basis to check anything and you just become a menace.

Orion’s framework (~1:12:30–1:13:40), agreed by Omar: “You need a certain limit of knowledge”

See it in contextFrom ep 009 · Omar HabibAlso filed under Careers & Talent

AI is the amplifier: humans keep the verdict

Ep 012 · Live Panel

The panel's shared position on AI: it is an enabler that collapses the monthly reporting cycle and mines more project data and benchmarks than any team could, putting live answers 'right in your face.' But the verdict layer stays human: someone who understands the project must still interpret the output, make the recommendation and know which three reports actually matter, with Bennink's caution that over-depended-on models have crashed markets before.

From the AI chapter · Darley's enabler case, Bennink's model-overdependence caution, Nosbisch's answer to worried students

See it in contextFrom ep 012 · Live PanelAlso filed under Governance / Reporting

Five systems, one view of the truth

Ep 021 · Omer Iqbal

Sydney Water's portfolio reporting once lived fragmented across five systems: SAP, Primavera P6, ARM, Unifier and Power BI. Unifying them into one portfolio intelligence view (cost, schedule, risk, benefits) gives Board and Executive Committees a consistent basis for capital prioritisation and risk posture. That integration is the difference between building a dashboard and building executive intelligence.

From Omer's Sydney Water remit, discussed in the tech & data chapter.

See it in contextFrom ep 021 · Omer IqbalAlso filed under Governance / Reporting

The Billion-Dollar Math

Ep 006 · Geoff Ryan

A decade of roughly 70 megaproject audits pairs CII scorecard compliance (45% versus 75%) with tool-time studies in the field, and the measured difference is 22% busier workers. That gap works out to about 10% of total project cost left on the table. Spending roughly $10M applying AWP on a $1B project to chase $100M back is a 1,000% return (figures directional, from Geoff's audits).

From the conversation, ~16:20–18:20 and ~1:10:40

See it in contextFrom ep 006 · Geoff RyanAlso filed under Field / Progress

The fundamentals, in order

Ep 008 · Akin Oni

Boards ask to see the dollars first, but Akin's order runs the other way: understand people, scope, risk, and schedule (in that order), and only then does cost mean anything, because the money makes zero sense without the first four. All of it must sit inside the license to operate; a project without one is a project waiting to be stopped.

From the episode, ~35:30–43:40 · the five fundamentals plus the license to operate

See it in contextFrom ep 008 · Akin OniAlso filed under Front-End Planning

The integrator

Ep 009 · Omar Habib

Engineering and project controls each hold numbers that are calculated correctly yet still disagree, because 'done' means installed on site in one world and committed-and-booked in the other. The bridge is not a tool but an integrator (a person fluent in both languages) backed by a KPI table that gives every metric an owner, a frequency and a data source.

From “sometimes I call myself an integrator” (~53:30), the KPI table (~54:10) and the window-package reconciliation (~55:50)

See it in contextFrom ep 009 · Omar HabibAlso filed under Governance / Reporting

Integration is a grid, not a line

Ep 014 · Ellie Moradinezhad

Ellie's integration framework is a nine-cell grid: integration runs in three directions: vertical (strategy to field), horizontal (function to function), and cross-functional (company to company). Each direction must hold across three domains: systems, procedures, and people. Most teams actively manage only one or two cells, and the neglected ones break quietly until the project suddenly fragments.

From the episode’s core framework (~9:30–20:00 and ~38:00–48:00) and the published episode summary

See it in contextFrom ep 014 · Ellie MoradinezhadAlso filed under Governance / Reporting

Delivered ≠ Successful

Ep 021 · Omer Iqbal

Delivery metrics and investment outcomes are different axes: a project can hit time, cost, scope and quality and still be the wrong thing to have built. The 2x2 maps delivery performance against investment value: the quadrant the episode warns about is “delivered, low value” (on time, on budget, failed investment), while “troubled, high value” is the uncomfortable one executives must still recognise. Only “delivered, high value” (benefits realised, strategy served, public value created) actually counts.

From the episode thesis · “a project can be delivered on time and on budget and still fail as an investment.”

See it in contextFrom ep 021 · Omer IqbalAlso filed under Governance / Reporting

Portfolio management is the missing bridge

Ep 021 · Omer Iqbal

Boards and delivery teams speak different languages: the boardroom talks strategy, risk appetite, benefits, public value and capital prioritisation, while delivery teams talk time, cost, scope, quality, progress and site-level risk. Portfolio management (Omer's Investment PMO) is the missing bridge that spans the two, translating both ways so board intent reaches the work and delivery reality reaches the board.

From the interview script · “portfolio management as a missing bridge between the boardroom and the people delivering the work.”

See it in contextFrom ep 021 · Omer IqbalAlso filed under Board

The contract as an alignment tool

Ep 005 · Tarun Gohel

West Qurna 2 treated its 200-300 pages of project-controls requirements as an alignment tool, not just an enforcement stick: embed the requirements in the contract, explain them to the contractor face to face, and incentivize the behavior you want instead of penalizing. The payoff is one reporting language, with every hub, yard and contractor rolling up to the same WBS structure.

From Chapter 02 (~4:20–13:00) and Orion’s three-levels reframe (~8:30)

See it in contextFrom ep 005 · Tarun GohelAlso filed under Governance / Reporting

The Installation Work Package

Ep 006 · Geoff Ryan

An Installation Work Package is one week of work for one crew, proven executable before the foreman ever sees it. Scope and drawings, materials on site, tools, crane and permits, crew size and budgeted hours, and safety and quality checks all feed the package, with every constraint removed up front. The output is a foreman who can actually execute: don't put out work you can't do; just put out work you can do.

From the conversation, ~5:40–11:20 · plus the risk register in the back of the package

See it in contextFrom ep 006 · Geoff RyanAlso filed under Front-End Planning

The solar 3× rule

Ep 003 · James Wiseman

Solar gives roughly eight productive hours a day against a 24/7 demand curve, so a solar project must produce about three times the energy it needs during daylight and store two-thirds of it just to reach the next day. The panels are the easy part - long-duration storage is the real project, and Wiseman says we've barely scratched the surface on it.

From James’s solar math, ~15:00–17:00

See it in contextFrom ep 003 · James WisemanAlso filed under Sustainability & Environment

What the PDRI Room Reports vs What Probing Reveals

Ep 007 · Roger Farish

A PDRI scope review is only as honest as its facilitation. The room reports deliverables as complete and a score pushed low enough to clear the gate, while probing reveals deliverables never started, gaps living with people outside the task force, and the disengaged discipline nobody thought to ask. Experienced facilitation that hears every voice is the bridge between the two.

From the PDRI stories, ~28:00–35:40 · lower PDRI score = better definition

See it in contextFrom ep 007 · Roger FarishAlso filed under Communication & Stakeholders

Six Dimensions of Decision Quality: the decision quality chain

Ep 017 · Iwona Wilson

Decision quality drawn as a six-link chain: appropriate frame, creative alternatives, relevant information, values and trade-offs, sound logic, and commitment to action. A decision is only as good as its weakest dimension, and commitment to action is flagged as the link that fails most: if the stakeholders who must act are not committed, nothing happens.

See it in contextFrom ep 017 · Iwona WilsonAlso filed under Governance / Reporting

The groan zone is not a facilitation failure

Ep 017 · Iwona Wilson

Divergence (inviting opinions, asking questions, surfacing concerns) necessarily produces a messy middle of disagreement and discomfort that Sam Kaner calls the groan zone. Leaders who bail out of it reschedule the same conversation for months, while teams that push through converge on shared understanding and execute faster with fewer surprises. The tension is not a facilitation failure; it is the cost of alignment.

From Iwona at ~45:50–49:00, citing Sam Kaner’s research on collaborative group decision-making · “this is the cost of alignment”

See it in contextFrom ep 017 · Iwona WilsonAlso filed under Reference