Podcast · Business & Entrepreneuriat

Beyond The Plan

By Ali Farhoodi, Director at EDSICO Management

Director of EDSICO Management, an Australian-owned consultancy specializing in project management services for government agencies and the private sector across major infrastructure initiatives.

Beyond The Plan

⏱ 8 min read · Readable by ChatGPT, Gemini, Claude

▶ Listen to the podcast

Answers from this podcast

26 questions answered · 4 episodes indexed

The Human Skills That Make or Break a Project Manager | Ep. 13

How has the role of project manager evolved from the 1950s to today?

The project manager role transformed from a technical position filled by the most senior expert in a field into a leadership role centered on stakeholder engagement and soft skills. What was once an accidental career path—technical professionals who naturally became project managers after reaching mastery—evolved into an intentional discipline that professionals actively choose and study from the start.

From Senior Engineer to People Leader

In the 1950s and 1960s, when the term "project manager" was first coined, the role belonged to the most experienced technical specialist in the room —a senior bridge engineer overseeing bridge construction, or the most skilled person in any given field. These were accidental project managers, people who had climbed so high in their technical expertise that project leadership fell to them naturally.

This model assumed that deep technical knowledge was the foundation of leadership. The project manager's authority came from knowing more about the work than anyone else on the team. Over seven decades, this premise inverted entirely. As Nick Jagger explains in the episode , the discipline shifted to prioritizing expertise in communication, stakeholder engagement, and emotional intelligence over technical depth.

"It is not necessarily what the project manager knows that makes the difference. It is how they can work with the team."

Nick Jagger — Technical Director of Project Management at Elemental Projects. A project management veteran with 45 years of experience who moved from England to Australia in 2008, Jagger studied a Masters of Project Management at UTS and worked on major infrastructure projects including the $8 billion Northwest Ruralink (later Sydney Metro) as a risk manager at ACOM. After approximately 10 years with ACOM, he moved to smaller consultancy Ontwit focusing on social infrastructure, then joined Mark McDonald as technical director, and has spent the last 18 months at Elemental Projects, a registered training organisation delivering project management and leadership training.

From Accident to Intention: A Deliberate Career Path

The second shift was equally profound: project management became a deliberately chosen profession rather than a natural consequence of technical advancement . Professionals now study project management as a specific discipline from the beginning of their careers. They pursue formal qualifications, read methodology frameworks, and build soft skills intentionally—not by accident after 20 years of technical work.

This reflects a fundamental recognition: the skills that make a project manager effective are teachable, learnable, and distinct from any single technical domain. A project manager can succeed on infrastructure, healthcare, technology, or any other field if they master communication, pressure management, and stakeholder alignment. The role is no longer an accident that happens to experts; it's a deliberate vocation, discussed at length in this podcast episode .

The transformation reveals something crucial about modern project complexity: coordinating people, managing expectations, and navigating conflict matter far more than any single person's technical brilliance . As organizations grew, projects became more interdisciplinary, and stakeholders more numerous, the old model broke down. The best engineer could not lead a team of diverse specialists by technical authority alone.

What is the core difference between managing under pressure and leading under pressure in project management?

Managing under pressure means you are handling your own performance adequately, but leading under pressure means you are actively helping your team navigate difficult phases as well. As a project manager, staying calm and providing clarity and direction to your team remains essential even when facing severe financial, time, personnel, or third-party pressures.

The distinction matters because many project managers conflate coping with crisis with actually leading their team through it. You might be meeting your own deadlines and maintaining your composure, yet if your team is confused, demoralised, or left without clear direction, you're only managing yourself—not leading.

Nick Jagger, whose 45 years of project management experience spans major infrastructure projects including work as a risk manager on the $8 billion Northwest Ruralink (later Sydney Metro), emphasises that this shift from managing to leading is fundamental. The technical aspects of the role—schedules, budgets, scope—pale in comparison to how you hold the space for your people during crisis.

Real leadership under pressure involves communicating with transparency . Your team needs to understand what constraints exist, what options remain on the table, and what you expect from them. Without that clarity, pressure cascades downward as anxiety rather than focus.

"It is not necessarily what the project manager knows that makes the difference. It is how they can work with the team."

Nick Jagger — Technical Director of Project Management, Elemental Projects. A project management veteran with 45 years of experience, Jagger studied a Masters of Project Management at UTS and worked on major infrastructure projects including the Northwest Ruralink as a risk manager. After approximately 10 years with risk management firm ACOM, he moved to smaller consultancy Ontwit focusing on social infrastructure, then to Mark McDonald as technical director, before joining Elemental Projects 18 months ago.

The emotional labour of this distinction is significant. As explored in this episode , managing pressure is a solo task; leading under pressure requires you to monitor how your team is absorbing the stress, stepping in to reset expectations when needed, and sometimes simply reassuring people that the situation, however difficult, is being stewarded responsibly.

This is why experience alone is not the strongest predictor of successful project delivery. A project manager with ten years of technical know-how but who isolates during crisis will fail to hold the team together. Conversely, a less experienced manager who focuses on keeping people aligned and motivated can often navigate pressure more effectively.

The pressure itself doesn't change—financial constraints, tight timelines, and competing stakeholder demands are real. What changes is your approach: are you surviving the pressure, or are you helping your team survive it together? That pivot from personal management to collective leadership is what separates the project managers who retain their teams from those who watch talented people leave during crisis.

Why This Matters in Practice

When a team senses that their project manager is merely holding on—barely coping, reactive, or worse, deflecting blame—morale collapses. People start protecting themselves rather than collaborating on solutions. Productivity drops, mistakes multiply, and the crisis deepens.

Leading under pressure reverses this pattern. When your team sees you present, thoughtful, and focused on helping them succeed within the constraints, they stay engaged. Jagger discusses how genuine culture—not just a launch event but sustained, authentic support—becomes the bedrock of how teams perform when everything is on the line.

The people skill of managing conflict and encouraging healthy dialogue becomes indispensable. Under pressure, tensions surface. If your team trusts you to handle disagreement fairly and to keep the conversation focused on solving the problem rather than blaming individuals, they will bring their concerns to you early. That transparency gives you a chance to course-correct before small issues become catastrophic.

Your Project Didn't Fail. Your Governance Did. | Ep. 14

How does poor governance experience transfer across organizations and impact future project outcomes?

Negative governance experiences are transferable across time and organizations —when people move to a new organization years after a poor experience, they carry that baggage with them. En masse, these bad experiences create a self-fulfilling prophecy around governance, embedding organizational reputations so deeply in culture that they persist regardless of what executives actually say or do.

How negative experiences become organizational identity

The damage doesn't reset when someone changes roles or companies. A person who experienced poor governance at one organization brings those scars forward, already skeptical and defensive before they even begin. Organizations develop reputations around governance that stick like mud , not because they lack good intentions, but because reputation is built on visible, lived behavior—not on aspirational messaging.

This is where the gap between language and action becomes critical. Executives can declare that governance has improved, that systems have changed, and that decision-making is now fit for purpose. But as Isabel Gray-Garraway discusses in the episode , the real signal is what people actually experience when they work through those governance structures day to day.

Culture embeds past failures into future projects

Once a governance failure happens—especially one visible across an entire organization or sector—that perception becomes embedded in organizational culture. New projects inherit that skepticism. Team members approach governance processes already expecting them to fail or obstruct, making it harder to rebuild trust even when structures genuinely improve.

The Australian government's RoboDebt program offers a stark example of how this ripples forward. Six years after the program ended in 2019 , the reputational damage from that governance failure—which cost close to $2 billion in refunds, compensation, and class action settlements—continues to influence how agencies approach new initiatives. A Royal Commission was held in 2023 specifically to examine what went wrong, cementing the memory of the failure in institutional culture.

"Governance is the structure and systems that ensure the right people make the right decisions at the right time about project and delivery risk."

Isabel Gray-Garraway — Director of ICT Corporate Portfolio at Fire and Rescue NSW. With 25 years of project delivery experience spanning defence, government, and public-private hybrid organisations, Gray-Garraway spent 17 years in government roles where she learned the relationship between risk, accountability, and governance. She led a 100-person team managing a $200 million rolling program at Transport for New South Wales focused on road safety and regulation transformation, and has worked extensively in audit, risk, security, architecture, and enterprise governance across multiple sectors.

