
The Second Biggest Productivity Drag . . .
Productivity, as I have discussed before, is a much-misunderstood and misrepresented topic.
Individual task productivity rarely scales to P&L impact (economic productivity).
I will never forget the CFO who taught me this very directly.
We had a business case that calculated that 2,000 employees each saving 15 minutes a day, would deliver a $2m p.a. saving.
I know, I was young đ.
The CFO looked at me and explained that there wasnât any saving to be had, because the 15 minutes per person per day would never see the light of a P&L.
âEveryone will just have another cup of coffee, and nothing will changeâ was the observation.
Maybe a little harsh on the younger me, but it does make sense.
The single biggest drag on enterprise productivity is effort that is wasted or poorly directed in functional, team and organisational silos. Effort that we often assume is important.
My favourite personal experience of this was a DSO reduction challenge in a global manufacturing business. There had been substantial investments in outside consultants and new technology with marginal impact.
A mid level finance manager suggested we were looking in the wrong places and that there was a major âblind spotâ.
It turned out that the incentive and reward structure of the global sales teams were unwittingly undermining all this investment and effort. A single change in performance and reward structures had a dramatic effect with zero external cost and relatively little pain and effort!Â
So, what, I hear you ask, is the Second Biggest Productivity Drag?
I often ask GBS, Shared Services and Finance Operations leaders what percentage of their organisations’ efforts they estimate are spent in fixing errors, re-work, responding to queries, and all the other classic elements of âFailure Demandâ.
The answers range between 25% and 50% of total effort.
This is a massive opportunity.
We tend to focus our time on speeding up the workflows and processes that support âFailure Demandâ rather than getting to, and fixing, the root causes.
We spend a lot more effort in fixing individual failed transactions in collections, payables and closing than we do in identifying and fixing the root causes.
Master Data is at the root of many, if not most, of these issues.
Mauro Portela wrote a very good piece on the foundational element of master data recently in âMaster Data Management as a Foundation for AI Successâ, as did Malcolm Hawker in his report âThe State of MDM 2026â.
Some examples put this into stark relief;
- 157 different vendor master records for the largest single supplier to one organisation. Some duplicated for understandable reasons, and others simply erroneous, but the impact being an inability to see, and thus make informed decisions on, aggregated spend with that supplier.
- 3,500 duplicate master data records for currently active vendors causing errors at PO, Invoice, Receiving and Payment stages.
- Up to 75% duplicated, inconsistent master data with multiple versions of contradictory, incomplete âtruthâ, numerous naming conventions, embedded âcodesâ in company names (âXXXâ etc).
- Different functional âsilosâ maintaining their own âshadowâ single source of truth on the same information.
- Agreed payment terms not captured in vendor or customer master data in 20% of cases, resulting in varying payment practices, denuding working capital and creating unnecessary customer and vendor queries based on misaligned expectations.
- 44% of active suppliers with bank detail + Tax/VAT issues, causing the obvious payment, tax and reporting issues.
- 85% of long-term inactive customers and vendors having master data that is still very much available for use, causing mistakes, errors and re-work. Â
- And the beat goes on . . .
The Harvard Business Review (HBR) estimates that âbad dataâ costs US businesses over $3 trillion per annum.
Gartner research asserts that 57% of organisations admit their data isn’t AIâready.
It is easy to see the impact of data quality and integrity having a big impact on the basic usefulness and effectiveness of a GenAI conversational service.
But it is a much deeper issue than this.
Before we even worry about âAI-readyâ, we need to address the fact that much of our data isnât even âtransaction readyâ . . .
Mauro states âyou canât AI your way out of a data problem, but you CAN data your way into AI successâ. I would add that you CAN also data your way to transactional success!
Malcolm comments in his report that master data “must support deterministic (classic, transactional) and probabilistic (AI) worlds simultaneously.”
Master data is both the context and the âglueâ that drives operational process efficiency AND effectiveness as well as providing the basis for effective analysis, assessment and decision-making.
It always seems that fixing master data is regarded as a technical challenge and an almost impossible mountain to climb.
But applying the Pareto Principle (80/20 rule) is a powerful way to drive âquick winsâ in business impact and continuous improvement with master data.
It seems to me this is a very practical example of the proverb that âyou can give someone a fish and you feed them for a day; teach them to fish and you feed them for a lifetime”.
Thatâs a productivity lesson in itself!
You can read Malcom Hawkerâs âThe State of MDM 2026â report from Profisee here . . .Â
The Second Biggest Productivity Drag . . .
Thanks for reading . . .Â
Â