Major Project PodcastProjects over $1B
The Major Project Podcast · Episode Brief

Systems Thinking in Megaprojects: How to Fix Broken Integration

Most project failures aren’t one cause: they’re broken integration. Ellie Moradinezhad, President & Founder of tactHive Consulting, on building vertical, horizontal and cross-functional integration across systems, procedures and people.

Ellie Moradinezhad Ellie MoradinezhadGuest · President & Founder, tactHive Consulting
Orion Matthews Orion MatthewsHost · Founder, Queryon
Released Apr 15, 2026 Main episode · 1h 30m Episode 014 Eglinton Crosstown · GO Expansion
Line 5 Eglinton (Eglinton Crosstown LRT), Toronto, 2026 · Transportfan70, Wikimedia Commons · CC BY 4.0 / CC0
Jump in Listen on Apple Podcasts Watch on YouTube Spotify
Share: LinkedIn X
The Conversation

Episode Overview

Most project failures aren’t caused by a single issue: they’re the result of broken integration. Orion Matthews sits down with Ellie Moradinezhad, President and Founder of tactHive Consulting and former Global Discipline Director for Project Management Development at Hatch, to unpack the most misunderstood concept in major project delivery. Ellie brings a practical framework (vertical, horizontal and cross-functional integration, running across systems, procedures and people) and ninety minutes of stories from Canada’s biggest transit programs, global oil and gas, and a PMO that spanned thousands of projects. If you’ve watched a project fall apart despite having the right tools and talent in the room, this episode explains what was actually missing.

90
Minutes on the record
~15k
Words spoken
59
Speaker exchanges
84%
Guest share of the words
The thesis

Projects don’t fail: they fragment

Integration means combining things effectively. Most organizations do the combining and forget the effectiveness, then blame the people when the seams split.

The guest

24 years, three sectors, one lens

Chemical engineer → oil & gas procurement and contracts → Canada’s transit megaprojects → a global PM-development remit at Hatch → founder of tactHive Consulting.

The framework

Three directions × three domains

Vertical, horizontal and cross-functional integration, each running through systems, procedures and people. Nine seams where a megaproject can quietly come apart.

About this brief

Quotes are transcribed from the published episode and lightly condensed for readability: fillers and transcription glitches removed, meaning untouched; timestamps are approximate. The chapter map follows the recorded conversation. Biographical facts come from the episode prep materials, the published show notes, Ellie’s LinkedIn bio, and what she says on the record; she speaks in a personal capacity, and her views are her own, not those of clients or former employers. Numbers cited on air from memory (project counts, contract values, forecasts) are directional. Banner photos: Line 5 Eglinton, Wikimedia Commons · full credits at the end of this page.

As Recorded

Inside the Episode

The conversation as it actually unfolded: eight chapters across 90 minutes, following the show’s four-act arc: intro, topics & projects, advice, wrap-up. The strip maps each chapter’s share of the runtime; timestamps are approximate. Click any block to jump to its chapter.

The line that frames it

“Blaming others is always the simplest way. Blaming ourselves is the most difficult.” · Ellie, on why integration failures get misread as people problems (~24:55)

0:00~9 min01

From Chemistry to the Giga Picture

The welcome, Ellie’s path from chemical engineering to megaprojects, and the factory owner who taught her to see systems.

~8:40~11 min02

What Integration Actually Means

The Cambridge definition, the forgotten word “effective,” systems–people–procedures, and how to sequence the build.

~20:00~18 min03

ROI & the People-Problem Trap

Why prevention doesn’t sell, the ERP case study, resistance, staying curious, and when to apply force.

~38:00~14 min04

Joint Ventures, RACI & One Team

Integrating across companies: common goals, team building, P3 role reversals, RACI as risk management, and co-location.

~51:40~10 min05

PMO at Scale & Measuring Maturity

The Hatch story (thousands of small projects, one platform, one “monster”) and how to measure integration maturity.

~1:01:10~7 min06

AI Meets Integration

An anti-AI industry, what gets automated first, and why agents may beat point-to-point systems integration.

~1:08:10~8 min07

Servant Leadership

The Statoil manager who never wanted thanks, personality types, an executive coach, and the human-level touch.

~1:16:30~14 min08

Advice, tactHive & the Takeaway

Career advice, what tactHive does, and the closing case: systems thinking is a mindset before it’s a method.

Each block links to its chapter below: the map mirrors how the recorded conversation flows.

Who carried the mic

Ellie Moradinezhad · ~12,500 words (guest) Orion Matthews · ~2,400 words (host)

A strongly guest-forward split, measured by words across the full conversation: Orion asks short, pointed questions and Ellie builds full answers.

The Guest

The Guest · Ellie Moradinezhad

Ellie Moradinezhad
Ellie Moradinezhad, BEng, MBA, PMP
President & Founder, tactHive Consulting
Burlington, Ontario, Canada
Systems ThinkingPMO DesignProject GovernanceTransit MegaprojectsChange Management

