Most Irish public sector bodies are not short of data. Between service requests, case files, inspections, permits, and years of manual returns, there's usually plenty of it. What's missing is a coherent way to use it. Ask most organisations where their reporting actually comes from and the honest answer is a patchwork of spreadsheets, manual extracts, and whoever happened to build the last dashboard before they moved teams.
The pattern is familiar
A monthly report gets assembled by hand from three different systems. Two departments quote different numbers for the same metric because nobody agreed on a single definition. A new starter has no idea which spreadsheet is actually current. None of this is unusual. It's the default state for an organisation that has been collecting data for years without ever deciding, deliberately, what it wants that data to do.
The frustrating part is that the underlying data is often perfectly usable. The problem isn't quality so much as structure: it sits in silos, in inconsistent formats, with no single source of truth anyone can point to with confidence.
Why "no strategy" is the norm, not the exception
This isn't a criticism of the teams involved. Public sector data teams are usually stretched thin, working against legacy systems they didn't choose, and funded project by project rather than platform by platform. A data strategy requires sustained investment and a mandate that spans multiple budget cycles, and that's a genuinely hard thing to secure when the pressure is always to deliver the next specific report, not the underlying capability.
The result is that most organisations end up with dozens of small, disconnected fixes instead of one coherent platform. Each one solves an immediate problem. None of them add up to something that lasts.
What a data strategy actually needs to contain
Not a slide deck, and not an exhaustive inventory of every system in the organisation. A workable data strategy is deliberately narrow:
- Clear ownership. A named accountable owner for data quality and platform decisions, not a committee.
- A small number of prioritised use cases. Three or four decisions the organisation actually needs data to support, not an attempt to model everything at once.
- An honest baseline. A real assessment of current data quality and system sprawl, not an assumption that the data is "mostly fine."
- A target architecture that fits how procurement actually works. Governed, well-structured reporting, built on tools your organisation can realistically support and procure, such as a properly governed Power BI environment rather than a bespoke platform nobody can maintain.
- A first phase that shows value quickly. One or two use cases delivered well within months, not a two-year programme with nothing to show until the end.
Building the internal case without losing the room
The mistake most people make when pitching a data strategy upward is leading with the technical detail: architecture diagrams, tooling choices, data models. None of that persuades a budget holder who isn't technical. What persuades them is the operational cost of not having it: how many hours go into manually reconciling numbers each month, how long it takes to respond to an FOI request, how often a decision gets delayed because nobody trusts the figures in front of them.
Frame the ask around specific, current pain, not a hypothetical future state. "This report takes three people two days to assemble by hand every month" is a far stronger case than "we should modernise our data architecture."
An honest note on where this fits
This is genuinely one of the clearer wins available to Irish public bodies right now. The technology involved, properly governed dashboards, a defined single source of truth, sensible data pipelines, is mature and well understood. The gap in most organisations isn't capability, it's that nobody has been given the time and mandate to build it properly. That's a solvable problem, and it doesn't require a multi-year transformation programme to start solving it.
If you're trying to build the internal case for this and want a second opinion on scope before you take it upstairs, we're glad to talk it through.