| 1 | Understand users and their needs | User research artefacts, personas, user stories |
| 2 | Solve a whole problem for users | Service map, end-to-end journey |
| 3 | Provide a joined-up experience | Consistent with NHS.UK, NHS App |
| 4 | Make the service simple to use | NHS Design System components, one-thing-per-page |
| 5 | Make sure everyone can use the service | WCAG 2.2 AA, axe-core results, assistive tech testing |
| 6 | Have a multidisciplinary team | Team roles documented, clinical + IG input |
| 7 | Use agile ways of working | Sprints, backlog (GitHub Issues), retros |
| 8 | Iterate and improve frequently | Git log shows iterative commits, not big-bang |
| 9 | Create a secure service | Security headers, dependency scanning, Key Vault |
| 10 | Define what success looks like | KPIs, performance targets, k6 thresholds |
| 11 | Choose the right tools and technology | ADRs explaining technology choices |
| 12 | Make new source code open | Public repo, open licence |
| 13 | Use and contribute to open standards | FHIR, OpenAPI, NHS Data Dictionary |
| 14 | Operate a reliable service | Monitoring, /health endpoint, runbook |