Summary
Use open standards, common components and patterns, and create new ones if there is not one that already meets your needs.
Why it's important
Open standards save money and make use of best practice.
Using common components, patterns, and technology stacks means you don't have to solve problems that have already been solved.
By using a component, pattern, or stack that's already been assured and extensively tested, you can provide users with a good experience in a cost-effective way. It also speeds up delivery and reduces risk.
Developing components and patterns that meet a shared need and sharing them allows others to benefit from your work.
How to meet this standard in every phase
You'll be assessed on what you've done to meet this standard at service assessments. However, even if the service you're working on is not being assessed, it's good practice to consider how you'll meet this standard point.
All phases
Things to consider:
- teams have reached out to other teams and similar services to consider possible patterns, architecture components, and tools
- open source tools and frameworks have been chosen or considered as the basis for the service components
- using GOV.UK Design System common components and patterns
- evidence of a design history to keep track of design decisions, options explored, and rationale for choices made
- recording architecture decision records to track decisions and rationale
- how to share and encourage use of new and existing design patterns and architecture components within the wider DfE service community
Things to avoid in all phases
- reinventing the wheel by not considering existing open standards, components, or patterns
- choosing proprietary solutions without exploring open and common alternatives
Profession specific guidance
Each DDaT profession in DfE has their own community and guidance.