Aligning Functional Organisational Design to Company Culture & Markets (Part II)
This is the second post in the mini-series on organisational design. Part 1 covered Corporate Headquarters design. Here, we look at functional design, using Procurement as the case study. Most of what follows applies equally to other operational functions - Sales, Planning, Service, Manufacturing - with appropriate adjustments for context.
The central argument is the same as in Part 1: if you design your organisation in alignment with its culture and surrounding markets, you can significantly reduce the costly cycle of redesign and reshuffling that most large companies experience every five to seven years.
The centralisation orthodoxy and why it broke down
Ask any senior procurement leader before 2010 what the right setup was, and the answer was almost always centralisation. The reasoning rested on two concepts that seemed self-evidently correct at the time.
The first was economies of scale: large volume drives down unit cost. For a long time, this was the primary lever for cost competitiveness in procurement. Today, with shorter product life cycles, smaller batch sizes driven by customer demand, and higher supply and demand volatility, applying this logic universally is like using a cannon to kill sparrows. The tool still works in specific circumstances - it is just not the universal answer it once appeared to be.
The second concept is what I call economies of skill: consolidating specialist category expertise in a central function, on the theory that deep market knowledge in a specific category drives better outcomes. In principle, this is sound. In practice, centralised category experts spend an increasing proportion of their time coordinating across the organisation rather than developing supply market knowledge. The more centralised the decision authority, the more time the best people spend in alignment meetings rather than in front of suppliers. I have rarely seen this model deliver on its theoretical promise in organisations of significant complexity.
Aligning functional design with the firm's organisational setup
The most important and most frequently ignored variable in functional design is fit with the overall organisational structure. When a company is genuinely decentralised, with business targets achieved through regional or business unit autonomy, procurement should be decentralised too. The modest gains from centralised bundling are consistently outweighed by the coordination costs, the latency, and - less discussed but equally real - the exclusion of central procurement staff from the management circles where actual decisions get made. The "Hi, I am from headquarters and here to help - please fill out my Excel sheet" joke exists because it describes a real and common dynamic.
Conversely, in highly centralised organisations, procurement centralisation makes sense - provided the supply markets are also centrally organised. If manufacturing and the supply base are still best served by local or regional relationships, a centralised procurement overlay adds cost and reduces access to innovation without delivering the promised efficiencies.
Aligning functional design with the firm's culture
Culture is the variable that gets the least analytical rigour in functional design decisions, yet it is often the most determinative of whether a design actually works in practice.
The framework I have found most useful comes from the book Die 3 Faktoren des Einkaufs by Schumacher, Schiele, Contzen, and Zachau (2008). It maps organisations on two dimensions: the degree of governance - whether leadership operates primarily through structure and process versus through targets and strong personalities - and the decision style - whether decisions are driven by hierarchy or by consensus. Once internalised, this framework allows you to assess quickly and reliably whether a proposed functional design will gain traction within the culture of a specific organisation.
Aspiring to centralised procurement in an organisation governed by individual business targets or consensus-based decision-making is a fool's errand. So is maintaining a decentralised setup within a process-driven, hierarchical organisation with the cultural infrastructure to make centralisation work. The mismatch between design aspiration and cultural reality is where most functional reorganisations fail.
A note on the hybrid model, which is often proposed as the solution that captures the best of both worlds: in my experience, it demands a disproportionate amount of energy from the CPO and procurement leadership to maintain the balance of forces across the organisation. It can work, but it is rarely worth the sustained effort required.
The dark side of functional design
No honest treatment of organisational design can ignore this. Some functional structures are built not around analytical logic but around the ego. Leaders who adopt Machiavellian approaches - building insular, hierarchical empires in functions or business units, relying on direction and autocracy rather than influence and cooperation - exist in every large organisation. Their structures tend to appear functional from the outside as long as the leader in question is performing. They ultimately fail, and when they do, the margin and cultural consequences for the company are real and lasting. As a colleague once put it: they starve the goose that laid the golden egg.
What is remarkable is that most modern HR processes remain poorly equipped to identify what psychologists call the dark triad of personality traits - Machiavellianism, narcissism, and lack of empathy - in candidates for leadership positions, despite the availability of straightforward assessment tools. This is a gap worth closing before the next leadership appointment, not after.
My preferred approach to functional design
There is no universal answer, but there is a principle that has held across my three-plus decades in operations, supply chain, and procurement across five industries: the most effective functional design consists of small, decentralised units operating interdependently within the larger organisational hierarchy, connected through a structured virtual knowledge network and governed by clearly defined swim lanes - payment terms, contracts, skill standards, training, functional career paths, and systems linked through centrally provided data lakes. This setup combines high agility with the coordination benefits that economies of scale and skill were originally meant to provide, without the costs and rigidities that centralisation tends to accumulate over time.
One exception: for fully centralised organisations, where that is the genuine culture and governance model, centralised functional design is correct and should prevail.
A word on span of control: procurement units - strategic sourcing teams, for example - should be large enough to reduce micromanagement by the layer above, but small enough to maintain effective communication and coordination internally. Anthropologist Robin Dunbar's research suggests that humans can maintain stable social relationships with around 150 people, with smaller groups being more effective in practice. For operational teams, five to twelve people is a well-supported working range. Bigger than that and cohesion starts to erode; smaller than that and the team is too fragile to absorb change.
Ten questions to assess the current state
Is your procurement organisation structurally aligned with the overall company organisation - whether centralised, by business unit, or by geography?
Does your supply chain experience minimal disruptions in terms of delayed deliveries and unexpected cost increases?
Is performance tracked consistently across the organisation, including cost reduction, supplier count, procurement-to-payment cycle time, and supplier sustainability metrics?
Is your procurement organisation competitive within your industry in terms of productivity and spend per employee, and are any deviations from the benchmark a deliberate and understood decision?
Do the divisions, business units, and functions across the company feel genuinely served by procurement, rather than processed by it?
Is procurement adequately funded relative to the spend it manages, validated by benchmarks rather than internal budget politics?
Is your supply base smaller relative to spend than your competitors'?
Is the procurement team incentivised based on the overall performance of the business area it serves, not just on procurement-specific metrics?
Is the corporate overhead for the procurement function below 10% of its total cost?
Does procurement report to a leader who has previously held the CPO role, or to a line with genuine procurement understanding - rather than being subordinated to supply chain leadership as a tactical afterthought?
A clear yes to most of those means the functional design is working. If most are no or unclear, the financial case for change is straightforward.
The size of the prize
In the short term, establish your annual cost reduction rate over the last three to five years. If it is running at 2 to 3%, a well-designed and culturally aligned procurement function should be delivering 4 to 5% - that delta is your gross margin improvement opportunity.
In the long term, the bigger prize is cross-functional. Set a joint target across sales, operations, and procurement for 5% or more gross margin improvement annually over three years, driven by cross-functional optimisation rather than functional silo work. Pair it with a transparent cost tool developed with finance so that the margin gains flow to EBIT and future investment rather than disappearing into budget absorption.
Setting up the programme
The timeline is 15 months: three months for blueprint design, twelve months for implementation. The board sponsor is the CEO or CFO. The lead is the Head of Procurement or Head of Operations.
Start by working with HR to establish an honest view of the firm's actual organisational and cultural design - not the aspirational version, the real one. Build the functional blueprint from there. After board agreement, run a weekly task force tracking clean output metrics: design finalised and approved, number of categories in new control, headcount in new design configuration, percentage of categories covered by category strategies, supplier reduction trend, and compliance with agreed swim lanes. Quarterly reporting to the management board by the CPO, with biannual reviews with business and regional presidents.
The digitalisation opportunity is medium. Large ERP systems are no longer the answer for organisational design support - that era has passed. With the right API architecture and process mining software, every system across the organisation can be connected to a central data lake, enabling optimisation spotting, compliance monitoring, and cross-sharing of supplier solutions.
The risk is low in the sense that procurement is, as I sometimes put it, like a bicycle: you will always get from point A to point B. The quality of the bicycle and the care you take of it determine how quickly and how much effort it takes. Getting the functional design wrong will not break the company, but it will cost gross margin and customer satisfaction while the correction is made.
Watch out for
Three failure modes deserve particular attention. Stopping implementation mid-way is the most common - the moment the design is announced, many people assume the change is done. It is not. Giving in to dark triad leaders in functions or business units during implementation will hollow out the new design faster than any structural error. And selecting the wrong functional leaders for the new setup is a silent killer - the old guard who performed well in the previous design is not automatically the right person to lead the next one.
Part 3 covers roles and responsibilities, competency frameworks, and job design - the level at which organisational design either becomes real or remains a set of boxes on a chart.
Stay safe. Be bold.
Daniel
The views expressed in this post are my personal professional opinions, based on research and publicly available information. They reflect analysis of industry trends and practices, not assertions of fact about specific companies or individuals. Nothing in this post constitutes legal, financial, or investment advice.
