We plan to complete 18 RAP transformation projects with the direct support of the Quality and Improvement Division’s Analysis Standards and Pipelines team, alongside existing transformation work supported by our Emerging Platforms and Digital Services and Technology teams.
We have developed a set of prioritisation criteria for new RAP projects. These draw on our experience of working with teams inside and outside the Office for National Statistics (ONS) to transform analytical workflows using RAP.
We will spread our support across ONS divisions
Working across the organisation spreads RAP expertise more quickly and creates a community of practice.
We will prioritise new projects that support Tier 0 outputs and activities
We will take these forward first.
We will apply our standard project viability criteria
The following questions will inform our approach:
1. What is the level of risk carried by the existing manual workflow?
High risk workflows with significant quality implications will be prioritised.
2. What are the likely productivity gains from transformation?
We will prioritise the projects with the highest productivity gains.
3. Is there commitment and trust from senior managers?
RAP projects succeed when senior managers are committed to the process and ensure that time and resource is available to do the work.
4. Is there commitment from team members?
RAP projects succeed when the team fully buy into the transformation project and are committed to implementing the outcome.
5. Is there enough time for team members to contribute?
RAP transformation projects take several months, and team members typically need to spend at least 20% of their time every week on transformation work to embed knowledge transfer. Where this commitment was not met in the past, projects have failed.
6. Is there a process to transition to business as usual (BAU)?
RAP projects need to work towards a sustainable business outcome. Having a clear plan from the business area for transition to BAU and long-term maintenance is essential.
7. Is there a base level of technical understanding?
RAP transformation involves mentoring and just-in-time learning, but team members need a base level of coding knowledge before they begin. Experience has shown that where this is not in place, teams struggle to cope with the amount they need to learn.
8. Do the team have the right tools in the right place?
RAP transformation requires that team members have the tools they need to implement the workflow and the right technology platform(s) for the project.