Ellie started as a chemical engineer with Rudolf Group (Lya Fam Chemie), the German-Iranian industrial firm where she spent six years, got curious about how anyone manages megaprojects “thousands of miles away,” and answered the question with an executive MBA (Industrial Management Institute, 2009–2011) and a move into oil and gas: a procurement role with Statoil (2007–2009), then international contracts with Payahoor and a country-level business-manager role with telecom contractor CSE-Transtel. After moving to Canada, she climbed from project coordinator (IBI Group, 2014) to project director on some of the country’s largest transit programs, including the Eglinton Crosstown LRT and Metrolinx’s GO Expansion (RER OnCorr), with global engineering firms including IBI Group, Hatch and GHD, and returned to Hatch as Global Discipline Director for Project Management Development (2023–2024), the role the episode introduces her by. Since March 2022 she has run tactHive Consulting, a boutique Canadian advisory firm focused on business-driven PMOs, project governance and performance improvement for complex capital programs, and, per her LinkedIn, since April 2026 she has also served as Sr. Commercial Director at Egis in Canada.

“Systems thinking, more than anything else, is a mindset: how to be open to contradictory information, how to review, analyze and absorb the right information rather than being affected by one specific methodology or one specific media.”Ellie Moradinezhad · on the show, ~1:22:50
24+
Years in capital project delivery
4,000+
Projects in the global PMO she led at Hatch
150+
Countries that portfolio delivered into
$15B
The OnCorr job her JV team won after a 2.5-year proposal

Portfolio and contract figures as cited by Ellie on air, from memory: directional, not audited.

Career journey

Engineering, procurement & contracts
Transit megaprojects, PMO & advisory
tactHive Consulting · 2022–
Iran
Canada · Greater Toronto Area
01Rudolf Group (Lya Fam Chemie)Chemical Textile Engineer / Technical Advisor2001–2007
02StatoilProcurement Expert2007–2009
03PayahoorInternational Contract Expert2009–2012
04CSE-TranstelBusiness Manager (country level)2012–2013
05IBI GroupSr. Project Coordinator · transit & power distribution2014–2017 · Toronto
06IBI GroupDesign Project Manager, Eglinton Crosstown LRT2017–2018 · Toronto
07HatchSr. Project Manager2019–2021
08GHDSr. Project Manager2021–2022 · Mississauga
09tactHive ConsultingPresident & Founder2022– · Burlington
10HatchGlobal Discipline Director, PM Development2023–2024 · Mississauga
11Egis in CanadaSr. Commercial Director2026– · Ontario

Roles, employers and dates from Ellie’s LinkedIn bio. The gold bar marks tactHive running concurrently: she founded the firm in March 2022 and has led it alongside the later Hatch and Egis engagements. The Egis role (April 2026–) is from her LinkedIn and isn’t discussed in the episode.

The résumé

Now
tactHive Consulting · President & Founder (March 2022–). Boutique project & program management advisory: PMO establishment and optimization, change management, governance. Since April 2026, also Sr. Commercial Director at Egis in Canada (per her LinkedIn; not discussed on air).
Global remit
Hatch · Global Discipline Director, Project Management Development (2023–2024): rebuilding PM practice across a portfolio of thousands of projects worldwide, after an earlier stint as Sr. Project Manager (2019–2021).
Transit years
Project and program roles with IBI Group (2014–2018, Sr. Project Coordinator → Design Project Manager on the Eglinton Crosstown LRT), Hatch and GHD on Canadian transit megaprojects: Eglinton Crosstown LRT and Metrolinx’s GO Expansion (RER OnCorr).
Early career
Six years as a chemical textile engineer and technical advisor with Rudolf Group (Lya Fam Chemie, 2001–2007); procurement with Statoil (2007–2009); international contracts with Payahoor (2009–2012); country-level business manager with telecom contractor CSE-Transtel (2012–2013).
Credentials
BEng Chemical Engineering (Guilan University) · MBA, EMBA program (Industrial Management Institute, 2009–2011) · Certificate in Business Analysis (University of Toronto, 2014) · PMP · Agile Hybrid Project Pro · Contract & Risk Management in the Built Environment.
Languages
Persian (native) · English (full professional) · French (limited working).

tactHive & finding her

The firm
“A boutique-style project and program management consulting firm”: PMO establishment & optimization, efficiency and quality improvement, gap analysis, change management, and portfolio-level data reliability (her words on air, ~1:20:30).
Signature method
An integration maturity checklist of her own: vertical, horizontal and cross-functional, checked across systems, procedures and people (~1:00:20).
Find her
LinkedIn: /in/ellie-moradinezhad · tact-hive.com (contact form, with a free consultation session offered on air)
The Host

The Host · Orion Matthews

Orion Matthews
Orion Matthews
Founder, Queryon · Host, The Major Project Podcast · PMO data & analytics
Eugene, Oregon, United States
Project Controls ReportingPMO Data AnalyticsCapital PortfoliosAI in ProjectsPower BI

Orion is an award-winning programmer, entrepreneur and technology executive who has spent the last decade in the engine room of major capital projects. He founded Queryon in Washington, D.C. in 2015 with a focus on data analytics and software for the construction industry, starting with bellwether client BP, whose project-controls solutions his team deployed globally, from the North Sea to Azerbaijan to Houston. Today he's a recognized expert in PMO data analytics and project-controls reporting, serving billion-dollar portfolios for owners including BP, Santos, Balfour Beatty and Turner & Townsend, a regular speaker at major industry conferences on AI and analytics in capital projects, and the host of this show.

Why this pairing works

Same seam, two sides
Ellie designs the integration: the governance, procedures and PMOs; Orion builds the data-and-reporting layer where vertical integration lives or dies. Her “project data rolling up to portfolio and business level” is literally his day job.
AI, compared notes
She’s building agent solutions for reporting-level integration; he ships AI in project controls. Chapter 06 is two practitioners trading predictions about whose job changes first.