Understanding this mechanism is essential: if you want to break the cycle of poor governance perception, you can't do it with statements or policies alone. You have to change the actual lived experience of governance. This is why this conversation goes deep into how organizations can rebuild trust through concrete governance structures rather than just fixing messaging.

Negative governance experiences travel with people across organizations and years, shaping how they approach new roles and projects.

Organizational reputations around governance are built on lived experience and behavior, not on what leaders say or policy documents claim.

Poor governance creates a self-fulfilling prophecy where teams approach processes with defensiveness and skepticism, making recovery harder.

Reputational damage from governance failures persists for years (as seen with RoboDebt, which still affects Australian public sector credibility six years after completion).

Why does good governance often have a poor reputation while bad governance is highly memorable?

Good governance is invisible because it works seamlessly —processes flow together, decisions are made, project teams feel supported, and it becomes business as usual. Bad governance is unforgettable because people remember negative experiences far longer than positive ones, creating a self-fulfilling prophecy where poor governance shapes organizational culture for years to come.

The Visibility Gap: Why Success Goes Unnoticed

When governance functions properly, no one talks about it. Teams receive clear decision-making authority, risk is managed transparently, and stakeholders know who decides what and when. The system becomes so routine that its effectiveness disappears into the background. This invisibility is actually governance working as intended —it enables delivery rather than impeding it.

In contrast, as Isabel Gray-Garraway explains in the episode , bad governance creates friction that people actively notice and discuss. Steering committees produce zero decisions. Project teams guess their way forward. Accountability vanishes. These experiences stick in organizational memory far more powerfully than smooth delivery ever does.

The Storytelling Problem: Offices as Gossip Networks

In office environments, people don't gather to celebrate when governance works. They compete to share worst-governance stories with colleagues, reinforcing a shared narrative of dysfunction. One person recalls a project where unclear authority delayed decisions for months. Another describes a steering committee that never actually decided anything. These anecdotes spread, shaping how new employees and incoming leaders perceive governance long before they experience it firsthand.

This creates a feedback loop: bad governance experiences carry forward to future projects and organizations, shaping negative expectations around governance itself. The reputation compounds even as specific circumstances change.

"Governance is the structure and systems that ensure the right people make the right decisions at the right time about project and delivery risk."

Isabel Gray-Garraway — Director of ICT Corporate Portfolio at Fire and Rescue NSW, with 25 years of project delivery experience spanning defence, government, and public-private hybrid organisations. She led a 100-person team managing a $200 million rolling program at Transport for New South Wales and has spent her career learning how governance directly determines whether projects deliver outcomes or fail.

The reputational damage of poor governance persists far longer than the incidents that caused it. As discussed at length in this podcast , the Australian government's RoboDebt program illustrates this: six years after the program completed in 2019, reputational damage around governance failures remained strong enough to warrant a Royal Commission review in 2023. The $2 billion in refunds and compensation became shorthand for governance gone wrong, defining how organizations subsequently approached risk and decision-making.

Recognizing this pattern is the first step toward change. Good governance doesn't need theatrical celebration—it needs explicit acknowledgment that it's working and why. When project teams understand that clear authority structures, transparent risk conversations, and timely decisions are the backbone of successful delivery, governance stops being invisible and becomes recognized as strategic infrastructure.

The challenge is cultural: shifting from a default narrative of dysfunction to one where good governance is acknowledged as the foundation of reliable outcomes. This requires leadership that actively talks about governance as enablement, not burden, and creates space for positive governance stories to compete with the negative ones that naturally dominate office conversation.

What financial and reputational consequences has the Australian government faced as a result of RoboDebt's governance failures?

The Australian government spent close to $2 billion on refunds, repayments, reimbursements, and compensation stemming from RoboDebt's failures. Beyond the direct financial cost, the program's reputational damage persists six years after its conclusion, with RoboDebt now referenced in mainstream media whenever new government initiatives are announced.

RoboDebt (2015–2019) represents not merely a failed program, but the most significant failure in public administration in modern Australian history . The scale of the financial consequence—nearly $2 billion in direct payouts—reflects the depth of governance breakdown that allowed the system to operate unchecked.

As Isabel Gray-Garraway explains in the episode , governance failures of this magnitude don't resolve quickly. Three years after RoboDebt ended, a Royal Commission was formally convened in 2023 to investigate how such a systematic failure had occurred and persisted within government systems.

A failure that rewrote Australian governance history

The reputational wound runs deeper than typical program failures. RoboDebt has become shorthand for government overreach without accountability —a reference point invoked in media coverage and public discourse whenever authorities propose new digital systems or automated decision-making processes. The program's legacy is one of institutional mistrust.

This lasting damage matters beyond optics. When a government program becomes synonymous with administrative failure, it affects public confidence in future government initiatives. The fact that RoboDebt remains a mainstream media reference six years later—and counting—demonstrates that the consequences of poor governance extend well beyond the program's closure , influencing policy acceptance and public trust in subsequent announcements.

Isabel Gray-Garraway — Director of ICT Corporate Portfolio at Fire and Rescue NSW. With 25 years in project delivery across defence, government, and public-private sectors, Gray-Garraway has spent 17 years in government roles where she developed deep expertise in risk, accountability, and governance structures. She previously led a 100-person team managing a $200 million rolling program at Transport for New South Wales focused on road safety and regulation transformation.

The political and institutional response also underscores the severity: a Royal Commission inquiry three years after program closure is not routine oversight—it reflects the magnitude of the governance breach. The episode explores how governance failures of this scale reshape public sector accountability frameworks , with RoboDebt now taught as a cautionary case in Australian public administration.

How does the RoboDebt program exemplify governance failure in public sector delivery?

RoboDebt (2015–2019) failed because no single executive held accountability for decision-making, despite governance structures being in place. Risk registers went unreviewed, frontline staff warnings about incorrect calculations were ignored, and legal concerns were never escalated to senior decision-makers—the machinery of governance existed, but nobody actually used it.

The RoboDebt story reveals a crucial distinction: governance failure is not the same as the absence of governance structures. The Australian government had all the formal frameworks in place—committees, risk registers, audit trails, oversight bodies. What was missing was the will to enforce them .

Multiple agencies and ministers shared responsibility, which meant nobody felt fully accountable. When a steering committee meets but produces zero decisions, as Isabel Gray-Garraway explains in the podcast , the project team fills the void with guesswork and pushes forward unsupervised. That's exactly what happened: the RoboDebt team operated in a decision-making vacuum, making critical choices without proper executive sign-off.

Frontline staff—the people closest to the data and the harm being caused—raised alarms about incorrect numbers and traumatized citizens. These escalations never reached the top. Risk signals were systematically ignored , not because they were hidden, but because nobody with real power was listening.

When governance theatre masks absence of accountability

The RoboDebt failure cost the Australian government close to $2 billion in refunds, repayments, reimbursements, and compensation . A Royal Commission wasn't held until 2023, three years after the program ended. Six years later, the reputational damage persists.

This is the signature of governance failure: the infrastructure looks solid on paper, but nobody is making the hard calls. Legal teams worried about the program's legality, but their concerns weren't escalated. Risk registers existed, but weren't reviewed. Audit processes happened, but findings were deprioritized. The governance machinery ran in neutral.

What made RoboDebt instructive is that it wasn't a technology problem—the systems worked fine technically. It wasn't a data problem; the algorithms did what they were told. As discussed in this episode , the program failed because the people at the top never took ownership of the risk trade-offs, never insisted on evidence before scaling up, and never listened to the voices warning them from the floor.

"Governance is the structure and systems that ensure the right people make the right decisions at the right time about project and delivery risk."

Isabel Gray-Garraway — Director of ICT Corporate Portfolio at Fire and Rescue NSW. With 25 years in project delivery spanning defence, government, and public-private hybrid organisations, she brings deep expertise in accountability, risk management, and enterprise governance. She previously managed a $200 million rolling program at Transport for New South Wales, leading a 100-person team focused on road safety regulation transformation. Her foundation in defence sector governance taught her the inseparable link between risk, accountability, and delivery outcomes.

