Tag: strategy & change

  • A Holistic View for the Concept of Project Performance Failure

    A Holistic View for the Concept of Project Performance Failure

    At Pioticon, we don’t just believe in tailored project management, we build for it. Our focus remains on Engineering & Construction projects because they require sector-specific systems, delivery-aligned teams, and capability development rooted in real-world complexity.

    We’re not here to offer templates.

    We’re here to offer purpose-built systems, tools, techniques and thinking built for the job at hand.

    Project failure is often misunderstood. It depends on who looks at it. Success from stakeholder doesn’t mean it is successful from the side of sponsors or owners. The same way, success from owner’s perspective doesn’t mean contractor share the same or vice versa.

    Delays, cost overruns, and stalled approvals are visible symptoms of performance failure, but not the cause. These symptoms are frequently discussed in isolation, yet they stem from one consistent issue observed across the industry: productivity.

    This edition of the PM² Series presents a holistic view of how major project breakdowns occur, drawing on project delivery processes, market behaviors, award mechanisms, and execution realities, especially across Engineering & Construction projects.

    Defining Project Delivery

    Project delivery varies not only by size and scope, but by industry type and delivery model, whether portfolio, program, or project. Each operates under a unique objective, stakeholder framework, and complexity profile.

    Previously in the PM² Series, we explored how delivery structures and project management differ across sectors. That baseline leads to a critical realization: failures don’t stem from poor intentions or low-quality engineering. They stem from delivery mismatches that appear long before problems are visible on the surface.

    Problem occurs depending on decision made at different stages

    STAGE 1 – The Starting Point: An Idea and the Business Case Development

    Most projects begin with a need or an idea, and a well-defined business case along with feasibility study. It estimates time, cost, and risk, typically developed with input from experienced professionals using historical data, risk classification (Class 1–5), and defined benefits.

    This is the point where decision-makers and sponsors sign off based on a projected value case, often optimistic but framed with the assumption that risk-adjusted contingencies can cover variability. The project is assessed as financially and strategically viable at this stage.

    There’s no sign of problem at this stage assuming expert estimate of scope, time, cost & risk is adequate.

    STAGE 2 – Defining Project Delivery Model, Market Engagement & Awarding the Program or Project

    Stage 2A This crucial step involves choosing the right delivery model to balance “value for money,” while building an asset that delivers economic benefits. The owner or sponsor decides on Project delivery Model (PMO, Program or Project as one Package or SPV or Integrated Project Delivery) depending on organisation maturity and capability, accordingly project or package of works is broken down suiting the sponsor funding. Stage 2B

    Project or Package of works are decided on which Contractual model (Construct only, Design & Construct, EPCM, Alliance or PPP) is right fit to deliver those projects.

    When looked as a combined stakeholder benefits, each contractual model has its own merits and demerits.

    Once the sponsor approves the project to go to market the next phase tests the market through design and construct procurement. Consultants and contractors submit proposals based on scope documents, interpretation, and assumptions, each applying their own risk assessments and pricing models. Procurement teams evaluate offers using both quantitative and qualitative measures. Most organizations follow strict administrative policies and compliance protocols. Often, market pricing returns higher than anticipated in the business case. In such instances, clients and sponsors must reassess and either approve increased costs and timelines or repackage the scope. Once awarded, a mega project is expected to deliver against time and cost agreements, but the foundation of that commitment is already on uncertain ground and won’t be visible.

    The only sign of the problem at this stage is that if the market indicates anything more time, cost and risk of the same scope.

    STAGE 3 – What Happens Post-Award Until Design is Complete

    The concept scope evolves through various engineering and design stages. By the time the design reaches the Issued for Construction (IFC) stage, the original awarded scope has often changed significantly at the detail scope item and its quantum level, requiring adjustments to construction delivery strategy, time and cost. These changes frequently exceed the risk contingency allowance.

    This is the first indication of potential failure stemming from previous stage problems and decisions. Examples include design changes to accommodate ground conditions and specifications, as well as ineffective project management.

    However, Contractor often take an over optimised biased decision to recover in construction methodology and efficiency.

    STAGE 4 – Construction and Handover post IFC

    Classic failure symptoms started coming to the surface at this stage, compounding all the bad decisions made in the earlier stages.

    In failed project cases, depending on contractual model, Principal Contractor marry to the high risk project to deliver committed contract with compressed timeline and cost. This environment automatically creates unrest and unnecessary pressure to the team to perform unrealistic output.

    In many cases, Estimate at Stage 3(above) also further blows out due to many reasons including ineffective project management, procurement or long lead delays, unproductive delivery performance and unforeseen conditions (weather or ground or market or all combined).

    Significance of the Project Performance Failure

    In the case of major project failures in Australia and New Zealand, a clear pattern is emerging. Data shows that nearly 51% of awarded projects deliver unfavorably to Owners compared to original expectations. Even the favorable projects from client/owner’s perspective, contractor might be facing significant loss and not meeting their financial benefits. That is due to the disparity between the contract amount and the contractors’ actual final cost and time.

    Depending on the contract model and conditions, it often becomes challenging for the Contractor to recover significant losses through forensic delay and disruption claims.

    The full impact on contractors is not always visible publicly, except through insolvency reports or financial disclosures. Big Tier 1 contractors often manage exposures through multi-project cash flow strategies, which mask deeper structural issues in project-by-project reporting. While there are projects that hit targets, those are becoming rare and are mostly legacy examples, not current trends.

    Hence, it is not practical to get accurate data points to get true picture, analyse the real root cause and contributing factors in the right significance order.

    The fundamental reason is that the As-Built Quantity* multiplied by the Unit Rate per Scope Item* has significantly exceeded the original estimate.

    Definitions for Clarity:

    * As-Built Quantity : This includes the total quantity of work actually executed for the scope item — covering not just the permanent work, but also any temporary or remedial works performed as part of delivering the final approved design.

    * Unit Rate per Scope Item : This refers to the actual cost rate to construct one unit of the scope item. It comprises the cost composition of all resource inputs, including labour, materials, plant, and subcontractor services used to deliver the unit quantity.

    Patterns That Point to the Core Issue

    Generally, delays and cost overruns are consistently traced back to three compounding realities:

    • The base assumptions were not realistic for the original scope intended for the project objective
    • Risk was underestimated or transferred without the capability and capacity to manage it
    • Execution systems couldn’t match the complexity

    Every layer adds friction. Individually, they are manageable. Together, they become overwhelming.

    Despite schedule and budget failures, most infrastructure projects still deliver high construction quality. Engineers and builders should be acknowledged for this. Quality proves that capability exists at a technical level.

    The issue isn’t the ability to build, it’s the ability to deliver within what was promised.

    This is a classic problem: an imbalance between Project Delivery and Performance Management.

    Project failures are rarely caused by one factor. They emerge from highly interconnected issues that influence each other throughout the lifecycle. These include:

    • Shifting scopes
    • Design development lag
    • Market pricing pressures
    • Resource unavailability
    • Delivery model mismatches
    • External events
    • Inflexible systems

    Each factor may seem isolated, but it contributes to overall delivery drift.

    A Holistic Picture of Project Failure: The Eight Clusters of Contributing Factors

    A review of industry-wide trends shows that challenges group into eight recurring clusters of root issues. These are not fully measurable yet due to data limitations, but they reflect broad causation themes visible across project audits, reports, and real-world execution:

     

    1. Underdeveloped scope with unclear ground condition and engineering
    2. Authorities delay of access & approvals
    3. Ineffective project management & control
    4. Inefficient engineering & design to meet objective
    5. Inefficient construction & delivery to meet objective
    6. Market condition- labour, materials, contractor shortage, and escalation
    7. Unforeseen factors
    8. A common factor of workspace + incompetency at various degree

    No single cluster explains all failures. The interdependency between them is what causes delivery to unravel.

    Final Thought

    Project performance failure transcends simplistic blame narratives. It emerges from a complex interplay of unrealistic expectations, misaligned delivery models, capability gaps, and systemic inefficiencies. While infrastructure projects often achieve world-class technical quality, the persistent gap between promise and delivery remains.

    True improvement requires a paradigm shift. Success depends not on fixing isolated factors, but on transforming the entire ecosystem: how projects are conceived, planned, resourced, and executed.

    Only by embracing this holistic, systemic perspective can we begin to bridge the critical divide between project ambition and actual achievement, ensuring projects are delivered not just with technical excellence, but within the time and cost frameworks promised.

  • Generic Project Management Kills Its Own Purpose

    Generic Project Management Kills Its Own Purpose

    Project management today is flooded with frameworks, content, and advice, much of it well-meaning, but often disconnected from the realities of delivery. Across platforms like LinkedIn and mainstream certification programs, a wave of generic project management thinking has emerged. It’s creating more noise than clarity, and in doing so, it’s slowly eroding the value of project management itself.

    Projects vary, not just by size or duration, but by industry, complexity, delivery model, and context. And each of those variables demands a tailored approach, not a standardised one.

    Why Project Type Matters More Than Most Acknowledge

    A glance at the project landscape quickly reveals its diversity. As illustrated in the visual mapping of hundreds of project types by industry, Engineering & Construction Projects (e.g., highways, tunnels, power plants) differ fundamentally from Non-Construction Projects (e.g., IT implementations, finance system rollouts, media production). And even within Engineering & Construction, a highway project is not the same as a high-rise tower or an underground metro system.

    Hundreds of Project Types

    Despite this, project management advice is often treated as one-size-fits-all. The result? Misalignment, reduced effectiveness, and repeated delivery failures.

    While generic project management principles can offer a foundational starting point, they fall short when complexity increases and sector-specific realities come into play. Each project type, and often, each sub-type, requires its own blend of methodology, leadership, and controls.

    Management Capability Must Reflect Project Reality

    To effectively deliver these diverse project types, the capability of the project manager and the structure of the management team must evolve accordingly.

    The graphic below outlines a structured hierarchy of project management categories from project-level to portfolio-level, and illustrates how roles and responsibilities shift across Owners/Client Representatives, Engineering Consultants, Principal Contractors, and Subcontractors in mega or major projects.

    Competency requirements across these roles vary not just by level, but by project category and type. Misunderstanding this often leads to a poor fit between management approach and project demands.

    The Myth of Seamless Transition into Project Management

    A persistent and damaging assumption in the industry is that successful engineers or construction managers can naturally transition into project management roles.

    This thinking fails to acknowledge a critical truth:

    “The skills required to construct a bridge are not the same as those needed to manage a bridge project to time, cost, scope, and quality targets.”

    Project managers require a deep understanding of planning, monitoring techniques, systems, controls, risk, stakeholder alignment, and commercial drivers, not just technical know-how to design or build.

    These misunderstanding fuels the rise of the “accidental project manager”—someone promoted based on just engineering or operational experience, rather than on their ability to manage the full complexity of a project lifecycle.

    Why Generic Tools and Systems Fall Short

    Not only are people misaligned to roles, but so are the tools they’re handed. Project management systems and software that work well for real estate high-rise building towers often fall short in linear infrastructure like highways, rail, or pipelines.

    While certain work or trade packages, like concrete or electrical, may appear similar across projects, they account for only a fraction of total complexity. Delivery environments, stakeholder interfaces, and risk profiles vary greatly.

    The widespread promotion of generic project management platforms and playbooks glosses over these nuances and creates a false sense of readiness.

    The Competency Blend That Actually Delivers

    At Pioticon, we emphasize a structured approach to building real capability. Based on our work in engineering and construction, we focus on five core skill domains:

    1. Business Skills [The know-why behind the work]
    2. Project Management Skills [The know-how to make the work happen successfully]
    3. Technical Skills (Engineering, Design, Construction) [The know-how to do the work]
    4. People Skills [The know-how to lead and influence people to perform]
    5. Best Practice Knowledge [The know-what and why behind doing things the right way]

    The visual framework below illustrates how these domains overlap. While few individuals possess all five at once, the most successful professionals in construction project management evolve along a deliberate path, starting from a strong technical base and progressively building business acumen, leadership capability, and project delivery systems thinking.

    *Technical skills for Categories 1-3 are typically developed through progression from other categories during career advancement. Project Management itself has technical elements that are gained from prior Engineering or Construction experience in other categories.

    ^Categories also apply to Project Management and Control professionals, including Project Controls, Planning & Scheduling, Cost Engineering & Estimation, Risk, and Reporting.

    These skills are essential for productive technical leadership in high-complexity projects. This integration of knowledge is where project control becomes proactive, not reactive. It’s what` enables PMs to navigate scope creep, shifting conditions, and cross-functional pressures.

    Purpose-Built for Engineering & Construction

    At Pioticon, we don’t just believe in tailored project management, we build for it. Our focus remains on Engineering & Construction projects because they require sector-specific systems, delivery-aligned teams, and capability development rooted in real-world complexity.

    We’re not here to offer templates.

    We’re here to offer purpose-built systems, tools, techniques and thinking built for the job at hand.

    Final Word

    Generic project management can actively derail project success by creating false confidence, mismatched expectations, and ineffective leadership paths.

    To achieve performance in complex environments, we must stop treating project management as a universal solution and start treating it as a purpose-built capability, developed in context, for context.

  • Seeing the Bigger Picture: How Perspective Shapes Project Success

    Seeing the Bigger Picture: How Perspective Shapes Project Success

    When infrastructure projects make headlines, it’s often for the wrong reasons—budget overruns, missed deadlines, and large-scale inefficiencies. The narrative seems straightforward: yet another failed project, another financial disaster.

    But is it really that simple?

    Before labeling a project as a failure, we need to step back and ask deeper questions:

    • What does the term project actually mean to different stakeholders?
    • Who defines success, and on what basis?
    • Why do certain projects face more obstacles than others?

    The answers lie in perspective, how different players within a project ecosystem define objectives, risks, and responsibilities. When these perspectives don’t align, the consequences ripple through the entire lifecycle of a project.

    One Project, Many Perspectives

    Let’s take a simple example of a 20km motorway project. While it might appear to be a well-defined endeavor, its meaning varies drastically depending on who you ask:

    • For the client, it’s just one piece of a larger 100km transportation program, where realistic expectations and clear scope drive its success.
    • For the principal contractor, it’s a contractual commitment that must be meticulously managed to avoid scope creep and unforeseen liabilities.
    • For the designer, success means finding a solution in the most economical way, efficiency, and compliance in both temporary and permanent design works.
    • For the subcontractor, the goal is to execute their specialized task as cost-effectively and efficiently as possible.
    • For politicians and governments, it is driven by public perception, funding, and election cycles, the project’s success is tied to policy objectives, economic impact, and public reception.

    Each of these players is operating within the same project, yet their definitions of success—and their risks—are vastly different.

    When Perspectives Clash, Projects Suffer

    The problem arises when these perspectives remain unaligned. Risks are unevenly distributed, decision-making slows down, and the entire project becomes vulnerable to:

    • Scope creep – Unreasonable or vague contractual obligations and Miscommunication between stakeholders leads to unclear or changing expectations.
    • Budget explosions – Cost assumptions made by one party may not reflect on-the-ground realities faced by another.
    • Timelines stretching indefinitely – Conflicting priorities delay decision-making and execution.

    Project success is not just about hitting schedules and staying within budgets—it’s about creating a shared understanding among all stakeholders from the start.

    Reframing Success in Project Management
    Instead of defining success in narrow terms like cost and time, we need a broader, more perspective-driven approach to project management:

    • Stakeholder Alignment: Before execution even begins, ensure every key player understands the project’s objectives and constraints from each other’s point of view. Align on key performance metrics to define success to both stakeholder and project
    • Risk Balancing: Clearly define where responsibilities lie so risks don’t accumulate disproportionately on certain teams.
    • Systems Thinking: A project is not just an isolated contract—it’s a dynamic system of people, decisions, and interdependent parts. Managing it effectively requires stepping back and seeing the bigger picture.

    If you are a project owner, contractor, policymaker, engineer, or anyone involved in large-scale projects, this series will provide valuable insights and strategies for improving project alignments for better outcomes.

    So, What’s Your Perspective?

    How do you define project success in your industry? Have you ever faced challenges aligning different stakeholder expectations?

    Stay tuned for more insights in the Project Management Perspective Matters (PM²) Series by Pioticon.

  • Project Management Perspective Matters: Why Aligning Stakeholder Views is Key to Project Success

    Project Management Perspective Matters: Why Aligning Stakeholder Views is Key to Project Success

    Every major engineering and construction project thrives when every stakeholder shares a common understanding of success. But in reality, perspectives differ.

    From sponsors, clients, principal contractors, and designers to subcontractors, suppliers, and community leaders, each stakeholder brings their own priorities, biases, and expectations to the table. These differences, if left unaddressed, create misalignment, setting the stage for delays, cost overruns, and even project failure.

    At the same time, project beneficiaries- local communities, organizations, end users, and political leaders, often have an entirely different outlook. Their focus is on the final impact, not the countless challenges faced during execution. This contrast can create friction, misunderstandings, and resistance.

    It’s important to note that delays and cost overruns are measured against the baseline plan. However, this baseline may sometimes be unrealistic from the start, while in other instances, inefficient project delivery is indeed the root cause.

    The Cost of Misalignment in Projects

    Misalignment isn’t just an operational hurdle—it’s a critical risk factor. When stakeholders lack a shared vision:

    • Teams struggle with conflicting priorities, leading to inefficiency.
    • Decision-making slows down, increasing costs.
    • Unrealistic expectations create tension and dissatisfaction.
    • Project execution deviates from the intended goals.

    Bridging these gaps requires more than just process optimization; it demands a shift in perspective.

    The Power of Perspective in Project Success
    In the Project Management Perspective Matters (PM²) Series, we’ll explore how these varying viewpoints shape project outcomes and, more importantly, how leaders can bring them into alignment.

    We’ll cover:

    • Why perspective is the missing piece in project success – Understanding how different stakeholders define success and why their perspectives must be accounted for.
    • How misalignment happens before execution even begins – Identifying the early warning signs of divergence and how to address them at the planning stage.
    • What practical steps can help teams work toward the same goal – Actionable strategies to create a shared vision, align expectations, and drive collaboration.

    Beyond Timelines and Budgets: Playing the Same Game

    A successful project isn’t just one that’s completed on time and within budget. True success means every stakeholder sees value in the outcome—because, ultimately, a project’s impact lasts far beyond its execution.

    It starts with understanding perspectives. It succeeds when everyone is playing the same game.

    What’s one perspective shift that completely changed the way you approach project management? Share your thoughts in the comments!

    Stay tuned for the upcoming posts in the Project Management Perspective Matters series, where we’ll dive deeper into these crucial insights.