Beyond the PMO

The builder’s arc
Founded Introspect Software out of high school; built and sold Design-PT (acquired 2015). His software has run from McMurdo Station to aircraft carriers, with write-ups in Scientific American, CNN and Maxim, and a BP Helios Award.
Chapter 01 · Act I · 0:00

From Chemistry to the Giga Picture

Orion opens with the show’s standing frame and a long, earned introduction. Then Ellie tells the origin story: a chemical engineer on small industrial projects who couldn’t stop wondering how anyone delivers the giant ones, and the factory owner whose end-of-day questions taught her to see the whole system before she had a name for it.

“I was always curious: if we are struggling to deliver small projects in the industrial sector, how are they delivering huge megaprojects thousands of miles away? How are they managing big corporates globally? That was the reason I started my MBA.”Ellie Moradinezhad · ~2:20

The mentor at the textile factory

As an intern, the factory’s owner visited the students’ office at the end of each day: what did you do, what did you learn, what’s your plan for tomorrow? His standing advice: don’t stay inside your technical lane. ~6:45

“Pay attention to the giga picture”

“He was inviting us to pay attention to the bigger picture, the giga picture: how the machinery is laid out, the relationships between different functions, finance, procurement, sales, even the personality types he selected to lead each area.” ~7:30

Key moments
  1. The guest intro lands the arc: 24+ years across transportation, infrastructure, energy and industrial; Hatch, GHD, IBI Group; Eglinton Crosstown and GO Expansion (RER OnCorr).~0:35
  2. The MBA as a systems-thinking bootcamp: finance, organizational behavior, negotiations, contracts (“courses we never had as engineers”), studied while working procurement on Statoil-led oil & gas projects.~3:00
  3. The Canada restart: oil and gas hiring was frozen, so she was “accidentally” hired by an engineering consultancy: project coordinator, then project manager, then director-level roles in transit.~4:20
  4. Why Hatch tapped her to reestablish global project management development: a diversified background, “and maybe because of the ideas I had.”~5:15
  5. “Even today, I consider it a platform for my systems thinking”: the internship, decades later.~8:05
Don’t miss The factory story (~6:45–8:10). Everything in the next eighty minutes (functions in interaction, personalities in the right seats, the wider environment) is already in that one anecdote.
Chapter 02 · Act II · ~8:40

What Integration Actually Means

Orion notes that integration usually only comes up in after-action reviews: after it broke. So they start from the definition, and Ellie immediately locates the failure inside the dictionary entry itself: everyone does the combining; almost no one checks the combination is effective. From there she lays out the three domains (systems, people, procedures) and a requirements-driven sequence for building integration deliberately.

“Integration is the action of combining two or more things in an effective way; that’s the Cambridge definition. In reality, we take the combination part and we forget about the effectiveness.”Ellie Moradinezhad · ~9:30

The three elements

Systems, people, procedures, with data and information management as a subcategory of systems. One level of integration is the integration between these three: “If they don’t understand it, they will not follow it. If they don’t find it effective for their specific work, they don’t follow it.” ~11:00

The oversimplification trap

“Human beings manage problems by simplifying them… the problem is sometimes we oversimplify. By oversimplifying, we isolate the systems, the behaviors, the processes, and that causes the bigger issues.” ~12:10

Key moments
  1. Define first, argue later: “Many misunderstandings start from different interpretations of one vocabulary.”~9:10
  2. Borrowing from software: map the functions up front, then build iteratively: you can’t address everything at once.~12:45
  3. The wider environment belongs in the system: communities, future economy, growth, environmental impacts: “we are designing the future.”~13:40
  4. Sequencing, answered like an engineer: interview projects to identify requirements → go vertical (what the portfolio, program and business need to see) → go horizontal (what each function needs and struggles with).~17:00–18:30
  5. Fit the sophistication to the tier: at Hatch, systems designed for major projects were crushing thousands of small ones: “when your budget is small, sophisticated procedures and systems may kill your budget.”~16:00
  6. Cross-functional review (routine in engineering management, rare in PMO and organizational development), and it never ends: “That review and continuous improvement should take forever. The needs are changing, the market is changing, your people are changing.”~19:20
Worth pausing on Orion’s chemistry riff (~14:20): mixing systems, people and procedures like reagents: “how long for the reaction to occur?” Ellie’s answer is the whole requirements cascade that follows.
Chapter 03 · Act II · ~20:00

ROI & the People-Problem Trap

The hardest part of integration work isn’t the design: it’s selling prevention to people who aren’t in pain yet. Ellie is unusually honest here: she names the symptoms that finally make leaders call for help, walks through an ERP failure that everyone had misdiagnosed, and admits the communication mistakes she made in her own corporate years. Then the conversation turns to resistance, curiosity, and when to reach for the hammer.

“I’ll tell you the truth. I made some mistakes myself. I didn’t communicate the ROI and the benefits in a way that could convince my own managers. You need to change your communication language, see the problems from their perspective, find the numbers at pilot level, and share the aggregated numbers gradually.”Ellie Moradinezhad · ~23:20

The ERP that “didn’t work”

A scaling ~2,000-person company bought a highly customizable ERP, then defined WBS impractically, left reporting open to manual manipulation, skipped training, never wrote procedures for their contract models, and deactivated half the system’s capacity. Everyone blamed the software. “When we started to evaluate, the system was good.” ~26:00–28:30