The RoboDebt Royal Commission found that the governance structures existed but were never actually invoked to manage escalations, challenge assumptions, or halt an obviously broken process —a pattern that repeats across failed public programs when accountability is distributed too widely.

You Can Predict Delivery Failure Before It Happens | Ep. 16

How should governance frameworks evolve once established to remain fit-for-purpose?

Governance frameworks must be living documents with continuous review and adjustment , not static structures. As market conditions shift, organizational context evolves, and risks emerge, frameworks require consistent monitoring and deep dives into problems early—before issues cascade into catastrophic failures like those in RoboDebt and Queensland Health.

The Governance Framework as an Active, Evolving System

Fit-for-purpose governance is not a set-and-forget model. Frameworks must reflect the actual risk environment and operational reality of the organization, adapting as circumstances change. When Isabel Grae Garaway discusses governance in this episode , she emphasizes that governance should enable decision-making at the right time—and that enablement must evolve as the organization and its challenges evolve.

The core principle is simple: governance should scale proportionally to risk , not remain static regardless of changing conditions. A framework designed for stable conditions may become ineffective when markets shift or organizational complexity increases. Equally, governance that was adequate five years ago may no longer suit the organization's current operating environment.

Early Detection and Intervention: The Cost of Delay

One of the starkest lessons from governance failures is that early intervention saves catastrophe. When risks are raised within a framework, they should trigger investigation and response immediately, not be deferred or ignored. The absence of this mechanism—where risks surface but no action follows—creates the conditions for collapse.

As explored in the Beyond The Plan episode , deep dives should be commissioned as soon as concerning signals appear, preventing the slow escalation that turns manageable problems into organizational crises . The failures seen in programs like RoboDebt and Queensland Health were not sudden; they were the result of risks ignored across months or years, compounded by governance structures that failed to demand action.

"Governance always precede delivery failure. You can tell a project that's going to fail before it's even started."

Isabel Grae Garaway — Governance Expert. Garaway began her career in defence, where she developed deep expertise in robust governance frameworks and risk management across large-scale infrastructure and complex programs. She specializes in fit-for-purpose governance structures that enable organizations to detect and prevent project delivery failures before they occur.

The governance review process itself must be continuous and reflexive , not an annual checkbox. As a point explored in detail in the podcast , organizations that treat governance as an active conversation—challenging processes, asking what could improve, and adjusting without fear—create resilience. Those that treat it as a static rulebook risk being blindsided by changing circumstances.

Governance frameworks must adapt as market conditions, organizational context, and risk profiles change—static frameworks become unfit over time.

Risk-based scaling means governance intensity should match actual risk exposure, not remain constant regardless of circumstances.

Early intervention on emerging risks prevents escalation into catastrophic failures; frameworks must demand investigation and response when signals appear.

Continuous review and self-reflection enable governance to remain fit-for-purpose; governance should be actively challenged and refined, not treated as static rules.

What role does independent challenge play in effective governance frameworks?

Independent external challenge prevents the "fox watching the henhouse" dynamic by removing internal pressure to suppress risks. External experts force accountable leaders to respond to independent review findings , creating a healthy tension that encourages early identification and resolution of problems rather than concealment.

When governance relies solely on internal assurance, decision-makers face an inherent conflict of interest: those most accountable for results are also those evaluating whether risks exist. This dynamic often leads to risk suppression rather than risk management. Independent external challenge breaks this cycle by introducing an impartial perspective that cannot be influenced by internal politics or performance pressure.

The power of independent challenge lies in its structural inevitability . External reviewers answer to different stakeholders and operate under different incentives than internal teams. This means accountability leaders cannot dismiss or ignore findings as easily as they might dismiss internal concerns. The tension created—where external findings demand response and cannot be silenced—actually improves governance rather than hindering it.

As detailed in this episode of Beyond The Plan , this principle has been embedded in major infrastructure frameworks. The New South Wales Investor Assurance Framework, created in 2012, relies heavily on independent expert challenge as a core governance control. Projects at different risk tiers —from quarter-million-dollar programs to $200 million initiatives—all require proportionate external review to ensure risks surface before failure becomes inevitable.

"Governance always precede delivery failure. You can tell a project that's going to fail before it's even started."

Isabel Grae Garaway — Governance Expert. Garaway began her career in defence, where she developed deep expertise in robust governance frameworks and risk management across large-scale infrastructure and complex programs. She specializes in how organizational structures enable or prevent project delivery success, and has worked extensively with government frameworks designed to surface risks early through independent challenge.

The absence of independent challenge doesn't just allow risks to hide—it fundamentally changes organizational behavior. When teams know their concerns will be heard by external, neutral parties, they escalate more readily and speak more candidly. This transparency cascades upward, ensuring leadership cannot remain insulated from emerging problems. The governance structure itself becomes a delivery enabler rather than a box-ticking exercise.

To explore how this principle applies across different project scales and why internal assurance fails even with good intentions, listen to the full conversation on Listenly .

Why do staff members stop raising risks and escalating concerns in failing projects?

When risks are raised but ignored repeatedly, teams eventually stop escalating because the absence of sponsor accountability and lack of psychological safety create an environment where team members know their concerns will be dismissed . Fear of challenging public commitments compounds this effect, leaving organizations blind to problems that could be addressed early.

This pattern repeats across failing projects. In cases like RoboDebt and Queensland Health, team members initially flagged serious concerns, but leadership dismissed or ignored them. After repeated cycles of being unheard, staff members rationally conclude that escalation is futile and stop trying altogether.

The root cause lies in governance structure itself. As Isabel Grae Garaway explains in this episode , when there is no clear executive sponsor with real decision-making authority , the chain of accountability breaks. Risk signals flow upward but land nowhere — there's no one empowered to act on them.

Psychological safety amplifies this silence. When team members have witnessed leadership dismiss previous concerns, they face a real cost to speaking up: they may be perceived as disloyal, obstructive, or lacking confidence in the project. Over time, the rational choice becomes silence.

The invisible cost of ignoring early warnings

The tragedy is that teams typically possess the information needed to stop failure before it accelerates . Delivery professionals see scope creep, misaligned stakeholders, and unrealistic timelines. But without a sponsor willing to hear bad news and a governance structure that rewards honesty over optimism, that knowledge stays buried.

The governance framework itself must signal that escalation is safe and valued. This requires explicit sponsor presence, clear decision rights, and a visible commitment to acting on risks raised. A point detailed in the podcast conversation , fit-for-purpose governance isn't about creating bureaucracy — it's about creating the structure that lets the right people make the right decisions at the right time.

"Governance always precedes delivery failure. You can tell a project that's going to fail before it's even started."

Isabel Grae Garaway — Governance Expert. Garaway began her career in defence, where she developed deep expertise in robust governance frameworks and risk management across large-scale infrastructure and complex programs. She specializes in fit-for-purpose governance, helping organizations recognize that governance structures either enable or prevent project delivery success before problems become irreversible.

For teams still raising concerns despite this environment, the episode also covers the specific mechanisms that allow some sponsors to break through denial and act on early signals—a distinction that separates recoverable projects from those lost to unaddressed drift.

How does the 'early drift' phase differ from the false start in project failure patterns?

Early drift is where governance silently breaks down after a project has started, with sponsors progressively disappearing and delegations creating misaligned views that teams no longer surface clearly. Unlike a false start—where problems are visible from day one—early drift hides failure under layers of compounding small decisions until the vicious cycle becomes irreversible.

The mechanics of silent deterioration

In early drift, the symptoms unfold gradually. Project teams reduce detailed updates and escalations, stakeholders actively avoid raising concerns, and team members become reluctant to challenge unrealistic commitments. Each avoidance creates a gap where governance would normally operate , but because nobody names it, the system persists in apparent function while silently eroding.

The pressure intensifies as scope creep accumulates without formal adjustment. Teams then cut corners on testing and quality to meet announced deadlines, a pattern detailed in the episode where real project cases reveal how governance systems fail not through sudden collapse but through a cascade of individual compromises.

