Data & decision capability
A reporting tool becomes valuable when people trust the measures, interpret them in context and have the authority and routines to act.
Published: · Last updated: · By Consultancy Mantra
The core idea
Data-use capability is the repeatable ability to turn relevant, responsibly managed data into a decision, action and learning. It combines shared definitions, usable access, analytical judgement, decision rights and an operating routine. It is not the same as possessing more data or publishing a dashboard.
A capable team can explain what a measure means, test its quality, interpret change, connect insight to a real choice and record what happened next. A capable organisation also maintains the ownership, standards, infrastructure and governance that allow those practices to continue.
Why dashboards stall
The OECD’s data-driven public sector framework treats data as a strategic asset and connects its use to planning, delivery, evaluation and monitoring. It also identifies leadership, coherent implementation, rules, architecture and infrastructure as parts of data governance. That wider system explains why interface design alone cannot create data-informed work.
Teams may use the same label for different populations, periods or calculation rules. Without a named owner, source, definition and limitation, debate shifts from the decision to whether the number can be trusted.
A dashboard can contain many indicators while leaving users unsure what deserves attention. The reporting cadence, thresholds, questions and available actions need to reflect a real management or service decision.
If nobody prepares the evidence, facilitates interpretation, records a decision or follows up, insight remains observational. Capability requires roles and a repeatable path from signal to response.
Design from the decision backwards
Start by specifying the decision and who makes it. Then identify the evidence, definitions, analysis and routine needed to make that choice well. This keeps the data product proportionate to its purpose.
Write the decision as a concrete choice: allocate support, adjust delivery, investigate a problem, continue an intervention or change a service. Identify the accountable decision owner and other people who contribute evidence or are affected. Clarify timing, constraints and what action is genuinely available.
State what success means for users or the organisation, then identify the few questions that would change a decision. The GOV.UK Service Manual guidance on performance metrics advises beginning with service purpose and user needs, deriving benefits and hypotheses, then deciding what to measure. This helps prevent available data from defining the question by default.
For each priority measure, record the calculation, source, refresh cycle, owner, population, exclusions and known limitations. Identify where data is created and transformed. A simple definition register can reduce ambiguity, while access and handling rules should match privacy, security and legitimate-use requirements.
Show comparison points that help users judge meaning: trends, targets, segments or relevant baselines. Provide enough context to distinguish a change in performance from a change in coverage, timing or data quality. Combine quantitative signals with appropriate qualitative evidence and user research where the decision needs it.
Agree who reviews which evidence, how often, with what preparation and authority. Record decisions, assumptions, actions and owners. At the next review, examine whether the action occurred and whether the expected change followed. This learning loop is what turns reporting into organisational practice.
Capability across roles
A single “data literacy” course can hide important differences between roles. Build practice around the actual contribution each role makes to the decision system.
Leaders need to distinguish outcomes from activity, ask what sits behind a trend, recognise uncertainty and make the action explicit. They also need to create conditions in which uncomfortable evidence can be raised rather than filtered out.
These roles translate questions into measures, test sources, document limitations and communicate findings without overstating certainty. Stewardship also includes access, definitions, lifecycle responsibilities and coordination across systems.
People close to delivery can explain workflow changes, exceptions and user experience that the aggregate view may miss. They need accessible evidence, space to challenge it and clarity about which actions they can take.
Someone must own refresh reliability, access, documentation, change control and the response to source or definition changes. Without continuity, confidence can deteriorate even when the original dashboard was well designed.
Evidence of capability
Useful evidence includes a team defining a measure correctly, diagnosing a data-quality issue, interpreting segmented or time-series information, explaining uncertainty, selecting a response and following up on the result. Repeated work products and observed review meetings are stronger evidence than self-reported confidence alone.
The OECD framework also connects data use with trust, privacy, transparency and ethical handling. Capability therefore includes knowing when data should not be used, where access should be limited and when a conclusion is not supported. Strong practice makes limitations visible rather than smoothing them away.
For service work, GOV.UK recommends measuring from the beginning, using multiple data sources, establishing a baseline, viewing performance over time and iterating measures as the service changes. Those principles can be adapted beyond digital services: begin with purpose, preserve context and improve the measurement system alongside the work.
Buyer checklist
Define the decisions, users, available actions, outcomes, current sources, known quality problems, access constraints, reporting cadence and existing tools. Name the people who own definitions, systems and decisions. Ask suppliers to explain how they will test usability, document logic, transfer ownership and verify that users can act on the evidence.
Consultancy Mantra’s Data & Insights services connect measurement, analysis and dashboards with decision workflows and handover. CA-PRAXIS™ can define and verify the required capability, while How We Work shows how a data solution and the capability to sustain it can be designed together.
Primary sources
Data-use capability
Define the decision, build trusted measures and establish the routine that turns insight into action.