Two budget conversations. The same underlying problem.

Two budget conversations. The same underlying problem.

Alicia Hue, MBA - Founder

Across more than a decade working with large and complex organisations through Australia, Singapore, Malaysia, and New Zealand, the same two conversations surface with remarkable consistency. In health networks, balancing the operational weight of running hospitals against the pressure to evaluate clinical and administrative technology. In the broader machinery of public administration, where federal and state institutions are navigating digital transformation mandates while managing the governance structures that regulate how decisions of that scale are made. In oil and gas and engineering environments, where asset integrity, safety-critical systems, and regulatory compliance frameworks mean the consequences of a poorly governed technology commitment extend well beyond the financial. The sectors differ significantly. The conversations are the same.

The first is about AI. A new initiative is on the table. Multiple vendors have presented, and each one is technically impressive in its own right. The use cases sound credible. The challenge is not finding technology that works in isolation. It is identifying which specific problem the organisation is actually trying to solve, and then determining whether any of the vendors' capabilities genuinely address that problem rather than a more interesting adjacent one.

In healthcare, this tension is particularly acute. A clinical decision support tool or an administrative automation platform each has its own vendor relationship, implementation timeline, and learning curve. For researchers, the proliferation of AI tools has created an entirely different problem. Each tool does one thing well, and the cumulative overhead of evaluating, onboarding, and integrating multiple fragmented tools is consuming the time and focus that should go to the science. The job is to do research. The tooling should serve that, not compete with it for attention.

In oil and gas, the stakes of evaluating the wrong technology are not primarily financial. A governance gap in a safety-critical or asset-integrity context has operational and regulatory consequences that a budget overrun cannot adequately capture.

What is consistent across all these environments is that the technology evaluation begins before the problem definition is precise enough to be evaluated meaningfully.

The second conversation is about cloud spend. Spend has grown, and leadership wants to understand why. As the environment gets worked through, the pattern becomes clear. The cost growth was not a decision. It was an accumulation. Resources were provisioned for a project that changed scope. Workloads that were never decommissioned. Commitments made at a point in time that no longer reflect how the organisation operates. This is worth pausing on because, for organisations that have not yet fully committed to the cloud and are already looking at AI, the lesson is the same. The governance discipline required to manage cloud spend well is the same discipline required to govern an AI investment well. The technology is different. The foundational work is not.

Different conversations. Same underlying problem.

In both cases, the organisation has activity without a clear decision. Reports without owners. Initiatives without accountability. Budgets were approved for outcomes that were never specifically defined. Steering committees convened regularly with no clear mandate to resolve anything. Teams are working hard in a direction that was never fully formed. Vendors selected before the problem arose. Researchers were asked to evaluate tools before the research question was sufficiently defined to know what a useful tool would even do.

This is a governance failure, and it is consistent across regulated sectors precisely because the pressure to adopt is high and the structures for governing that adoption have not kept pace. The 2025 Gartner CIO and Technology Executive Survey found that only 48% of digital initiatives meet or exceed their intended business outcomes. Gartner found that in organisations with high AI maturity, nearly 60% have centralised their AI strategy, governance, data, and infrastructure capabilities, compared to far lower rates in low-maturity organisations. The gap between investment and outcome is not a technology problem. It is a decision discipline problem. And it has been a decision-discipline problem throughout every major technology adoption cycle over the last two decades.

The organisations that get this right share a pattern.

DBS Bank in Singapore built a governance framework around four defined principles before scaling AI across the organisation, with a senior-level committee overseeing use cases before deployment. This approach reduced time-to-market for AI initiatives from 15 months to under 3 months.

Commonwealth Bank, ranked the top APAC bank for AI maturity in the 2024 Evident AI Index, built its governance architecture before scaling its deployment.

Both move quickly. They move quickly because the governance was built first. The same principle applies to a health network, a public-sector institution, an engineering firm, or a research environment. The discipline is the same. The prerequisite is the same.

That prerequisite is an internal willingness to define the problem before selecting the technology, and to build the decision structure before approving the budget. An advisory can help structure those conversations and give leadership the language to act. The willingness to have them has to come from inside the organisation first.

If this pattern is familiar across your sector, share it or leave a comment with what you have seen work or not work. The most useful perspectives in this space come from people who have been inside these environments and have navigated the gap between the investment case and the governance reality.

JR Advisory is opening late April bookings for scoping calls. Whether you're deciding on an AI investment, bringing accountability to cloud spend, or assessing governance before the next technology commitment, let's start the conversation at jradvisory.co.

Citations:

 

LinkedIn Follow the conversation on LinkedIn — Alicia Hue
Back to blog

Leave a comment