"Governance always precede delivery failure. You can tell a project that's going to fail before it's even started."

Isabel Grae Garaway — Governance Expert. Garaway began her career in defence, where she developed deep expertise in robust governance frameworks and risk management across large-scale infrastructure and complex programs. She is recognized as a thought leader on fit-for-purpose governance, specializing in how organizational structures enable or prevent project delivery success.

Why early drift is harder to catch than false start

A false start is immediate and visible: scope is unsigned, budgets are unapproved, expectations clash openly. Early drift hides because the project appears to move forward—reports are filed, work is done, deadlines are tracked. The problem is not absence of activity but absence of alignment within that activity .

Sponsors who become absent are not literally gone; they are mentally checked out, delegating without clarity. Governance does not fail spectacularly; it fails through small omissions—one skipped meeting, one unescalated risk, one corner cut, then another. By the time the pattern is visible, the recovery window has closed, as Isabel Grae Garaway explains in detail in the podcast .

What is the 'false start' phase in the progression toward governance and delivery failure?

The false start occurs at project beginning when scope documents remain unsigned while work has already started , budgets await approval, governance meetings are cancelled or postponed, and sponsor representatives lack decision rights. This creates a dangerous gap where projects are moving forward without the structural foundation needed to succeed.

Starting work before you're ready

The false start phase is a predictable pattern that emerges when organizational pressure to show progress overrides the discipline of proper setup. Work launches despite unfinished governance basics—scope hasn't been formally signed off by stakeholders, but teams are already mobilizing. Budgets remain in approval limbo. Most critically, decision-making authority fractures when sponsors send delegates to governance meetings who cannot commit to decisions or lack continuity across sessions.

This fragmentation guarantees failure. As Isabel Grae Garaway explains in the episode , the hiatus between starting work and completing governance setup is where projects lose control. Teams operate without clear authority above them, stakeholders remain unaligned, and scope shifts become inevitable.

Why the false start dooms delivery

Absent sponsors or sponsors who delegate without decision rights leave projects orphaned at precisely the moment accountability is most critical. When governance meetings are postponed or cancelled, the project enters a vacuum where nobody is actively managing risk or settling scope disputes. The combination creates conditions for compounding failures—scope creep, budget overruns, and stakeholder misalignment that could have been prevented with proper setup.

The false start is not accidental. It's a systemic problem rooted in the gap between what governance should accomplish—enabling the right decision-making at the right time—and what organizations actually do when they rush. You can hear more specifics about how to recognize and avoid this trap in the full episode , where Garaway walks through real examples of false starts across infrastructure and government programs.

"Governance always precede delivery failure. You can tell a project that's going to fail before it's even started."

Isabel Grae Garaway — Governance Expert. Garaway began her career in defence, where she developed deep expertise in robust governance frameworks and risk management across large-scale infrastructure and complex programs. She specializes in fit-for-purpose governance—the principle that organizational structures should match project risk, not bureaucratic habit—and how that alignment prevents delivery disasters.

The false start phase is one of several predictable stages that signal incoming delivery failure. The episode explores how pre-project red flags and governance breakdowns cascade into the operational failures that ultimately derail projects—some costing hundreds of millions of dollars.

False start occurs when project work begins before scope is formally signed off and governance structures are in place.

Cancelled or postponed governance meetings combined with absent sponsors create an accountability vacuum that guarantees failure.

Delegates attending governance meetings without decision rights cannot move projects forward or settle scope disputes.

This predictable phase signals delivery failure well before operational problems emerge, making it identifiable and preventable.

What are the pre-project red flags that indicate delivery failure is likely?

Governance failures precede project delivery failure , and the warning signs appear before work even starts. Unclear sponsorship with no executive accountability, contested or unclear scope, a weak business case, unsecured budget, and lack of organizational change readiness are all red flags that predict failure is already predetermined.

The clearest signal comes from unclear sponsor accountability . Without a named executive who owns the outcome and bears responsibility for success, governance breaks down immediately. This isn't about having a sponsor on paper—it's about a person with real authority, real skin in the game, and real consequences for failure.

When scope remains contested or undefined, teams are already operating in chaos. Nobody knows what success looks like, boundaries shift constantly, and decisions get made reactively instead of deliberately. This ambiguity invites mission creep and ensures that stakeholders will pull in different directions from day one.

A business case that fails to articulate intended benefits is particularly dangerous. Projects driven by what Isabel Grae Garaway calls "Stars in Eyes" or vanity projects—where sponsor enthusiasm replaces rigorous reasoning—are almost guaranteed to deliver disappointment. The business case must answer why this project exists and what concrete outcome it will produce.

Unsecured or contested budget creates constant friction. When money is promised but not locked in, or when stakeholders argue over resources before work starts, the project enters delivery with a fundamental credibility problem. Teams cannot operate effectively when funding is unstable.

Organizational change readiness is often overlooked but critical. If the organization cannot absorb the change that a project is meant to create, then delivery success becomes technically possible but organizationally impossible. As discussed in this episode , governance structures must account for resistance at all levels, not just process resistance but cultural inertia as well.

"Governance always precede delivery failure. You can tell a project that's going to fail before it's even started."

Isabel Grae Garaway — Governance Expert. Grae Garaway began her career in defence, where she developed deep expertise in robust governance frameworks and risk management across large-scale infrastructure and complex programs. She is recognized as a thought leader on fit-for-purpose governance, specializing in how organizational structures enable or prevent project delivery success.

The deeper insight—one that separates experienced delivery leaders from those still learning—is that governance is not scary or bureaucratic . It's a way of enabling delivery, not hindering it. Poor governance often masquerades as risk management when it's actually just compliance theater. Real governance answers a single question: do the right people have the right information to make the right decision at the right time?

None of these red flags require a project to proceed. Each one is an opportunity to stop, reassess, and either fix the root cause or cancel the initiative altogether. Waiting until work has started to discover these problems is far more expensive than addressing them in the planning phase.

What makes the New South Wales Investor Assurance Framework considered best-in-class governance practice?

The NSW Investor Assurance Framework, established in 2012, is built on risk-based assurance rather than budget-based governance , meaning scrutiny and reporting intensity are matched to project complexity and value, not simply applied uniformly. It combines independent external expert challenge, clear executive accountability, transparent government reporting, and a four-tier risk classification system that determines which projects receive intensive oversight and when concerns can escalate early.

How risk-based assessment shapes the framework

The framework's core innovation is its risk tiering system that categorizes all infrastructure projects into four levels . Each tier is determined by evaluating project value, complexity, delivery model, risk profile, agency capabilities, and market conditions—not simply budget alone. This means a $200 million infrastructure program and a smaller capital project each receive governance proportionate to their actual risk exposure, avoiding both over-governance and under-governance.

As discussed in the Beyond The Plan episode , this approach eliminates the common mistake of treating all projects as if they require the same governance intensity. Projects in lower risk tiers require less frequent reporting and less intensive scrutiny, while high-risk, high-complexity programs receive the detailed oversight they genuinely need . The framework ensures that governance effort is directed where it adds real value.

Independent challenge and early escalation

A second defining feature is the presence of independent external experts embedded in the assurance process . These experts provide objective challenge to project teams and sponsors, questioning assumptions and identifying risks that internal teams might normalize or overlook. This isn't adversarial—it's a structured mechanism to surface issues early, before they become critical delivery threats.

The framework also enables early escalation pathways , meaning governance problems or delivery risks identified at tier 2 or 3 can be flagged to senior government leadership without delay. This prevents situations where warning signs are ignored until a project reaches crisis point. Isabel Grae Garaway emphasizes in this podcast that governance is fundamentally about enabling the right decisions at the right time—and early escalation is how that actually happens in practice.

"Governance always precede delivery failure. You can tell a project that's going to fail before it's even started."

Isabel Grae Garaway — Governance Expert. With a career rooted in defence sector projects, Garaway developed deep expertise in governance frameworks and risk management across large-scale infrastructure programs. She is recognized as a thought leader on fit-for-purpose governance, specializing in how organizational structures enable or prevent project delivery success.

