Something is changing in the way infrastructure professionals talk about their work — and it goes deeper than terminology. Two recent pieces from IPWEA signal a quiet but significant reorientation in how the sector thinks about what it is actually trying to achieve. For planners and asset managers, the implications are practical, not merely philosophical.
The question worth asking is: what does this shift actually demand of the people responsible for infrastructure investment decisions?
The Old Framing and Its Limits
For most of its modern history, infrastructure asset management has organised itself around the asset. Condition assessments, renewal forecasts, maintenance schedules, capital works programmes — the asset sits at the centre of nearly every planning workflow. It is a logical starting point. You can see an asset, measure it, model its deterioration, and assign it a value.
But as IPWEA CEO David Jenkins argued in late 2025, this framing carries a hidden cost:
"Our central question should not be about the asset."— David Jenkins, CEO, IPWEA Insite, December 2025
The asset-centred mindset tends to produce plans that justify renewal or replacement based on physical condition alone, without adequately connecting those decisions to what the asset is actually delivering for communities, economies, or ecosystems. You end up with technically defensible programmes that are strategically thin.
The outcome? Investment decisions that are well-documented but poorly aligned to what matters most.
Systems Thinking Enters the Room
A follow-up piece published in February 2026 pushed the argument further, drawing on systems thinking as a framework for understanding infrastructure not as a collection of discrete physical objects, but as an interconnected set of functions that together produce — or fail to produce — value for users and communities.
The aerial view of Sydney’s Rozelle Interchange under construction in 2023 serves as a striking illustration of this tension. A project of that scale is not simply a road. It is a node in a transport network, a land use trigger, a noise and amenity event for surrounding suburbs, and a long-term liability on public balance sheets. Viewed through an asset lens, it is a piece of civil infrastructure. Viewed through a systems lens, it is a bet on a particular vision of how a city should move and grow.
Systems thinking asks planners to map those connections explicitly — to understand how a decision about one asset propagates through a network of dependencies, and to evaluate investment options against the outcomes they enable, not just the conditions they correct.
Why This Matters Now
This is not an abstract debate. Several converging pressures are making the outcomes-and-systems framing genuinely urgent for infrastructure organisations:
Fiscal constraint is tightening. Capital budgets in local and state government are under sustained pressure. When renewal backlogs compete with growth infrastructure and community expectations continue to rise, asset managers can no longer afford plans that simply rank assets by condition score. Every dollar needs a justification that connects to service delivery.
Accountability is increasing. Governance frameworks are evolving. Councils and agencies are being asked — by auditors, by ministers, by communities — to demonstrate not just that they are maintaining assets, but that their asset portfolios are actually producing the services and outcomes they were built to provide.
Climate and resilience are reshaping risk profiles. A bridge in acceptable condition is not the same as a bridge that will remain serviceable after a one-in-fifty-year flood event. Condition-based planning does not capture that distinction. Outcome-based and systems-aware planning must.
Data capability is finally catching up. For decades, asset managers have known that broader systems analysis was theoretically correct but practically impossible. Data was too sparse, too siloed, and too slow. That is changing. The tools and data infrastructure to support genuine outcome-oriented planning are becoming accessible to organisations that were previously limited to spreadsheets and standalone asset registers.
The Language Problem Is Also a Process Problem
One underappreciated point in the IPWEA systems thinking piece is that the language we use shapes the processes we design — and the decisions we make. If your planning templates ask “what is the condition of this asset?” you will build an organisation that excels at answering that question. If your templates ask “what service does this asset enable, and is that service being delivered at the required level?”, you build something quite different.
This is not a trivial distinction for planners. It has real consequences for:
How investment options are framed. An outcome lens opens up non-asset solutions — demand management, service redesign, shared infrastructure, digital alternatives — that an asset-first process would never surface.
How trade-offs are communicated to decision-makers. “This bridge is at condition grade 3” lands very differently with elected members than “failure to renew this crossing within five years will isolate 2,400 residents from emergency services.” Both statements are true. Only one drives good decisions.
How long-term financial sustainability is modelled. Asset management plans grounded in outcomes can be directly connected to Long-Term Financial Plans in ways that condition-based plans struggle to achieve. The link between “what we manage” and “what it costs to maintain service levels” becomes explicit rather than assumed.
What Good Practice Looks Like in Transition
For organisations that recognise themselves in this critique but are not sure where to start, the path forward does not require wholesale reinvention. It requires a series of deliberate reorientations:
Start with service, not asset class
Map the services your community relies on — mobility, water access, open space, waste management — and work backwards to the assets that enable them. This simple inversion changes the shape of your planning conversations immediately.
Define levels of service with specificity
Vague commitments to “maintain roads to an acceptable standard” are not levels of service — they are deferrals of the hard conversation. Meaningful levels of service statements define what the community should experience, at what frequency, and to what degree of reliability. They create a basis for genuine investment prioritisation.
Connect asset risk to service risk
Not all asset failures are equal. A pothole on a low-traffic rural road and a pothole on a school access route may share a condition score, but they have entirely different consequence profiles. Organisations that model consequence — not just likelihood — make materially better investment decisions.
Build the language into governance artefacts
Asset Management Policies, Strategic Asset Management Plans, and Capital Investment Frameworks should reflect outcomes-oriented language explicitly. If the governance documents still organise thinking around asset class hierarchies, the cultural shift will not hold.
The Planning Tool Question
None of this is achievable at scale without planning infrastructure that supports it. Spreadsheet-based asset registers and siloed condition databases do not readily support the kind of cross-asset, service-outcome analysis that systems thinking demands. The gap between aspiration and capability is where many organisations stall.
This is precisely the problem that platforms like Modelve are designed to address. When asset data, financial modelling, scenario analysis, and strategic planning exist within a connected environment — rather than across a patchwork of disconnected tools — the shift from asset-centred to outcome-centred planning becomes operationally feasible, not just theoretically desirable. Planners can model trade-offs across service categories, stress-test investment scenarios against funding constraints, and communicate strategic choices with the clarity that governance and community engagement demands.
The technology is not the strategy. But without capable tools, the strategy remains a document rather than a practice.
A Moment of Genuine Opportunity
The shift being articulated by IPWEA contributors is neither radical nor new in concept — outcomes-based management has been discussed in public administration for decades. What is different now is that the conditions for actually implementing it are aligning: governance expectations are rising, data capability is maturing, and the cost of continuing with asset-only thinking is becoming more visible in poor delivery outcomes, strained balance sheets, and communities that feel unheard in infrastructure decisions that affect them.
For infrastructure planners, this is a genuine moment of professional opportunity. The organisations that move early — that reorient their planning frameworks, sharpen their service definitions, and invest in the tools to connect asset data to strategic outcomes — will be better placed to make the case for investment, to defend their programmes under scrutiny, and to deliver infrastructure that actually serves the communities that depend on it.
The language is changing. The practice needs to follow.
