DDTS doctrine: our non-negotiables¶
Seven non-negotiables set by the Chief Digital and Information Officer for Defra's Digital, Data and Technology Services (DDTS). They give everyone a common way of thinking and a consistent basis for decisions, so people can decide well without escalating every choice.
Draft - to be confirmed
This is the CDIO's initial draft. It will be refined, challenged and improved with colleagues across DDTS over the coming months.
Why doctrine, not principles
Principles are often interpreted as advisory; a doctrine is different. It provides a common way of thinking and a consistent basis for decision-making. It helps people make good decisions without needing to escalate every choice, while ensuring we move in the same direction as a function.
The doctrine sits above the architecture principles and the guardrails. The principles explain how architecture applies the doctrine; the guardrails make it practical for delivery teams. See how they fit together.
1. Platforms before projects. Built as products.¶
We will increasingly invest in reusable platforms and long-lived products rather than creating one-off solutions for individual programmes. This will let us scale delivery, reduce duplication and improve consistency across Defra.
For example: instead of every programme commissioning its own technology solution, we build reusable capabilities on the Core Delivery Platform that can be used many times.
Where this shows up: GR-PRIN-01 Delivery-focused architecture, GR-PRIN-03 Maximise value, minimise waste, GR-HOST-01 Use Defra's strategic delivery platform, technology capabilities.
2. Standards and guardrails before exceptions.¶
Standards exist to help us move faster, reduce risk and improve interoperability. Exceptions will always be possible where justified, but they should be the exception rather than the starting point.
For example: teams use Defra's approved identity, security and hosting patterns by default, and only seek exceptions where there is a clear business need.
Where this shows up: the guardrails, exceptions to guardrails, GR-IAM-01, GR-SEC-01, GR-HOST-01.
3. Reuse before buy.¶
Before procuring new technology, we first ask whether an existing capability, platform or service can meet the need. This reduces complexity, improves value for money and creates a more coherent technology landscape.
For example: before buying a new workflow tool, we first ask whether an existing platform already provides that capability.
Where this shows up: GR-PRIN-03 Maximise value, minimise waste, GR-TECH-01 Look for something to reuse first, technology capabilities.
4. Data is an enterprise asset.¶
Data belongs to the organisation, not to individual systems, teams or programmes. We manage data as a strategic asset that can be reused securely to improve services, decisions and outcomes.
For example: we do not ask colleagues or citizens for the same information more than once if we already hold it and can use it appropriately and lawfully.
Where this shows up: GR-PRIN-04 Clean data, clear decisions, GR-DATA-01 Every data set has an owner, GR-DATA-04 Collect once, share safely, Defra on a page.
5. Assume AI until proven otherwise.¶
When tackling a problem or designing a service, we actively consider whether AI can improve quality, productivity, user experience or outcomes. This does not mean using AI everywhere. It means being deliberate about exploring the opportunity before dismissing it.
For example: when designing a new process, we first consider whether AI could automate repetitive tasks, improve decision-making or enhance the user experience, before defaulting to a traditional approach.
Where this shows up: GR-PRIN-07 Empower to innovate, GR-AI-01 Consider AI first, artificial intelligence guardrails.
6. Outcomes and services over organisational structures.¶
Citizens and colleagues experience services, not organisational charts. We organise our thinking around outcomes, user needs and end-to-end services rather than internal boundaries.
For example: when improving a service, we focus on the end-to-end experience for the user, even if that needs several teams to work across organisational boundaries.
Where this shows up: GR-PRIN-02 Design for users, business capabilities, which are deliberately independent of organisation structure.
7. Digital first where appropriate.¶
We challenge manual and paper-based processes by default, and design digital services that are simpler, faster and easier to use.
For example: when redesigning a process, we start by asking how it could work digitally, rather than replicating existing manual steps online.
Where this shows up: GR-PRIN-02 Design for users, front end and accessibility, the Defra Digital Service Manual.
Help shape the doctrine¶
The doctrine is not being developed behind closed doors. Over the coming months it will be refined, challenged and improved with colleagues from across DDTS, and it will evolve as we learn. Tell us how it works in practice by opening an issue or talking to your head of profession.