Procure too early and suppliers price uncertainty. Procure too late and the project may lose schedule, competition and supplier innovation.
The Week 6 slides distinguish concept design from detailed design. Concept design defines the proposed product or solution at a high level. Detailed design refines the solution into plans, specifications, estimates and other information from which procurement can often proceed.
The important strategic question is not whether concept or detailed design is “better”.
It is how much definition is needed before the market can respond intelligently.
The Strategic Context
Engineering projects face a recurring timing tension.
Early market engagement can improve constructability, manufacturability, innovation and lead-time knowledge.
But if procurement begins before the requirement is mature, suppliers may have to interpret missing information themselves.
That can produce:
- qualifications;
- risk premiums;
- incomparable tenders;
- scope disputes;
- post-award changes.
Detailed design reduces uncertainty, but too much pre-market design can freeze the organisation's preferred solution and prevent suppliers from proposing better alternatives.
What Leaders Commonly Misread
The first mistake is believing procurement should wait until every detail is fixed.
That may be appropriate for some build-to-print work but not for every sourcing model.
The second is assuming early supplier involvement means the buyer can avoid defining outcomes.
Supplier expertise cannot compensate for an organisation that does not know what success means.
The third is confusing technical detail with commercial clarity. A hundred drawings may still leave responsibilities, interfaces and acceptance criteria ambiguous.
The fourth is treating design maturity as a purely engineering decision. It affects price certainty, competition, risk allocation and schedule.
Reframing the Issue
Design readiness for procurement should be judged against the commercial decision required from the supplier.
If the organisation wants suppliers to compete on a prescribed technical solution, more detailed definition may be necessary.
If it wants suppliers to innovate around a performance outcome, excessive technical prescription can be counterproductive.
The procurement model should therefore fit the maturity of the requirement.
Strategic Analysis: Performance Versus Prescription
The Week 6 slides discuss using performance specifications as a way to allow alternative goods or services to be considered.
Hypothetical manufacturing example: A plant needs to increase throughput by 20 per cent. One procurement route specifies a particular conveyor configuration, drive arrangement and control system. Another specifies required throughput, product characteristics, safety constraints, interfaces and acceptance tests.
The first gives the buyer more design control.
The second gives suppliers more solution freedom.
Neither is automatically superior. The right choice depends on retained engineering capability, risk tolerance, market expertise and the importance of standardisation.
Decision Framework
Before market release, test design maturity across five dimensions.
Outcome
Is required performance clear?
Interfaces
Are physical, digital and organisational boundaries understood?
Constraints
Which standards, safety, environmental and site conditions are non-negotiable?
Freedom
Where should suppliers be allowed to innovate?
Acceptance
Can the buyer objectively determine whether the delivered solution works?
If these are clear, procurement may be viable even where every design detail is not fixed.
From Strategy to Execution
Immediate action: classify significant procurement packages by required design maturity before tendering.
Medium-term capability building: create different sourcing pathways for build-to-print, design-and-supply, performance-based and early supplier involvement models.
Long-term strategic positioning: improve the organisation's ability to preserve technical intent while using market expertise intelligently.
The goal is not maximum design detail. It is sufficient definition for the commercial model chosen.
Governance Implication
Design maturity should also be matched to contractual responsibility. If the buyer retains detailed design authority while the supplier merely manufactures, the buyer carries more design risk. If the supplier is asked to design to performance requirements, the supplier may carry more solution responsibility but will also need sufficient freedom to exercise that responsibility.
Problems arise when the contract mixes these models. The buyer may prescribe critical details and then expect the supplier to carry full performance risk, or invite innovation but retain approval processes that effectively control every design decision. This can create blurred accountability.
A useful pre-market review therefore asks not only “How complete is the design?” but “Who will own the remaining design decisions after award?” That answer should align with the specification, evaluation criteria, professional responsibilities and acceptance regime. Design maturity is ultimately about allocating future decisions as much as documenting past ones.
Signals to Monitor
Watch for large tender qualification schedules, many supplier assumptions, post-award redesign, procurement delays blamed on “engineering not finished”, and engineering teams rejecting alternative solutions because the tender unintentionally encoded preferences as mandatory requirements.
Questions for the Leadership Team
- What parts of the design must be fixed before market engagement?
- Where would supplier innovation create value?
- Are interfaces clearer than the internal design details?
- Can suppliers price the remaining uncertainty rationally?
- Are acceptance criteria mature enough to judge performance?
- What schedule value is gained by going to market earlier, and what risk is created?
Closing Perspective
Design maturity is not a percentage-complete question.
It is a judgement about whether the organisation has defined enough of the right things for suppliers to compete, price and perform responsibly.
Related article: Write Requirements Suppliers Can Actually Bid Against
Related article: Procurement Under Constraints: Plan Logistics and Bottlenecks Before They Reach the Site
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.