Talha Asif — Infrastructure & PMO Executive

Category: PMO

  • P3 Governance: What Good Looks Like and Why Most Programs Do Not Have It

    What Governance Actually Is

    The most common misconception about P3 governance is that it is a passive function — the public authority monitoring compliance, reviewing reports, approving change orders, and waiting for things to go wrong. This misconception produces governance structures that are technically present but operationally ineffective.

    Effective P3 governance is active management of a long-term commercial relationship. The distinction is not semantic. Passive oversight asks: is the concessionaire meeting the contract? Active management asks: is the concession delivering the outcomes the public needs, and what can the public authority do to support and improve that delivery?

    An authority that only monitors compliance and processes deductions is performing a fraction of the governance function that a P3 concession requires. Over a 25-30 year concession term, the difference between passive oversight and active management compounds into an enormous gap in outcomes — for the public authority, for the concessionaire, and for the communities whose services depend on the asset.

    The Four Functions of Effective P3 Governance

    Performance monitoring is the function that most programs establish first and most visibly. The public authority tracks availability metrics, performance indicators, and deduction calculations against the contract framework. On an availability payment P3, this is where the payment mechanism operates. The failure mode is over-complication: monitoring frameworks that track fifty indicators for a single facility generate data without generating insight. Design the monitoring regime around the metrics that drive payment outcomes and asset performance.

    Risk management is the function that governance frameworks most commonly underinvest in during the operational phase. The risk register was built during procurement. It gets reviewed annually if the program is disciplined, and ignored entirely if it is not. On a 25-year concession, risks that were theoretical at financial close will materialize in various forms: demand assumptions that prove wrong, technology that changes operational requirements in unexpected ways, geopolitical conditions that create force majeure events. Governance that treats risk management as a procurement-phase activity will always be reactive when these events occur.

    Relationship management is the governance function that receives the least formal attention and has among the highest impact on concession outcomes. The relationship between the public authority and the concessionaire across 25-30 years determines whether problems get solved collaboratively or litigated expensively. Governance structures should include mechanisms for regular senior-level engagement — not just performance reviews and deduction disputes, but genuine dialogue about operational challenges and emerging risks.

    The UK’s PFI experience demonstrates what happens when this dimension deteriorates. By the midpoint of many PFI concessions, the relationship between authority and operator had become adversarial enough that routine variation requests were treated as commercial battles. The governance framework had no mechanism to reset the relationship. The cost of that deterioration accumulated over years of sub-optimal concession management.

    Change management is the fourth governance function — technically the most complex and most consequential in rapidly changing markets. A hospital P3 signed in 2005 needs to manage new clinical technologies, changing bed configurations, updated infection control requirements, and evolving maintenance standards across its remaining concession period. Each change requires a variation mechanism that is pre-agreed, fairly priced, and fast enough to keep pace with operational reality. Programs that establish clear variation procedures at contract execution manage change as a normal operational activity. Programs that do not, renegotiate every change under conditions where the concessionaire holds significant leverage.

    The Metrolinx Governance Lesson

    The experience I described in earlier articles — where the Bowmanville CMAR program’s collaborative delivery model met Metrolinx’s traditional governance framework — illustrates this point clearly. The organization had rigorous oversight processes: multiple committee reviews, external advisors, approval layers designed to protect public expenditure. These served an important purpose. But when applied to a progressive contract model that required collaborative decision-making at the pace of design and construction, the oversight framework became a delivery constraint. Decisions that needed to be made in days took weeks. The contract was structured for collaborative speed. The governance was structured for sequential control. They were not designed to work together.

    That mismatch is not unique to Metrolinx. It is one of the most common delivery problems on complex programs globally. And it is entirely preventable if governance is designed as part of the delivery model, not imposed on top of it.

    What Saudi Arabia’s P3 Program Needs

    The NPS is creating a P3 program at scale. The transactions being procured now will require governance capability that many Saudi government entities are still developing. Several foundations are particularly important.

    Owner capability must be developed in parallel with transaction volume. Dedicated P3 governance units with appropriately skilled commercial managers, technical monitors, and legal advisors with concession experience need to be operational before the operational phase of the first concessions begins.

    Standardized governance frameworks across sectors reduce the cost of capability development and produce more consistent outcomes across the portfolio. The programs Saudi Arabia builds over the next decade will operate for 25-30 years each. The governance capability established at the start of that period shapes every outcome across its duration.

  • The PMO Gap in Saudi Construction: Why Project Management Office Capability Determines Program Success

    The PMO as the Backbone of Mega-Program Delivery

    Saudi Arabia’s Vision 2030 programs are among the most ambitious public investment commitments in history. NEOM. Diriyah Gate. Red Sea Project. Qiddiya. ROSHN. The giga-project portfolio collectively represents hundreds of billions of dollars of infrastructure investment being designed, procured, and delivered simultaneously across a country that is also managing the largest peacetime fiscal transformation in its history.

    The physical challenge of building at that scale is enormous. But the governance and management challenge — coordinating hundreds of concurrent projects, multiple delivery entities, thousands of contractors, and the interests of multiple government stakeholders across 10-30 year program horizons — is arguably greater. This is the challenge that the Program Management Office is designed to address. And it is the challenge where Saudi Arabia’s mega-programs are most consistently underequipped.

    What an Effective PMO Actually Does

    The misconception about PMOs in many organizations is that they are a reporting function — a team that collects status reports from project managers, compiles them into a dashboard, and presents the dashboard to leadership. This conception of the PMO is not wrong so much as it is insufficient. A reporting PMO is better than no oversight at all, but it is a fraction of what a high-performing program management office contributes.

    An effective PMO performs five distinct functions. Strategic alignment ensures that the portfolio of projects being delivered is consistently prioritized and resourced in alignment with the program’s strategic objectives — and that tradeoff decisions about which projects to accelerate, defer, or modify are made on the basis of strategic rationale rather than whoever is loudest in the project team meeting. Performance monitoring is the tracking function most PMOs perform — but done properly, it is not just status collection. It is the analysis of performance data to identify leading indicators of risk, compare actual performance against benchmarks, and surface issues before they become crises. Resource optimization addresses the allocation of the program’s shared resources — people, equipment, budget, contractor capacity — across competing project demands in a way that maximizes program throughput. Risk management at the program level identifies and manages risks that exist between projects — interface risks, shared resource constraints, cumulative schedule pressures — that individual project managers cannot see from their project vantage point. Knowledge management captures and shares lessons across the project portfolio, ensuring that the experience earned on early projects informs better decisions on later ones.

    The Gaps in Saudi Arabia’s PMO Capability

    The PMO capability gap in Saudi Arabia’s construction sector is real and well-understood by those working within it. It manifests consistently in several ways: project controls systems that generate data but not insight, reporting that describes what happened rather than predicting what will happen, interface management between concurrent projects that is reactive rather than proactive, and resource allocation decisions made by whoever applies pressure most effectively rather than by an analytical process.

    The root causes are organizational rather than technical. The tools to run an effective PMO — schedule management software, cost management systems, risk modelling tools, dashboard and reporting platforms — are available and often installed. The capability to use those tools for genuine analytical decision support — rather than compliance reporting — is the gap. That capability is a function of the people who run the PMO, the authority they have to access and analyze project data honestly, and the organizational culture that receives their output as decision-relevant information rather than as an accountability mechanism to be managed.

    Building PMO Capability for Vision 2030

    The path to effective PMO capability in Saudi Arabia’s infrastructure sector runs through several parallel investments. International PMO practitioners with giga-project experience provide the technical baseline. Saudi nationals trained in program management create institutional capability that persists through program transitions. Technology platforms — built specifically for construction PMO rather than adapted from corporate management frameworks — provide the analytical infrastructure. And organizational culture that treats honest, forward-looking program intelligence as valuable rather than threatening makes all of the above investments effective.

    Concept Dash’s PMO practice provides exactly this integrated capability for clients in Saudi Arabia. We design and staff PMO functions for major programs, implement project controls systems that produce genuine program intelligence, and build the local capability that allows Saudi program teams to manage these functions independently as programs mature. For an introduction to how we approach PMO design and implementation for programs at the scale of Saudi Arabia’s giga-project portfolio, visit pmo.conceptdash.ca.

  • Schedule Risk in Mega-Programs: Leading Indicators That Prevent Delay

    The Schedule Failure Pattern

    After managing rail corridor projects, highway rehabilitation programs, and billion-dollar transit delivery at Metrolinx, I have observed a consistent pattern in schedule failures on large infrastructure programs: the delay is visible in the data long before it is acknowledged in the report.

    The projects that finish late almost always showed warning signs six to twelve months before the delay became undeniable. Those warning signs were present in the schedule data, in the procurement lead time tracking, in the RFI log, and in the change order trend analysis. But the systems that would have aggregated those signals into an early warning were absent, or the culture that would have surfaced the warning to decision-makers was not in place.

    The problem on most delayed mega-programs was not that the delay could not have been seen coming. It was that no one was looking for it systematically and honestly.

    The Difference Between Leading and Lagging Indicators

    A lagging indicator tells you what has already happened. Schedule performance index, actual progress against planned progress, percentage complete — these are lagging indicators. They tell you, with accuracy, that you are behind. They do not tell you why, or how far behind you will be at completion, or what to do about it.

    A leading indicator tells you what is likely to happen if current conditions persist. A leading indicator for schedule risk might be the trend in RFI response time — if the designer is taking three weeks to respond to RFIs that should be turned around in three days, that is a leading indicator of design coordination problems that will create field disruption in 4-8 weeks. Or the trend in planned versus actual drawing release dates — if drawings are consistently releasing two weeks later than the schedule requires, the construction activities dependent on those drawings are carrying two weeks of unplanned float that will eventually become a delay.

    Effective schedule risk management requires both, with an emphasis on leading indicators proportional to the time horizon of the program. A mega-program with 48 months of construction remaining needs a robust leading indicator system. A program with 6 months remaining needs lagging indicators — there is no longer enough time for leading indicators to produce actionable early warning.

    Critical Path Monitoring

    The critical path is the sequence of activities that determines the project’s completion date. Monitoring the critical path means monitoring the activities on that sequence — their progress, their resource loading, their dependencies, and the float that separates them from near-critical activities that could become critical if conditions change.

    On complex mega-programs, the critical path is not static. It migrates as work advances, as sequence changes are approved, as acceleration or de-acceleration of different work packages changes the relative timing of activities. A project control system that identifies the critical path at baseline and monitors it without reassessing which path is actually critical at any given point in the project lifecycle is providing false assurance.

    I built Project Management dashboards at Metrolinx that integrated critical path monitoring with a four-week lookahead schedule, current EAC variance reporting, and change order trend analysis. That integration — seeing critical path progress, near-term lookahead, cost trajectory, and commercial trend in a single view — is what enables proactive management rather than reactive reporting.

    Recovery Planning: When to Invoke It and How

    Recovery planning — the development and analysis of schedule recovery strategies — should be triggered by leading indicator signals, not by the point at which delay has become undeniable. When the leading indicators are trending negative and the critical path analysis shows a completion exposure, that is the time to develop recovery options — before the delay has materialized in the schedule record.

    Recovery options fall into several categories: acceleration of critical activities through additional resources or extended work hours; sequence changes that allow work to proceed in parallel rather than in series; scope adjustments that defer non-critical scope elements to reduce the critical path duration; and commercial mechanisms that realign incentives toward delivery performance.

    Each recovery option has a cost, a feasibility constraint, and a time horizon for effectiveness. Recovery planning is the analysis of which options are available, what they cost, and which combination produces the best balance of schedule recovery and cost exposure. It is a professional planning discipline, not a crisis response exercise. Treating it as the latter produces worse outcomes than treating it as the former.

    Building a PMO Control System That Catches Problems Early

    The organizational capability that makes leading indicator monitoring possible is the program management office — specifically, a PMO with the analytical capability to synthesize data from multiple systems into early warning signals, and the organizational authority to surface those signals to decision-makers without them being filtered by project teams protective of their schedule.

    The PMO design choices that matter most for schedule risk management are: independent reporting authority (the PMO should report to program leadership, not to the project team whose schedule it is monitoring), analytical depth (schedule analysts who can interrogate the programme rather than just read it), integration with procurement tracking (schedule risk almost always has a procurement component), and a cadence of honest schedule assessment that is separate from the project team’s status reporting.

  • The Right Stakeholders Problem: Why Governance Readiness Determines Progressive Contracting Success

    The Half of the Equation Nobody Talks About

    When infrastructure professionals discuss progressive contracting, the conversation focuses almost entirely on the model. Which framework? CMAR or Alliance? PDB or IPD? How do you structure the GMP? What does the pain/gain sharing look like? These are important questions. They are also, in my experience, only half the question.

    The other half — the half that actually determines whether the model delivers — is organizational readiness. The governance structures, decision-making culture, and stakeholder capabilities that sit behind the contract form.

    I have watched a well-designed progressive contract underperform because the owner’s organization was not set up to participate collaboratively. And I have seen a relatively simple delivery model produce excellent results because the right people were empowered to make decisions quickly and held accountable for outcomes. The model matters. The organization matters more.

    What Collaborative Preconstruction Actually Requires

    Progressive models are built on a core assumption: that the owner, the contractor, and the designer will work together during design to share information, solve problems jointly, and make better decisions than any one party could make alone. That assumption sounds reasonable. In practice, it requires something that many organizations do not have — a governance structure that actually allows people to make decisions in real time.

    If the owner’s organization requires every significant design decision to pass through three committees, two review panels, and a 60-day approval cycle, then the collaborative preconstruction phase that makes CMAR valuable becomes a bottleneck instead of an accelerator. The Construction Manager is ready to provide input. The designer is ready to iterate on design alternatives. But the owner’s internal process cannot keep pace with the tempo of collaboration that the contract is designed to produce.

    I saw this firsthand on a major North American transit program. The progressive contract was well-structured. The financial model was sound. The CM had genuine preconstruction capability. But the owner’s governance framework was built for a traditional procurement environment where decisions could be sequential and deliberate. When that framework met a contract model that demanded fast, empowered, collaborative decision-making, the friction was immediate and persistent. The governance did not adapt to the contract. The contract’s potential was constrained by the governance.

    The Contractor Readiness Problem

    Owner governance is not the only readiness gap. The contractor matters equally. A CMAR arrangement requires a Construction Manager with genuine preconstruction expertise — not just a general contractor who wants early project access and will figure out preconstruction deliverables as they go.

    Real preconstruction capability means cost estimators who can maintain an open-book rolling estimate as design evolves, constructability specialists who can review drawings critically and propose alternatives, procurement strategists who can identify long-lead risks and develop mitigation strategies, and schedule analysts who can build and maintain a construction programme that reflects how the project will actually be sequenced. When that capability is thin, the preconstruction phase becomes a billing exercise rather than a value creation exercise. The owner is paying preconstruction fees without getting preconstruction value. The result is a GMP that does not reflect reality, followed by construction phase surprises that should have been resolved during preconstruction.

    The Designer’s Cultural Shift

    The designer is the third party in the readiness equation. In a traditional design environment, the designer is the technical authority and the contractor is the party who builds what the designer specifies. That hierarchy does not serve a collaborative preconstruction process. The CM needs to be able to say ‘this will be very difficult to build as drawn’ and the designer needs to be willing to explore alternatives rather than defend completed design decisions.

    That cultural shift — from technical authority to collaborative partner — is one that not every design firm has made, and not every project team can make it mid-project if it was not established at the beginning of preconstruction.

    Assessing Readiness Before Selecting a Model

    For anyone evaluating which delivery model to use on their next program, my advice is direct: spend as much time assessing your organization’s readiness to execute a progressive contract as you do assessing which progressive contract to select. The best model in the world will underperform if the stakeholders behind it are not ready.

    That readiness assessment should cover decision-making authority (who can approve what, and how quickly), governance design (how will the collaborative management team be structured and empowered), procurement culture (can the owner’s procurement framework accommodate a qualifications-based selection), and organizational capacity (does the owner’s team have the bandwidth to actively participate in preconstruction).

    Getting this right at the beginning is cheaper than correcting it mid-program.

Powered by
►
Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
None
►
Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
None
►
Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
None
►
Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
None
Powered by