Excellent delivery cannot fully recover value that was designed out of the project before procurement reached the market.
A familiar management instinct is to concentrate attention where expenditure becomes visible: tender evaluation, contract award, construction, implementation and supplier performance.
But much of the project’s value potential is shaped earlier.
The supplied Walker chapter presents a project-value trajectory across initiation, design, delivery and decommissioning. Its central implication is consequential. Stakeholder input, planning knowledge, design choices and procurement decisions made near the front of the lifecycle can create or destroy value before the delivery team has had an opportunity to perform.
This challenges a common assumption: that a strong contractor can compensate for weak project definition.
Sometimes it can mitigate the damage. It cannot reliably reverse strategic choices that have already fixed the wrong need, the wrong design, the wrong sourcing boundary or the wrong commercial structure.
The Strategic Context
Projects exist to produce beneficial change, not merely to produce outputs.
The source material emphasises value to customers and stakeholders and notes that value is broader than time, cost and quality. It can include trust, reputation, relationships, learning and other less tangible outcomes. It also observes that an inexpensive project can be strategically poor if it satisfies the wrong need. A factory delivered cheaply in the wrong location is the obvious illustration: delivery efficiency does not compensate for strategic error.
That is why procurement must start before tender documents.
The early questions include what problem the project is solving, which stakeholders define value, which requirements are essential, which capabilities should be internal or external, how suppliers can contribute to design, what risks can be transferred in reality and what information is needed before market commitment.
These are not administrative questions. They determine the option space available later.
What Leaders Commonly Misread
“Value” means compliance plus low cost
Compliance matters, but compliance with an inadequate requirement simply produces the wrong result efficiently.
Walker and colleagues distinguish tangible project measures from less explicit expectations. Their argument is that project value includes both specified outputs and important intangible outcomes. For leaders, that means the procurement team must understand not only what is written in the specification but why the specification exists.
Procurement influence begins when tendering begins
By tender stage, many choices may already be locked.
Scope boundaries have been drawn. Internal capability has been allocated. Design assumptions may have hardened. The delivery model may be politically or organisationally committed. Supplier engagement may be constrained by a procurement route selected months earlier.
The earlier the project identifies value drivers and uncertainty, the larger the range of viable choices.
Delivery performance is the main determinant of value
Delivery matters greatly, but the source’s project-phase discussion makes a more difficult point: a well-executed project can still underperform a strategically well-designed project delivered by a merely competent team.
This is not an argument for tolerating poor delivery. It is an argument for protecting the front end.
Reframing the Issue
The right question is not merely:
How do we obtain the required product or service?
It is:
How should the project be configured so that suppliers, internal teams and stakeholders can collectively maximise the intended value?
That changes procurement from downstream acquisition to upstream value architecture.
A procurement route can encourage early knowledge, competition, innovation, collaboration or price certainty. It can also suppress those things. A contract can allocate responsibility, but if responsibility is allocated to a party that cannot realistically control the risk, the document creates the appearance of transfer rather than the reality.
Similarly, supplier engagement can be delayed in the name of procedural neatness even when specialist market knowledge is necessary to define the project correctly.
The task is not to invite suppliers into every decision. It is to know when external knowledge materially changes the quality of the decision.
Where Early Procurement Creates Value
Clarifying the real requirement
A requirement should express the value the organisation needs, not simply reproduce the first technical solution proposed.
At initiation, leaders should distinguish needs from preferred solutions. That preserves optionality and allows the market to contribute where appropriate.
Revealing hidden constraints
Stakeholders often hold information that formal project documents do not. Operations may know maintainability constraints. Engineering may understand interface tolerances. Finance may know funding conditions. Procurement may understand market capacity and lead times. Suppliers may know manufacturing or logistics limitations.
The earlier these constraints are surfaced, the cheaper they usually are to address.
Choosing the right participation model
The make-or-buy decision determines who will contribute capability. The contracting strategy determines how those parties will engage.
A highly specified commodity purchase can benefit from competitive price tension. A novel, uncertain or highly integrated work package may require earlier collaboration or a different allocation of risk.
No single procurement model is intrinsically superior. Fit matters.
Preserving reversibility
Early decisions vary in reversibility.
Changing a supplier before contract award may be possible. Changing a delivery model after mobilisation may be expensive. Rebuilding internal expertise after years of outsourcing may take much longer. Reversing a proprietary technology choice may become economically unrealistic.
Executives should therefore give disproportionate attention to high-impact decisions that become difficult to reverse.
Decision Framework
A useful front-end procurement review can be organised around five value questions.
1. What value is the project meant to create?
Identify tangible outcomes and important intangible outcomes. Separate end-user value from internal delivery convenience.
2. Which assumptions are carrying the business case?
List assumptions about demand, supplier capability, schedule, integration, technology, regulation, cost and stakeholder behaviour.
3. Where does essential knowledge sit?
Determine whether the best knowledge is internal, with users, with specialist advisers or in the supply market.
4. Which decisions reduce future options?
Identify sourcing choices, design commitments, proprietary dependencies and contract structures that may be hard to reverse.
5. What evidence should exist before market commitment?
Set thresholds for scope maturity, market sounding, stakeholder agreement, cost confidence and risk ownership.
The purpose is not to eliminate uncertainty. It is to ensure the project understands which uncertainty it is accepting.
From Strategy to Execution
Immediate action: add a procurement-value review to project initiation and design governance. Require the team to show how the proposed sourcing approach supports the business outcome, not merely the project schedule.
Medium-term capability: integrate procurement, engineering, operations, commercial, finance and end-user input earlier for high-value or high-uncertainty procurements. The point is not to create a larger committee; it is to bring the right knowledge into irreversible decisions.
Long-term positioning: build procurement models that deliberately support different strategic needs: commodity efficiency, specialist access, innovation, collaborative problem solving, capability transfer or long-term service performance.
Related article: In-House, Out-Task or Outsource? Choosing the Right Sourcing Model
Signals to Monitor
Watch for requirements that are repeatedly rewritten after tender release, extensive bidder clarification, large post-award variation volumes, supplier claims that assumptions were unclear, internal teams discovering integration constraints late, or projects selecting a delivery model primarily because “that is how we normally procure it”.
Another warning sign is when the organisation can describe the price of the procurement in detail but cannot describe the value logic behind it.
That imbalance usually means commercial activity has become detached from strategic purpose.
Questions for the Leadership Team
- Which project assumptions would be most expensive to discover are wrong after contract award?
- Which stakeholders possess knowledge that could materially change the sourcing decision?
- Are we specifying the required outcome or prematurely specifying the solution?
- What value could be lost even if the supplier delivers exactly what the contract says?
- Which procurement decisions are becoming irreversible in the next 90 days?
- What evidence would justify delaying commitment rather than rushing to tender?
Closing Perspective
The decisive procurement moment is often not contract signature.
It is the earlier moment when leaders decide what the project really needs, who should participate, which knowledge matters, what should be retained internally and what commercial structure will shape behaviour for the rest of the lifecycle.
Once those decisions harden, delivery teams inherit the consequences.
The strategic discipline is therefore to move procurement thinking forward, while choices are still reversible and value can still be designed into the project rather than negotiated back after it has been lost.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.