Table 4 Design principles of a process... | Emerald Publishing

Table 4

Design principles of a process for developing PIs

	Principle description
Principle 1	Establish an agreed and explicitly stated long-term vision comprising the socially desired outcomes that infrastructure is expected to enable before designing PIs.
Principle 2	Create a traceable audit trail of design decisions (and their justification) at every stage of the process.
Principle 3	Analyse and decompose each desired outcome into a set of outcome dimensions and subdimensions that collectively represent the desired outcome. Note: This is necessary because outcomes are typically multidimensional and difficult to measure directly.
Principle 4	Frame desired outcomes and outcome dimensions in solution neutral terms – that is, when framing desired outcomes, do not make reference to specific technologies or infrastructures that can be used to enable the desired outcome. For example, a desired outcome connected to energy should avoid specifying which technology is used to generate the energy.
Principle 5	Avoid making decisions based on current data availability. The process should aspire to create indicators aligned with those elements of performance that need to be measured, not just those already measured.
Principle 6	Produce a set of indicators for each desired outcome. The indicator set should comprise (a) one or more partial indicators for each of the outcome dimensions identified during desired outcome decomposition and (b) a headline indicator (outcome-oriented PI) for each desired outcome. Explanation of how the headline indicator for a desired outcome is calculated from the partial indicator set must be provided alongside the indicator set.
Principle 7	Whenever indicators are published, each indicator should be accompanied by a statement of their intended value to the audience they are designed for; these statements should be an output from the indicator design process.
Principle 8	Make the process collaborative, such that implementation of the PI development process involves all affected stakeholders at all stages. Understanding of the purpose of infrastructure, how that purpose can be fulfilled and the reason for the PI developed are all likely to be improved by making the process inclusive and transparent in this way.
Principle 9	Ensure that the process is sufficiently flexible to be revisited and modified in the light of data availability, without modifications affecting the underlying purpose of the PI.
Principle 10	Any process for PI creation needs to be flexible such that it can be applied at any geographic scale, in any sector and at a cross-sectoral infrastructure scale, to allow comparisons between different regions and different sectors (where appropriate) and to promote a systemic perspective that recognises actions in one sector to achieve performance targets that can impact on the ability of other sectors to achieve performance targets.

	Principle description
Principle 1	Establish an agreed and explicitly stated long-term vision comprising the socially desired outcomes that infrastructure is expected to enable before designing PIs.
Principle 2	Create a traceable audit trail of design decisions (and their justification) at every stage of the process.
Principle 3	Analyse and decompose each desired outcome into a set of outcome dimensions and subdimensions that collectively represent the desired outcome.Note: This is necessary because outcomes are typically multidimensional and difficult to measure directly.
Principle 4	Frame desired outcomes and outcome dimensions in solution neutral terms – that is, when framing desired outcomes, do not make reference to specific technologies or infrastructures that can be used to enable the desired outcome. For example, a desired outcome connected to energy should avoid specifying which technology is used to generate the energy.
Principle 5	Avoid making decisions based on current data availability. The process should aspire to create indicators aligned with those elements of performance that need to be measured, not just those already measured.
Principle 6	Produce a set of indicators for each desired outcome. The indicator set should comprise (a) one or more partial indicators for each of the outcome dimensions identified during desired outcome decomposition and (b) a headline indicator (outcome-oriented PI) for each desired outcome. Explanation of how the headline indicator for a desired outcome is calculated from the partial indicator set must be provided alongside the indicator set.
Principle 7	Whenever indicators are published, each indicator should be accompanied by a statement of their intended value to the audience they are designed for; these statements should be an output from the indicator design process.
Principle 8	Make the process collaborative, such that implementation of the PI development process involves all affected stakeholders at all stages. Understanding of the purpose of infrastructure, how that purpose can be fulfilled and the reason for the PI developed are all likely to be improved by making the process inclusive and transparent in this way.
Principle 9	Ensure that the process is sufficiently flexible to be revisited and modified in the light of data availability, without modifications affecting the underlying purpose of the PI.
Principle 10	Any process for PI creation needs to be flexible such that it can be applied at any geographic scale, in any sector and at a cross-sectoral infrastructure scale, to allow comparisons between different regions and different sectors (where appropriate) and to promote a systemic perspective that recognises actions in one sector to achieve performance targets that can impact on the ability of other sectors to achieve performance targets.