Skip to main content

8 posts tagged with "Data Management Methodology"

Content related to Data Management Methodologies.

View All Tags

The end of the copy-everything era: five enterprise data predictions for 2027

· 10 min read

2027 marks the end of the copy-everything era — the next phase is using less data, better.

The short answer

After the warehouse, the lake and the cloud data platform, the next phase is Enterprise Data Efficiency: business meaning defined once, one governed copy, and every report and AI tool reading the same facts. Five shifts follow in 2027 — unmanaged AI drives compute costs up, the data layer outlasts the apps, fewer copies become the cheapest security control, AI agents need data someone can vouch for rather than more of it, and the data team moves from building pipelines to owning meaning.

Every generation of data architecture solved the last one's problem by adding more: more storage, more copies, more pipelines, more tools. Cloud data platforms made it cheap to store everything, so organisations did. Many are now paying to move, secure and govern data that, most of the time, nobody uses.

The next phase is not another place to put data. It is Enterprise Data Efficiency — using less of it, better. That shift reframes the five predictions below, which span cost, strategy, security, AI agents and the people who run the data estate.

How to build a business case for reducing repeated data and reporting work

· 13 min read

Build the case around one recurring workflow, measure the work honestly and ask leadership for a small, specific decision.

The short answer

Build the case around one recurring reporting workflow. Measure its current effort and delays, find the cause of the repeated handling, compare realistic options and include the full cost of change. Then propose a limited pilot with agreed success measures. Treat staff time released as capacity unless you can show a genuine budget saving.

Every month, someone on your finance team reformats a file, chases a correction and reconciles the result. The report goes out on time, so the work stays invisible. A business case makes it visible.

If you lead forecasting, planning and analysis, you may already see the problem. Finance managers and controllers know where the work happens. A useful proposal brings that knowledge together in a form that finance leadership and IT can evaluate.

Why do finance, sales and operations report different numbers?

· 14 min read

They count different events on different dates. Some differences are legitimate. The problem starts when nobody can explain how the figures relate.

The short answer

Finance, sales and operations report different numbers because they count different events, use different dates and apply different definitions and adjustments. Some differences are legitimate. A reporting problem starts when teams cannot explain how their figures relate, or when one agreed KPI is calculated in more than one way.

At month-end, finance collects actuals from subsidiaries that run different ERPs. Forecasts add another set of spreadsheets and CRM inputs. Before anything reaches leadership, finance has to bring the figures together, explain the differences and say why actuals moved away from the forecast.

If you lead forecasting, planning and analysis, or work as a finance manager or financial controller, you need data that is consistent enough to use and a way to spot the submissions that need correcting. Data and systems colleagues can help trace the technical causes.

Post-Acquisition Data Integration

· 10 min read

You have acquired a business. It has been trading successfully for years on its own systems, with its own processes and its own way of describing what it does.

Within weeks, someone will propose moving it onto yours.

That instinct is understandable and it is usually expensive. There is another way to get what the board actually wants, and it starts by separating two problems that are almost always treated as one.

How Do You Know If Your Data Is AI-Ready?

· 9 min read

Most organisations answer "is our data AI-ready?" with a feeling rather than a fact. The platform is modern, the warehouse is populated, a governance programme exists — so it probably is.

It usually is not, and the gap only surfaces once a model is in production and its answers start contradicting things the business knows to be true.

These seven questions give you a straight answer. They are deliberately phrased so you can respond yes or no. If a question needs a qualified answer, treat that as a no.

AI-Ready Data Starts With Master Data

· 7 min read

"AI-ready data" is now everywhere, and most definitions of it agree: clean, governed, contextualised, accessible, traceable. All true, and all hard to argue with.

The trouble is that these describe the destination. They do not explain why so few organisations arrive.

The reason is narrower and more awkward than "data quality". Most organisations cannot agree what their core business objects actually are — and no AI system will resolve that for you. It inherits the disagreement and scales it.

CryspIQ® — my first thoughts

· 3 min read

"We're building something amazing"​

When I spoke to Vaughan a couple of years ago he told me that Dan and he was building something amazing. He spoke about a data model that can take in any type of data and report on it.

Having worked in large corporate and government data warehouse environments, I was naturally sceptical as you may be. I also fiddled with universal data models when I was studying at university, so the project and product had my attention.

I really wanted to see it in action and after spending some time on the East Coast in another BI role and trying my hand as an IT Manager, I joined the CryspIQ® team.