There's a particular kind of optimism that takes hold when an organisation decides to invest in a new warehouse management system or transport management system. The vendor demonstrations look impressive. The business case projects compelling returns. The implementation timeline seems manageable. And then reality arrives.

The warehouse team discovers the system doesn't handle their specific pick-and-pack processes without expensive customisation. The transport planners find the routing algorithms don't account for the access restrictions at half their delivery sites. The integration with the ERP turns out to be far more complex than anyone estimated. The go-live date slips. The budget expands. And six months after implementation, half the warehouse staff are still using workarounds because the system doesn't match how the operation actually runs.

This isn't a rare outcome. Industry data suggests that roughly 60% of WMS projects experience budget overruns or schedule delays, often because organisations underestimate the complexity of change management and system integration. Over 44% of companies report delayed return on investment due to prolonged integration timelines and training requirements. Average WMS implementation costs range from US$70,000 to US$500,000 depending on features and scale — before you account for the overruns.

The pattern for TMS implementations is similar. Organisations invest in sophisticated route optimisation and freight management capabilities, only to discover that the technology works brilliantly in the demonstration environment and poorly in the messy reality of their actual transport network, carrier relationships, and operational constraints.

None of this means the technology isn't valuable. WMS and TMS platforms, properly selected and implemented, transform warehouse and transport operations. They drive measurable improvements in productivity, accuracy, visibility, and cost performance. The problem isn't the technology itself — it's how organisations go about choosing and deploying it.

The selection problem: why organisations pick the wrong system

The most consequential mistake in any WMS or TMS project happens before a single line of code is configured — it happens during selection. And the root cause is almost always the same: the organisation starts with the technology rather than starting with the operation.

Vendor-led versus requirements-led selection

Most WMS and TMS selection processes begin when a vendor approaches the business, or when someone in the leadership team sees a compelling demonstration at a conference. The conversation immediately shifts to features, modules, and pricing tiers. What gets skipped is the hard, unglamorous work of understanding what the operation actually needs.

