Problem solving is one of the most essential, and underestimated, competencies in procurement. While negotiation and supplier management often receive the spotlight, the reality is that procurement professionals spend a significant part of their time resolving issues. Late deliveries, incorrect specifications, conflicting internal requirements, cost escalations, or supplier capacity shortages are not exceptions; they are the operational landscape.
Content..
For buyers in training, learning problem solving in procurement is not simply a matter of applying tools. It is about adopting a disciplined, analytical, and structured mindset that prevents quick fixes, escalations, and poor decisions. Because in procurement, the wrong solution can create more damage than the original problem.
This article takes a deep dive into problem solving in procurement, exploring the nature of problems in supply chains, the pitfalls of inaccurate root-cause identification, and two highly effective tools: the 5 Whys method and the Fishbone (Ishikawa) Diagram.
1. Why Problem Solving Is a Core Procurement Competence
Procurement operates at the crossroads of internal demand, supplier performance, and market uncertainty. This position brings structural complexity—and structural problems.
1.1 Internal complexity
Procurement must reconcile:
- technical specifications,
- commercial constraints,
- operational priorities,
- budget limitations,
- and compliance requirements.
Problems often arise when these internal elements do not align. A change in schedule from production can disrupt supplier deliveries. Finance targets may conflict with technical needs. Operational urgency may clash with sourcing rigor.
1.2 Supplier and market uncertainty
Suppliers face:
- fluctuating raw material costs,
- labour shortages,
- geopolitical disruptions,
- transportation delays,
- technical failures.
Procurement must manage these uncertainties while ensuring continuity of supply and commercial performance.
1.3 The cost of wrong problem solving
Decades of research in quality management and operations show that solving the wrong problem can create:
- repeated failures,
- worsening supplier relations,
- unnecessary cost,
- overcomplicated processes,
- and erosion of procurement credibility.
Wrong solutions often come from treating symptoms rather than causes. This is why root-cause analysis is a cornerstone skill for any professional buyer.
2. What Is Problem Solving in Procurement?
Stéphane Morel defines problem solving as identifying the real root cause(s) of an issue and finding practical solutions to move forward. This matches academic definitions from quality management: problem solving is a structured process to understand issues, analyse their causes, and develop actions that prevent recurrence.
In procurement, this means:
- diagnosing supply problems,
- assessing supplier failures,
- analysing process breakdowns,
- understanding internal misalignments,
- and building corrective measures that address systemic causes.
Problem solving is not firefighting. It is disciplined analysis to ensure better performance over time.
3. Recognizing Procurement Problems Early
Before a buyer can solve a problem, they must recognise when one exists. Common signs include:
3.1 Operational symptoms
- late deliveries,
- quality deviations,
- invoice mismatches,
- incorrect quantities,
- stockouts.
3.2 Behavioural symptoms
- stakeholders escalating issues,
- suppliers becoming silent or defensive,
- decisions being delayed or avoided,
- repeated misunderstandings.
3.3 Systemic symptoms
- recurring issues with the same category or supplier,
- constant pressure to expedite,
- reliance on emergency purchasing or premium freight,
- internal silo behaviours.
Buyers in training should learn to identify not only the visible problem (“delivery is late”) but also the underlying pattern: Why is this happening? Why does it keep happening?
This is where structured tools become essential.
4. Two Powerful Tools for Problem Solving in Procurement
Morel highlights two foundational methods: the 5 Whys and the Fishbone Diagram. Both are widely applied in lean, quality, engineering, and supply chain environments. They are simple, accessible, and exceptionally effective for procurement situations.
Below is an expanded and academically grounded explanation of each tool.
5. The 5 Whys Method
The 5 Whys is a root-cause analysis technique originally developed by Toyota. Its purpose is to move beyond symptoms and identify the underlying drivers of a problem.
5.1 Why procurement needs the 5 Whys
Procurement teams often jump to conclusions:
- blaming suppliers too quickly,
- implementing corrections that address the effect, not the cause,
- making reactive decisions under pressure.
The 5 Whys prevents this by enforcing logical progression.
5.2 How the 5 Whys works
- Define the problem clearly
Be precise: “Delivery failed” is too broad.
“Supplier failed to ship material X on 14 March” is actionable. - Ask: Why did this happen?
Each answer must be validated using data, examples, or stakeholder confirmation. - Continue asking ‘Why?’
The point is not to reach exactly five questions, but to keep drilling down. - Stop when the root cause is reached
Typically when the answer identifies a process, assumption, behaviour, or system weakness.
5.3 Example in a procurement context
Morel’s example clearly shows how the problem shifts from “supplier failure” to internal planning issues:
- Why did delivery fail? Supplier did not ship.
- Why did they not ship? They were missing stock.
- Why did they miss stock? They lacked a raw material.
- Why was the raw material missing? Our schedule was too short-term.
Result: The true root causes lie in scheduling and forecast accuracy, not supplier negligence.
5.4 Benefits for buyers in training
- improves analytical thinking,
- reduces reactive decision-making,
- strengthens supplier relationships by using facts not blame,
- supports continuous improvement.
6. The Fishbone Diagram (Ishikawa)
For more complex or multi-causal problems, the Fishbone Diagram is one of the most powerful tools available.
6.1 Why procurement needs the Fishbone
Procurement problems often have multiple causes:
- internal processes,
- supplier failures,
- system limitations,
- unclear specifications,
- communication breakdowns.
The Fishbone allows teams to map these causes visually and systematically.
6.2 How the Fishbone works
- Define the problem
Example: “Frequent quality issues on Component A.” - Describe the effects
Late production, increased scrap, supplier dissatisfaction. - Choose a categorisation framework
Common frameworks include:- 6Ms: Methods, Machines, Materials, Manpower, Measurement, Management
- 4Ps: Place, Procedure, People, Policies
- 4Ss: Surroundings, Suppliers, Systems, Skills
- Brainstorm causes for each category
Small cross-functional teams are ideal. - Link each cause to its impact
Identify the causes that actually matter.
6.3 Why it works
The method transforms chaos into clarity.
Instead of arguing about what went wrong, teams map how and why failures occur across the supply chain.
6.4 Benefits for buyers in training
- develops systems thinking,
- encourages structured brainstorming,
- integrates cross-functional perspectives,
- reduces emotional debate and defensiveness,
- supports supplier development and SRM.
7. Common Pitfalls in Procurement Problem Solving
7.1 Jumping to conclusions
Blaming the supplier or rushing corrective action without analysis.
7.2 Treating symptoms, not causes
Expediting instead of fixing forecasting.
Adding safety stock instead of addressing quality issues.
Escalating instead of solving.
7.3 Lack of documentation
Issues recur when lessons are not captured and shared.
7.4 Overcomplicating the method
Tools work when used consistently, not perfectly.
7.5 Not involving the right people
Procurement cannot solve problems alone.
Effective solutions require operations, planning, suppliers, and quality teams.
8. Integrating Problem Solving into Everyday Procurement Work
To become a skilled buyer, you must adopt a proactive approach:
8.1 Build problem-solving discipline
Start every issue with:
- What is the problem?
- What data do we have?
- What data is missing?
8.2 Engage suppliers constructively
Invite them into the analytical process.
Suppliers are often eager to help when approached collaboratively.
8.3 Use tools consistently
Routine use builds your reputation as a professional who solves problems methodically.
8.4 Document root causes and solutions
Use supplier scorecards, issue logs, and continuous improvement plans.
8.5 Share insights internally
Procurement becomes more strategic when it shapes organisational learning.
9. Conclusion: Turning Problems into Opportunities
Problems are not the enemy in procurement.
Repeated problems, misdiagnosed problems, and poorly solved problems are.
When buyers approach issues with structured methods—such as the 5 Whys and Fishbone Diagram—they move from firefighting to value creation. They build credibility, strengthen supplier relationships, and improve organisational performance.
For buyers in training, developing strong problem-solving skills is one of the most important steps toward becoming a mature, trusted procurement professional. When used correctly, the simple tools highlighted here can transform obstacles into opportunities and elevate procurement’s impact across the organisation.
When answering NCRs (Non Conformity Reports), these methods are very relevant.
References
- Ishikawa, K. (1985). What Is Total Quality Control?
- Ohno, T. (1988). Toyota Production System.
- Liker, J. (2004). The Toyota Way.
- van Weele, A. (2018). Purchasing and Supply Chain Management.
- Lysons, K. & Farrington, B. (2020). Procurement and Supply Chain Management.
- Slack, N., Brandon-Jones, A., & Johnston, R. (2019). Operations Management.
- Morel, S. (2025). “Problem Solving in Procurement” – LinkedIn Post (used only as inspiration).
- Ishikawa, K., & Loftus, J. H. (1990). Introduction to Quality Control.