When Your ICT Procurement Function Isn't Broken, It's Just Irrelevant

You've got the frameworks. You've mapped the processes. You might have even hired consultants who delivered elegant transformation roadmaps in beautiful slide decks.

Yet your IT procurement function still gets bypassed. Technology decisions happen without you. By the time procurement sees a requirement, the vendor's already been chosen and someone's asking you to "just process the paperwork."

Sound familiar?

This article is written for CTOs, IT General Managers, Transformation Managers, and senior IT leaders in Australian organisations who suspect their ICT procurement function could deliver more value but can't quite articulate why it isn't.

The problem isn't usually what you think it is.

The Misdiagnosis That Wastes Six Months

Most procurement transformation efforts start with an audit. Someone maps your current state, identifies gaps, and produces recommendations around:

• System consolidation and technology upgrades
• Process standardisation and documentation
• Capability frameworks and training programs
• Governance structures and approval hierarchies
• Metrics dashboards and reporting cadences

These things might all be legitimate needs. But they're symptoms, not causes.

Here's what these diagnostics consistently miss: if your business fundamentally sees IT procurement as order-takers, cost police, or compliance gatekeepers, no amount of process improvement will change that perception.

You can't rebuild trust with a Gantt chart.

What Actually Keeps ICT Procurement Irrelevant

The dysfunction usually looks like this in practice.

Your technology teams make architecture decisions without procurement input because "we're just exploring options." By the time procurement gets involved, you're negotiating at the margins of a deal that's already been shaped by someone else's conversations.

Your IT leaders don't loop procurement into early strategic discussions because previous interactions felt like interrogations rather than collaborations. Procurement asked for three quotes when the technical requirement clearly pointed to one vendor. They questioned decisions without understanding the technology context.

Your budget planning happens in isolation. IT forecasts spending, finance allocates budget, and procurement only sees the requirement when someone's ready to buy. No opportunity to shape demand, consolidate spend, or identify commercial risks before they're baked into commitments.

Your procurement team measures themselves on savings percentages while your IT leaders measure success on speed to capability. These misaligned metrics create friction at every interaction. Procurement wants to run a tender. IT needs to start the implementation next month.

None of this means your procurement people are incompetent. It means they're operating in a structure where relevance is nearly impossible.

The Interventions That Actually Shift Perception

Fixing this doesn't require a multi-year transformation program. It requires targeted interventions that change how people experience procurement.

Kill the theatre. Most procurement functions have "strategic initiatives" that sound impressive but deliver nothing. Supplier relationship management frameworks that nobody uses. Category strategies that sit in SharePoint. Risk assessment templates that add paperwork without adding insight. Cut them. Immediately. Every initiative that exists for its own sake damages credibility.

Change the entry point. The problem with most ICT procurement processes is they start too late. Instead of engaging at tender stage, create one simple rule: any technology spend above a meaningful threshold (say $50k in Australia) requires procurement involvement at concept stage. Not to approve. Not to audit. To advise. This single change repositions procurement from approver to advisor.

Stop measuring the wrong things. Savings percentages create perverse incentives. They reward delay (more time to negotiate) and punish speed (less time to shop around). Start measuring speed to value instead. How quickly did we get from concept to contract? How much effort did the business have to expend? How confident are we that we've mitigated commercial risk? These metrics align procurement with what IT leaders actually care about.

Show up where decisions happen. Embed procurement in budget planning conversations, not as approvers but as commercial advisors. When IT leaders are forecasting their technology roadmap, procurement should be identifying commercial opportunities, flagging vendor risks, and shaping how requirements are structured before they become purchase orders. This is where strategic ICT procurement influence actually happens.

Prove value in small doses. Don't try to transform everything at once. Pick one technology category where procurement can demonstrably add value and do it well. Maybe it's your cloud infrastructure renewal. Maybe it's standardising your hardware refresh approach. Show IT leaders that procurement involvement leads to better commercial outcomes without slowing them down. Then expand from that foundation of demonstrated capability.

What Good Looks Like in Practice

