-

What to prepare for 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 your 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 you show could be a mixture of sharing Lucid boards, docs, and sketches. It could include slides but it doesn't have to.

What to expect during a discovery peer review

After you request the review

You'll recieve an email with next steps. This includes how to share links to artefacts for the panel to read. For example Lucid boards, docs or slide decks. You can add links to work in progress, it doesn't need to be finished, it just gives the panel an idea of the discovery.

One to 2 days before

The team will have a call with the panel. This is a chance for everyone to meet and agree what will happen during the session.

On the day

Peer reviews are 2 hours. People who attend include members of the discovery team and a peer review panel. The panel usually includes a user researcher, designer and product or delivery manager. There may also be silent observers for learning and development opportunities.

How you want the review to run is for you to agree with the panel. You could, for example, agree to have 45 minutes to an hour Show & Tell, with the remaining time for questions and answers. You should aim to explore the problem space, the users and agree next steps.

See an example agenda.

After the review

The panel will aim to complete the report within 3 days. The service assessment team will review and share it with the team.

The report will include a RAG (red, amber, green) status for the discovery, feedback and recommendations for next steps.

Updated: February 2023

Part of Service assurance: step by step

  1. Step 1 Check what assurance you need

    All digital delivery work in DfE will need some kind of assurance.

    1. Types of assurance
    2. Check what assurance you need for your service
    3. Why you need to assure your work

  2. Step 2 Prepare for a discovery peer review

    1. What a discovery peer review is

    If you're a team having a peer review.

    1. Who should attend a peer review
    2. What to prepare for a peer review

    If you're an assessor.

    1. Your role as an assessor

  3. Step 3 Book and manage a discovery peer review

    You need to give at least 5 weeks notice when booking a peer review.

    1. Book your peer review online
    2. Manage your peer review online

  4. Step 4 After a discovery peer review

    If you're a team having a peer review.

    1. Receive feedback and recommendations in a report
    2. How to take action on any recommendations

    If you're an assessor.

    1. Complete the report

    Everyone involved in the peer review.

    1. Give feedback on the discovery peer review process

  5. Step 5 Prepare for a service assessment

    Service assessments are done in the alpha, public and private beta, and live phases.

    1. What a service assessment is
    2. DfE panel assessments
    3. Cross-government panel assessments previously GDS/CDDO assessments

  6. Step 6 Book a service assessment

    You need to give at least 6 weeks notice when booking a service assessment.

    1. Book your service assessment online

  7. Step 7 After a service assessment

    If you're a team having a service assessment.

    1. Receiving the assessment report
    2. How to take action on any recommendations
    3. If you need a reassessment

    If you're an assessor.

    1. Completing the assessment report
    2. Reassessing the service