The NSW framework operationalizes this insight: clear executive sponsorship and accountability are embedded in the tier-based structure, ensuring that projects do not advance without identified leaders who own their delivery and outcomes.

Transparency and government accountability

A final dimension that distinguishes the framework is its requirement for government transparency . Public reporting of project status, risks, and escalations is mandated at certain tier levels, creating visibility and accountability that extends beyond internal agency silos. This transparency both deters poor governance and builds public confidence in how major infrastructure investments are managed.

The combination of risk-based assessment, independent expert challenge, early escalation, and public transparency creates a governance model that prevents delivery failure rather than simply responding to it. Learn more about how governance structures are designed to prevent project failure from the start in the full episode.

How should governance scale across projects of different sizes and risk profiles?

Governance should be relative to the risk. If a $200 million program building an airplane or major infrastructure requires extensive governance because the…

What is the difference between minimum viable governance and minimum governance?

Minimum viable governance is not about doing less—it's about doing exactly what's needed . It means creating structures and systems that enable the right people to make the right decisions at the right time to manage project risk, calibrated precisely to the project's actual risk profile, not its budget.

The core misconception: less is not the goal

The term "minimum viable" often gets confused with "minimal," but as Isabel Grae Garaway explains in the episode , they are fundamentally different. Minimum viable governance is about fitness for purpose—creating governance that fits the actual needs of the project, not creating the least governance possible.

Think of it this way: a quarter-million-dollar project and a half-million-dollar project may require different governance structures entirely , not simply less governance. The difference lies in understanding what risk actually exists and what decision-making architecture is required to manage it effectively.

Governance scaled to risk, not to budget

The critical principle is that governance should be relative to risk . If the risk is low, governance ideally should be low to reflect that. If the risk is high, governance must rise to meet it. The mistake most organizations make is either applying one-size-fits-all governance or stripping it away entirely because they think it slows delivery.

What minimum viable governance prevents is the trap of doing work to feed the process rather than to enable delivery. As discussed in this podcast episode , bureaucratic governance becomes a barrier when it exists without a clear purpose. Minimum viable governance, by contrast, is lean because every structure and system exists for one reason: to ensure the right decision is made by the right person at the right time.

"Governance always precedes delivery failure. You can tell a project that's going to fail before it's even started."

Isabel Grae Garaway — Governance Expert. Grae Garaway began her career in defence, where she developed deep expertise in robust governance frameworks and risk management across large-scale infrastructure and complex programs. She is recognized as a thought leader on fit-for-purpose governance, specializing in how organizational structures enable or prevent project delivery success.

The real insight here—one that becomes clear when you listen to the full conversation —is that governance frameworks like the New South Wales Investor Assurance Framework use a four-tier risk classification system precisely because different projects need different levels of oversight. Minimum viable governance is not a single template; it's a principle applied thoughtfully to each context.

Minimum viable governance is fit-for-purpose governance, not minimal governance—it's calibrated to the actual risk profile of the project.

Governance structures should enable decision-making, not hinder it by creating bureaucracy that feeds itself rather than serves delivery.

Risk and governance levels must be aligned: low-risk projects need proportionally lower governance, high-risk projects need robust structures.

Without clear sponsor accountability and executive governance, projects fail before they start—governance precedes delivery failure, not the reverse.

How can governance structures be designed to prevent project delivery failure before a project even starts?

Project failure is predictable before execution even begins. If a project lacks clear sponsorship with explicit executive accountability , it is fundamentally compromised from the start. Five structural elements must be locked in place before launch: uncontested scope definition, an articulated business case with intended benefits, secured budget, organizational change readiness assessment, and robust governance scaled to the real risk profile.

Governance precedes failure, not the reverse

Isabel Grae Garaway emphasizes that governance always precedes delivery failure. The problem is not that governance fails during execution—it is that the failure was already embedded in weak governance decisions made before the project even launched. Weak sponsorship, undefined scope, or misaligned budget are not obstacles to fix mid-project; they are red flags that the project was never properly chartered.

As Garaway explores in the episode , the governance structure must reflect the actual risk level of the project. Too much governance creates bureaucratic drag; too little leaves critical decisions unmade. The goal is fit-for-purpose governance —exactly the right level of structure and decision authority to enable the right people to make the right decisions at the right time.

Five non-negotiable governance foundations

The first foundation is clear sponsorship and executive accountability . Without a named sponsor who owns the outcome and commands enough organizational authority to remove obstacles, the project is already set up to fail. Accountability must be personal and visible, not diffused across a committee.

The second is uncontested scope definition . If scope remains contested or ambiguous at the start, every downstream decision—from budget to timeline to resource allocation—will inherit that ambiguity and collapse under it.

Third, the business case must articulate intended benefits and measurable outcomes . This is not a document written for approval theater; it is the project's north star. Without it, there is no way to know what success looks like or whether the project remains aligned with business strategy.

Budget must be secured before execution , not hoped for or contingent on quarterly approvals. As detailed in this episode on governance structures , projects that enter execution without locked-in budget are vulnerable to mid-course cancellation or resource starvation.

Finally, organizational change readiness must be assessed . A project can be technically sound but fail because the organization is not ready to adopt the change. Governance must include explicit evaluation of whether the people, processes, and culture are prepared for what the project will deliver.

"Governance always precede delivery failure. You can tell a project that's going to fail before it's even started."

Isabel Grae Garaway — Governance Expert. Garaway began her career in the defence sector, where she developed deep expertise in robust governance frameworks and risk management across large-scale infrastructure and complex programs. She is recognized as a thought leader on fit-for-purpose governance and the structural conditions that enable or prevent project delivery success.

Why governance is enablement, not constraint

A common misconception is that governance exists to slow projects down or protect organizations from risk through bureaucratic control. The truth, as discussed in Beyond The Plan , is that governance is a structure for enablement. It removes decision ambiguity, clarifies authority, and ensures the right people have the information they need to act decisively.

When governance is fit-for-purpose—neither bloated nor skeletal—it becomes the mechanism that accelerates delivery by eliminating rework and misalignment . The alternative is not freedom; it is drift, conflict, and eventual project collapse.

Project failure is predictable at the governance stage, before execution begins; clear sponsorship with executive accountability is non-negotiable.

Five governance foundations must be established before launch: defined scope, articulated business case, secured budget, change readiness assessment, and sponsor accountability.

Fit-for-purpose governance is sized to the actual risk level of the project, not applied uniformly; minimal governance for low-risk work, structured governance for complex programs.

Governance enables delivery by clarifying decisions and authority; weak governance does not reduce bureaucracy, it increases rework and delays.

How Collaborative Working Saves Projects | Project Management | Ep. 15

Why must collaborative working culture be designed to be enduring beyond individual relationships?

Collaborative culture must be embedded in processes and shared values rather than depending on specific individuals, because personal relationships are inherently fragile—they shift when people move roles, projects change phase, or new stakeholders enter the work. When relationship management becomes structural, collaboration survives these inevitable transitions.

The fragility of relationship-based collaboration becomes apparent in complex, multi-year projects. When trust exists only between two people—say, a project manager and a vendor account lead—what happens the moment one of them leaves or rotates to a different assignment? The institutional knowledge of how decisions are really made, what behaviors are expected, and how conflicts get resolved walks out the door with them.

This is why Brett Ackroyd discusses the ISO 44001 framework , which codifies collaborative behaviors and relationship management into organizational systems. Rather than relying on personalities to drive collaboration, elite delivery teams make collaboration predictable. The values—trust, transparency, mutual accountability—become documented principles that new team members inherit the moment they join, regardless of who they're replacing.

Building collaboration into the operating system, not just the people

The real work lies in examining your processes and systems to see whether they actually support the collaborative behaviors you claim to value. A team might say it believes in transparency, but if the contract structure encourages each party to hoard information for leverage in disputes, transparency will fail the moment pressure arrives.

When you design collaboration into roles, approval workflows, risk-sharing mechanisms, and reporting cadences, it survives the personnel churn that is inevitable in long-running infrastructure and government projects. A new commercial manager arriving mid-project can immediately see how decisions flow, how conflicts are escalated, and what behaviors are non-negotiable—because these are embedded in the system, not hidden in the relationships of their predecessors.

