For those seeking to lift their organisation's data capability, this guide provides expanded information about the Data Capability Framework, including the levels of capability, descriptions of use, and example use cases.
Data capability framework guide [PDF, 6MB]
The framework is a tool designed to help define and develop data & analytical capabilities.
Data has the power to change lives and create better outcomes for New Zealanders, by informing government policy and decision-making. The value of data can be maximised by those who have suitable data and analytical capabilities to use it, and decision-makers who understand how the data can be used in their decision-making processes.
The importance of improving these capabilities is not new in the data system. However, it is becoming more relevant to a wider range of roles as more data becomes available and its value is more widely recognised.
The benefits of using the framework are:
The framework is for managing capability at an individual, team, or potentially organisational level. Its intended users are everyone in central government agencies who needs to use data in their work. It may also be useful to people working with data in other organisations, such as local government, NGOs, iwi, or Māori organisations.
It has been deliberately created in a “broad brush” way so that it can appeal to and be used by as wide a data-using community as possible. It is not designed specifically for statistics and data professionals.
The framework has been constructed according to the data lifecycle:
Plan | The processes and resources are mapped out for the lifecycle of the data. The project’s goals are stated, and a full data management plan is created. | |
Collect | Data is gathered or generated by the individuals/ organisation wanting to use it. | |
Describe |
The data is accurately described using the appropriate metadata standards. |
|
Store |
The data is stored in a digital repository, is made secure and reusable. This often very quickly follows collection. |
|
Analyse |
The data is analysed (that is, explored and interpreted). |
|
Use |
The data is used for the purpose for which it was collected or generated, and reused for additional value. |
|
Save or Destroy |
Actions are taken to safeguard the long-term viability and availability of the data. |
The framework defines 25 capabilities that are associated with data use. They are grouped into the 7 categories of the data lifecycle.
Many of the capabilities naturally fall into more than one category. Depending on how you want to use the Framework, you can look at all the capabilities together in no particular order or look at each category and the capabilities that they contain.
Each capability is also described with 3 levels of skill or knowledge: “New”, “Proficient” and “Expert”.
The following example shows one capability with all the categories it is in, and the levels of skill or knowledge that can be reached:
Categories: Describe, Store, Use, and Save/Destroy
New |
|
Proficient |
|
Expert |
|
The following describes possible positive impacts the framework could have for an individual, a team or an organisation. Three particular contexts are identified with the possible impacts included in bulleted form, followed by a more detailed example involving an organisation.
Once individuals have used the questionnaire to assess their capability levels and their managers are in agreement, there are a number of ways the framework can enhance performance and development:
Once an organisation or team has clarified what capabilities it needs and at what levels, recruitment can be more targeted and informative:
The following is a summary of how an organisation might use the framework to strengthen its data and information use.
The organisation identifies that it is not making the best use of its data, in terms of its decision-making and impact. It recognises that its current data capability levels or future data capability needs remain unclear, which represents a definite risk.
The organisation decides to take a workshop-based approach, after first using role descriptions to confirm who should be in attendance (i.e. all of those who work with data and analytics, plus a small number of individuals in key policy and leadership roles).
Desired state after one year
The resulting conversation reveals that, within one year, participants think the organisation should be clear on the existence, level, and location (i.e., who has them) of capabilities. Participants also agree that the organisation should be clear on how individuals/teams can develop capabilities, either from scratch or by increasing the current level.
It is recognised that the way data is handled needs to change. It is felt that data should be more readily available (while still staying secure) within the organisation, and that there needs to be better communication between those who create and gather the data and those who analyse and use it.
The final desired change is in how data is visualised. Workshop participants want an increase in this capability to improve how data is communicated and understood.
Desired state after two years
Participants are keen for the organisation to have a reputation for using data well. They want the appropriate technology and tools to enable data producers and analysts to collaborate fully and maintain best practice. They also feel it is important that all data users, not only analysts, are upskilled enough to ask good data questions and reach useful answers.
The organisation found that using the framework as a tool for exploration and identification was vital. The framework was able to surface gaps, strengths and needs in a way that was easily translatable in to action.
Please refer below for the terms and definitions used in the framework:
Term | Definition | |
Administrative data | Data which is derived from the operation of administrative systems (e.g. data collected by government agencies for the purposes of registration, transaction and record keeping, which is then used for statistical purposes). | |
Classification | A way to group a set of related categories in a meaningful, systematic, and standard format, e.g., country or region. | |
Data assets | Data collected and/or sourced and stored by an organisation. | |
Data governance | Data governance is a collection of practices and processes, which help to ensure the formal management of data assets within an organisation. | |
Data sources | A place or system or service where data is obtained. | |
Exploratory data analysis | The analysis of datasets to describe their main characteristics, e.g., the distribution of variables. | |
Information management principles | Gathering data and then analysing, categorising, contextualising, and archiving (and in some cases, deleting) it, in order to support a business's needs. | |
Output | Analytical outputs may be graphs, charts, infographics, or reports with analytical content. | |
Processing Methodology | Statistical procedures used to deal with intermediate data and statistical outputs, e.g., weighting schemes, statistical adjustment, or methods for imputing missing values or source data. | |
Time series Forecasting | Use of statistical methods to predict future behaviour based on historical data. |
If you’d like more information, have a question, or want to provide feedback, please email datalead@stats.govt.nz.
Content last reviewed 18 September 2020.