Content by type
| Title | Description |
|---|---|
| Architecture | Principles, standards and guidance we expect teams working in the Department for Education to follow. |
| Assurance | Guidance to help teams understand, prepare for and pass assurance, including service assessments, standards compliance and governance expectations. |
| Job descriptions | Find and use job descriptions if you're hiring for digital, data, and technology professions in the Department for Education. |
| Product management | Guidance and information for any product manager working in the Department for Education. |
| Standards | Understand the standards you must follow when designing, building and running digital services in the Department for Education. |
| Title | Description |
|---|---|
| Apply the Service Standard in the Department for Education | Guidance and information for how to apply the GOV.UK Service Standard to design and build accessible, user centred and secure services in DfE. |
| Architecture capability framework | tk |
| Architecture community | tk |
| Architecture documentation | tk |
| Architecture principles | The principles we follow when designing services. |
| Architecture profession | tk |
| Architecture roles | tk |
| Assess a service | Support delivery teams to create and run accessible services that meet the Service Standard. |
| Business architecture | tk |
| Contribute to this service | tk |
| Create and manage DDT standards | Guidance and information to create and manage DDT standards. |
| Developing our profession | Our vision for the product management practice at DfE, and how we'll get there. |
| Get feedback from users on your service | Collect feedback from users of a beta or live product or service using a form. |
| New to product management | Information if you're joining DfE as a civil servant or contractor product manager. |
| Peer reviews | Peer reviews provide informal assurance at the discovery phase and throughout the agile lifecycle. |
| Product communication | Communicate with other product managers. |
| Product community | Our people, meetups, and how we're developing product management capability across the department. |
| Product leadership | Our product management profession leadership team, what they do, and how to contact them. |
| Product management principles | The 8 principles for how we deliver our best work. |
| Product values | The characteristics that we aspire to as product managers. |
| Repositories | tk |
| Roadmap | tk |
| Service assessments | Find out what you need to do to book and prepare for a service assessment or discovery peer review. |
| Title | Description |
|---|---|
| 1. Understand users and their needs | Take time to understand users' needs and the problem you're trying to solve for them. |
| 10. Define what success looks like and publish performance data | Collect performance data across online and offline channels to measure and show that your service is effective and improving. |
| 11. Choose the right tools and technology | Choose tools and technology that let you build a good service in an efficient, cost-effective way. |
| 12. Make new source code open | Aim to make all new source code open and reusable, and publish it under appropriate licences. |
| 13. Use and contribute to open standards, common components and patterns | Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs. |
| 14. Operate a reliable service | Ensure your service is available for use at the time users need to access it. Where a service is unavailable, have a plan to deal with its recovery. |
| 2. Solve a whole problem for users | Consider where your service fits in your users' journey and whether you can solve a whole problem or influence a wider solution. |
| 3. Provide a joined up experience across all channels | Consider where your service fits into a wider journey or alongside other DfE services, and how it will join up across channels. |
| 4. Make the service simple to use | Build a service that's simple to use so that people can succeed first time. Test it with users to make sure it works for them. |
| 5. Make sure everyone can use the service | Make sure your service can be used by people with different needs, whether it's for public use, DfE staff or across the education sector. |
| 6. Have a multidisciplinary team | It's important to have the right mix of the skills and roles, and make decisions as a team to respond quickly to user needs. |
| 7. Use agile ways of working | Build quickly, test what you have built and iterate your work based on regular feedback and other useful data. |
| 8. Iterate and improve frequently | Make sure you have the capacity, people, and technical flexibility to iterate and improve frequently. Focus on improvements that deliver most value. |
| 9. Create a secure service which protects users' privacy | Understand what data your service collects, and how it's stored and used. Identify and address security, legal, privacy and confidentiality risks. |
| Book a mid-phase alpha or beta peer review | A mid-phase peer review can help you prepare for a service assessment. |
| Book an assessment | When to book a service assessment and what to prepare. |
| Business architects | tk |
| Business architecture principles | Business architecture principles serve as a set of rules and guidelines that shape business architecture activities. |
| Complete an assessment report | Guidance to write an assessment report as a trained assessor. |
| Data architecture principles | tk. |
| Discovery peer reviews | A discovery peer review is a 2-hour informal review of your work in the discovery phase. |
| Draft DDT standards | The lifecycle of standards, from concept to publication and use across DfE. |
| Enterprise architects | tk |
| Enterprise architecture principles | General rules and guidelines that inform and support decisions in how DfE should deliver services, to align with its vision and objectives. |
| Get an assessment report | The service assessment report and green, amber and red ratings explained. |
| Get DDT standards approved | How standards are approved by the standards forum. |
| Give feedback on the assessment process | How to give feedback as a service team or assessor after an assessment. |
| Identity principles | tk |
| Manage actions from an assessment report | How to manage actions as a team from a service assessment. |
| Principle 1: Set your vision, mission and strategy | We set the vision, mission and strategy for our products, and share it. We know how this fits into the bigger picture. |
| Principle 2: Understand your users | We know and understand our users and customers. We act as their voice. |
| Principle 3: Be accountable for your outcomes | We deliver outcomes, not outputs. We're accountable for them. We make sure they're measurable, attainable and valuable. |
| Principle 4: Prioritise with your roadmap | We align and prioritise our work towards the outcomes, using a roadmap. |
| Principle 5: Work with your stakeholders | We identify our stakeholders and take them on a journey with us. We work with them, not at them. |
| Principle 6: Do the hard work with your team | We do the hard work so that everyone on our team knows what's expected of them. |
| Principle 7: Lead with evidence | We're evidence led. We do not let our own preferences guide our thinking. We know our products better than anyone. |
| Principle 8: Raise the bar | We help raise the bar for product management. We help people where we can and are not afraid to ask for help ourselves. We are bold. |
| Publish and manage DDT standards | Guidance to publish and manage DDT standards. |
| Purpose of architecture framework | tk |
| Review DDT standard categories | Standards are grouped into categories to make finding and applying them relevant to the need. |
| Run a discovery peer review | As an assessor you'll help a team to understand if they've completed their discovery or progress through an agile phase. |
| Run an assessment | Guidance to prepare for and run an assessment as a trained service assessor. |
| Title | Description |
|---|---|
| Roadmap | Our roadmap for delivering the DDT Manual. |
Content by phase
Content tagged with delivery phases.
| Title | Type | Description |
|---|---|---|
| Architecture | Collection | Principles, standards and guidance we expect teams working in the Department for Education to follow. |
| Assurance | Collection | Guidance to help teams understand, prepare for and pass assurance, including service assessments, standards compliance and governance expectations. |
| Job descriptions | Collection | Find and use job descriptions if you're hiring for digital, data, and technology professions in the Department for Education. |
| Product management | Collection | Guidance and information for any product manager working in the Department for Education. |
| Standards | Collection | Understand the standards you must follow when designing, building and running digital services in the Department for Education. |
| Title | Type | Description |
|---|---|---|
| 1. Understand users and their needs | Detailed Guide Page | Take time to understand users' needs and the problem you're trying to solve for them. |
| 10. Define what success looks like and publish performance data | Detailed Guide Page | Collect performance data across online and offline channels to measure and show that your service is effective and improving. |
| 11. Choose the right tools and technology | Detailed Guide Page | Choose tools and technology that let you build a good service in an efficient, cost-effective way. |
| 12. Make new source code open | Detailed Guide Page | Aim to make all new source code open and reusable, and publish it under appropriate licences. |
| 13. Use and contribute to open standards, common components and patterns | Detailed Guide Page | Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs. |
| 2. Solve a whole problem for users | Detailed Guide Page | Consider where your service fits in your users' journey and whether you can solve a whole problem or influence a wider solution. |
| 3. Provide a joined up experience across all channels | Detailed Guide Page | Consider where your service fits into a wider journey or alongside other DfE services, and how it will join up across channels. |
| 4. Make the service simple to use | Detailed Guide Page | Build a service that's simple to use so that people can succeed first time. Test it with users to make sure it works for them. |
| 5. Make sure everyone can use the service | Detailed Guide Page | Make sure your service can be used by people with different needs, whether it's for public use, DfE staff or across the education sector. |
| 6. Have a multidisciplinary team | Detailed Guide Page | It's important to have the right mix of the skills and roles, and make decisions as a team to respond quickly to user needs. |
| 7. Use agile ways of working | Detailed Guide Page | Build quickly, test what you have built and iterate your work based on regular feedback and other useful data. |
| 8. Iterate and improve frequently | Detailed Guide Page | Make sure you have the capacity, people, and technical flexibility to iterate and improve frequently. Focus on improvements that deliver most value. |
| 9. Create a secure service which protects users' privacy | Detailed Guide Page | Understand what data your service collects, and how it's stored and used. Identify and address security, legal, privacy and confidentiality risks. |
| Complete an assessment report | Detailed Guide Page | Guidance to write an assessment report as a trained assessor. |
| Get an assessment report | Detailed Guide Page | The service assessment report and green, amber and red ratings explained. |
| Give feedback on the assessment process | Detailed Guide Page | How to give feedback as a service team or assessor after an assessment. |
| Manage actions from an assessment report | Detailed Guide Page | How to manage actions as a team from a service assessment. |
| Run an assessment | Detailed Guide Page | Guidance to prepare for and run an assessment as a trained service assessor. |
| Title | Type | Description |
|---|---|---|
| 1. Understand users and their needs | Detailed Guide Page | Take time to understand users' needs and the problem you're trying to solve for them. |
| 10. Define what success looks like and publish performance data | Detailed Guide Page | Collect performance data across online and offline channels to measure and show that your service is effective and improving. |
| 2. Solve a whole problem for users | Detailed Guide Page | Consider where your service fits in your users' journey and whether you can solve a whole problem or influence a wider solution. |
| 3. Provide a joined up experience across all channels | Detailed Guide Page | Consider where your service fits into a wider journey or alongside other DfE services, and how it will join up across channels. |
| 4. Make the service simple to use | Detailed Guide Page | Build a service that's simple to use so that people can succeed first time. Test it with users to make sure it works for them. |
| 5. Make sure everyone can use the service | Detailed Guide Page | Make sure your service can be used by people with different needs, whether it's for public use, DfE staff or across the education sector. |
| 6. Have a multidisciplinary team | Detailed Guide Page | It's important to have the right mix of the skills and roles, and make decisions as a team to respond quickly to user needs. |
| 7. Use agile ways of working | Detailed Guide Page | Build quickly, test what you have built and iterate your work based on regular feedback and other useful data. |
| 9. Create a secure service which protects users' privacy | Detailed Guide Page | Understand what data your service collects, and how it's stored and used. Identify and address security, legal, privacy and confidentiality risks. |
| Title | Type | Description |
|---|---|---|
| 1. Understand users and their needs | Detailed Guide Page | Take time to understand users' needs and the problem you're trying to solve for them. |
| 10. Define what success looks like and publish performance data | Detailed Guide Page | Collect performance data across online and offline channels to measure and show that your service is effective and improving. |
| 13. Use and contribute to open standards, common components and patterns | Detailed Guide Page | Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs. |
| 14. Operate a reliable service | Detailed Guide Page | Ensure your service is available for use at the time users need to access it. Where a service is unavailable, have a plan to deal with its recovery. |
| 6. Have a multidisciplinary team | Detailed Guide Page | It's important to have the right mix of the skills and roles, and make decisions as a team to respond quickly to user needs. |
| 7. Use agile ways of working | Detailed Guide Page | Build quickly, test what you have built and iterate your work based on regular feedback and other useful data. |
| 8. Iterate and improve frequently | Detailed Guide Page | Make sure you have the capacity, people, and technical flexibility to iterate and improve frequently. Focus on improvements that deliver most value. |
| 9. Create a secure service which protects users' privacy | Detailed Guide Page | Understand what data your service collects, and how it's stored and used. Identify and address security, legal, privacy and confidentiality risks. |
| Complete an assessment report | Detailed Guide Page | Guidance to write an assessment report as a trained assessor. |
| Get an assessment report | Detailed Guide Page | The service assessment report and green, amber and red ratings explained. |
| Give feedback on the assessment process | Detailed Guide Page | How to give feedback as a service team or assessor after an assessment. |
| Manage actions from an assessment report | Detailed Guide Page | How to manage actions as a team from a service assessment. |
| Run an assessment | Detailed Guide Page | Guidance to prepare for and run an assessment as a trained service assessor. |
| Title | Type | Description |
|---|---|---|
| 1. Understand users and their needs | Detailed Guide Page | Take time to understand users' needs and the problem you're trying to solve for them. |
| 10. Define what success looks like and publish performance data | Detailed Guide Page | Collect performance data across online and offline channels to measure and show that your service is effective and improving. |
| 11. Choose the right tools and technology | Detailed Guide Page | Choose tools and technology that let you build a good service in an efficient, cost-effective way. |
| 12. Make new source code open | Detailed Guide Page | Aim to make all new source code open and reusable, and publish it under appropriate licences. |
| 13. Use and contribute to open standards, common components and patterns | Detailed Guide Page | Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs. |
| 14. Operate a reliable service | Detailed Guide Page | Ensure your service is available for use at the time users need to access it. Where a service is unavailable, have a plan to deal with its recovery. |
| 2. Solve a whole problem for users | Detailed Guide Page | Consider where your service fits in your users' journey and whether you can solve a whole problem or influence a wider solution. |
| 3. Provide a joined up experience across all channels | Detailed Guide Page | Consider where your service fits into a wider journey or alongside other DfE services, and how it will join up across channels. |
| 4. Make the service simple to use | Detailed Guide Page | Build a service that's simple to use so that people can succeed first time. Test it with users to make sure it works for them. |
| 5. Make sure everyone can use the service | Detailed Guide Page | Make sure your service can be used by people with different needs, whether it's for public use, DfE staff or across the education sector. |
| 6. Have a multidisciplinary team | Detailed Guide Page | It's important to have the right mix of the skills and roles, and make decisions as a team to respond quickly to user needs. |
| 7. Use agile ways of working | Detailed Guide Page | Build quickly, test what you have built and iterate your work based on regular feedback and other useful data. |
| 8. Iterate and improve frequently | Detailed Guide Page | Make sure you have the capacity, people, and technical flexibility to iterate and improve frequently. Focus on improvements that deliver most value. |
| 9. Create a secure service which protects users' privacy | Detailed Guide Page | Understand what data your service collects, and how it's stored and used. Identify and address security, legal, privacy and confidentiality risks. |
| Complete an assessment report | Detailed Guide Page | Guidance to write an assessment report as a trained assessor. |
| Get an assessment report | Detailed Guide Page | The service assessment report and green, amber and red ratings explained. |
| Give feedback on the assessment process | Detailed Guide Page | How to give feedback as a service team or assessor after an assessment. |
| Manage actions from an assessment report | Detailed Guide Page | How to manage actions as a team from a service assessment. |
| Run an assessment | Detailed Guide Page | Guidance to prepare for and run an assessment as a trained service assessor. |
| Title | Type | Description |
|---|---|---|
| 1. Understand users and their needs | Detailed Guide Page | Take time to understand users' needs and the problem you're trying to solve for them. |
| 10. Define what success looks like and publish performance data | Detailed Guide Page | Collect performance data across online and offline channels to measure and show that your service is effective and improving. |
| 11. Choose the right tools and technology | Detailed Guide Page | Choose tools and technology that let you build a good service in an efficient, cost-effective way. |
| 12. Make new source code open | Detailed Guide Page | Aim to make all new source code open and reusable, and publish it under appropriate licences. |
| 13. Use and contribute to open standards, common components and patterns | Detailed Guide Page | Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs. |
| 14. Operate a reliable service | Detailed Guide Page | Ensure your service is available for use at the time users need to access it. Where a service is unavailable, have a plan to deal with its recovery. |
| 2. Solve a whole problem for users | Detailed Guide Page | Consider where your service fits in your users' journey and whether you can solve a whole problem or influence a wider solution. |
| 3. Provide a joined up experience across all channels | Detailed Guide Page | Consider where your service fits into a wider journey or alongside other DfE services, and how it will join up across channels. |
| 4. Make the service simple to use | Detailed Guide Page | Build a service that's simple to use so that people can succeed first time. Test it with users to make sure it works for them. |
| 5. Make sure everyone can use the service | Detailed Guide Page | Make sure your service can be used by people with different needs, whether it's for public use, DfE staff or across the education sector. |
| 6. Have a multidisciplinary team | Detailed Guide Page | It's important to have the right mix of the skills and roles, and make decisions as a team to respond quickly to user needs. |
| 7. Use agile ways of working | Detailed Guide Page | Build quickly, test what you have built and iterate your work based on regular feedback and other useful data. |
| 8. Iterate and improve frequently | Detailed Guide Page | Make sure you have the capacity, people, and technical flexibility to iterate and improve frequently. Focus on improvements that deliver most value. |
| 9. Create a secure service which protects users' privacy | Detailed Guide Page | Understand what data your service collects, and how it's stored and used. Identify and address security, legal, privacy and confidentiality risks. |
| Complete an assessment report | Detailed Guide Page | Guidance to write an assessment report as a trained assessor. |
| Get an assessment report | Detailed Guide Page | The service assessment report and green, amber and red ratings explained. |
| Give feedback on the assessment process | Detailed Guide Page | How to give feedback as a service team or assessor after an assessment. |
| Manage actions from an assessment report | Detailed Guide Page | How to manage actions as a team from a service assessment. |
| Run an assessment | Detailed Guide Page | Guidance to prepare for and run an assessment as a trained service assessor. |
Content by profession
Content tagged with professions.
View content index for Accessibility specialist
| Title | Type | Description |
|---|---|---|
| 1. Understand users and their needs | Detailed Guide Page | Take time to understand users' needs and the problem you're trying to solve for them. |
| 5. Make sure everyone can use the service | Detailed Guide Page | Make sure your service can be used by people with different needs, whether it's for public use, DfE staff or across the education sector. |
| Apply the Service Standard in the Department for Education | Detailed Guide | Guidance and information for how to apply the GOV.UK Service Standard to design and build accessible, user centred and secure services in DfE. |
View content index for All DDT professions
| Title | Type | Description |
|---|---|---|
| Assess a service | Detailed Guide | Support delivery teams to create and run accessible services that meet the Service Standard. |
| Assurance | Collection | Guidance to help teams understand, prepare for and pass assurance, including service assessments, standards compliance and governance expectations. |
| Complete an assessment report | Detailed Guide Page | Guidance to write an assessment report as a trained assessor. |
| Contribute to this service | Detailed Guide | tk |
| Get an assessment report | Detailed Guide Page | The service assessment report and green, amber and red ratings explained. |
| Give feedback on the assessment process | Detailed Guide Page | How to give feedback as a service team or assessor after an assessment. |
| Run an assessment | Detailed Guide Page | Guidance to prepare for and run an assessment as a trained service assessor. |
| Service assessments | Detailed Guide | Find out what you need to do to book and prepare for a service assessment or discovery peer review. |
| Standards | Collection | Understand the standards you must follow when designing, building and running digital services in the Department for Education. |
View content index for Business analyst
| Title | Type | Description |
|---|---|---|
| 10. Define what success looks like and publish performance data | Detailed Guide Page | Collect performance data across online and offline channels to measure and show that your service is effective and improving. |
View content index for Business architect
| Title | Type | Description |
|---|---|---|
| Architecture profession | Detailed Guide | tk |
| Architecture roles | Detailed Guide | tk |
| Business architecture | Detailed Guide | tk |
| Repositories | Detailed Guide | tk |
View content index for Content designer
| Title | Type | Description |
|---|---|---|
| 1. Understand users and their needs | Detailed Guide Page | Take time to understand users' needs and the problem you're trying to solve for them. |
| 13. Use and contribute to open standards, common components and patterns | Detailed Guide Page | Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs. |
| 2. Solve a whole problem for users | Detailed Guide Page | Consider where your service fits in your users' journey and whether you can solve a whole problem or influence a wider solution. |
| 3. Provide a joined up experience across all channels | Detailed Guide Page | Consider where your service fits into a wider journey or alongside other DfE services, and how it will join up across channels. |
| 4. Make the service simple to use | Detailed Guide Page | Build a service that's simple to use so that people can succeed first time. Test it with users to make sure it works for them. |
| 5. Make sure everyone can use the service | Detailed Guide Page | Make sure your service can be used by people with different needs, whether it's for public use, DfE staff or across the education sector. |
| 8. Iterate and improve frequently | Detailed Guide Page | Make sure you have the capacity, people, and technical flexibility to iterate and improve frequently. Focus on improvements that deliver most value. |
View content index for Data architect
| Title | Type | Description |
|---|---|---|
| 11. Choose the right tools and technology | Detailed Guide Page | Choose tools and technology that let you build a good service in an efficient, cost-effective way. |
| 12. Make new source code open | Detailed Guide Page | Aim to make all new source code open and reusable, and publish it under appropriate licences. |
| 13. Use and contribute to open standards, common components and patterns | Detailed Guide Page | Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs. |
| 14. Operate a reliable service | Detailed Guide Page | Ensure your service is available for use at the time users need to access it. Where a service is unavailable, have a plan to deal with its recovery. |
| 9. Create a secure service which protects users' privacy | Detailed Guide Page | Understand what data your service collects, and how it's stored and used. Identify and address security, legal, privacy and confidentiality risks. |
| Architecture | Collection | Principles, standards and guidance we expect teams working in the Department for Education to follow. |
| Architecture profession | Detailed Guide | tk |
| Architecture roles | Detailed Guide | tk |
| Business architecture | Detailed Guide | tk |
| Repositories | Detailed Guide | tk |
View content index for Delivery manager
| Title | Type | Description |
|---|---|---|
| 14. Operate a reliable service | Detailed Guide Page | Ensure your service is available for use at the time users need to access it. Where a service is unavailable, have a plan to deal with its recovery. |
| 6. Have a multidisciplinary team | Detailed Guide Page | It's important to have the right mix of the skills and roles, and make decisions as a team to respond quickly to user needs. |
| 7. Use agile ways of working | Detailed Guide Page | Build quickly, test what you have built and iterate your work based on regular feedback and other useful data. |
| 8. Iterate and improve frequently | Detailed Guide Page | Make sure you have the capacity, people, and technical flexibility to iterate and improve frequently. Focus on improvements that deliver most value. |
| 9. Create a secure service which protects users' privacy | Detailed Guide Page | Understand what data your service collects, and how it's stored and used. Identify and address security, legal, privacy and confidentiality risks. |
View content index for Enterprise architect
| Title | Type | Description |
|---|---|---|
| Architecture | Collection | Principles, standards and guidance we expect teams working in the Department for Education to follow. |
| Architecture profession | Detailed Guide | tk |
| Architecture roles | Detailed Guide | tk |
| Business architecture | Detailed Guide | tk |
| Repositories | Detailed Guide | tk |
View content index for Frontend developer
| Title | Type | Description |
|---|---|---|
| 12. Make new source code open | Detailed Guide Page | Aim to make all new source code open and reusable, and publish it under appropriate licences. |
| 13. Use and contribute to open standards, common components and patterns | Detailed Guide Page | Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs. |
| 14. Operate a reliable service | Detailed Guide Page | Ensure your service is available for use at the time users need to access it. Where a service is unavailable, have a plan to deal with its recovery. |
| 9. Create a secure service which protects users' privacy | Detailed Guide Page | Understand what data your service collects, and how it's stored and used. Identify and address security, legal, privacy and confidentiality risks. |
View content index for Interaction designer
| Title | Type | Description |
|---|---|---|
| 12. Make new source code open | Detailed Guide Page | Aim to make all new source code open and reusable, and publish it under appropriate licences. |
| 13. Use and contribute to open standards, common components and patterns | Detailed Guide Page | Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs. |
| 2. Solve a whole problem for users | Detailed Guide Page | Consider where your service fits in your users' journey and whether you can solve a whole problem or influence a wider solution. |
| 3. Provide a joined up experience across all channels | Detailed Guide Page | Consider where your service fits into a wider journey or alongside other DfE services, and how it will join up across channels. |
| 4. Make the service simple to use | Detailed Guide Page | Build a service that's simple to use so that people can succeed first time. Test it with users to make sure it works for them. |
| 5. Make sure everyone can use the service | Detailed Guide Page | Make sure your service can be used by people with different needs, whether it's for public use, DfE staff or across the education sector. |
| 8. Iterate and improve frequently | Detailed Guide Page | Make sure you have the capacity, people, and technical flexibility to iterate and improve frequently. Focus on improvements that deliver most value. |
View content index for Network architect
| Title | Type | Description |
|---|---|---|
| Architecture | Collection | Principles, standards and guidance we expect teams working in the Department for Education to follow. |
| Architecture profession | Detailed Guide | tk |
| Architecture roles | Detailed Guide | tk |
| Business architecture | Detailed Guide | tk |
| Repositories | Detailed Guide | tk |
View content index for Performance analyst
| Title | Type | Description |
|---|---|---|
| 10. Define what success looks like and publish performance data | Detailed Guide Page | Collect performance data across online and offline channels to measure and show that your service is effective and improving. |
View content index for Product manager
| Title | Type | Description |
|---|---|---|
| 11. Choose the right tools and technology | Detailed Guide Page | Choose tools and technology that let you build a good service in an efficient, cost-effective way. |
| 13. Use and contribute to open standards, common components and patterns | Detailed Guide Page | Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs. |
| 14. Operate a reliable service | Detailed Guide Page | Ensure your service is available for use at the time users need to access it. Where a service is unavailable, have a plan to deal with its recovery. |
| 6. Have a multidisciplinary team | Detailed Guide Page | It's important to have the right mix of the skills and roles, and make decisions as a team to respond quickly to user needs. |
| 7. Use agile ways of working | Detailed Guide Page | Build quickly, test what you have built and iterate your work based on regular feedback and other useful data. |
| 8. Iterate and improve frequently | Detailed Guide Page | Make sure you have the capacity, people, and technical flexibility to iterate and improve frequently. Focus on improvements that deliver most value. |
| 9. Create a secure service which protects users' privacy | Detailed Guide Page | Understand what data your service collects, and how it's stored and used. Identify and address security, legal, privacy and confidentiality risks. |
| Developing our profession | Detailed Guide | Our vision for the product management practice at DfE, and how we'll get there. |
| Get feedback from users on your service | Detailed Guide | Collect feedback from users of a beta or live product or service using a form. |
| New to product management | Detailed Guide | Information if you're joining DfE as a civil servant or contractor product manager. |
| Principle 1: Set your vision, mission and strategy | Detailed Guide Page | We set the vision, mission and strategy for our products, and share it. We know how this fits into the bigger picture. |
| Principle 2: Understand your users | Detailed Guide Page | We know and understand our users and customers. We act as their voice. |
| Principle 3: Be accountable for your outcomes | Detailed Guide Page | We deliver outcomes, not outputs. We're accountable for them. We make sure they're measurable, attainable and valuable. |
| Principle 4: Prioritise with your roadmap | Detailed Guide Page | We align and prioritise our work towards the outcomes, using a roadmap. |
| Principle 5: Work with your stakeholders | Detailed Guide Page | We identify our stakeholders and take them on a journey with us. We work with them, not at them. |
| Principle 6: Do the hard work with your team | Detailed Guide Page | We do the hard work so that everyone on our team knows what's expected of them. |
| Principle 7: Lead with evidence | Detailed Guide Page | We're evidence led. We do not let our own preferences guide our thinking. We know our products better than anyone. |
| Principle 8: Raise the bar | Detailed Guide Page | We help raise the bar for product management. We help people where we can and are not afraid to ask for help ourselves. We are bold. |
| Product communication | Detailed Guide | Communicate with other product managers. |
| Product community | Detailed Guide | Our people, meetups, and how we're developing product management capability across the department. |
| Product leadership | Detailed Guide | Our product management profession leadership team, what they do, and how to contact them. |
| Product management | Collection | Guidance and information for any product manager working in the Department for Education. |
| Product values | Detailed Guide | The characteristics that we aspire to as product managers. |
View content index for Security architect
| Title | Type | Description |
|---|---|---|
| Architecture | Collection | Principles, standards and guidance we expect teams working in the Department for Education to follow. |
| Architecture profession | Detailed Guide | tk |
| Architecture roles | Detailed Guide | tk |
| Business architecture | Detailed Guide | tk |
| Repositories | Detailed Guide | tk |
View content index for Service designer
| Title | Type | Description |
|---|---|---|
| 1. Understand users and their needs | Detailed Guide Page | Take time to understand users' needs and the problem you're trying to solve for them. |
| 2. Solve a whole problem for users | Detailed Guide Page | Consider where your service fits in your users' journey and whether you can solve a whole problem or influence a wider solution. |
| 3. Provide a joined up experience across all channels | Detailed Guide Page | Consider where your service fits into a wider journey or alongside other DfE services, and how it will join up across channels. |
| 4. Make the service simple to use | Detailed Guide Page | Build a service that's simple to use so that people can succeed first time. Test it with users to make sure it works for them. |
| 5. Make sure everyone can use the service | Detailed Guide Page | Make sure your service can be used by people with different needs, whether it's for public use, DfE staff or across the education sector. |
| 8. Iterate and improve frequently | Detailed Guide Page | Make sure you have the capacity, people, and technical flexibility to iterate and improve frequently. Focus on improvements that deliver most value. |
| Apply the Service Standard in the Department for Education | Detailed Guide | Guidance and information for how to apply the GOV.UK Service Standard to design and build accessible, user centred and secure services in DfE. |
View content index for Software developer
| Title | Type | Description |
|---|---|---|
| 11. Choose the right tools and technology | Detailed Guide Page | Choose tools and technology that let you build a good service in an efficient, cost-effective way. |
| 12. Make new source code open | Detailed Guide Page | Aim to make all new source code open and reusable, and publish it under appropriate licences. |
| 13. Use and contribute to open standards, common components and patterns | Detailed Guide Page | Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs. |
| 14. Operate a reliable service | Detailed Guide Page | Ensure your service is available for use at the time users need to access it. Where a service is unavailable, have a plan to deal with its recovery. |
| 9. Create a secure service which protects users' privacy | Detailed Guide Page | Understand what data your service collects, and how it's stored and used. Identify and address security, legal, privacy and confidentiality risks. |
View content index for Solution architect
| Title | Type | Description |
|---|---|---|
| Architecture | Collection | Principles, standards and guidance we expect teams working in the Department for Education to follow. |
| Architecture profession | Detailed Guide | tk |
| Architecture roles | Detailed Guide | tk |
| Business architecture | Detailed Guide | tk |
| Repositories | Detailed Guide | tk |
View content index for Technical architect
| Title | Type | Description |
|---|---|---|
| Architecture | Collection | Principles, standards and guidance we expect teams working in the Department for Education to follow. |
| Architecture profession | Detailed Guide | tk |
| Architecture roles | Detailed Guide | tk |
| Business architecture | Detailed Guide | tk |
| Repositories | Detailed Guide | tk |
View content index for User researcher
| Title | Type | Description |
|---|---|---|
| 1. Understand users and their needs | Detailed Guide Page | Take time to understand users' needs and the problem you're trying to solve for them. |
| 2. Solve a whole problem for users | Detailed Guide Page | Consider where your service fits in your users' journey and whether you can solve a whole problem or influence a wider solution. |
| 3. Provide a joined up experience across all channels | Detailed Guide Page | Consider where your service fits into a wider journey or alongside other DfE services, and how it will join up across channels. |
| 5. Make sure everyone can use the service | Detailed Guide Page | Make sure your service can be used by people with different needs, whether it's for public use, DfE staff or across the education sector. |
| 8. Iterate and improve frequently | Detailed Guide Page | Make sure you have the capacity, people, and technical flexibility to iterate and improve frequently. Focus on improvements that deliver most value. |
| Apply the Service Standard in the Department for Education | Detailed Guide | Guidance and information for how to apply the GOV.UK Service Standard to design and build accessible, user centred and secure services in DfE. |