The Specify Needs phase doesn't explicitly refer to proposing statistical solution options to addressing client needs, it just separately mentions various aspects of these solutions, probably because a survey solution is assumed. Some of the sub-processes also don't seem big enough to warrant being explicit at this level (e.g. identify concepts). In the new ABS Business Architecture we have combined and re-focussed 1.1 - 1.5 into two sub-processes - 'Understand and confirm statistical needs' and 'Scope statistical solution' (scoping and preparing a high level solution design is effectively what a business area does to get approval to proceed with the project, and before the detailed design, build/assembly and implementation processes commence in earnest). To be in scope of the GSBPM any solutions prepared would need to result in the creation of data outputs.
Statistics New Zealand response to GSBPM v4.0
Responsiveness to indigenous peoples
Statistics New Zealand has moved a long way towards making the organisation’s commitment to responding to the information needs of the Māori people more visible in our documentation and in our work generally. In light of this, we have been considering whether it is worthwhile adding an explicit sub-process within the Specify Needs process to better highlight this need. Currently, activities associated with identifying and responding to the information needs of Māori would sit under each of the sub-processes within Specify Needs, but are nowhere referenced explicitly.
Meeting legislative requirements
Similarly, there may be legislative requirements that form part of the assessment of information needs. Examples relevant to Statistics New Zealand include preparing and submitting a Privacy Impact Assessment to New Zealand’s Privacy Commissioner when information about individuals is involved, and obtaining Ministerial approval for new statistical surveys commissioned by government departments (including Statistics New Zealand). At present, activities associated with meeting legislative requirements are implicit in one or more of the sub-processes within the Specify Needs process. It may be useful to have legislative requirements explicitly referenced as a sub-process in the Specify Needs process.