"You will know a collaborative culture exists when one party will take it on themselves to actually act to their detriment for the other party, because that allows for the achievement of the overall outcome."

Brett Ackroyd — Commercial Lawyer with 25 to 26 years of experience in mega projects for the Department of Defence and Government Security. He has spent his career helping major organisations move projects to success after contract execution, focusing on systems and behaviors that sustain collaboration beyond contractual obligation.

That definition points to the depth required: true collaboration isn't just politeness or regular meetings. It's a structural setup where each party accepts short-term costs for long-term collective gain—and that only happens when the system makes such behavior the path of least resistance, not a heroic choice dependent on individual goodwill.

As Ackroyd explains in this episode , the moment a key relationship owner leaves a project, the entire foundation shouldn't crack. The values, the escalation paths, the problem-solving routines—all of it should remain intact for whoever arrives next. That's endurance. That's institutional resilience.

How should teams respond to emergent complexity discovered during project execution?

When unexpected complexity surfaces during project execution—contaminated ground discovered during excavation, corroded equipment, new technical obstacles—the team's response should be predictable and collaborative, with members taking ownership of problems as a shared responsibility rather than assigning blame or filing contractual claims. The paperwork and formal change orders follow after the problem is already solved.

This principle flips the traditional project playbook. Most teams operate in reactive mode, waiting for formal processes before acting. Under collaborative working, the opposite happens: the team acts first to protect the overall project outcome, and the administrative machinery catches up later.

As Brett Ackroyd explains in the Beyond The Plan podcast , this isn't about heroic individual sacrifice—it's about designing predictable team behaviour. When one party knows the other will act to resolve an issue even if it costs them short-term resources, both parties can move faster and with less friction.

The psychology of predictable action

Collaborative response to emergent complexity requires a shift in how teams think about responsibility. Instead of asking "whose contract fault is this?" or "can we claim variation costs?", the first question becomes "what's the fastest way to fix this and keep the project moving?"

This works only when team members trust that others will reciprocate the same behaviour . If one party consistently acts in good faith to solve problems, the other party is more likely to do the same when the shoe is on the other foot. That reciprocal safety creates psychological permission to take intelligent risks.

The contrast with claims-focused culture is stark. In defensive environments, people document everything, raise variations immediately, and protect their contractual position first—even when they know how to solve the problem. As discussed in this episode of Beyond The Plan , Australia spends more of the project budget on claims than any other Western nation, a direct symptom of this fragmented approach.

"You will know a collaborative culture exists when one party will take it on themselves to actually act to their detriment for the other party, because that allows for the achievement of the overall outcome."

Brett Ackroyd — Commercial lawyer with 25 years of experience in mega defence and government projects. He has spent his career working within major organisations on complex project delivery, focusing on moving projects to success after contract execution rather than relying solely on contractual terms.

When paperwork follows, not leads

In traditional project governance, formal change control comes before resolution: identify the issue, lodge a claim, negotiate the terms, approve the variation, then execute the fix. This sequence creates delay, friction, and often results in problems staying unsolved while parties argue over cost allocation.

Collaborative teams invert this. The team fixes the problem immediately using available resources , then documents what happened and what it cost. The paperwork becomes a record of a decision already made to protect the project, not a gatekeeper preventing action.

This doesn't mean ignoring contracts or accountability. It means understanding that paperwork is a tool for managing relationships after delivery, not a tool for preventing intelligent response during execution. More detail on how this transforms productivity can be found in the Beyond The Plan episode on Scottish Water's collaborative results .

What happens when teams take a claims-focused approach instead of collaborative problem-solving?

Australia spends more of its project budget on claims than any other Western nation , a direct result of teams prioritizing contractual leverage over collaborative problem-solving. When parties adopt a claims-focused mindset, they hold back discovered problems for future negotiation, eroding trust and making everyone defensive about contractual certainty rather than focused on achieving the shared project objective.

The Cost of Holding Back Information

In a claims-focused culture, teams treat problems as negotiating ammunition rather than shared challenges to solve together. When someone discovers an issue, instead of raising it immediately for the team's benefit, they file it away as a potential claim. This defensive posture transforms relationships from collaborative to adversarial , where each party views the other as a future opponent rather than a partner in delivery.

As Brett Ackroyd explains in the episode , this mindset makes people reluctant to expose vulnerabilities or admit they need help. Problems that could be solved quickly and cheaply spiral into expensive disputes because they were never raised in real time. The financial impact compounds across years of project execution.

The Trust Erosion Cycle

Trust is fragile in a claims-focused environment. Once teams sense that others are withholding information or waiting for an opportunity to lodge a claim, defensive behaviour spreads across the entire organisation. People become focused on protecting their contractual position rather than solving problems, which directly undermines project performance and delivery timelines.

The irony is that this defensive approach creates the very conditions it claims to protect against. By withholding information, teams actually increase risk and cost exposure for everyone. What should have been a minor fix becomes a full-blown dispute because it was never addressed when it was small and manageable.

"You will know a collaborative culture exists when one party will take it on themselves to actually act to their detriment for the other party, because that allows for the achievement of the overall outcome."

Brett Ackroyd — Commercial Lawyer with 25 years of experience in mega projects. Ackroyd has spent his career working within the Department of Defence and Government Security sector, helping major organisations move beyond contractual frameworks to achieve complex project outcomes through intentional relationship management and shared values.

The contrast is stark: true collaborative cultures operate on a fundamentally different principle. Teams are willing to absorb short-term costs or take on extra work if it serves the overall project objective. This willingness to act against immediate self-interest for collective benefit is the hallmark of high-performing delivery environments, and it's completely incompatible with a claims-focused approach. You can explore how Scottish Water and Sydney Water used collaborative frameworks to reduce delays and improve outcomes in the full episode.

Claims-focused cultures reward information hoarding and defensive behaviour, turning teammates into adversaries.

Problems discovered but withheld for future claims escalate in cost and complexity rather than being solved in real time.

Collaborative cultures operate when parties are willing to absorb short-term costs for the collective project objective.

Australia's disproportionate spending on claims compared to other Western nations reflects widespread reliance on contractual leverage instead of partnership.

How can predictable relationship management improve project productivity?

When teams understand how their colleagues will respond to problems, they can pre-plan and respond predictively rather than reactively . Scottish Water's research demonstrated that projects using collaborative working experienced significantly reduced delay times compared to those without it, because everybody knew exactly how to handle unforeseen issues together.

This shift from reactive crisis management to predictive problem-solving is fundamentally about relationship clarity. When you work alongside the same partners repeatedly, patterns emerge—you learn their decision-making styles, their risk tolerance, their communication preferences, and their commitment to shared outcomes.

As Brett Ackroyd explains in Beyond The Plan , the foundation of this predictability is establishing common values and behaviours across the entire delivery team. Once those are explicit, teams can design systems and processes that actively support them, rather than creating friction.

From reactive delays to predictive delivery

Scottish Water's comparative research was telling: projects that had invested in building collaborative working relationships cut their delay times dramatically. The difference wasn't about better technology, more budget, or longer schedules—it was purely about relationship certainty enabling anticipation .

When a problem emerges on a collaborative project, teams don't spend time negotiating blame, checking contracts, or waiting for sign-off from distant stakeholders. They already know how their partner operates, what trade-offs they'll accept, and what the shared priority actually is. A potential five-day delay becomes a one-day adjustment.

This is particularly valuable in complex infrastructure and defence projects, where unforeseen conditions are guaranteed and change is constant. As detailed in this podcast episode , teams that have practised responding to problems together—not just planned for them—move faster when reality doesn't match the blueprint.

Why contract alone isn't enough

Most organisations assume that a comprehensive contract creates safety and predictability. In reality, a contract only describes what happens if things go wrong—and most project failures happen not from breach, but from the inability to act on problems teams already know how to fix .

Contractual boundaries can actually prevent the very speed and collaboration that reduce delay. If Party A is afraid that helping Party B will count against them in a dispute, or if decision-making is locked into formal approval chains, the organisation loses its agility. Predictable relationship management removes this friction.