The symptoms that finally sell it

Growth exposes the cracks: inconsistencies, claims and legal escalations, client dissatisfaction, project teams acting as firefighters: “the leaders don’t see reliable data. They know something is wrong; they don’t know what it is.” ~21:30

Key moments
  1. Why prevention doesn’t sell: “It’s like problem solving versus risk management: when the problem is not there, people are not investing in preventative solutions.”~20:40
  2. Orion’s confession: his leadership instinct is to pick one lane (“it’s a people problem”) and launch an initiative; Ellie’s reframe: treat it as an integration issue and root-cause the combination.~24:00
  3. “Blaming others is always the simplest way. Blaming ourselves is the most difficult.”~24:55
  4. The full report lands: leadership “so surprised how much more complex the problem is, they thought, ‘we’ll just change the setup in the system and everything will be fine.’”~29:10
  5. On resistance: “As an engineer I underestimated this in the past and I overestimate it today: a big portion of our decisions are made emotionally rather than logically.”~30:00
  6. The toolkit: engage people from day one, workshops plus confidential private interviews (“that should be part of any contract”), stay curious, connect their reasons to your root causes, and prioritize what they see as the priority.~31:00–33:45
  7. On force: it depends on your role and authority: read the room, adapt mid-presentation, put concerns in writing, and remember “ultimately they are the decision makers.”~34:30–37:30
The consultant’s discipline Her executive coach’s advice, passed on (~32:20): stay curious even when you’re sure you see the problem: “if your client, your team, the leadership don’t see the same problem as you, they will not buy it. They will not spend money on it.”
Chapter 04 · Act II · ~38:00

Joint Ventures, RACI & One Team

Inside one company, integration is hard. In a joint venture, you’re integrating entities whose objectives “may not be aligned at all, except one: delivering the project successfully.” Ellie compares oil-and-gas EPC culture with Ontario’s alliance-model transit programs, explains why the P3 era flipped long-standing roles overnight, and makes the case that a RACI isn’t paperwork: it’s how collaborative models survive contact with pressure.

“On Eglinton Crosstown I was sitting at this desk, my construction team member was sitting next to me, the client was a few floors down. It created an environment where we really didn’t feel we were from different teams; you want to feel that you are one team.”Ellie Moradinezhad · ~50:50

The P3 role reversal

Under design-bid-build, the engineer advises the owner and supervises the contractor: “two sides of one table, literally not that collaborative.” On a P3, the same engineer suddenly becomes the construction team’s subcontractor. Same people, new geometry, real friction, until team building and new leadership shifted the culture. ~40:35

Team building is not a luxury

“In oil and gas EPC we were spending lots of money on team building. On infrastructure joint ventures I see less investment in this area. In my opinion it is essential, essential.” Alliance and progressive models are collaborative by design; if the people aren’t culturally adopting that, “you’ll be in serious problems.” ~39:10

Key moments
  1. Start from the common goal: it may be the only objective the JV partners actually share.~38:30
  2. PMO playbook for collaborative models: understand the contract and delivery model, strategize, engage early: “bring people in and let them be part of that governance creation.”~42:00
  3. System selection as a JV negotiation: capability is only one factor: cost, integration with the owner’s systems and reporting, and how many people can use it without retraining decide the pick. On OnCorr, leadership ran dedicated sessions just to choose the software.~43:20
  4. RACI, taught properly: define the structure, roles and authority levels; decisions escalate by thresholds: PM → steering or alliance committee → client and investors. The decision-maker and the ultimately accountable person are often not the same, and delegation must be explicit.~44:40–46:50
  5. The bottleneck test: on paper the PM reviews every invoice; on a major project that PM becomes the constraint, so responsibilities get delegated deliberately, not by accident.~47:00
  6. Remote vs in-person: a 2.5-year OnCorr proposal ran across Australia, the Middle East, South Africa, the Americas and two Canadian provinces, and won a $15B job. It worked, “but you can do it for a certain time”; by the end (mid-COVID) she was exhausted, and today she wants both modes.~49:20
Don’t miss The RACI segment (~44:15–48:00). Orion asks for the beginner’s version and Ellie delivers a working session: authority thresholds, alliance committees, why the decision-maker and the accountable person are often different people, and how “informed” protects the stakeholders you didn’t realize were impacted.
Chapter 05 · Act II · ~51:40

PMO at Scale & Measuring Maturity

Orion asks for a concrete story, and Ellie delivers the biggest one she has: leading global project management development at Hatch, where the problem wasn’t one megaproject but thousands of small ones: every sector, every contract model, dozens of countries. Her team’s answer, a step-by-step delivery platform, worked, and then created its own new problem. The chapter closes with the honest state of the art in measuring integration maturity.

“You solve some problems, and then it creates new problems. We started to think: OK, who will be responsible to maintain this huge monster now?”Ellie Moradinezhad · ~57:50

The scale of the problem

Over 4,000 small-to-medium projects globally, delivery into 150+ countries, roughly 70 offices, with wildly diversified sectors, sizes, risks and contract models. “You need to start somewhere”: classify projects into tiers, pick the critical segment, and go through the data. ~53:15 (figures as recalled on air; directional)

The platform, not the training budget

The typical PM on these jobs is a technical expert (a bridge engineer with two geotech colleagues) who never asked to run invoicing or risk. Training everyone was unaffordable and unwanted, so the team built a platform: every mandatory and recommended step, template and system training, phase by phase, proposal through closing. ~55:50–57:30

