Get Into Teaching
Service report for DFE's Get Into Teaching beta assessment
Service Standard assessment report
Get Into Teaching
| Assessment date: | 03/04/2025 |
| Phase: | Public Beta |
| Outcome: | Green |
About the service
The Get Into Teaching website exists to inspire, inform, reassure and support people considering teaching as a career, from those just starting to consider teaching as a possible option through to those already involved in the application process. We promote and enable sign-up to the wider Get Into Teaching support services and signpost people to Find and Apply
The Get Into Teaching CRM holds the records for people who have signed up for a support service and enables the service teams to contact them through the Dynamics Marketing app. It supports the management of Get Into Teaching events and also underpins the contact centre and adviser services
Overall feedback from the panel
- the team went from one user researcher doing content design to a UR plus two content designers and a defined way of working as content practice. They peer review, work closely with the user researcher as well as content designers from adjacent services, the teacher content group, and utilise technology to ensure plain English.
- creating a format for documentation connecting user needs and evidence for them, integrated into design and development workflow
- a wide variety of research methods have been used during public beta. Research activities have also been completed in a healthy cadence, so that a large number of users have participated in some form of research activity between April 2021 and the present
- the team has demonstrated they have embedded a proactive data culture within their team. They have a great relationship with the teams in the wider service when it comes to deriving, sharing and acting on insights to improve their service. This allows the team to have a more holistic view not only of how their product is performing but also how it affects other services further downstream.
- they worked closely with CDDO to develop measurements suitable for benchmarking a content style product. The team utilises a number of suitable data sources like GA4, CR and Bigquery data
- the team makes good use of shared DfE components, and makes good use of Azure components to provide a reliable and resilient service. The team’s use of Microsoft Dynamics and close working relationship with Microsoft ensure that they are not limited by their software choices. The team open source all frontend and API code.
1. Understand users and their needs
Decision
The service was rated amber for point 1 of the Standard.
2. Solve a whole problem for users
Decision
The service was rated green for point 2 of the Standard.
3. Provide a joined-up experience across all channels
Decision
The service was rated green for point 3 of the Standard.
4. Make the service simple to use
Decision
The service was rated green for point 4 of the Standard.
5. Make sure everyone can use the service
Decision
The service was rated green for point 5 of the Standard.
6. Have a multidisciplinary team
Decision
The service was rated green for point 6 of the Standard
7. Use agile ways of working
Decision
The service was rated green for point 7 of the Standard
8. Iterate and improve frequently
Decision
The service was rated green for point 8 of the Standard
9. Create a secure service which protects users’ privacy
Decision
The service was rated green for point 9 of the Standard
10. Define what success looks like and publish performance data
Decision
The service was rated green for point 10 of the Standard
11. Choose the right tools and technology
Decision
The service was rated green or point 11 of the Standard
12. Make new source code open
Decision
The service was rated green for point 12 of the Standard
13. Use and contribute to open standards, common components and patterns
Decision
The service was rated green for point 13 of the Standard
14. Operate a reliable service
Decision
The service was rated green or point 14 of the Standard