At the start of alpha we wanted to explore and identify potential service solutions and the value they could offer users (the service assessment team, service teams, assessors and peer reviewers).
We sketched 3 potential service solutions for a discovery peer review process based on user needs and business requirements. We reviewed them with stakeholders and senior leaders, looking at risks, where we could make things simpler, and cost.
In short, the 3 solutions:
Use PowerBi: a low code solution, already in use in DfE, only works for DfE staff, accessibility is unknown
Guidance only: a light touch solution using current service assessment team processes, no automation or time and effort saved, delays in process
Build a service using open source code: a digital service built using GOV.UK frontend, can be scaled, fully accessible, would need developer time to build and support
Solution 3, building a service usings GOV.UK patterns and components was agreed to be the favoured solution to test further. Using open source code and being able to scale up the service from discovery peer reviews to also include assessments and other assurance types were felt to be benefits worth exploring.
Our first designs to find out about and book a discovery peer review
We sketched ideas for page structures based on user journeys, thinking about what users need to know and at what point in their assurance journey. Starting with pen and paper, we moved to Google docs and Lucid frames to crit the structure with the wider team, and the wider content design community.
What we found
There’s lots of conflicting information that contributes to mental models and pre-conceptions of peer reviews in DfE as it’s not always clear where people should go to find out about or book a discovery peer review.
What we did as a result
Ran a content audit of all content relating to assurance and assessments in DfE, checking messaging and who owns the content so that we review the content as we build out the service as part of the content strategy. We want to create a single source of truth for assurance in DfE with a single message.
Moved the book a discovery peer review button higher up on the find out about page so that it’s clear users can continue on their journey.
What we found
As well as wanting to know how to book a discovery peer review, users want to know what the purpose of the review is. If it’s not mandatory, why have one? What’s the benefit to an already time-stretched team?
What we did as a result
Pair wrote content with lead assessors and assessors to show what a team gets out of having a review.
What a team gets out of having a review
If the review panel has recommendations for the team these will be detailed in the report. The team can then decide on how they want to act on the recommendations, this could mean having a follow-up call, or a workshop.
Use the report to the team's advantage. Communicate recommendations with stakeholders or use it to prepare for the next phase of delivery.
What we found
From working with lead assessors and Heads of Profession to pair write content, we found that not all service standard points relate to discovery peer reviews, but sometimes have been referred to and measured against at past peer reviews.
What we did as a result
Added a bullet list of things to consider for teams when preparing for their review and referred teams to Service Standard points 1 to 7 that could be considered at a discovery peer review.
Think about the best way to show the narrative of your discovery.
Include things like:
- how you've explored the problem space
- who are users and their needs
- existing services that meet your users' needs
- any current user journeys
- any existing policy or solution constraints
- next steps to take
These pointers are taken from things teams should consider in the discovery phase for standards 1 to 7. Show what you've done to explore these at your peer review.
What comes next
Add the content to the prototype kit and run a design crit for finding out about and booking a discovery peer review. Following iterations, we’ll be ready for our first round of research for booking a discovery peer review.