Pioticon Blog

Tag: Eight Clusters

  • Underdeveloped Scope with Unclear Ground Condition and Engineering: A Deep Dive into Root Causes and Solutions

    Underdeveloped Scope with Unclear Ground Condition and Engineering: A Deep Dive into Root Causes and Solutions

    Major infrastructure projects continue to face one persistent and costly problem: underdeveloped scope combined with unclear ground conditions and immature engineering practices. This issue is not confined to one country or sector; it appears repeatedly across geographies, budgets, and delivery models. Budget overruns, delays, disputes, and even outright failures all trace back to these foundational weaknesses.

    The discussion usually focuses on surface symptoms like, budget blowouts and schedule slips, but these are merely the outcomes of deeper structural and behavioral issues. A closer look reveals that these problems arise long before the first shovel touches the ground.

    The Visible Symptom: Underdeveloped Scope and Unclear Ground Conditions

    Many leaders and teams first notice these problems only after execution begins. By that point, incomplete scopes and vague ground data have already introduced hidden risks into the project. Teams then scramble to solve issues that could have been avoided with more rigorous preparation.
    Projects often move into execution phases with incomplete scopes. Key information on ground conditions remains missing or generalized. Engineering assumptions are based on minimal evidence, and contingency planning often lacks rigor.
    Some uncertainty is expected early on. However, many projects advance with a level of ambiguity far beyond what should be acceptable. Risks become embedded into the project from the outset, making future challenges unavoidable.
    These symptoms do not emerge by accident. They result from a set of root causes embedded in governance, financial incentives, organizational culture, and decision-making processes.


    1.1. Incomplete Early Stage Site Investigation

    The Initial Chain of Causes

    Insufficient site investigation during feasibility and pre-design phases stands as a primary contributor. Essential activities such as geotechnical surveys, environmental assessments, and detailed topographical studies are either minimized or entirely skipped.
    Several systemic factors drive this behavior:

    1. Limited Funding and Compressed Budgets Sponsors frequently restrict early-stage spending. Comprehensive site investigations require significant upfront investment, and decision-makers often hesitate to commit before full project approvals.
    2. Pressure for Fast-Track Approvals Sponsors prioritize early green lights to secure funding or meet political and regulatory promises. Project readiness often takes a back seat.
    3. Misaligned Incentives Project leaders receive recognition for achieving initial approvals rather than ensuring robust technical readiness. This misalignment pushes teams to rush.
    4. Milestone-Driven Governance Structures Approval frameworks emphasize stage-gate milestones rather than actual readiness, allowing projects to proceed despite unresolved technical gaps.
    5. Weak Independent Reviews The absence of strong third-party validations leaves scope and technical assessments unchecked.
    6. Cultural Acceptance of Uncertainty Many organizations hold a belief that unknowns can be managed later, underestimating future impact.
    7. Optimism Bias and High-Risk Appetite Overconfidence in later-stage problem-solving often leads to freezing scope prematurely.

    The Solution

    Front-end loading (FEL) processes with strict readiness criteria set a stronger foundation. Independent scope and site validations before approvals ensure critical risks are addressed. Incentive structures should reward thoroughness and technical quality rather than speed alone.

    1.2. Poor Interdisciplinary Coordination

    The Fragmentation Challenge

    Disciplines such as geotechnical, civil, environmental, and structural engineering frequently work in silos. Gaps between these areas create conflicting assumptions and elevate risks.

    Several reasons drive this fragmentation:

    1. Siloed Organizational Structures
      Departments operate as isolated units, reducing information flow and collaboration.
    2. Absence of Integrated Digital Platforms
      Critical data remains trapped in disconnected systems without a unified view.
    3. Legacy Processes
      Reliance on outdated document transfers stifles dynamic design evolution.
    4. Resistance to Digital Adoption
      Teams often hesitate to embrace new systems like BIM or GIS, viewing them as optional rather than essential.
    5. Inadequate Training and Change Support
      Teams receive insufficient guidance and support to adopt new practices effectively.
    6. Leadership Underestimation
      Senior leaders sometimes treat digital transformation as an IT task instead of a core strategic shift.
    7. Limited Investment in Capability Building
       Budgets focus heavily on delivery at the expense of internal capability and digital maturity.

    The Solution

    Mandating integrated digital platforms improves transparency and cross-disciplinary alignment. Investment in comprehensive training and change support builds true adoption. Leaders must treat digital enablement as a central business strategy rather than a side initiative.


    1.3. Limited Access to Historical Data

    The Data Deficit

    Many projects start without access to valuable data from earlier studies or nearby projects, forcing teams to rebuild knowledge from scratch.

    Key reasons for this gap include:

    1. Fragmented Data Ownership
      Data resides across different private and public entities, making access difficult.
    2. Absence of Centralized Repositories
      National or regional infrastructure data repositories are rare or nonexistent.
    3. Lack of Policy Frameworks
      Without clear regulations, data sharing remains inconsistent and discretionary.
    4. Legal and Commercial Barriers
      Concerns around liability and intellectual property discourage open data sharing.
    5. No Standardized Legal Protections
      Absence of consistent agreements makes data custodians hesitant to release valuable information.
    6. Short-Term Political Focus
      Leaders prioritize quick wins over systemic improvements, leaving data strategies neglected.
    7. Weak Industry Pressure for Reform
      Stakeholders rarely push hard enough for collective data sharing reforms.

    The Solution

    Establishing national infrastructure data repositories with mandatory submission requirements supports transparency. Developing legal frameworks ensures safe and fair data sharing. Tying data compliance to funding or permit approvals encourages participation.

    1.4. Inadequate Subsurface Risk Modeling

    Blind Spots in Modeling

    Available data often receives simplistic treatment, leading to unrealistic assumptions or overly conservative designs.

    Key reasons for weak subsurface modeling include:

    1. Simplistic or Conservative Approaches
      Teams may oversimplify or adopt overly cautious assumptions due to confidence gaps.
    2. Underuse of Advanced Tools

       Tools, techniques and skills to accurately perform 3D geotechnical modeling and probabilistic risk analysis remain inadequate.

    3. Shortage of Specialized Expertise

       Skilled professionals in advanced geotechnical modeling are in limited supply.

    4. Low Priority for Geotechnical Work
      Compared to other engineering disciplines, geotechnical input often receives less attention and investment.
    5. Procurement Focus on Lowest Cost
      Tender processes reward cheaper options instead of thorough technical analysis.
    6. Contract Evaluations Emphasize Price
      Procurement scoring frameworks undervalue technical rigor.
    7. Procurement Misalignment with Lifecycle Risk
      Short-term cost focus disregards long-term risk exposure.

    The Solution

    Organizations should mandate advanced geotechnical modeling early, invest in 3D modeling training, use probabilistic risk analysis, and elevate geotechnical work’s importance. Procurement frameworks must prioritize technical submissions. Requiring advanced risk modeling in feasibility phases strengthens project readiness. Moving evaluations beyond price toward lifecycle value reduces future overruns and delays.


    1.5. Frequent Scope Revisions During Construction

    The Cascade of Unknowns

    Unforeseen ground conditions force redesigns mid-construction, driving up costs and timelines.

    Key reasons for ongoing scope changes include:

    1. Lack of Early Utility Mapping
      Inadequate investment in tools like GPR and LiDAR leaves subsurface surprises.
    2. Reluctance to Spend on Early Detection
      Decision-makers consider upfront investigations an unnecessary expense.
    3. Underestimation of Variation Costs
      Many organizations fail to appreciate the true cost impact of late-stage changes.
    4. No Structured Cost-Benefit Analysis
      Few institutions compare early detection investment against potential redesign costs systematically.
    5. Absence of Formal VOI Studies
      Projects rarely quantify the benefits of better information before construction.
    6. Qualitative Treatment of Ground Risks
      Risks appear as generic entries in registers without quantified impacts.
    7. Optimism in Early Estimates
      Understated risks help secure approvals but undermine delivery integrity.

    The Solution

    Mandating VOI studies in planning phases quantifies early information value. Quantitative ground risk registers throughout design and construction phases support realistic decision-making. Frameworks comparing early and late-stage cost impacts help stakeholders make informed investments upfront.

    Cross-Cutting Recommendations: Linking Scope to the Wider Delivery System

    Fixing underdeveloped scope cannot stand alone. Each solution must connect with other systemic levers across the project lifecycle to prevent overruns and delays. The following integrated pathways highlight how scope-related reforms interface with other critical clusters of PM²:

    • Front-End Loading (FEL) and Independent Readiness Reviews Strengthens early project assurance and ensures that authorities’ approvals (Cluster 2) are based on realistic, fully validated baselines, reducing late-stage regulatory challenges.
    • Integrated Digital Engineering Platforms and Leadership Alignment Improves coordination between disciplines while simultaneously feeding accurate, real-time data into performance reporting and intelligence systems, breaking silos and enabling predictive insights.
    • National Infrastructure Data Repositories and Legal Frameworks Enhances not only early scope development but also supports risk management (Cluster 4) and future project benchmarking, creating an institutional knowledge base for ongoing PMC governance (Cluster 7).
    • Advanced Geotechnical Modeling and Risk-Based Procurement Reform Directly improves subsurface risk management while ensuring procurement decisions align with broader integrated project control standards (Cluster 6), preventing lowest-cost bias from undermining delivery.
    • Institutionalized Value of Information (VOI) Studies and Quantitative Ground Risk Registers Provides a structured approach to weighing early detection costs against late-stage redesign impacts, directly linking with risk buffers in planning and scheduling (Cluster 3) and ensuring better control over change management (Cluster 1).

    Why Integration Matters

    Addressing scope in isolation only shifts the problem elsewhere. Each recommendation reinforces not only the cluster of underdeveloped scope but also the broader ecosystem of approvals, controls, risk management, and governance. Only by treating these interdependencies as one connected system can major projects break the cycle of overruns and deliver outcomes that match ambition.

    Challenge

    Solution

    Incomplete Scope

    Front-End Loading (FEL), independent readiness reviews, governance reform

    Poor Interdisciplinary Coordination

    Integrated digital engineering platforms, capability-building, leadership alignment

    Data Access Gaps

    National infrastructure data repositories, legal frameworks for data sharing

    Weak Subsurface Modeling

    Advanced geotechnical modeling requirements, procurement reform

    Costly Scope Revisions

    Institutionalized VOI studies, quantitative ground risk management

    Conclusion

    Project failures do not arise from random technical errors or delivery team missteps alone. They are rooted in a systemic failure to connect realistic early-stage assumptions with market realities, workforce capacity, and delivery frameworks.
    Technical excellence in construction remains strong, but consistent failure to meet budget and time commitments signals a deeper structural problem.
    Successful outcomes depend on reforming how projects are scoped, awarded, and managed. Leadership courage, not technical knowledge, stands as the true barrier to progress.Shifting from a focus on isolated problems to a comprehensive, systemic understanding offers the only path to bridging the gap between project ambition and actual delivery.

  • 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.