Key moments
  1. “In engineering companies, to be honest, anybody can be a project manager”, and many of them don’t want the PM half of the job: “Why do I have to issue the invoice? Because now you are a project manager in addition to the technical expert.”~56:30
  2. The unsolved ending, admitted openly: maintaining the platform stayed a problem when she left. “These are the real struggles.”~58:00
  3. Maturity models exist (PMI’s OPM3, PRINCE2’s model, P3M3, plus IT- and BIM-aligned checklists), but they mostly grade one area at a time.~59:00
  4. The gap she built her own method for: “Many of these methodologies focus on a specific area; they are not covering the integration: vertical, horizontal and cross-functional, and between systems, procedures and people.”~59:40
  5. The humility clause: “It’s an improving method… I don’t think I know everything. I learn a lot.”~1:00:45
Don’t miss The tiering insight (~53:40–55:30): the fix for thousands of small projects wasn’t scaling the megaproject machinery down: it was admitting a $30k advisory study and a transit program shouldn’t share a process at all.
Chapter 06 · Act II · ~1:01:10

AI Meets Integration

Orion asks where AI intersects the cross-functional space, and the exchange gets genuinely two-sided: Ellie is already building agent solutions with client teams, and Orion is shipping AI into project controls. Her most interesting claim is architectural: that agents may make today’s brutally expensive point-to-point systems integration unnecessary, starting at the reporting layer.

“Integrating these platforms on infrastructure projects is extremely expensive and not cost-effective, and you cannot just integrate on each project, leave it, and jump to another project with new systems. The best thing might be integrating via agent solutions at the reporting level.”Ellie Moradinezhad · ~1:03:40

An anti-AI industry, for real reasons

“Our industry is a little bit anti-AI, which I understand”: rail transit, nuclear and aviation carry heavy confidentiality, IP and security constraints, and clients are reluctant to join the wave. “But like it or not, it will be part of our day-to-day life in managing megaprojects.” ~1:01:20

What changes first

Her call: the pure analytical share of planning and monitoring (project controls mainly) gets absorbed; human judgment, stakeholder management and communication don’t. Scheduling is the hardest, but planning, cost monitoring and estimating are already being attacked by companies she declines to name. ~1:02:30, ~1:05:30

Key moments
  1. She’s in the arena: “I got engaged with a few teams to develop agent solutions for a few small areas and analysis… it needs a lot of fine-tuning.”~1:03:00
  2. Orion’s counterpart thesis, AI as a “decision accelerator”: the Markov simulation is done before the meeting, so the cost engineers and schedulers spend their time on the decision itself.~1:05:15
  3. His prediction, flagged as such: by 2028, 15% of decisions in the construction space made autonomously (cited from memory on air; treat as directional).~1:05:20
  4. Her sleeper pick, risk: “We are extremely underestimating risk management.” Geopolitics moving steel prices, multi-front changes rippling beyond the critical path: “AI can evaluate all the scenarios simultaneously and calculate the probabilities of the outcome much quicker than we could.”~1:06:10
Listen for the convergence Guest and host arrive at the same architecture from opposite directions: she wants agents stitched across systems at the reporting level; he builds the reporting level. Neither thinks the analyst disappears: the 80% grunt share of the job does (~1:05:00–1:07:45).
Chapter 07 · Act II · ~1:08:10

Servant Leadership

Orion pivots to the part of Ellie’s bio he hadn’t introduced: she’s a vocal advocate for servant leadership. Her answer starts with a Statoil-era manager two layers up who redefined the job for her, and lands somewhere unusual for an engineering podcast: personality types, executive coaching, and a story about grief on a joint venture that explains why “the human-level touch” is an integration tool.

“He would say: don’t apologize, and never thank me for the job I’m here to do. I’m here to solve the problems that you alone couldn’t solve, and support you to achieve what you are supposed to achieve.”Ellie Moradinezhad, on her Statoil-era manager · ~1:08:50

The practice, day to day

Grow the team so you can grow; create a safe environment; “be brave to admit my own mistakes, take the blame on behalf of the team, and share the wins with the team, introduce the team as the main winner. No leader alone can deliver anything big.” ~1:10:10

The dreamer and her critics

She’s a self-described big-vision dreamer, so she deliberately staffs detail-oriented reviewers around herself and asks them to be brutal: “I know they are brutal in criticizing work, and that’s how I improve it.” ~1:12:10

Key moments
  1. The humility of the welcome line: that manager and his wife greeted every team member one by one at events, and said goodbye the same way.~1:09:20
  2. Mentorship as future-building: the next generation is “extremely clever, with a different mindset; we are building the future with them and for them.”~1:10:50
  3. The engineer’s conversion: “I was totally against psychology: everything should be two plus two.” A struggle on a major project led her manager to suggest an executive coach; the tests were “very eye-opening.”~1:14:30
  4. What the coaching fixed: an intuitive who jumps to conclusions learning to ask analytical teammates what they observe: “not to assume that whatever I see, everybody else sees.”~1:15:40
  5. The story that stays with you: she lost her father mid-project, and her JV counterpart never acknowledged it: “that human-level touch actually connects us together.”~1:13:30
Worth pausing on Her caveat on personality tests (~1:15:10): useful for self-knowledge, but she stops short of recommending them universally: “sometimes the results can be misused.” A rare both-sides answer in a space full of evangelists.
Chapter 08 · Acts III & IV · ~1:16:30

