The Map Is Not the Territory: Why Sourcing Needs a Holistic Lens
How our obsession with frameworks and tools is blinding us to what actually makes sourcing work
There is a famous saying in philosophy and systems thinking: the map is not the territory. A map is useful — it helps you navigate, plan, and communicate. But it is always a simplification. It leaves things out by design. And if you forget that, you stop navigating reality and start navigating the map.
This tension sits at the very heart of modern sourcing practice.
Over the past few decades, the sourcing profession has produced an impressive arsenal of tools, frameworks, and methodologies. We have contract management systems, stakeholder mapping models, governance frameworks, and process libraries. Each one promises clarity, control, and optimisation. Each one, in its own way, is a map. And each one, if followed too faithfully, risks leading us away from the territory.
This is the story of reductionism in sourcing — and why it is time to look up from the map.
What Is Reductionism, and Why Does It Dominate?
Reductionism is the intellectual habit of understanding complex systems by breaking them into their component parts. It is the scientific method’s greatest strength: isolate variables, control conditions, and draw conclusions. It gave us modern medicine, aviation, and semiconductors.
It also gave us Gantt charts, ITIL process libraries, and RACI matrices.
In sourcing, reductionism is seductive because sourcing is genuinely complex. You are coordinating multiple organisations, managing contracts worth millions, aligning stakeholders with competing interests, and doing it all while the business keeps changing around you. Of course, you reach for tools that promise to impose order.
The problem is not that these tools exist. The problem is what gets lost when we mistake the tool for the reality it was designed to represent.
The Frameworks We Love — and What They Miss
CATS CM: Governance Without Soul
CATS CM (Contract Management) is a well-regarded methodology for structuring contract governance. It offers detailed guidance on contract lifecycle management, compliance obligations, relationship structures, and performance monitoring. For organisations drowning in unmanaged contracts, it can be genuinely transformative.
But look closely at what it optimises for: documents, obligations, and processes. What it cannot capture — what no contract management framework can fully capture — is why parties entered the agreement in the first place, what they actually need from each other, and what the relationship must feel like for both sides to invest in making it work.
A contract is not a relationship. It is a record of what two parties agreed to in a room on a particular day, based on incomplete information, under time pressure, with lawyers present. The moment the ink dries, the real work of the relationship begins — and that work is fundamentally human. It is about trust, communication, and the willingness to solve problems together when (not if) reality diverges from the contract. CATS CM has little to say about any of that.
Org Charts: Stakeholders Without Ecosystem
Stakeholder mapping is a staple of any serious sourcing engagement. Who are the decision-makers? Who are the influencers? Who has veto power? Draw them in boxes, connect them with lines, and assign colours to them based on their attitude toward the project. It feels rigorous and complete.
Except it is not complete. An org chart is a photograph of a moment in an organisation — a snapshot of formal reporting lines and designated roles. It does not show you the informal power networks, the colleague who has no title but enormous influence, or the executive who left six months ago but whose ghost still haunts every decision.
More fundamentally, it treats the sourcing engagement as a self-contained system. But sourcing never happens in isolation. Every supplier relationship is embedded in a wider ecosystem: other suppliers, other customers, market dynamics, regulatory environments, and industry relationships. The org chart gives you a view of a single room while ignoring the building it sits in — and the city around that building.
SIAM: Optimising the Machine at the Cost of the People Inside It
Service Integration and Management (SIAM) emerged in response to a real problem: as organisations disaggregated their IT services across multiple suppliers, coordination among them became a nightmare. SIAM offers a structured answer — a governance layer that manages dependencies, interfaces, and performance across the multi-supplier landscape.
In principle, this is sound. In practice, it can produce something deeply counterproductive.
SIAM works by standardising interfaces, clarifying accountabilities, and creating formal mechanisms for collaboration. What it tends to produce, if implemented without care, is a world where every interaction is mediated by process, every decision escalated through governance, and every supplier’s energy focused on managing the interface rather than solving the actual problem.
Human beings do their best work when they feel ownership of something and can see the connection between their effort and the outcome. When they are trusted to make decisions and held accountable for results. SIAM, in its more bureaucratic implementations, systematically erodes all of this. The complexity gets managed. The people inside the complexity do not thrive.
ITIL: The Process Religion
ITIL — the IT Infrastructure Library — is perhaps the most widely adopted framework in IT service management. It defines processes for incident management, change management, problem management, and dozens more. Organisations have spent enormous energy and money achieving ITIL certifications, implementing ITIL processes, and building ITIL-compliant tools.
And yet, anyone who has worked in IT services knows that the quality of those services depends less on the maturity of the processes than on the attitude and behaviour of the people delivering them. A team with high morale, strong ownership, and genuine care for the customer can deliver excellent service despite imperfect processes. A team that is disengaged, burned out, or politically fragmented will deliver poor service regardless of how well its incident management procedure is documented.
Sourcing is, at its core, a people business. It is conducted by people, for people, through relationships between people. ITIL’s instinct to formalise and proceduralize is useful at the margins — it creates consistency and sets minimum standards — but it can never be a substitute for the human qualities that make a sourcing engagement actually work: curiosity, empathy, judgment, and the willingness to go beyond the letter of the contract when the situation demands it.
We Have Seen This Movie Before
What is striking about the dominance of reductionist thinking in sourcing is that the rest of the world has already lived through the correction in other domains.
The Fall of Waterfall
For decades, software development was dominated by the waterfall model: define requirements in full, design the system, build it, test it, deliver it. It was logical, orderly, and deeply reductionist. It is assumed that complex software systems could be fully specified in advance, that requirements would remain stable, and that the best way to build something was to plan it exhaustively before touching a keyboard.
Reality had other ideas. Requirements changed. Assumptions proved wrong. The system delivered six months later was no longer the one the business needed. The industry learned, painfully, that software development is not a manufacturing process. It is an iterative exploration of a problem space involving constant learning and adaptation.
Agile development did not abandon structure — it adapted it. Agile frameworks like Scrum and Kanban are also reductionist, simplified models. But they are reductionist in a smarter way: they accept uncertainty, build in feedback loops, and treat collaboration and communication as first-class concerns rather than things to be eliminated through better planning.
The lesson was not “throw away the frameworks.” It was: “choose frameworks that are humble about what they can control and invest in the human conditions that make good work possible.”
Teal Organisations and the Limits of the Hierarchy
Frederic Laloux’s Reinventing Organisations documents a parallel awakening in management theory. The dominant model of organisational design for most of the twentieth century was hierarchical: clear reporting lines, defined roles, top-down decision-making, performance management through KPIs and cascading objectives. Like ITIL and SIAM, it was an attempt to make the complex manageable by breaking it into controllable pieces.
Laloux argues — and documents extensively — that this model, whatever its merits in the industrial age for which it was designed, is increasingly mismatched with the complexity, dynamism, and human needs of contemporary organisations. The organisations he calls “Teal” — characterised by self-management, wholeness, and evolutionary purpose — are not less structured than their hierarchical counterparts. They are differently structured, in ways that trust people more, activate more of their capabilities, and are more adaptive to complexity.
Again, the lesson is not “structure is bad.” It is: “structure that ignores the human beings inside it will eventually fail — not because it is wrong in theory, but because it is incomplete.”
Toward a Holistic Sourcing Practice
What would it look like to practice sourcing with a genuinely holistic lens?
It would not mean abandoning the tools. It would mean using them for what they are actually good for — creating a shared language, establishing minimum standards, reducing avoidable ambiguity — while being clear-eyed about what they cannot do.
A holistic sourcing practice would hold the following truths in tension:
- Contracts matter, but relationships are primary. The contract is the floor, not the ceiling. The real measure of a sourcing engagement is whether the parties trust each other enough to solve problems together when the contract does not have the answer, which is always.
- Stakeholders have formal roles and informal identities. The org chart tells you where people sit. It tells you nothing about what they care about, what they fear, what political dynamics shape their behaviour, or how they relate to the colleagues around them. Understanding the human behind the title is not a soft, nice-to-have. It is the actual work of stakeholder management.
- Governance enables, or it stifles. The right governance model is not the most comprehensive one. It is the one that gives people enough structure to collaborate effectively while preserving enough autonomy for them to take ownership and bring their full capabilities to bear. The question is never “what does the governance framework say?” but “what does this governance model do to the human beings who have to live inside it?”
- Culture eats process for breakfast. This phrase, often attributed to Peter Drucker, is a cliché because it is true. Process compliance is measurable. Attitude is not. But the empirical reality of every sourcing engagement is that the character of the people — their willingness to be honest, to take responsibility, to invest in each other’s success — matters more than process maturity. Invest accordingly.
- Every sourcing engagement is part of a larger story. The supplier you are managing today is also someone else’s customer, someone else’s partner, someone embedded in market dynamics, workforce constraints, and strategic priorities you may not fully see. The org chart you drew captures none of this. The humility to know that your model is partial — and to keep asking what you are missing — is not a weakness. It is the beginning of wisdom.
Conclusion: Hold the Map Lightly
The frameworks and tools of modern sourcing are genuinely valuable. They encode hard-won experience, create shared vocabulary, and help organisations avoid repeating the same mistakes. They are worth knowing and worth using.
But they are maps. The territory they represent is always richer, messier, more human, and more dynamic than any framework can capture. The moment we start treating the map as the territory — when compliance with the framework becomes the goal rather than the instrument — we have already started to lose our way.
The best sourcing professionals we have seen are not the ones who know the most frameworks. They are the ones who hold those frameworks lightly, using them as tools for thinking while remaining genuinely curious about the people, relationships, and ecosystem dynamics that no framework can fully capture.
In a world of increasing complexity and accelerating change, that combination of structure and human judgment, of method and wisdom, is not just a better sourcing practice.
It is the only kind that works.
What has your experience been with reductionist tools in sourcing? Have you found ways to use them while preserving what they miss? We’d love to hear your perspective.
AI supported in editing and illustrating this blog