In mega-projects within defence and government, as Brett Ackroyd's 25 years of experience has shown, the organisations that deliver on time and on budget are those that made relationship management as intentional as schedule management. You can read more about his framework for this in the full episode .

"You will know a collaborative culture exists when one party will take it on themselves to actually act to their detriment for the other party, because that allows for the achievement of the overall outcome."

Brett Ackroyd — Commercial Lawyer with 25 to 26 years of experience in mega-projects within the Department of Defence and Government Security area. He has worked with major organisations on complex project delivery and specialises in moving projects to success after contract execution, focusing on the systems and relationship foundations that enable teams to act decisively when conditions change.

If you're curious about how elite teams actually structure this predictability at scale—including the ISO 44001 framework designed specifically for business relationship management— the full conversation is worth your time .

Why do most project failures occur after a contract is signed?

Project failures rarely stem from budget, timeline, or scope alone—they emerge from teams' inability to act on problems they already know how to solve due to contractual boundaries, organisational silos, lack of authority, or a priority on commercial outcomes over actual project success. A signed contract, no matter how detailed, cannot by itself mobilise individuals to work effectively together within a truly collaborative framework.

The Hidden Problem: Contracts Don't Guarantee Collaboration

Most project managers assume a signed contract marks the beginning of execution. In reality, it often marks the moment when structural barriers emerge that prevent teams from acting . Brett Ackroyd, a commercial lawyer with 26 years of experience on defence and government mega-projects, explains that contractual language addresses only one dimension of project delivery—the legal one.

The real failure mechanism is more subtle. Teams possess the knowledge and capability to solve problems, but organisational boundaries, lack of cross-functional authority, and competing commercial incentives create paralysis. A developer knows how to fix a design flaw; a supply chain manager sees a cost-saving opportunity; a partner identifies a risk—yet none act, because the contract, the hierarchy, or the fear of liability stops them first.

As Ackroyd discusses in the podcast , this isn't a training or communication problem. It's a systemic one embedded in how organisations structure relationships and incentives around projects. When people prioritise protecting their contractual position over advancing the collective outcome, the project—not the contract—suffers the consequences.

Values and Behaviours: The Foundation Contracts Miss

The core insight is this: people operate because of their values and their behaviours , not because a clause compels them. A contract can enforce penalties, but it cannot create the conditions for genuine collaboration. Yet most organisations invest entirely in contract drafting and legal protection, leaving values and behaviours unaddressed.

This is where the distinction between contractual collaboration and cultural collaboration becomes critical. You can write "all parties shall work collaboratively" into every clause, and it will remain ink on paper if the surrounding systems, processes, and incentive structures don't actively support the behaviours required to make it real.

Evidence from projects using true collaborative frameworks tells a different story. Scottish Water's projects built on collaborative working principles showed significantly reduced delay times compared to projects relying solely on traditional contract management. The difference wasn't the contract—it was the intentional design of the working culture itself.

"You will know a collaborative culture exists when one party will take it on themselves to actually act to their detriment for the other party, because that allows for the achievement of the overall outcome."

Brett Ackroyd — Commercial Lawyer with 25 to 26 years of experience in defence, government security, and complex project delivery. Ackroyd has worked within major organisations managing billion-dollar infrastructure outcomes and has specialised in moving projects from contract execution to genuine success through collaborative working frameworks rather than reliance on contractual terms alone.

This single definition encapsulates what separates surviving projects from failing ones. It's not altruism—it's the recognition that individual loss in service of collective gain is the only sustainable path to project success. Yet no contract can mandate this mindset; it must be built into the culture from day one.

The Australian government and defence sector data underscores this urgently: Australia spends more of project budgets on claims than any other Western nation , a metric that reflects the cost of contractual adversarialism and the absence of genuine collaboration. These are not project failures caused by poor planning—they are failures caused by teams unable to transcend the very contracts meant to protect them.

What role does ISO 44001 play in managing collaborative working?

ISO 44001 is the business relationship management standard that provides a structured framework for organisations to intentionally manage collaborative working. While not a complete solution on its own, it supports a systematic approach to ensuring all parties work together to create mutual additional value in delivering project outcomes.

A framework for intentional collaboration

ISO 44001 addresses a critical gap in project delivery: most organisations assume good relationships will happen naturally, but they rarely do without deliberate design. The standard provides a starting point for building intentionality around business relationship management , helping teams move beyond contract compliance to genuine partnership.

The real power of ISO 44001 lies in its systematic nature. Rather than leaving relationship quality to individual personalities or goodwill, it creates a structured approach that can be applied consistently across large, complex organisations. As discussed in the Beyond The Plan episode , the framework helps teams understand their values and behaviours, then audits the surrounding systems and processes to identify gaps that might undermine those values.

Why contracts alone are insufficient

Most project failures don't stem from poorly drafted contracts—they begin after the contract is signed. Contracts define obligations but cannot mandate collaboration or trust , and this is where ISO 44001 becomes essential. The standard shifts focus from what people must do (contractual obligations) to how they work together (relationship culture).

Organisations working within Australia's Department of Defence and Government Security on mega projects have discovered that collaborative frameworks like ISO 44001 reduce blame-shifting and create mechanisms for parties to solve problems together rather than escalate disputes. When teams adopt this standard, they establish a shared language and accountability structure that supports the overall outcome rather than protecting individual positions.

"You will know a collaborative culture exists when one party will take it on themselves to actually act to their detriment for the other party, because that allows for the achievement of the overall outcome."

Brett Ackroyd — Commercial Lawyer with 25 to 26 years of experience working on mega projects within the Department of Defence and Government Security area. Ackroyd specialises in moving projects to success after contract execution, focusing on how organisations can intentionally design business relationships that support complex delivery outcomes across multiple parties and industries.

The example of Scottish Water's collaborative projects demonstrates this in practice: organisations implementing collaborative working frameworks showed significantly reduced delay times compared to non-collaborative projects, translating the relationship standard into measurable schedule benefits.

How should business relationship management be structured in major projects?

Collaborative working is a systemic approach to managing business relationships that must be intentional, enduring, and scalable. Organisations need to integrate business relationship management into their overall integrated management system, backed by frameworks like ISO 44001, rather than relying solely on personal relationships that become fragile when individuals change roles or project phases shift.

Why personal relationships alone will fail you

Most project failures happen not during contract negotiation, but after the contract is signed . When relationships exist only between individuals, the entire project delivery depends on their continued presence and goodwill. Remove one person, and the foundation crumbles.

As Brett Ackroyd explores in the episode , the cost of this fragility is real. Australia spends more of its project budget on claims than any other Western nation—a direct result of relationship breakdowns and the adversarial dynamics that follow.

Building systems that outlast individuals

ISO 44001 is the framework most project leaders have never heard of but should have. It provides a structured approach to collaborative relationship management, embedding values and behaviours into organisational systems rather than personalities.

The logic is straightforward: people operate because of their values and their behaviours. Once you have certainty around what those values and behaviours are, you can audit the surrounding systems and processes to identify gaps or barriers that don't support their execution. A systematic approach ensures that when roles change or tensions arise, the relationship framework remains intact.

Evidence of this works appears in real-world projects, such as Scottish Water's collaborative working initiatives , which showed significantly reduced delay times compared to non-collaborative projects—proof that intention and structure deliver measurable results.

"You will know a collaborative culture exists when one party will take it on themselves to actually act to their detriment for the other party, because that allows for the achievement of the overall outcome."

Brett Ackroyd — Commercial Lawyer with 25 to 26 years of experience in major defence and government projects. Ackroyd has spent significant time working within large organisations managing complex project delivery outcomes, with particular focus on moving projects to success after contract execution rather than relying solely on contractual terms.

This insight—that true collaboration means acting against immediate self-interest for the collective good—cannot be legislated by contract. It emerges only when values, systems, and processes align. Listen to the full conversation to explore specific methods elite delivery teams use to implement these frameworks at scale.

What defines a collaborative working culture in complex project delivery?