Advice, tactHive & the Takeaway

The close covers three beats: career advice for the young and the pivoting (including her own unvarnished account of founding a firm), what tactHive actually does, and the takeaway Orion asked for: where to go deeper on systems thinking. Her answer refuses the reading-list format entirely, and it’s the strongest section of the episode.

“Starting a business in Canada is not easy. Consulting at all is not easy. I’m not a hundred percent sure even today if it was the right decision, but I owed it to myself to give it a try. That was my dream for many years.”Ellie Moradinezhad · ~1:17:30

Career advice, compressed

Follow what actually makes you happy; don’t let others define what you’re capable of; rotate through roles the way Hatch’s own CEO did (process engineering, project controls, commissioning); and learn the technical basics of whatever you manage: she took track-geometry and train-control courses as a chemical engineer running transit work. ~1:17:00–1:19:30

What tactHive does

Boutique project & program management consulting: PMO establishment and optimization, efficiency and quality improvement, gap analysis, and change management, “one of the top reasons for project failure,” which she argues starts at bid phase, not during execution. Contact via tact-hive.com; a free consultation session is offered on air. ~1:20:30

Key moments
  1. “Be patient, step by step. Accept more responsibility, be brave, try different things… this life is beautiful, and there are so many things to learn.”~1:19:40
  2. Change management, redefined: not a cost-and-schedule addendum but a lifecycle discipline: “it starts much earlier, from bid phase, proposal preparation and negotiation, and continues to project closing.”~1:20:50
  3. The anti-reading-list: “You can Google and find thousands of reference books. But real systems thinking, more than anything else, is a mindset: be open to contradictory information.”~1:22:40
  4. Widen the aperture: project leaders need finance, economy and politics (“politics is one of the main influencers on these major projects”), plus economic, environmental and social risk, not just project risk.~1:23:40
  5. “We have become very polarized… read totally contradictory opinions. It’s important to hear them, because your client might have the same perspective.”~1:25:40
  6. The gardening masterclass: soil, water, sun, zone, climate shift: a complete systems-mapping tutorial disguised as a hobby, ending at “then we can start to make the right decisions and design the best systems.”~1:28:00
  7. Orion’s synthesis: you don’t have to become the IT expert: take little bites of everyone’s world, “because you can’t think in systems if you can’t see a little bit from other people’s perspective.”~1:26:40
The takeaway in one move Ask her for a book and she hands you a discipline instead (~1:22:40–1:26:00): deliberately consume information you disagree with, weekly. Not because it’s right: because your client believes it, and you need to understand their concern before they’ll buy your fix.
Concepts, Drawn Out

The Big Ideas

Three ideas carry the episode. Sketched here the way a PMO war room would whiteboard them.

1 · Integration is a grid, not a line

Ellie’s framework: integration runs in three directions, and each direction must hold across three domains. Most teams actively manage one or two cells: the rest break quietly until the project “suddenly” fragments.

Systems
Procedures
People
Verticalstrategy ↔ field
SystemsProject data rolls up cleanly: portfolio ROI, resources, revenue projections come from the same source the field uses.
ProceduresStandards proportional to project tier: megaproject machinery doesn’t crush the $30k study.
PeopleLeaders see reliable data; the field understands why it’s collected, or they simply won’t follow.
Horizontalfunction ↔ function
SystemsOne platform serving PM, controls, HR, finance and quality, not a silo tool per function.
ProceduresCross-functional review of each other’s work: routine in engineering, rare in PMO development.
PeopleEvery function interviewed for its needs, constraints and forecasting problems before anything is built.
Cross-functionalcompany ↔ company
SystemsSoftware chosen jointly: on cost, owner integration and team familiarity, not capability alone.
ProceduresRACI with explicit authority thresholds and delegation: who decides, who’s accountable, who’s informed.
PeopleTeam building and co-location until the JV genuinely feels like one team.
From the episode’s core framework (~9:30–20:00 and ~38:00–48:00) and the published episode summary
2 · The misdiagnosis loop: it’s never just the people

When integration fails, every faction blames a different single cause, because blaming others is the simplest move. Ellie’s ERP case study shows what happens when someone finally root-causes the combination instead.

“Wrong people on deck”
“The old system was better”
“The procedures don’t fit us”
Root-cause analysisInterviews · workshops · private conversations · data
Fix the combinationTraining + procedures + system configuration, together: “if you fix three of them, you get much better results.”
From the ERP case study (~25:30–29:10) and the buy-in discussion (~29:30–33:45)
3 · From the lab bench to the giga picture

The mentor’s advice that shaped her career, generalized in the closing takeaway: systems thinking is the bridge between mastering your slice and seeing the whole, and it’s a mindset before it’s a method.

The specialist view
  • Your discipline, your deliverable, your slice of the schedule
  • “I love what I do. Why do I have to issue invoices?”
  • One methodology, one publisher, one media diet
Systems thinking
A mindset before a method
The giga picture
  • Functions in interaction, and the personalities leading them
  • Finance, economy, politics as project influencers
  • Communities, environment, the future you’re designing
From the mentor story (~6:45–8:10) and the closing takeaway (~1:22:40–1:29:00)
Quick Reference

Quote Bank

The best on-the-record lines, gathered in one filterable place. “Highlight” marks the lines most worth scrubbing back for; quotes are lightly condensed and timestamps are approximate.

