1.1Expressing and analysing needs
The essentials in 30 seconds
- Right need = what, how much, when, quality, budget — ten lines are enough to frame the purchase.
- 80% of cost is decided before tendering: challenging the need pays more than negotiating.
- Expected outcome, not imposed brand: open competition instead of paying for lock-in.
Running mini-case — Nadia and the oversized packaging
Nadia, buyer at an agri-food SME importing to Algiers, receives a request: premium wrapping film for export dates. Before tendering, she questions real use: standard protects just as well, and just-in-case volume would trap cash. She rephrases as expected outcome and opens competition.
This same case runs through the course, the diagram, the script and the 48h challenge — and continues in 1.2, 1.3, 1.4 and 1.5.
1. The five dimensions of a need
A well-expressed need answers what (truly required characteristics), how much (quantity and rhythm: at once or staggered?), when (real deadline and margin), at what quality level (useful conformity threshold, not the best possible) and within what budget.
Ten lines are often enough. Without this formalisation, failed purchases follow: too much, too expensive, too complex or simply unsuitable, because the need was vague from the start.
The golden rule is to describe the expected outcome rather than the solution: this lets competition propose its best options instead of freezing a brand.
2. Challenging: hunting classic drifts
Over-specification is requiring top-tier by habit when standard covers the use. "Just in case" quantity immobilises cash and creates dormant stock. Comfort urgency deprives you of bargaining power and imposes express transport.
Lock-in (naming a precise brand) prevents competition and makes you pay for the brand, not the function. Each locked characteristic has a price: it must be made explicit.
Challenging means asking the right questions: what is it exactly for? What is lost with the standard model? Can we group, rent, share or do nothing? Upstream savings exceed any later negotiation.
3. Role split: requestor and buyer
The requestor knows the usage and non-negotiable technical constraints. The buyer knows the market and alternatives. Alone, the requestor over-specifies; alone, the buyer risks unsuitability.
The dialogue produces the right need: sufficient for use, no more. The buyer translates functional into open specification, brings families of solutions and questions what is expensive.
Even when one person holds both roles, imposing this inner dialogue — distinguishing what is truly necessary from what is habitual — avoids locked purchases.
🔎 Concrete example — The unnecessary premium
A department requests premium professional equipment for occasional use. By questioning real usage (frequency, required performance), the buyer proposes a standard model half the price covering 100% of measured need.
Test: for each characteristic, ask "what is it concretely for and what is lost without it?"
Gain: 50% saving without loss of use, and a need reformulated as expected outcome to open competition.
Section vocabulary
- Needs statement
- Formalisation of what to buy: what, how much, when, at what quality level, within what budget.
Simple example: Nadia rewrites the film request in five lines before any tender.
What it is not: copying a brand's datasheet as the needs statement.
Reflex: every request received = five written dimensions before tendering.
- Right need
- Specification level that covers real use — neither under-sized (risk) nor over-sized (permanent overcost).
Simple example: standard film covers 100% of the measured date need.
What it is not: just-in-case premium doubling the cost.
Reflex: for each requirement, ask what is lost with standard.
- Over-specification
- Requirements above real need (premium by default, copy of a brand); major source of overcosts.
Simple example: demanding premium by habit when standard suffices.
What it is not: challenging means lowering useful quality.
Reflex: hunt one over-specification per purchase this week.
- Requestor
- The person who expresses the business need; the buyer challenges without replacing their expertise.
Simple example: the production manager describes the use, Nadia translates into open specification.
What it is not: the buyer imposing technical choices alone without knowing the use.
Reflex: separate the necessary from the habitual with the requestor.
- Make or buy
- Trade-off between doing in-house and buying (or renting, sharing, refurbishing); first question before any major purchase.
Simple example: renting a bagging machine for the season peak instead of buying it.
What it is not: buying without testing rental or sharing.
Reflex: ask “can we rent, share or do nothing” before any major purchase.
In practice — Formalise and challenge a real need
- Take an upcoming purchase and write its statement in 5 lines: what, how much, when, quality, budget.
- Hunt over-specification: for each requirement, ask what it's for and what standard costs.
- Check sizing: does quantity match real need (not just in case) and is the deadline real?
- Rephrase as expected outcome rather than brand/reference to let competition play.
Ready-to-say script — challenge without offending (1 min)
“Thanks for your request. To buy well, I need to understand the use: what exactly is it for, and what is lost with the standard model? My role is not to refuse — it is to avoid paying for a useless brand or option. Shall we rephrase together as expected outcome?”
Say to the requestor, calmly, with the request in front of you; note one challenged requirement from this exchange.
Copy-paste template — needs statement in 5 lines
WHAT (expected outcome, no brand): _______________
HOW MUCH (quantity + real rhythm): _______________
WHEN (real deadline + margin): _______________
QUALITY (useful threshold, not maximum): _______________
BUDGET: _______________
CHALLENGE (standard? quantity? deadline? brand?): _______________Small business / tight budget
No form: five lines in a notebook or message, and one standard-vs-premium question before each order.
Algeria SME
On imports, add sea freight and customs lead time to the real deadline: a comfort urgency costs an avoidable express freight.
Seasonal agri-food
Size quantity on the real peak (harvest, holidays) with possible top-up rather than just-in-case stock gathering dust.
Occasional equipment
Test rental or sharing with a non-competing peer before buying a rarely used machine.
✓ Best practices
- Set the real deadline vs comfort deadline: a true date leaves time to compare and negotiate.
- Require written justification for each technical characteristic that locks competition.
- Test the "do nothing / rent / share" option before validating the purchase: 100% saving if the need disappears.
✗ Common pitfalls
- Copying a brand's datasheet as specification: you pay for the brand and kill competition.
- Confusing challenging the need with criticising the person: you question the spec, not the requestor.
- Neglecting upstream: when tendering starts, 80% of cost is already frozen by need definition.
Key takeaways
- Formalise in five dimensions: what, how much, when, quality, budget — even in ten lines.
- Challenge over-specification, just-in-case quantities, comfort urgencies and imposed brands.
- Express as expected outcome to open competition.
- Upstream saving exceeds any downstream negotiation.
48h Challenge — apply tomorrow
Take 1 upcoming purchase and write its statement in five lines (template above). Challenge one requirement with “what is it for and what is lost without it?”. 20 minutes is enough.
- I can name the five dimensions of need without hesitating.
- I can challenge a requirement without offending the requestor.
- I have formalised a real need in five lines.
Frequently asked questions
Why waste time challenging the need?
Because 80% of cost is determined at this stage. Good negotiation gains 5-15%; questioning the need can save 30-100% (purchase avoided, standard instead of premium, rental vs purchase). Ten minutes of questions beats a week of negotiation.
Who should define the need: requestor or buyer?
Both. Requestor owns the functional what (use, indispensable performance), buyer the how (translation into open spec, market knowledge). Their dialogue produces the right need: sufficient, not more.
What is the first source of savings in purchasing?