A collaborative working culture exists when people will act in situations without certainty of their commercial outcome to benefit the overall project, and when one party will take actions to their own detriment if it allows the achievement of the collective goal. It is fundamentally about resolving problems beyond individual functional or organisational boundaries.

The distinction here is crucial: collaboration is not simply agreement or cooperation on paper. It emerges when people prioritise the project outcome over their individual interests , even when doing so carries personal cost. This happens not because contracts force it, but because the shared values and behaviours of the team make it possible.

According to Brett Ackroyd in the episode , most project failures do not stem from budgets, timelines, or scope alone—they emerge from fractured relationships and misaligned incentives after the contract is signed. The real work of collaboration begins once the contract is executed, not before.

When Values and Behaviours Align With Systems

People operate because of their values and behaviours , not because of contractual clauses. This insight explains why two projects with identical contracts can deliver vastly different results. If your organisation has clarity around what values and behaviours are non-negotiable, you can examine the surrounding systems and processes to identify gaps or barriers that undermine those values.

This is where frameworks like ISO 44001 become relevant—they provide a structured approach to collaborative working that extends far beyond the contract document itself. Ackroyd discusses how elite delivery teams use such frameworks to embed collaboration as a cultural practice rather than a compliance exercise.

Real-world evidence supports this approach. Projects using collaborative working methods have demonstrated significantly reduced delay times compared to non-collaborative counterparts, as seen in infrastructure projects across Australia and internationally, including Scottish Water's experience.

"You will know a collaborative culture exists when one party will take it on themselves to actually act to their detriment for the other party, because that allows for the achievement of the overall outcome."

Brett Ackroyd — Commercial Lawyer with 25 to 26 years of experience in mega projects within the Department of Defence and Government Security, as well as other industries. He has spent significant time working within major organisations seeking to engage industry on complex project delivery outcomes, with particular focus on moving projects to success after contract execution.

What makes this definition practical is that it is testable. You can observe whether parties genuinely act in cross-boundary problem-solving, or whether they retreat into blame-shifting and contractual posturing when pressure mounts. The episode explores specific methods that defence and government projects use to maintain this culture at scale , even as projects become more complex and involve multiple organisations and stakeholders.

Collaborative culture is defined by action beyond individual interest—people must be willing to absorb cost to serve the collective project outcome.

Contracts are necessary but insufficient; the critical phase for building collaboration is after the contract is signed and execution begins.

Alignment of values and behaviours must be supported by systems and processes that remove barriers to cross-functional and cross-organisational problem-solving.

Projects demonstrating collaborative working practices report measurably reduced delays and improved outcomes compared to siloed delivery models.

What Beyond The Plan covers

Beyond The Plan serves infrastructure and government professionals navigating complex, high-stakes project delivery. The podcast examines why governance frameworks fail, how human leadership skills outweigh technical expertise, and why collaborative contracting delivers better outcomes than traditional adversarial approaches. Episodes draw directly from real Australian projects—Sydney Metro, Sydney Light Rail, Lane Cove Tunnel—providing field-tested strategies applicable to any major infrastructure initiative.

Key facts

Explore all episodes of Beyond The Plan for actionable strategies from seasoned practitioners.

What this podcast really covers

Beyond The Plan dissects the operational realities of major infrastructure delivery—not the marketing narratives. The podcast reveals systematic patterns: why organizations select the wrong problems to solve at project inception, how planning tools become substitutes for actual decision-making, and why PMO structures often obstruct rather than enable delivery. Ali Farhoodi and his guests pull back the curtain on projects like Sydney Metro and Lane Cove Tunnel, isolating the specific governance, contracting, and leadership decisions that determined success or failure. The episodes demonstrate that infrastructure project outcomes depend less on budget or timeline sophistication than on governance clarity, collaborative alignment, and the human capability to navigate complexity.

Who this podcast is essential for

Project managers and delivery leaders working on government or private sector infrastructure programs find immediately applicable insights. Senior executives overseeing major capital initiatives—who must diagnose why internal PMOs fail or why expert consultants underperform—gain diagnostic frameworks for root-cause analysis. Government officials responsible for approving or overseeing major infrastructure spending learn why contractual terms, governance design, and leadership selection matter more than technical forecasting. Consultants and procurement professionals working within complex infrastructure ecosystems hear field-verified perspectives on what actually drives delivery success in contested, politically sensitive, multi-stakeholder environments.

What the episodes really reveal

The episode titles and subjects expose a consistent thesis: infrastructure delivery failure is almost never technical—it is structural. "Your Project Didn't Fail. Your Governance Did" directly challenges the assumption that projects fail due to scope creep or resource constraints. "80% of Expert Leaders Fail in Complex Projects. Here's Why" isolates the human and systemic factors that separate expertise from effectiveness. "Why Projects Keep Solving the Wrong Problems" identifies the upstream decision point where projects derail before execution begins. "The Human Skills That Make or Break a Project Manager" establishes that technical credentialing means nothing without emotional intelligence, stakeholder navigation, and conflict resolution. "How Collaborative Working Saves Projects" and "Why Mega Projects Fail (And How Collaborative Contracting Fixes Them)" present contracting philosophy as a determining variable in outcomes. Together, these episodes form a coherent argument: infrastructure success requires governance discipline, human maturity, and collaborative alignment—not more advanced planning software.

What this changes in practice

Organizations applying Beyond The Plan insights begin by auditing governance design before adding resources or extending timelines. They recognize that PMO tools and templates, without clear decision-making authority and accountability, become busy-work that obscures real problems. Project leadership selection prioritizes emotional intelligence and stakeholder management over technical certification. Contract design shifts from risk-transfer mechanisms toward collaborative alignment clauses that incentivize all parties to solve problems jointly. Government buyers start by defining the problem clearly—a step typically skipped—rather than rushing into procurement. Teams invest in learning human skills—communication, influence, conflict resolution—recognizing that these determine project outcomes more reliably than Gantt charts or earned-value management. The practical outcome is slower project starts, clearer governance at the outset, and significantly faster and less contentious delivery once execution begins.

Infrastructure projects fail not because of inadequate resources or poor forecasting, but because governance structures lack clarity, teams lack the human skills to navigate complexity, and contracting frameworks treat collaboration as optional rather than essential to delivery.

Listen to Beyond The Plan for practical strategies on governing, structuring, and delivering major infrastructure initiatives.

Discover how seasoned infrastructure leaders solve real project challenges in every episode.

The podcast answers these questions

What are the main causes of project failure in infrastructure development?

Project failures in infrastructure development stem from poor governance structures, inadequate human skills in leadership, misaligned problem definitions at the outset, and ineffective use of planning tools. When governance frameworks fail to provide clear accountability and decision-making pathways, even well-resourced projects derail. Additionally, the human dimension—leadership capability, stakeholder engagement skills, and team collaboration—directly determines project success regardless of technical competence.

How does collaborative contracting improve mega-project outcomes?

Collaborative contracting aligns all parties—government, contractors, and consultants—around shared project objectives rather than adversarial cost-cutting. This approach reduces disputes, enables faster problem-solving, and creates transparency that prevents scope creep and hidden risks. Case studies of Sydney Metro and Lane Cove Tunnel demonstrate that when teams work toward mutual success rather than contractual protection, project delivery improves significantly.

Why do expert leaders struggle with complex projects?

Expert leaders often fail in complex projects because deep technical expertise does not translate to managing ambiguity, stakeholder dynamics, and organizational change. Complex projects require adaptive thinking, political awareness, and the ability to navigate competing priorities—skills that differ fundamentally from domain expertise. The episode data indicates that 80% of expert-level leaders face serious challenges when context shifts from specialist to systemic.

How should organizations approach AI implementation in project management?

Successful AI adoption in project management requires clear definition of the problem AI solves before implementing tools. Organizations must align AI deployment with actual workflow friction points and ensure teams understand how to interpret and act on AI-generated insights. Technology fails when introduced as a solution searching for a problem rather than as a response to a concrete operational gap.

Beyond The Plan

Discover Beyond The Plan

Ali Farhoodi · Beyond The Plan

Listen to the podcast

Découvrir Beyond The Plan sur Listenly →