From Chemistry to the Giga Picture 0:00–8:40

  • Highlight“I was always curious: if we are struggling to deliver small projects in the industrial sector, how are they delivering huge megaprojects thousands of miles away? That was the reason I started my MBA.”Ellie Moradinezhad · ~2:20
  • Highlight“He was inviting us to pay attention to the bigger picture, to the giga picture: the machinery layout, the relationships between different functions, even the personality types he selected for leading each area.”Ellie, on her internship mentor · ~7:30
  • “I don’t think I am different; everybody is unique. Our background, our culture, our family, the way we’ve been educated, that’s how differently we see things.”Ellie Moradinezhad · ~6:00
  • “Even today, I consider it a platform for my systems thinking.”Ellie, on the factory internship · ~8:05

What Integration Actually Means ~8:40–20:00

  • Highlight“Integration is the action of combining two or more things in an effective way; that’s the Cambridge definition. In reality, we take the combination part and we forget about the effectiveness.”Ellie Moradinezhad · ~9:30
  • Highlight“If they don’t understand it, they will not follow it. If they don’t find it effective for their specific work, they don’t follow it.”Ellie, on why people belong in the system design · ~11:00
  • “Human beings manage problems by simplifying them… the problem is sometimes we oversimplify, and by oversimplifying, we isolate the systems, the behaviors, the processes, and that causes the bigger issues.”Ellie Moradinezhad · ~12:10
  • “When we are designing an infrastructure project, what are the effects on the communities, on the future economy, on future growth, on the environment? We are designing the future.”Ellie Moradinezhad · ~13:40
  • “When your budget is small, sophisticated procedures and systems may kill your budget. This is not what you necessarily need to apply.”Ellie, on right-sizing standards · ~16:00
  • Highlight“That review and continuous improvement should take forever. The needs are changing, the market is changing, your projects are changing, your people are changing, so you need to update them continuously.”Ellie Moradinezhad · ~19:20

ROI & the People-Problem Trap ~20:00–38:00

  • “It’s like problem solving versus risk management: when the problem is not there, people are not investing in preventative solutions.”Ellie Moradinezhad · ~20:40
  • Highlight“The leaders don’t see reliable data. They know something is wrong; they don’t know what it is.”Ellie, on the moment clients call · ~21:30
  • Highlight“Blaming others is always the simplest way. Blaming ourselves is the most difficult.”Ellie Moradinezhad · ~24:55
  • “They were blaming the system. When we started to evaluate, the system was good. They had deactivated a lot of its capacity, and there weren’t any formal procedures for the different contractual models.”Ellie, on the ERP case · ~27:45
  • “They were so surprised how much more complex the problem was. They thought: we’ll just change the setup in the system and everything will be fine. Normally, that’s not the case.”Ellie Moradinezhad · ~29:10
  • Highlight“Something I underestimated as an engineer in the past and overestimate today: a big portion of our decisions are being made emotionally rather than logically.”Ellie Moradinezhad · ~30:00
  • Highlight“Stay curious. If your client, your team, the leadership don’t see the same problem as you, they will not buy it. They will not spend money on it. They will not allocate the resources for it.”Ellie Moradinezhad · ~32:20
  • “In more political organizations, people are not interested in sharing their real ideas in workshops. In private, they may share something confidential, so private interviews should be a part of any contract.”Ellie Moradinezhad · ~33:00
  • “Sometimes you need to change your strategy at the moment you’re presenting: you may pass a few slides you worked so hard on, because you don’t observe interest among the audience.”Ellie, on reading the room · ~36:20
  • “Ultimately they are the decision makers; we cannot decide on behalf of our clients. Stay flexible and curious: OK, this is not possible, what else is possible that still addresses the objective?”Ellie Moradinezhad · ~37:15

Joint Ventures, RACI & One Team ~38:00–51:40

  • Highlight“In joint ventures we are dealing with totally different entities, with totally different objectives, which may not be aligned at all, except one: delivering the project successfully. So we start from the common goal.”Ellie Moradinezhad · ~38:30
  • Highlight“In oil and gas EPC we were spending lots of money on team building. On infrastructure joint ventures I see less investment in this area. In my opinion, it is essential, essential.”Ellie Moradinezhad · ~39:10
  • “Alliance and progressive models are extremely collaborative in nature; they should be, in order to succeed. If your people are not culturally adopting that collaborative culture, you’ll be in serious problems.”Ellie Moradinezhad · ~39:40
  • “Under design-bid-build, the engineer supervises the general contractor, two sides of one table. On a P3, all of a sudden the same teams are acting differently: the engineer who advised the owner becomes the subcontractor of the construction team.”Ellie Moradinezhad · ~40:35
  • “Engage early, bring people in and let them be a part of that governance creation.”Ellie, on the PMO’s role in JVs · ~42:00
  • “On paper, project managers should review the costs and invoices. On a major project they cannot review everything; they become a bottleneck. So they delegate their responsibilities, deliberately.”Ellie, teaching RACI · ~47:00
  • Highlight“We worked on the OnCorr proposal for two and a half years. We won the job and it was a $15 billion job.”Ellie Moradinezhad · ~49:20
  • Highlight“On Eglinton Crosstown, my construction team member was sitting next to me and the client was a few floors down. We really didn’t feel we were from different teams; you want to feel that you are one team.”Ellie Moradinezhad · ~50:50