A requirements-led selection process starts differently. It starts with a thorough assessment of current warehouse and distribution operations — how goods flow through the facility, where the bottlenecks are, what workarounds the team relies on, where errors originate, and what the operation needs to look like in three to five years. It documents the non-negotiable functional requirements (the things the system absolutely must do on day one), the desirable capabilities (the things that would improve operations but aren't essential at launch), and the integration requirements (how the WMS or TMS needs to communicate with ERP, order management, carrier systems, and hardware like scanners, sorters, and printers).

This requirements work is what separates organisations that select a system well-matched to their operation from organisations that spend eighteen months and several hundred thousand dollars implementing a platform that was never the right fit.

The tier mismatch

WMS and TMS platforms exist across a spectrum from lightweight, cloud-based solutions designed for simpler operations through to enterprise-grade platforms capable of managing complex, multi-site, multi-channel operations with advanced optimisation, labour management, and automation interfaces.

One of the most common selection errors is a tier mismatch — either over-specifying (selecting a complex, expensive Tier 1 system for an operation that doesn't need or can't absorb that level of sophistication) or under-specifying (selecting a basic system that can't handle the operational complexity, forcing expensive customisation or an eventual re-implementation).

Getting the tier right requires an honest assessment of operational complexity — current and projected. A single-site operation running straightforward pick-pack-ship processes has fundamentally different requirements from a multi-site distribution network managing mixed B2B and B2C fulfilment, cross-docking, value-added services, and automation interfaces. The right system for one is the wrong system for the other.

Ignoring the integration reality

No WMS or TMS operates in isolation. It sits within an ecosystem of enterprise systems — ERP, order management, e-commerce platforms, carrier systems, yard management, and potentially warehouse automation control systems. The quality of these integrations determines whether the technology delivers its promised value or becomes a source of ongoing operational friction.

Yet integration complexity is consistently underestimated during selection. Organisations evaluate WMS and TMS platforms based on their standalone capabilities and assume the integration will be straightforward. It rarely is. Legacy ERP systems may lack the APIs or data standards needed for real-time integration. Data formats may be inconsistent. Business rules embedded in existing systems may conflict with the logic in the new platform.

A proper selection process evaluates integration requirements with the same rigour as functional requirements. It identifies the specific data flows between systems, the frequency and latency requirements for those flows, and the technical approach to integration — whether through middleware, direct API connections, or file-based exchange.

The implementation problem: where good selections go wrong

Even when an organisation selects the right system, implementation is where value is won or lost. The technology vendors have strong implementation methodologies. The challenge is that implementation is not primarily a technology project — it's an operational transformation project that happens to involve technology.

Process design before system configuration

The single most important principle in WMS and TMS implementation is this: design your processes before you configure your system, not the other way around.

Too many implementations begin with system configuration based on how the operation currently works. The team documents existing processes, configures the system to replicate them, and then wonders why the new technology hasn't delivered the step-change improvement they expected. The answer is obvious in hindsight — if you automate a bad process, you get a faster bad process.

Effective implementation starts with process redesign. Before the system is configured, the project team should define the target-state processes — how receiving, put-away, replenishment, picking, packing, shipping, cycle counting, and returns should work in the new environment. For TMS, this means defining how orders are consolidated, how loads are planned and optimised, how carriers are selected and tendered, how shipments are tracked, and how freight is audited and settled.

This process design work often reveals opportunities that the technology alone would never have surfaced — changes to warehouse layout, slotting strategy, pick methodology, wave planning logic, or transport routing that deliver benefits independent of the system. It also ensures that the system is configured to support the operation you want, not the operation you have.

Data readiness: the unsexy foundation

Every WMS and TMS implementation depends on clean, accurate master data — item masters with correct dimensions and weights, location masters with accurate capacity and constraint information, carrier rate tables, vehicle specifications, delivery windows, and customer shipping requirements. If this data is incomplete, inconsistent, or wrong, the system will produce incorrect put-away decisions, suboptimal pick paths, inaccurate load plans, and unreliable cost estimates.

Data migration and cleansing is consistently the least glamorous and most underestimated workstream in any implementation. It requires painstaking effort to audit existing data, identify and correct errors, fill gaps, and establish data governance processes to maintain quality post-go-live. Organisations that shortcut this work pay for it repeatedly in operational errors, workarounds, and lost confidence in the system.

Change management: the difference between go-live and adoption

A WMS or TMS goes live on a specific date. But going live and achieving adoption are very different things. Industry research indicates that 70% of software implementations fail to deliver expected results due to poor user adoption, and 63% of employees stop using technology if they don't see its relevance to their daily work.

In a warehouse environment, this translates directly to operational performance. If pickers revert to paper-based processes because the RF-directed workflow is confusing, you've spent hundreds of thousands of dollars on a system that isn't being used. If transport planners override the TMS optimisation because they don't trust it, you're paying for a planning tool that's functioning as an expensive spreadsheet.

Effective change management for WMS and TMS implementations requires investment in three areas. First, stakeholder engagement — involving warehouse supervisors, team leaders, and experienced operators in process design and system configuration so they understand and own the new way of working. Second, training — not generic vendor training, but role-specific training that shows each user exactly how the system supports their daily tasks, delivered close to go-live and reinforced in the weeks afterwards. Third, sustained support — recognising that the first four to eight weeks after go-live are when adoption is won or lost, and providing sufficient floor support, super-users, and rapid issue resolution to build confidence.

This is where project and change management capability makes the difference between a system that delivers its business case and a system that becomes an expensive source of operational frustration.

WMS and TMS: different systems, different challenges

While WMS and TMS share many of the same selection and implementation pitfalls, they present distinct challenges that warrant separate consideration.

WMS-specific considerations

Warehouse management systems are deeply operational — they direct the physical movement of goods through a facility, and their effectiveness is measured in real-time productivity metrics. Key considerations for Australian businesses include hardware dependency (WMS relies on scanners, mobile devices, label printers, and potentially automation interfaces — hardware selection and network infrastructure are implementation workstreams in their own right), warehouse layout and slotting (the system's performance depends on how well the facility is configured to support directed work — poor slotting or layout design will undermine even the best WMS), scalability for peak periods (Australian retail and FMCG operations experience significant seasonal peaks, and the WMS needs to handle peak volumes — including temporary labour using the system with minimal training — without degradation), and multi-channel complexity (organisations running B2B wholesale and B2C e-commerce from the same facility need a WMS that can manage fundamentally different fulfilment profiles without operational conflict).

The global WMS market is growing at roughly 19.5% CAGR, with cloud-based deployments gaining share rapidly. For Australian businesses, cloud WMS platforms offer faster deployment and lower upfront capital, but require careful evaluation of data sovereignty, network latency, and vendor support in Australian time zones.

TMS-specific considerations

Transport management systems operate across a broader ecosystem of carriers, routes, rates, and service levels, and their value depends heavily on the quality of data flowing in and out. Key considerations include carrier integration (a TMS is only as useful as its connectivity to your carrier base — Australian businesses often work with a mix of national carriers, regional operators, and specialist providers, and the system needs to accommodate this diversity), rate management complexity (Australian freight operates across a complicated rate structure involving zone-based pricing, weight breaks, fuel levies, accessorial charges, and contract-specific arrangements — the TMS must handle this granularity accurately or its cost calculations are meaningless), geographic and network challenges (Australia's vast distances, concentrated population centres, and thin regional freight networks create optimisation challenges that many TMS platforms — designed primarily for denser US or European markets — handle poorly without configuration), and visibility and exception management (the real value of a TMS often isn't in the initial load plan but in the ability to identify and manage exceptions — late pickups, missed deliveries, carrier capacity issues — in near real time).

The Australian context

Australian supply chain operations face specific challenges that influence both WMS and TMS selection. Our geographic distances make transport cost a larger proportion of total supply chain cost than in most comparable markets. Our concentrated population distribution — with the majority of demand in the eastern seaboard capital cities — creates particular network design dynamics. Our labour market — characterised by higher wages and increasing difficulty in recruiting warehouse and transport workers — makes the productivity improvements from well-implemented WMS and TMS especially valuable.

At the same time, the Australian market is smaller than the US or European markets that most WMS and TMS vendors are primarily designed for. This means that vendor presence, local support, implementation partner availability, and the depth of Australian reference sites all require careful evaluation. A system that works brilliantly for a 500,000-square-foot distribution centre in Ohio may not have the local support infrastructure to deliver the same experience for a 20,000-square-metre facility in western Sydney or Melbourne's south-east.

The sector matters too. FMCG and manufacturing operations have different WMS requirements from retail e-commerce fulfilment centres. Government and defence supply chains operate under compliance and security requirements that constrain technology choices. Health and human services organisations managing pharmaceutical or cold-chain distribution need specialised capabilities. A good selection process accounts for these sector-specific requirements rather than treating WMS and TMS as generic horizontal technologies.

What good looks like

Organisations that consistently deliver successful WMS and TMS implementations share several characteristics.

They invest in upfront requirements definition — spending eight to twelve weeks documenting operational requirements, integration needs, and future-state process designs before engaging with vendors. This investment feels slow at the start but dramatically reduces rework, scope creep, and misalignment later.

They run structured selection processes — evaluating a shortlist of vendors against weighted criteria, using scripted demonstrations based on their specific operational scenarios rather than the vendor's standard demo script, and checking references with comparable Australian operations. They include operational stakeholders in the evaluation, not just IT and procurement.

They treat implementation as an organisational change programme, not a technology installation. They appoint a business-side project lead with the authority and capacity to make decisions, assign experienced operators to the project team, and invest in change management from day one rather than bolting it on as an afterthought.

They plan realistic timelines and budgets — acknowledging that a typical WMS implementation for a mid-complexity operation takes six to twelve months, and a TMS implementation of similar complexity takes four to nine months, and that these timelines include process design, data preparation, integration development, testing, training, and post-go-live stabilisation. They budget for the full programme cost, not just the software licence and implementation services.

They stage their go-live — starting with core functionality, building confidence and competence, and then progressively activating more advanced features like labour management, slotting optimisation, or advanced transport planning. Trying to implement every feature simultaneously is how projects collapse under their own weight.

They also protect institutional knowledge during the transition. The experienced warehouse supervisor who knows every quirk of the operation is not an obstacle to the new system — they're the person who can tell you whether the configured processes will actually work on a Monday morning in peak season. Smart implementation teams capture that knowledge and build it into the system design.

And they define success in business terms — not "the system went live" but "pick productivity improved by X%, inventory accuracy reached Y%, transport cost per unit decreased by Z%." They track these metrics through go-live and hold the programme accountable for delivering the business case.

How Trace can help

At Trace Consultants, we help Australian organisations select and implement WMS and TMS platforms that actually deliver their business case. Our interest is in helping you choose the right system for your operation and getting the implementation right first time.

Our work in this space covers the full lifecycle. We start with operational assessment and requirements definition — working with your warehouse and transport teams to document how the operation runs today, where the pain points and opportunities are, and what the target-state operation needs to look like. This produces the functional and technical requirements specification that drives a rigorous selection process.

We then manage structured vendor evaluation — developing evaluation criteria, scripting vendor demonstrations around your operational scenarios, facilitating site reference visits, and conducting commercial analysis that goes beyond licence fees to evaluate total cost of ownership including implementation, integration, training, and ongoing support.

During implementation, we provide programme management, process design, and change management support — ensuring the project stays on track, the system is configured to support redesigned processes rather than replicate existing ones, and the organisation is ready to adopt the new way of working at go-live. We work alongside your team and the vendor's implementation consultants, providing the independent perspective that keeps the project focused on business outcomes.

We work across planning and operations, warehousing and distribution, procurement, and strategy and network design — which means we understand how WMS and TMS fit within the broader supply chain operating model, not just as standalone technology deployments.

We've supported WMS and TMS selections and implementations across FMCG and manufacturing, retail, resources and energy, health, and government — sectors where getting the technology right has direct, measurable impact on operational performance and cost.

If you're considering a WMS or TMS investment — or if you're partway through an implementation that isn't going to plan — get in touch. The difference between a technology investment that delivers and one that disappoints is almost always in the approach, not the software. We can help you get the approach right.

Trace Consultants is an Australian supply chain and procurement consulting firm. We help organisations select, implement, and optimise logistics technology — independently, practically, and with a relentless focus on operational outcomes. Visit our insights page for more on the challenges shaping Australian supply chains.

‍

There's a pattern we see repeatedly in Australian organisations attempting to transform their supply chains. It starts with a compelling case for change — costs are too high, service levels are inconsistent, inventory is bloated, planning is reactive rather than proactive. Leadership agrees something needs to change. A project is initiated. And almost immediately, the conversation turns to technology.

Which planning system should we implement? Should we move to a cloud ERP? What AI tools are available? Who are the leading vendors? Can we see a demo?

This is understandable. Technology is tangible. It can be evaluated, costed, and procured. It has a vendor behind it who will show up with a team and a project plan. It feels like progress. And in a world where 82% of supply chain organisations report increasing their IT spending, the expectation that technology will solve the problem is reinforced at every conference, in every analyst report, and by every vendor pitch.

But here's the uncomfortable truth that the data keeps confirming: the technology is rarely why supply chain transformations fail. McKinsey estimates that more than 70% of digital transformations fail to deliver their expected results. Gartner puts ERP implementation failure rates above 75%. BCG's study of over 850 companies found that only 35% of digital transformations meet their value targets globally. These aren't technology failures — they're failures of everything that surrounds the technology. Process redesign. Organisational change. Executive alignment. Capability building. Governance. The human side of transformation.

This article is about that human side — and why the organisations that get it right consistently outperform those that don't, regardless of which technology they choose.

The technology illusion

The technology market for supply chain management has never been more capable. Advanced planning systems can run probabilistic demand forecasts across thousands of SKUs. Digital twins can simulate network configurations before committing capital. AI-powered analytics can identify patterns in procurement data that humans would miss. Real-time visibility platforms can track shipments across global supply chains. The tools exist.

And yet, McKinsey's 2025 survey of 100 global supply chain leaders confirms that the majority of companies understand their supply chain risks only up to tier one — and that this visibility has actually deteriorated since 2022 as pandemic urgency faded. PwC's 2025 Digital Trends in Operations Survey found that 82% of operations leaders face challenges balancing short-term needs with long-term strategic change. Ninety percent expect supplier and material costs to increase significantly. The technology is deployed, but the outcomes lag.

The reason is what we might call the technology illusion: the belief that implementing a new system will, by itself, change how the organisation operates. It won't. A new planning system layered over a broken S&OP process will produce better-formatted reports about the same bad decisions. A new ERP implemented without redesigning the underlying business processes will, as one observer put it, simply automate chaos faster. A visibility platform that nobody trusts or acts on is an expensive dashboard.

We see this in Australia regularly. An organisation invests $5-15 million in a new ERP or planning platform. The implementation partner delivers the system on time and on budget. The project is declared a success. Six months later, planners are running the same spreadsheets alongside the new system because they don't trust the outputs. Procurement is processing purchase orders through the new platform but hasn't changed any of its sourcing processes. Warehouse operations have reverted to manual workarounds because the system configuration doesn't match how the warehouse actually operates. The technology was successfully implemented. The transformation never happened.

The organisations that succeed treat technology as an enabler of transformation, not the transformation itself. They invest as much — often more — in the process redesign, organisational change, and capability building that allow the technology to deliver its potential. The ones that fail treat the technology implementation as the project, and then wonder why nothing actually changed.

The five things that actually determine whether a transformation succeeds

1. Process redesign before system design

The single most cited cause of ERP and supply chain technology implementation failure is poor business process mapping. Organisations jump into implementations without thoroughly understanding or redesigning their current processes. The technology then gets configured to replicate existing workflows — including all their inefficiencies, workarounds, and dysfunction.

Lidl's experience is a cautionary example at scale: the German retailer spent an estimated €500 million over seven years on a SAP implementation before abandoning the project entirely and reverting to its legacy system. The failure was attributed not to the software but to an inability to reconcile the company's operating processes with the system's design philosophy.

In our experience at Trace, the organisations that succeed in supply chain transformation invest significant effort — often three to six months — in process design before making technology decisions. This means mapping current-state processes end to end, identifying where value is created and where waste accumulates, defining the target-state operating model, and only then determining what technology is needed to enable it. The technology selection follows the process design, not the other way around.

This is particularly important for planning transformations. The difference between a functional S&OP process and a dysfunctional one isn't the planning software — it's whether demand and supply planners collaborate effectively, whether commercial teams contribute meaningful demand signals, whether the executive S&OP meeting makes real decisions or just reviews slides, and whether the planning outputs actually drive operational execution. These are process and behavioural challenges, not technology challenges. The best APS in the world cannot compensate for a planning process where commercial and operations teams don't trust each other's numbers.

2. Executive alignment and sustained sponsorship

Insufficient executive sponsorship kills more supply chain transformations than technical issues. This isn't just about a CEO signing off on a business case. It's about sustained, visible leadership commitment through the difficult middle phase of transformation — when the old ways no longer work, the new ways aren't yet embedded, and the organisation is tempted to revert.

Supply chain transformation is inherently cross-functional. It touches procurement, manufacturing, logistics, commercial, finance, and IT. Each of these functions has its own priorities, its own metrics, and its own definition of success. Without executive alignment on what the transformation is trying to achieve — and a willingness to resolve the trade-offs that inevitably emerge — the project fractures along functional lines.

PwC's survey found that 82% of operations and supply chain leaders face challenges balancing short-term needs with long-term strategic changes. This tension plays out in transformation programmes constantly: the supply chain director wants to transform planning processes, but the sales director won't release commercial staff for the S&OP redesign because they have quarterly targets to hit. The CFO approved the business case but now wants to cut the change management budget because Q3 results are soft. The IT department insists on a different technology platform than the one the supply chain team evaluated.

The organisations that navigate this successfully have a senior executive — ideally at C-suite level — who owns the transformation outcome (not just the project), who has the authority to resolve cross-functional conflicts, and who maintains visible engagement throughout the multi-year programme. In our experience, transformations without this level of sponsorship have a near-zero success rate, regardless of how good the technology or the implementation partner is.

3. Change management as a core workstream, not an afterthought

Deloitte has identified change management as the single biggest failure point for ERP and supply chain transformation projects, citing the critical people-related challenges that leaders face at every stage. Research suggests that 70% of all software implementations fail due to poor user adoption. Forty-five percent of employees say new software is introduced without adequate training, and 63% will stop using new technology if they don't see its relevance or receive help.

Yet in most supply chain transformation budgets, change management is a fraction of the investment — if it's budgeted explicitly at all. The technology licence, the implementation partner fees, and the data migration dominate the cost structure. Training is compressed into a few sessions near go-live. Communication is limited to project updates in the company newsletter. The organisational redesign that should accompany the new ways of working is deferred because it's "too disruptive."

Effective change management in supply chain transformation involves several elements. Stakeholder analysis and engagement from the outset — understanding who will be affected, what their concerns are, and how to bring them on the journey. Role and process redesign — defining explicitly how each role changes under the new operating model, and ensuring people understand and accept their new responsibilities. Capability building — not just system training (how to use the tool) but process training (how to work differently) and analytical training (how to interpret and act on the new information available). Communication that goes beyond project updates to address the "what's in it for me" question that every affected employee is asking. And sustained reinforcement after go-live — because the hardest phase of any transformation is the three to six months after implementation, when old habits reassert themselves and the system hasn't yet proven its value.

At Trace, we've seen organisations that invest 15-20% of total transformation spend on change management consistently outperform those that invest less than 5%. The delta isn't marginal — it's often the difference between a transformation that delivers its business case and one that becomes an expensive technology deployment with no measurable impact.

This is especially true in supply chain, where the people affected by the transformation are often the most operationally critical. Warehouse managers, demand planners, procurement specialists, logistics coordinators — these are the people who keep the supply chain running day to day. If they don't understand, accept, and adopt the new ways of working, no technology investment will deliver its promised returns. And unlike office-based knowledge workers who might adapt to a new CRM, supply chain professionals operate under real-time pressure where a clunky workaround today means a missed shipment tomorrow. The stakes of poor adoption are immediate and visible.

4. Data foundations that actually support decision-making

There's a common assumption that implementing a new system will fix data problems. It won't. If your master data is inconsistent, your demand history is unreliable, your inventory records are inaccurate, and your cost data doesn't reflect reality, a new system will simply process bad data faster and present it more attractively.

Panorama Consulting found that 23% of ERP projects exceed budgets, with half requiring additional technology that nobody planned for and 40% discovering organisational issues that should have been obvious from the start. Much of this unplanned effort relates to data: the migration, cleansing, and harmonisation work that nobody fully scoped because it's unglamorous and hard to estimate.

In supply chain transformation specifically, the data challenge has several dimensions. Master data harmonisation — ensuring consistent product hierarchies, supplier records, customer classifications, and location data across business units. Demand data quality — ensuring the demand history that will feed new planning algorithms actually reflects true demand rather than constrained shipments, one-off promotions, or data entry errors. Inventory accuracy — ensuring the system's view of inventory matches physical reality, which for many organisations means investing in cycle counting, warehouse management processes, and potentially warehouse technology before a planning system can be effective. Cost data integrity — ensuring that the cost models driving procurement, make-or-buy, and network design decisions reflect actual costs rather than averaged or allocated figures that obscure the true economics.

This data work isn't optional, and it can't be deferred until after the technology is implemented. It needs to run in parallel with — or ideally ahead of — the system implementation. Organisations that treat data readiness as a prerequisite rather than an afterthought dramatically reduce implementation risk and accelerate time to value.

In practice, this means appointing data owners for each critical data domain well before the implementation begins, establishing data governance processes that will persist after the project, investing in the often tedious work of data cleansing and standardisation, and testing the new system with real data — not sanitised test data — before go-live. The organisations that do this well often find that the data remediation effort alone delivers value, because clean, consistent data improves decision-making even in existing systems.

5. Organisational design that reflects the new operating model

Supply chain transformation changes how work gets done, which means it changes what skills are needed, how roles are defined, and how the organisation is structured. Yet many transformations leave the organisational design unchanged — implementing new technology and processes within the same reporting structures, role definitions, and capability profiles that existed before.

This creates a predictable set of problems. New planning processes require analytical skills that existing planners don't have — but there's no plan to recruit, develop, or supplement that capability. Cross-functional processes like IBP require regular collaboration between demand planners, supply planners, commercial managers, and finance — but the organisation still operates in functional silos with no shared forums or decision-making processes. The new operating model requires someone to own end-to-end supply chain performance — but accountability remains fragmented across procurement, manufacturing, logistics, and customer service.

McKinsey's research on successful enterprise platform transformations highlights that the organisations that deliver sustained value combine technology implementation with cross-functional working groups, capability building, and a continuous improvement culture. The technology is the platform, but the organisational design is what determines whether the platform generates value.

In Australia, this challenge is compounded by the structural talent shortage in supply chain and operations. With 90% of supply chain leaders globally reporting their companies lack the necessary talent and skills to achieve digitisation goals, the gap between what the new operating model requires and what the existing workforce can deliver is often substantial. Closing that gap requires a deliberate capability strategy — combining recruitment, development, process simplification, and strategic use of external expertise — that runs alongside the technology implementation rather than being addressed after it.

The failure patterns we see most often

Having worked across dozens of supply chain transformation programmes in Australian organisations, we see several recurring patterns that lead to disappointing outcomes.

The vendor-led transformation. The organisation selects a technology vendor or implementation partner and then allows the vendor's methodology to define the transformation scope, timeline, and approach. Because the vendor's incentive is to implement the software (and bill consulting hours), the non-technology workstreams — process redesign, organisational change, capability building — are under-scoped or treated as secondary. The system goes live on schedule, but the business outcomes don't materialise because the surrounding transformation was never adequately addressed.

The IT-owned transformation. Supply chain transformation is positioned as an IT project with a technology-focused project manager and governance structure. Business stakeholders are consulted but don't own the outcomes. Decisions default to what's easiest to implement technically rather than what delivers the most business value. The result is a technically sound system that doesn't match how the business needs to operate — leading to workarounds, shadow systems, and frustrated users.

The big-bang approach. The organisation attempts to transform everything simultaneously — new ERP, new planning system, new warehouse management system, new procurement platform, new organisational structure — in a single programme. The complexity overwhelms the organisation's capacity to absorb change. Testing is compressed because the timeline is aggressive. Training is superficial because there's too much to cover. Go-live is chaotic, and the organisation spends the next 12-18 months stabilising rather than realising benefits. Research consistently shows that incremental approaches have significantly lower failure rates than these large-scale overhauls.

The underfunded change programme. The business case includes $10 million for technology and implementation but $200,000 for change management — essentially a communications plan and a few training sessions. The system is technically functional but user adoption is poor, process compliance is low, and the organisation gradually reverts to old ways of working. Twelve months after go-live, an internal review finds that the transformation hasn't delivered its expected benefits, and the finger-pointing begins.

The transformation without a target operating model. The organisation implements new technology without first defining the target operating model — including governance, decision rights, process ownership, performance metrics, and organisational structure. The technology gets layered onto the existing operating model, which wasn't designed for it. The mismatch creates friction, workarounds, and frustration, and the promised benefits of integration and visibility are never realised because the organisational design doesn't support them.

Each of these patterns is avoidable. But avoiding them requires recognising that supply chain transformation is fundamentally an organisational change programme that happens to involve technology — not a technology project that happens to affect the organisation.

What good looks like in practice

The organisations we've seen succeed in supply chain transformation — whether they're implementing a new planning system, redesigning their network, restructuring their procurement function, or building end-to-end visibility — share several characteristics that transcend the specific technology or initiative.

They start with the business problem, not the technology solution. The transformation is driven by a clear articulation of what needs to change in business outcomes — service levels, cost performance, working capital, resilience, agility — and the technology is selected and configured to deliver those outcomes. When McKinsey documented a successful enterprise platform transformation that identified over 40 operational initiatives worth approximately $250 million, the key difference from the company's previous failed attempt was that the successful effort focused on achieving combined business and IT benefits rather than treating it as a technology project.

They invest in process design before system design. Target-state processes are defined, tested, and agreed before the technology is configured. This means the technology is built to support the way the organisation wants to work, not the way it works today.

They budget realistically for change. The total cost of transformation includes not just the technology and implementation but the process redesign, data remediation, organisational restructuring, capability building, and sustained change management that determine whether the investment delivers returns. The best organisations we work with allocate 30-40% of total programme spend to these non-technology elements.

They sequence deliberately. Rather than attempting a big-bang transformation across the entire supply chain, they identify the highest-value, lowest-risk starting points, build capability and confidence, and expand from there. This mirrors the broader finding that incremental approaches show significantly lower failure rates than large-scale overhauls, because they reduce complexity and allow the organisation to learn as it goes.

They measure what matters. Success metrics are defined at the outset in business terms — not in project management terms like "on time" and "on budget" but in operational terms like forecast accuracy improvement, inventory days reduction, service level uplift, or cost per unit shipped. These metrics are tracked from before the transformation through to steady state, creating accountability for actual business impact rather than just system delivery.

And they sustain the effort after go-live. The three to six months after a system goes live is the most critical period — and the period most likely to be under-resourced because the project team has moved on and the organisation assumes the transformation is "done." In reality, this is when new processes need to be reinforced, when users need the most support, when workarounds need to be identified and eliminated, and when the benefits start to materialise (or don't). Organisations that maintain dedicated transformation support through this period consistently outperform those that don't. Successful companies also conduct formal post-implementation reviews — not to assign blame, but to capture what worked, identify what didn't, and feed those lessons into the next phase of the transformation or the next initiative. Without this discipline, the same mistakes are repeated across the organisation, and institutional learning from expensive transformation experience is lost.

What this means for Australian supply chains

Australian organisations face specific dynamics that make the non-technology dimensions of transformation even more critical.

Geographic dispersion means that supply chain processes must work across multiple time zones, climates, and operating environments — from dense urban distribution networks in Melbourne and Sydney to remote operations in Western Australia and the Northern Territory. Technology that works in a single-site pilot may not scale without significant process adaptation.

The concentrated supplier market means that procurement and supply chain transformations must work within the reality of limited supplier optionality. Transformations designed for markets with deep supplier bases need to be adapted for categories where there may be two or three viable suppliers nationally.

The talent challenge means that transformation programmes can't assume access to the specialist skills they need — whether in planning, analytics, technology, or change management. Capability building and knowledge transfer must be embedded in the programme design, not treated as something that happens organically.

And the scale of most Australian organisations — smaller than US or European peers in most sectors — means that transformations need to deliver value faster and with lower total investment. This argues for pragmatic, phased approaches rather than multi-year, enterprise-wide programmes that defer benefits while accumulating cost.

The good news is that this same scale can be an advantage. Smaller organisations can move faster, with shorter decision-making chains and less organisational inertia. Cross-functional alignment is easier to achieve when the supply chain director and the commercial director sit in the same office. Process redesign can be tested and refined quickly when there are dozens of users rather than thousands. The key is to design the transformation approach for the Australian operating context rather than importing a methodology designed for Fortune 500 scale.

This also means being realistic about the role of emerging technologies like AI and generative AI. While these tools offer genuine potential — particularly in demand sensing, spend analytics, and exception management — the foundational work of process design, data quality, and organisational alignment must come first. Organisations that rush into AI before their core processes and data are sound will repeat the same failure patterns that have plagued ERP implementations for decades, just with newer technology.

How Trace can help

At Trace, we help Australian organisations design and deliver supply chain transformations that actually work — by focusing on the business outcomes, process redesign, organisational change, and capability building that determine whether a technology investment pays off.

Our approach begins with understanding the business problem, not the technology landscape. We work with clients to define what good looks like in operational terms, design the target-state processes and operating model, identify the technology requirements that follow from that design, and then support the implementation with the change management, capability building, and governance that sustains the transformation.

We work across planning and operations, procurement, warehousing and distribution, strategy and network design, organisational design, and project and change management. We serve clients across FMCG and manufacturing, retail, government, health, and resources.

We're independent — we don't sell software, we don't take commissions from technology vendors, and we don't have implementation partnerships that bias our recommendations. When we advise on technology, our only interest is what will deliver the best outcome for your organisation.

If you're planning a supply chain transformation — or recovering from one that didn't deliver — get in touch. The technology is the easy part. Let us help you get the hard part right.

Trace Consultants is an Australian supply chain and procurement consulting firm. We help organisations transform their supply chains by getting the fundamentals right — process design, organisational change, capability building, and governance — so that technology investments deliver real business impact. Visit our insights page for more on the challenges shaping Australian supply chains.

‍

Ask most supply chain leaders what their operating model is, and you'll get one of two responses. The first is a blank look followed by something about the org chart. The second is a detailed description of their technology stack. Neither answer is right. An operating model is not an organisational structure, and it's not a set of systems. It's the blueprint for how a supply chain actually works — how decisions get made, where accountabilities sit, how processes connect across functions, what gets measured, and how people and technology work together to deliver outcomes.

Most supply chain operating models aren't designed. They're inherited. They evolve through a succession of reorganisations, system implementations, acquisitions, and responses to crises. The demand planning process works one way because that's how it was set up when SAP went in eight years ago. The procurement team reports to finance because of a restructure three CEOs ago. The warehouse operates semi-independently because it was an acquisition that was never fully integrated. Each individual decision may have been reasonable at the time. But the cumulative effect is an operating model that nobody designed, that doesn't align with the current business strategy, and that creates friction, duplication, and gaps that cost real money and slow everything down.

The McKinsey Global Supply Chain Leader Survey has consistently found that nine in ten organisations report supply chain challenges in a given year. Gartner's Future of Supply Chain 2025 report reveals that only 29% of supply chain organisations have embraced at least three of the five key characteristics that define future readiness. These numbers aren't just about external disruption. A significant portion of what organisations experience as supply chain "problems" are actually symptoms of an operating model that doesn't work — unclear decision rights, disconnected planning processes, misaligned metrics, and structural gaps between functions that should be working in lockstep.

This article is about what a well-designed supply chain operating model actually looks like, why it matters, and how Australian organisations can close the gap between what they have and what they need.

What an operating model actually is

A supply chain operating model answers a set of foundational questions that most organisations have never explicitly addressed.

The first is scope: where does the supply chain function begin and end? Does it include procurement, or does procurement sit elsewhere? Does it extend to customer fulfilment and last-mile delivery? Does it encompass manufacturing operations, or only planning and logistics? The answer varies by organisation, but what matters is that it's deliberate — that someone has consciously decided where the boundaries sit and how the interfaces across those boundaries work.

The second is governance: how do decisions get made? Who has authority over inventory policy? Who resolves the tension between customer service levels and cost? Who decides when to accept a customer order that the supply chain can't currently fulfil? Who owns the trade-off between holding safety stock and risking stockouts? In organisations without a clear operating model, these decisions either get escalated to people who don't have enough context to make them well, or they get made implicitly by whoever happens to be in the room — which leads to inconsistency, finger-pointing, and suboptimal outcomes.

The third is process: what are the core end-to-end processes, how do they connect, and who owns each one? A supply chain has a relatively small number of critical processes — demand planning, supply planning, procurement, order management, warehousing and distribution, and the integrating process that sits above all of them (typically S&OP or IBP). In a well-designed operating model, each process has clear ownership, defined inputs and outputs, established cadences, and explicit connections to the processes it feeds and that feed it. In most organisations, these processes exist but aren't connected — demand planning runs on a different cycle to supply planning, procurement operates independently of both, and the S&OP meeting is a monthly ritual where people share information but don't actually make decisions.

The fourth is organisation: how are people structured, and what capabilities does the function need? This is the piece most people jump to first — the org chart. But the org chart should be the output of the operating model design, not the starting point. Structure follows strategy, and in the supply chain, structure should follow the answers to the previous three questions. Get the scope, governance, and process design right, and the right organisational structure usually becomes obvious. Start with the org chart, and you're likely to design something that perpetuates the existing problems.

The fifth is technology: what systems and data are needed to enable the operating model? Again, technology should serve the model, not define it. The right technology configuration depends on what the operating model requires — which decisions need real-time data, which processes need to be automated, where manual intervention adds value, and how information needs to flow across functions and between the organisation and its suppliers, customers, and logistics partners.

And the sixth is performance: how does the organisation know whether the operating model is working? What gets measured, how frequently, and by whom? How are trade-offs between competing objectives — cost versus service, speed versus efficiency, risk versus cost — quantified and managed? Performance management sounds straightforward, but in practice it's where most operating models fall apart, because organisations measure activity rather than outcomes, or measure the right things but at the wrong level, or measure everything and therefore nothing.

Why it matters now

Australian supply chain functions are under more pressure than at any point in recent memory. The combination of tariff volatility, geopolitical complexity, rising customer expectations, sustainability reporting requirements, and persistent cost pressure means that the supply chain is being asked to deliver on multiple, often competing objectives simultaneously.

Gartner's research shows that 60% of C-level executives view the external environment as unfavourable to business performance, with reduced demand and accelerated inflation identified as the most significant pressures. CSCOs are being asked to shift from reactive cost-cutting to proactive cost leadership — which requires governance, transparency, and accountability that most supply chain operating models simply don't provide.

At the same time, the talent market is tight and getting tighter. Jobs and Skills Australia's 2025 Occupation Shortage List shows that 29% of assessed occupations are in national shortage. The Supply Chain and Logistics Association of Australia has highlighted an emerging "skills cliff" — not just a shortage of warehouse labour and truck drivers (which persists), but an accelerating gap in data analytics, automation, systems engineering, and the hybrid technical-operational roles that modern supply chains require. The World Economic Forum's 2025 Future of Jobs Report reinforces ongoing global shortages in supply chain skills. Companies that can't attract or retain talent in a tight market need an operating model that makes the most of the people they have — one that puts the right people in the right roles, eliminates waste in how people spend their time, and uses technology to amplify human capability rather than create additional administrative burden.

The organisations getting ahead are treating their operating model as a strategic asset, not an administrative inheritance. Gartner's research categorises the most successful supply chain organisations as following a "Design" pathway — proactively investing in long-term capability and deliberate strategy rather than reacting to short-term pressures. Those organisations have embedded agility, resilience, and integration as structural features of how they operate, not just aspirational goals.

The six elements of a well-designed operating model

1. A planning architecture that actually integrates

The heart of a supply chain operating model is its planning architecture — the set of interconnected processes that translate business strategy and customer demand into operational execution. In most organisations, this architecture has three layers: strategic planning (network design, capacity planning, long-range sourcing — typically 1-5 year horizons), tactical planning (S&OP or IBP, demand planning, supply planning — typically 1-18 month horizons), and operational execution (scheduling, order management, warehouse operations, transport — daily to weekly horizons).

The critical word is "interconnected." Each layer should feed and constrain the layers below it — strategic decisions about network configuration should shape the parameters within which tactical planning operates; tactical plans should set the guardrails for operational execution. And information should flow upward — execution reality should inform tactical plans, which should inform strategic reviews.

In practice, these layers are usually disconnected. Strategic network reviews happen once every few years (if at all). The S&OP process runs monthly but doesn't connect to the financial planning cycle. Operational execution proceeds largely independently, reacting to whatever arrives in the order book. The result is a supply chain that's perpetually misaligned — strategic intent doesn't translate into operational reality, and operational reality doesn't inform strategic direction.

The most mature organisations have evolved their planning architecture toward Integrated Business Planning, where demand and supply planning connects directly to financial planning and strategic objectives. McKinsey's research on mature IBP practitioners shows they enjoy meaningfully better performance on metrics including forecast accuracy, inventory turns, customer service, and margin. But achieving this requires more than implementing planning software — it requires redesigning how planning decisions actually get made, who's in the room when they're made, and what information those people have access to.

2. Clear governance and decision rights

The most common symptom of a dysfunctional operating model is that nobody knows who decides. Not in theory — most organisations have RACI matrices filed somewhere. In practice: when the sales team accepts a large order that exceeds available capacity, who decides whether to expedite production (at cost), delay other orders (with service impact), or push back on the customer? When inventory levels exceed target, who decides whether to adjust production, run promotions, or write down stock? When a key supplier signals a potential disruption, who decides how to respond?

In well-designed operating models, these decisions are pre-allocated. Decision rights are defined not just at the process level but at the decision level — and they distinguish between decisions that should be made locally (by the person closest to the situation), decisions that need cross-functional alignment (because they involve trade-offs between competing objectives), and decisions that need executive escalation (because they're material or precedent-setting).

This governance architecture also includes the forums where cross-functional decisions get made — S&OP meetings, supply reviews, risk committees — with clear terms of reference, decision authority, escalation pathways, and, critically, accountability for outcomes. Too many S&OP processes are information-sharing sessions, not decision-making forums. The difference between a functional and dysfunctional S&OP is not the quality of the data deck — it's whether real decisions get made in the room and whether the people making them have the authority and information to make them well.

3. End-to-end process integration

A supply chain operating model must define the core end-to-end processes and, more importantly, the interfaces between them. The processes themselves are well-understood: plan-to-produce, source-to-pay, order-to-deliver, forecast-to-fulfil. The SCOR model provides a useful reference framework, organising supply chain processes across five areas — plan, source, make, deliver, return — with standardised metrics at each level.

But knowing what the processes are is not the same as having them work together. The most common breakdowns occur at the handoffs: between demand planning and supply planning (where forecast assumptions don't translate into executable production plans), between procurement and operations (where sourcing decisions are made without understanding manufacturing constraints, or vice versa), between planning and execution (where the plan says one thing but the warehouse or transport team does something different because they lack visibility or capability to execute the plan), and between supply chain and commercial functions (where customer commitments are made without understanding supply implications).

Process integration means that each process has defined inputs, outputs, owners, and cadences — and that the outputs of one process reliably become the inputs of the next. It means that the interfaces between processes are explicit, governed, and measured. And it means that when processes change (because the business changes, or technology changes, or the external environment changes), the interfaces are deliberately redesigned rather than left to break.

4. An organisational structure that follows the model

Once scope, governance, and processes are defined, the organisational structure should reflect them. There are three broad archetypes for supply chain organisation, and the right choice depends on the business context.

A centralised model works best when products across business units are similar, when geographic concentration allows shared services, and when leverage and consistency are the primary objectives. Centralisation enables standardised processes, leveraged procurement spend, unified planning, and consistent performance management. But it can be slow to respond to local market conditions and can feel distant from the operational reality of individual business units.

A decentralised model works best when business units are genuinely independent — different products, different markets, different supply chain characteristics. Decentralisation enables responsiveness, local accountability, and deep category expertise. But it sacrifices leverage, creates duplication, and makes it difficult to share best practices or maintain consistent performance standards.

The model that works best for most multi-business-unit organisations in Australia is what practitioners call a centre-led or federated model — where a central supply chain function sets strategy, defines standards, manages enterprise-level processes (like S&OP and strategic sourcing), and governs performance, while business unit or regional supply chain teams execute within those frameworks with appropriate autonomy. Gartner's research reinforces this, recommending that CSCOs consider which activities need enterprise-level integration and which should be differentiated at the business unit level.

The centre-led model requires only a small central team — the authors of the CLAN (Centre-Led Action Network) concept estimated 3-4 people per functional discipline — but it requires that team to be highly capable, credible with the business units, and focused on value creation rather than compliance. The central team's job is to make the business units better, not to control them.

Regardless of archetype, the organisational structure must address capability. What skills does the function need? Where are the gaps? How will those gaps be closed — through recruitment, development, automation, or outsourcing? Given that supply chain skills remain in shortage in Australia (SEEK lists over 3,000 supply chain data analyst roles alone), the capability plan needs to be realistic about the talent market and creative about how to build capability in ways that don't depend solely on hiring people who don't exist in sufficient numbers.

5. Technology that enables rather than constrains

A supply chain operating model should define what technology is needed, not start with what technology is available. In practice, most organisations do it backwards — they implement an ERP system, a WMS, a TMS, and various planning tools, and then try to build an operating model around whatever those systems can do. The result is processes shaped by system limitations rather than business needs, workarounds in spreadsheets for what the system can't handle, and technology investments that don't deliver the intended value because the operating model wasn't designed to use them effectively.

The technology component of the operating model should address several questions. What data is needed to support the decision-making architecture? Where does that data come from, and how is its quality maintained? What processes should be automated (because they're high-volume, rules-based, and don't benefit from human judgement) versus technology-assisted (where technology provides information and recommendations but humans make the final call)? Where does end-to-end visibility need to extend — within the four walls, across the domestic supply chain, across the international supply chain, into the supplier base?

Gartner reports that 82% of CSCOs expect to increase investment in supply chain technology over the next two years, and 72% of supply chain organisations have deployed generative AI in some form. But most are experiencing middling results — because the technology is being layered on top of an operating model that wasn't designed for it. Investments in AI-driven demand sensing, control towers, or digital twins deliver their full value only when the underlying operating model defines how those tools integrate with decision-making processes, who acts on the insights they generate, and how their output connects to execution.

6. Performance management that drives behaviour

The final element is performance management — the metrics, targets, reviews, and incentives that tell people what matters and drive behaviour accordingly. This sounds simple but is routinely done poorly.

The most common mistake is measuring too many things. A supply chain dashboard with fifty KPIs measures nothing, because no one can manage fifty metrics simultaneously. A well-designed performance framework has a small number of top-level metrics (typically five to eight) that capture the essential trade-offs the supply chain must manage: cost efficiency (supply chain cost as a percentage of revenue, not an absolute dollar figure — Gartner's research emphasises this distinction), service performance (order fill rates, on-time delivery, customer satisfaction), asset efficiency (inventory turns, working capital, capacity utilisation), risk and resilience (supplier concentration, disruption response time, plan adherence), and increasingly, sustainability (Scope 3 emissions, waste reduction, circular economy metrics — with 67% of CSCOs now accountable for environmental and social sustainability KPIs according to Gartner).

Below these top-level metrics, more detailed operational KPIs cascade to individual process owners. But the cascade should be deliberate — each lower-level metric should connect logically to a top-level outcome, and people should understand the connection between what they're measured on and what the supply chain is trying to achieve.

Equally important is how performance is reviewed. The operating model should define the cadence and forums for performance review — from daily operational huddles to weekly tactical reviews to monthly S&OP meetings to quarterly business reviews. Each forum should have a clear purpose, the right attendees, the right data, and the authority to make decisions. And the performance framework should include explicit recognition that some objectives conflict — that pursuing cost reduction may reduce service, that increasing resilience may increase inventory, that sustainability investments may not have short-term financial returns. The operating model should define how those trade-offs are managed, not leave them to individual interpretation.

The common patterns we see in Australian organisations

Having described what good looks like, it's worth naming the patterns that most Australian organisations exhibit — not to be critical, but because recognising the pattern is the first step toward changing it.

The inherited model. The operating model was never deliberately designed. It evolved through successive reorganisations, system implementations, and leadership changes. Individual components may work well, but they don't connect into a coherent whole. Planning, procurement, logistics, and operations each optimise within their silo, and the end-to-end result is suboptimal.

The ERP-shaped model. The operating model is defined by what the ERP system does. Processes follow system workflows rather than business logic. Planning tools are used for transaction management rather than decision support. The system dictates the operating cadence rather than the business need determining what the system should do.

The person-dependent model. The operating model works because of specific individuals who bridge the structural gaps through personal relationships, institutional knowledge, and sheer effort. When those individuals leave — which in a tight talent market, they increasingly do — the gaps they were papering over become immediately visible.

The strategy-execution gap. The organisation has a supply chain strategy, often articulated in a well-crafted presentation. But the operating model — the processes, governance, structure, and capabilities that would need to exist to deliver that strategy — hasn't been designed. The strategy says "demand-driven," but the planning process is still forecast-push. The strategy says "customer-centric," but service levels are managed by product rather than by customer segment. The strategy says "integrated," but procurement, operations, and logistics still report to different executives with different incentives.

The perpetual firefighting model. Teams spend most of their time reacting to urgent operational issues — stockouts, delivery failures, supplier problems, quality issues — and have no bandwidth for the strategic and tactical work that would prevent those issues from recurring. This pattern is self-reinforcing: because there's no time to fix the root causes, the fires keep burning, which consumes more time, which leaves even less capacity for improvement. Breaking this cycle requires a deliberate redesign of how the function spends its time — which is fundamentally an operating model question.

How to get from here to there

Designing or redesigning a supply chain operating model is a significant undertaking. McKinsey estimates that a typical supply chain transformation is an 18-24 month effort requiring motivated leadership, careful sequencing, and substantial investment in change management. It shouldn't be approached lightly — but it shouldn't be deferred indefinitely either, because the cost of operating with a dysfunctional model accumulates every day.

The practical approach involves several phases.

Diagnose the current state honestly. Map the existing operating model — not how it's documented, but how it actually works. Where do decisions actually get made? What processes actually run, on what cadence, with what inputs? Where are the disconnects, duplications, and gaps? Where do people spend their time, and how much of that time is on value-adding work versus firefighting and administrative overhead? This diagnostic phase requires honesty and a willingness to hear uncomfortable truths from the people who live within the current model every day.

Define what the operating model needs to deliver. Start with the business strategy and the supply chain strategy, and translate those into specific requirements for the operating model. If the strategy requires demand-driven responsiveness, the operating model needs short-cycle planning, real-time demand sensing, and flexible execution capability. If the strategy requires cost leadership, the operating model needs rigorous performance management, leveraged procurement, and process standardisation. If the strategy requires resilience, the operating model needs risk visibility, scenario planning capability, and pre-defined response protocols.

Design the target model. Work through the six elements — scope, governance, process, organisation, technology, performance — in sequence. Design the model from the outside in: start with what external outcomes the supply chain needs to deliver (customer service, cost position, working capital, risk profile, sustainability), then design the processes that deliver those outcomes, then the governance that ensures those processes work, then the organisation that staffs them, then the technology that enables them, then the performance framework that manages them.

Plan and execute the transition. A new operating model can't be implemented overnight. It requires a phased approach — prioritising the changes that will have the greatest impact, sequencing structural and process changes so they reinforce each other, investing in training and capability development to ensure people can operate effectively in the new model, and managing the change explicitly through communication, engagement, and support. This is where most operating model redesigns fail — not in the design, but in the execution. The design is intellectually satisfying; the change management is hard, human work.

Embed and continuously improve. An operating model isn't a one-time exercise. It should be reviewed periodically — particularly when the business strategy changes, when significant external changes occur (new markets, acquisitions, regulatory shifts), or when performance data indicates the model isn't delivering as intended. The best operating models include feedback loops that allow for continuous adjustment, not just periodic redesign.

How Trace can help

At Trace, we work with organisations across FMCG and manufacturing, retail and consumer, resources and energy, health and human services, and government and defence to design and implement supply chain operating models that actually work. Our engagements span operating model diagnostics, planning and operations process design (including S&OP and IBP), organisational design and capability assessment, governance framework design, technology strategy and selection, performance framework development, and the change management required to make it all stick.

We're independent — we don't implement ERP systems, sell planning software, or have commercial relationships with technology vendors. That means our operating model recommendations are driven by what your business needs, not by what a particular software platform can do.

We've written previously about why supply chain AI projects fail — and one of the core reasons is that organisations layer technology onto broken operating models and wonder why they don't get results. We've also explored the real cost of reshoring and the most common supply chain problems in Australia. In each case, the operating model is a central factor in whether organisations navigate these challenges well or poorly.

If your supply chain operating model was inherited rather than designed — or if it was designed for a business that no longer exists — it's worth the investment to get it right. Get in touch to discuss how we can help.

Trace Consultants is an Australian supply chain and procurement consulting firm. We help organisations design and deliver supply chain operating models that connect strategy to execution — grounded in deep operational experience and independent of any technology vendor or platform. Visit our insights page for more on the challenges shaping Australian supply chains.

‍