When this works, the conversation changes.

Your CTO starts asking procurement to join architecture discussions because they want commercial input on build versus buy decisions before the technical design is locked in.

Your transformation managers voluntarily include procurement in project kick-offs because they've learned that early commercial thinking prevents problems later.

Your IT General Managers reference procurement advice in budget papers because it's genuinely useful context for investment decisions.

Your CFO starts saying things like "I can't imagine making these technology decisions without procurement input now."

None of this requires procurement to become technology experts. It requires them to be credible commercial advisors who understand enough about IT context to ask useful questions and spot risks that technical teams might miss.

Why This Matters for IT Procurement in Australia

Australian organisations face particular challenges here.

Your local IT talent market is tight, making speed to capability critical. You can't afford procurement processes that add months to technology decisions.

Your vendor landscape is increasingly complex, with local subsidiaries of global vendors, direct relationships, and channel partners all offering different commercial models. Navigating this requires procurement capability that understands technology, not just purchasing.

Your regulatory environment around data sovereignty, privacy, and security means technology contracts carry genuine risk. Generic procurement approaches that work for facilities or professional services often miss critical ICT considerations.

Most Australian IT leaders are running lean teams. You don't have capacity for procurement dysfunction. If the function isn't adding value, it's costing you time you don't have.

The Uncomfortable Truth About Transformation

Here's what most procurement transformation programs won't tell you.

If your business has learned to work around procurement, they're probably getting adequate outcomes. Not optimal, but adequate. Your technology teams have figured out how to move at the pace they need. Your vendors have learned how to navigate your organisation.

The problem is what you're leaving on the table.

Commercial risk you haven't properly mitigated because the contract review happened after commercial terms were agreed. Leverage you didn't exercise because spend was fragmented across business units. Vendor relationships you couldn't optimise because no one had visibility across the portfolio.

The cost of irrelevant procurement isn't dramatic failure. It's unrealised value that never shows up in any report.

Where to Start

If this resonates, the diagnostic you need isn't about procurement maturity. It's about business perception.

Talk to three IT leaders who regularly bypass procurement. Not to defend the function, but to genuinely understand why they make that choice. What would procurement need to do differently for them to voluntarily include it earlier?

Look at your last five technology sourcing activities. At what point did procurement first see the requirement? What commercial risks or opportunities existed before that point? What would have been different with earlier involvement?

Review your procurement metrics. Are you measuring things that matter to IT leaders or things that matter to procurement professionals? If your IT stakeholders don't care about your KPIs, they're the wrong KPIs.

Map where technology investment decisions actually happen in your organisation. Budget allocation, architecture reviews, business case approvals, vendor selections. Is procurement present at any of these moments? If not, why not?

This isn't comfortable work. It requires acknowledging that your current approach might not be working, regardless of how theoretically sound your processes are.

When Internal Capacity Isn't Enough

Sometimes the challenge isn't knowing what needs to change. It's having the bandwidth to actually drive that change while keeping the function operational.

Your procurement team is already underwater with tactical work. Your IT leaders don't have time to fix someone else's function. Your transformation managers are focused on technology initiatives, not procurement redesign.

This is where targeted external support can provide the capacity and credibility to make change happen without becoming another multi-year program that delivers PowerPoints instead of results.

The Bottom Line

Your IT procurement function probably isn't broken. The processes might be fine. The people might be competent.

The problem is relevance.

And you can't fix relevance with process documentation, system upgrades, or capability frameworks. You fix it by changing how your business experiences procurement, one interaction at a time.

That requires less theatre and more substance. Less audit and more advice. Less measurement of savings and more demonstration of value.

Most procurement transformations fail because they try to fix procurement in isolation. The successful ones recognise that the real work is changing how the business uses procurement.

If your technology teams are making decisions without procurement input, that's not a sign that they're rogue. It's a sign that procurement hasn't yet proven why it should be in the room.

The good news? That's fixable. But only if you're willing to acknowledge the real problem.

This article provides general commercial and procurement commentary only and does not constitute legal, financial, or professional advice.