PMO at Scale & Measuring Maturity ~51:40–1:01:10

  • Highlight“We had over 4,000 small-to-medium projects globally… we were delivering projects in over 150 countries, with around 70 offices. It was very difficult to identify one solution to address the needs of everybody.”Ellie, on the Hatch remit (directional figures) · ~53:15
  • “In engineering companies, to be honest, anybody can be a project manager. We couldn’t train everybody: it was becoming extremely expensive, and a lot of them were not interested.”Ellie Moradinezhad · ~56:00
  • “‘Why do I have to issue the invoice? Why do I have to take care of risk?’ Because now you are a project manager in addition to the technical expert.”Ellie Moradinezhad · ~56:45
  • Highlight“You solve some problems, and then it creates new problems. Who will be responsible to maintain this huge monster now?”Ellie, on the PM platform · ~57:50
  • Highlight“PMI has OPM3, PRINCE2 has one, there’s P3M3, but many of these methodologies focus on a specific area. They are not covering the integration: vertical, horizontal and cross-functional.”Ellie Moradinezhad · ~59:00
  • “It’s an improving method; it’s not finalized, and I’m learning from others along the way. I don’t think I know everything.”Ellie, on her own checklist · ~1:00:45

AI Meets Integration ~1:01:10–1:08:10

  • Highlight“Our industry is a little bit anti-AI, which I understand, but like it or not, it will be a part of our day-to-day life in managing megaprojects. And it can create a lot of value.”Ellie Moradinezhad · ~1:01:20
  • “A big part of our planning and even monitoring teams will be replaced, project controls mainly, the pure analytical part. But the way humans interact, decide and analyze is different: stakeholder management, communication.”Ellie Moradinezhad · ~1:02:30
  • Highlight“Integrating these platforms is extremely expensive and not cost-effective… the best thing might be integrating via agent solutions at the reporting level.”Ellie Moradinezhad · ~1:03:40
  • “The prediction is that by 2028, 15% of all decisions will be made autonomously within the construction space… I think of it as a decision accelerator.”Orion Matthews (cited from memory; directional) · ~1:05:20
  • Highlight“We are extremely underestimating risk management… AI can evaluate all the scenarios simultaneously and calculate the probabilities of the outcome much quicker than what we could do in the past.”Ellie Moradinezhad · ~1:06:10

Servant Leadership ~1:08:10–1:16:30

  • Highlight“Don’t apologize, and never thank me for the job I’m here to do. I’m here to solve the problems that you alone couldn’t solve, and support you to achieve what you are supposed to achieve.”Ellie, quoting her Statoil-era manager · ~1:08:50
  • Highlight“Be brave to admit my own mistakes, take the blame on behalf of the team, and share the wins with the team, introduce the team as the main winner. There is no leader who can deliver anything big alone.”Ellie Moradinezhad · ~1:10:10
  • “If I want to grow, my team should grow, and then we can deliver much more complex, more difficult projects successfully, and learn from each other.”Ellie Moradinezhad · ~1:09:50
  • “I’m a dreamer. I like big visions, and a lot of people find them very unrealistic. So I work with detail-oriented team members and ask them to review my work, because I know they are brutal in criticizing it.”Ellie Moradinezhad · ~1:12:10
  • “I lost my father during a project, and my counterpart in our joint venture never said anything… that human-level touch actually connects us together.”Ellie Moradinezhad · ~1:13:30
  • “I was totally against psychology as an engineer: everything should be two plus two. Then I worked with an executive coach, and it was very eye-opening: to understand human beings, to understand our differences.”Ellie Moradinezhad · ~1:14:30
  • “Not to assume that whatever I see, everybody else sees, because they see different things that I don’t see.”Ellie Moradinezhad · ~1:15:40

Advice & the Takeaway ~1:16:30–1:30:00

  • Highlight“Look at what you are interested in and what makes you happy… and don’t let others tell you what you are capable of. Decide for yourself.”Ellie Moradinezhad · ~1:17:00
  • “Starting a business in Canada is not easy. Consulting at all is not easy. I’m not a hundred percent sure even today if it was the right decision, but I owed it to myself to give it a try.”Ellie Moradinezhad · ~1:17:30
  • “Everybody who manages a project needs technical knowledge of that specific area. I didn’t have a civil background. I took track-geometry and train-control courses, because you need the basis to communicate with the team.”Ellie Moradinezhad · ~1:19:00
  • “We are in a rush to go fast, but we need to be patient, step by step. Accept more responsibility, be brave, try different things… this life is beautiful, and there are so many things to learn.”Ellie Moradinezhad · ~1:19:40
  • Highlight“Change management is one of the top reasons for project failure, and it starts much earlier in the project lifecycle: from bid phase, proposal preparation and negotiation, and it continues to project closing.”Ellie Moradinezhad · ~1:20:50
  • Highlight“Systems thinking, more than anything else, is a mindset: how to be open to contradictory information, rather than being affected by one specific methodology or one specific media.”Ellie Moradinezhad · ~1:22:50
  • “Politics is one of the main influencers on these major projects. As project managers we need to understand risk beyond the project level: economic risk, political risk, environmental risk, social risk.”Ellie Moradinezhad · ~1:23:40
  • “We have become very polarized… read totally contradictory opinions. It’s important to hear them, because your client might have the same perspective, and you need to understand that concern.”Ellie Moradinezhad · ~1:25:40
  • “You can’t think in systems if you can’t see a little bit from other people’s perspective.”Orion Matthews, summing it up · ~1:26:40