You can buy the best procurement analytics platform on the market, populate it with clean data, and configure beautiful dashboards. And if your team does not use it, you have wasted your money.
Technology adoption in procurement is not primarily a technology problem. It is a people problem. A data culture — where decisions are routinely informed by data, where analytics is a daily habit rather than an occasional exercise, and where evidence is valued over opinion — does not emerge simply because you install new software. It must be intentionally built, carefully nurtured, and persistently reinforced.
Here is how to build a genuine data culture in your procurement team.
What a Data Culture Is (and Is Not)
A data culture does not mean that every decision requires a spreadsheet analysis. It does not mean that intuition and experience are discounted. And it certainly does not mean that procurement professionals need to become data scientists.
A data culture means:
- Data is the starting point for discussion. When evaluating a sourcing strategy, reviewing supplier performance, or assessing a budget, the team begins with data rather than opinions.
- Questioning is encouraged. When someone cites a number, it is acceptable — even expected — to ask where it came from, how it was calculated, and whether it is current.
- Decisions are documented. The data and reasoning behind significant decisions are recorded, creating an institutional memory that does not walk out the door when someone leaves.
- Continuous learning is valued. The team actively seeks to improve its analytical capabilities, learn from outcomes, and refine its approaches based on what the data reveals.
Why Procurement Teams Resist Analytics
Understanding resistance is the first step to overcoming it. Common barriers include:
"I Don't Have Time"
This is the most frequently cited reason for not using analytics, and it is often legitimate. Procurement professionals are busy with tactical work — processing requisitions, resolving supplier issues, managing contracts. Analytics feels like an additional task on top of an already overwhelming workload.
The solution is not to add analytics to the existing workload but to use analytics to reduce it. When EVA from Sharpe Project Consulting (SPC3) automates spend reporting that previously took hours, or surfaces supplier issues that would otherwise consume days of investigation, it creates time for strategic analysis rather than competing with it.
"I Don't Trust the Data"
If procurement professionals have experienced inaccurate reports in the past — numbers that did not match their reality — they will be sceptical of any new analytical tool. Trust must be earned through transparency: showing where the data comes from, how it is processed, and allowing users to validate it against their own knowledge.
"I Already Know My Categories"
Experienced category managers have deep knowledge of their suppliers, markets, and spend patterns. They may feel that analytics is telling them what they already know. The key is to show them what they do not know — the cross-organisational patterns, the hidden fragmentation, the gradual trends that are invisible to individual experience but clear in the data.
"It's Too Complicated"
Complex dashboards with dozens of metrics and unfamiliar visualisations can be intimidating. Analytics tools must be designed for procurement professionals, not data analysts. Simple, focused views that answer specific procurement questions are far more effective than comprehensive but overwhelming dashboards.
Seven Steps to Build a Data Culture
1. Start With Leadership
Culture change starts at the top. If the CPO and procurement leadership team do not consistently use data in their own decision-making and discussions, the rest of the team will not either.
Practical actions for leaders:
- Begin every management meeting with a review of key procurement metrics
- Ask for data to support recommendations before approving significant decisions
- Reference analytics findings in communications to the broader team
- Visibly use dashboards during stakeholder conversations
2. Create Quick Wins
Early adoption is driven by perceived value, not mandates. Identify specific, common pain points that analytics can solve immediately:
- "How much are we spending with Supplier X across all business units?" (Previously required hours of data gathering — now answered in seconds)
- "Which suppliers are consistently late?" (Previously anecdotal — now quantified with trend data)
- "Are we buying at contract rates?" (Previously unknown — now visible at the transaction level)
When the team experiences these quick wins, their attitude toward analytics shifts from scepticism to interest.
3. Embed Data in Existing Processes
Do not create new analytics processes — embed data into processes that already exist.
- Category reviews: Require a data-based category profile as the starting document
- Sourcing events: Mandate a spend analysis and supplier performance review before launching any RFP
- Supplier reviews: Structure meetings around scorecard data, not anecdotes
- Budget discussions: Use spend trend analytics to inform forecasts rather than flat-line projections
When analytics is part of the workflow rather than separate from it, adoption becomes natural rather than forced.
4. Invest in Training (But Keep It Practical)
Training should focus on practical skills, not tool features. Do not teach people how to use every button in the analytics platform. Teach them how to answer the questions they face every day:
- How to find their category's total spend and supplier breakdown
- How to read a supplier performance trend and identify concerns
- How to compare prices across business units to find savings opportunities
- How to track the impact of their sourcing initiatives
Short, focused training sessions — 30 to 60 minutes each, covering one use case — are far more effective than comprehensive multi-day training programmes.
5. Celebrate Data-Driven Successes
When a team member uses data to identify a savings opportunity, prevent a supplier problem, or improve a negotiation outcome, celebrate it. Share the story across the team. Quantify the impact. Make data-driven success visible and valued.
This positive reinforcement is far more powerful than mandating analytics use. People adopt behaviours that are recognised and rewarded.
6. Create Data Champions
Identify team members who are naturally curious about data and enthusiastic about analytics. Give them additional training, involve them in tool configuration and dashboard design, and position them as go-to resources for their peers.
Data champions bridge the gap between the technology and the team. They provide informal support, share tips and tricks, and demonstrate through their own work how analytics adds value.
7. Measure Adoption and Act on It
Track analytics adoption metrics — dashboard login frequency, report usage, self-service query volumes — and use them to identify where adoption is strong and where it needs support.
Low adoption in a particular team or category is not a failure — it is a signal. Investigate the cause. Is the data for their category incomplete? Is the dashboard not addressing their questions? Do they need additional training? Address the specific barrier rather than applying generic pressure.
The Technology Factor
The right technology makes culture change easier. The wrong technology makes it harder.
EVA is designed specifically for procurement teams working with Oracle Fusion Cloud data. This matters for culture building because:
- Relevance: Every metric and dashboard is procurement-specific, so the team immediately sees its value
- Familiarity: Data structures align with how procurement professionals think about their work — by category, supplier, contract, and business unit
- Accessibility: Insights are presented in plain language, not technical jargon, making the tool approachable for all skill levels
- Trust: Because EVA connects directly to Oracle Fusion, the data source is known and verifiable, building confidence in the results
SPC3's consulting and implementation services include change management and adoption support specifically designed for procurement analytics deployments, ensuring that technology investment translates into genuine cultural change.
The Long Game
Building a data culture is not a three-month project. It is a multi-year journey of incremental change, persistent reinforcement, and continuous improvement. There will be setbacks — people who resist, initiatives that stall, data quality issues that undermine trust.
But the organisations that persevere build a lasting competitive advantage. Their procurement teams make better decisions, faster. Their suppliers receive clearer performance feedback. Their stakeholders receive more credible reporting. And their procurement professionals find their work more satisfying because they are operating as strategic advisors, not administrative processors.
The tools exist. The data exists. The question is whether your organisation has the commitment to build the culture that brings them together.
Get in touch with SPC3 to discuss how EVA and our consulting expertise can support your journey toward a data-driven procurement culture — starting with quick wins and building toward lasting transformation.