Procurement is the mechanism through which a project decides who will create value, under what obligations, with which risks, and at what long-term cost.
A purchase order can look administrative. A procurement decision rarely is.
When a project acquires design expertise, equipment, construction capability, software, logistics or specialist services from outside the project team, it is doing more than buying an input. It is deciding which capability will sit inside the organisation, which capability will sit outside it, how performance will be specified, how risk will be shared, how knowledge will move and how much freedom the organisation will retain when circumstances change.
That is why weak procurement can undermine an otherwise competent project. The supplied Week 1 material makes the point directly: projects often outsource major deliverables, and poor specification or poor supplier delivery can materially affect the project outcome. It also describes procurement as a lifecycle activity that begins with defining needs and market analysis, continues through tendering and contract formation, and extends into contract performance, administration and finalisation.
The executive implication is simple: procurement belongs inside project strategy, not downstream from it.
The Strategic Context
The narrow view of procurement is transactional: identify a need, obtain quotations, choose a supplier and raise an order.
The broader project-management view is different. Procurement includes deciding whether external supply is appropriate, shaping the commercial strategy, selecting suppliers, forming contractual arrangements, managing changes, monitoring performance and closing the relationship. The Week 1 framework also distinguishes project procurement from operational procurement. Operational procurement supports continuing business activity; project procurement supports a temporary endeavour with a defined outcome, separate constraints and often a dedicated budget.
That distinction matters because project demand is often uncertain, temporary and interdependent. A supplier is not merely filling inventory. It may be designing an interface, installing a system, delivering a critical work package or contributing expertise that the project team itself does not possess.
Walker and colleagues extend this further. Their procurement-fundamentals chapter frames project management around value generation for customers and stakeholders and positions the make-or-buy decision at the heart of procurement. In that framing, procurement becomes a design choice about participation in value creation: who is best equipped to perform which part of the work, and how should those resources be engaged?
Related article: Why Procurement Decisions Shape Value Before the Contract Is Signed
What Leaders Commonly Misread
The first misreading is to equate procurement with purchasing.
Purchasing is a component of procurement. It is not the whole system. A project may purchase at an excellent unit price and still make a poor procurement decision if it selects the wrong sourcing model, fails to define the requirement, creates an unmanageable interface, transfers critical knowledge without protecting it, or accepts contract terms that make change expensive.
The second misreading is to assume that procurement responsibility sits entirely with a procurement department. The source material recognises that large organisations may have specialist procurement functions, while project managers coordinate the process. In smaller projects, the project manager may perform much of the work directly. Either way, the accountability for project outcomes cannot be outsourced to a function. The project leadership team still needs to understand what is being committed.
The third misreading is to treat contract award as the end of procurement. In reality, award changes the nature of the work. Before award, the focus is market engagement, selection and negotiation. After award, the focus becomes performance, interfaces, change, claims, payments, supplier relationships and eventual closure.
Reframing the Issue
A more useful executive question is not, “What do we need to buy?”
It is:
What capabilities and commitments must be assembled so that the project can reliably produce the intended outcome?
That reframing forces several questions to the surface.
Which work is strategically important enough to retain internally? Which work can be sourced as a commodity? Which interfaces could become failure points? What information must suppliers receive? What knowledge must the organisation retain? What decisions will be expensive to reverse? What happens if the selected supplier underperforms, exits or becomes commercially dependent on the project?
Procurement is therefore an operating model for a temporary enterprise.
A large project can involve clients, project managers, contractors, subcontractors, consultants, suppliers and specialist providers. Contracts connect these parties, but contracts alone do not make the system perform. The project also needs governance, clear decision rights, competent contract administration, reliable information and working relationships across organisational boundaries.
Procurement as an Enterprise System
Strategy determines the boundary
The first procurement decision is often a boundary decision: make or buy.
The source material describes this as a comparison between internal provision and external acquisition. Walker and colleagues add that cost is only one input. Strategy, transaction costs, risk, opportunity, capability and context also matter.
That moves make-or-buy away from a purchasing calculation and towards enterprise design.
Related article: The Executive Decision Behind Make-or-Buy
Planning converts strategy into an executable approach
Procurement planning asks what should be procured, when, in what quantity, through which process and with what documentation. It should follow strategic choices rather than substitute for them.
A project can have a detailed procurement schedule and still have a weak procurement strategy. Planning improves execution only when the underlying choices are sound.
Related article: Procurement Strategy Is Not Procurement Planning
Tendering converts requirements into a market decision
RFI, RFP and RFT processes are not interchangeable paperwork. They represent different forms of market engagement. The Week 1 framework presents tendering as a supplier-selection process supported by qualification, evaluation criteria, bidder information and solicitation documents.
The quality of the tender process therefore depends on whether the project knows what it is trying to learn or decide.
Contracts convert decisions into obligations
The supplied slides describe a contract as a mutually binding agreement that obligates the seller to provide specified products or services and the buyer to pay. More strategically, the contract allocates obligations, interfaces, commercial exposure and mechanisms for dealing with change.
A poorly designed contract can make an attractive supplier relationship difficult to manage. A well-designed contract cannot rescue a fundamentally wrong sourcing decision, but it can make responsibilities and responses clearer.
Governance protects value after award
Once work begins, procurement becomes a control system.
The project must compare supplier performance with requirements, manage changes, deal with claims and payments, coordinate interfaces, maintain records and preserve the commercial position of the organisation.
This is where procurement and project management become inseparable.
Decision Framework
Before treating an external requirement as a purchase, leaders can test it through six questions.
| Decision test | Executive question |
|---|---|
| Strategic relevance | Does this requirement affect a capability, asset or relationship that matters beyond the project? |
| Sourcing logic | Why should this work be external rather than internal? |
| Market capability | Does the market have suppliers able to meet the requirement reliably? |
| Interface risk | What must integrate with internal teams, systems or other suppliers? |
| Commercial control | How will performance, change, payment and failure be governed? |
| Lifecycle consequence | What remains after the contract ends: capability, dependency, knowledge, asset or obligation? |
If the team cannot answer these questions, it is not yet ready to reduce the issue to a requisition.
From Strategy to Execution
Immediate action: identify the project’s major externally sourced deliverables and classify them by strategic importance, value, uncertainty and dependency. Do not focus only on spend.
Medium-term capability: create a procurement decision process that connects business case, make-or-buy reasoning, market analysis, tendering, contract formation and post-award governance. Ensure project and procurement roles are explicit rather than assumed.
Long-term positioning: build organisational memory about supplier performance, sourcing outcomes, contract problems, hidden transaction costs and capability effects. Procurement quality improves when the organisation learns across projects rather than restarting from zero each time.
Signals to Monitor
Leaders should pay attention when procurement activity begins before requirements are stable, when supplier selection is dominated by price without lifecycle analysis, when project teams cannot explain why work is outsourced, or when contract award is treated as a hand-off to someone else.
Other warning signals include growing numbers of variations, ambiguous interfaces, repeated expediting, unplanned supplier dependencies, loss of internal technical knowledge and disputes that reveal expectations were never aligned.
These are not merely procurement problems. They are evidence that the project’s value-creation system is becoming unstable.
Questions for the Leadership Team
- Which externally sourced project components could materially affect enterprise capability or future strategic options?
- Where are we treating a sourcing decision as a purchasing transaction?
- Which supplier interfaces could cause failure even if every individual contract appears compliant?
- What knowledge must remain inside the organisation after project completion?
- Which procurement decisions would be costly or difficult to reverse?
- How will we know that procurement has created value rather than merely achieved a low purchase price?
Closing Perspective
Procurement begins with acquisition, but its consequences extend far beyond acquisition.
It decides how a temporary project organisation will access capability, distribute risk, govern external performance and preserve value through uncertainty. Leaders who see procurement only as purchasing arrive late to the most important decisions. By the time the order is raised or the contract is signed, the strategic architecture may already have been fixed.
The stronger discipline is to treat procurement as part of project design itself: a system for assembling the right capabilities, under the right commercial conditions, to produce an outcome the organisation can defend and sustain.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.