This standard ensures developer workflows are optimised for speed, clarity, and flow—minimising friction, blockers, and waste. It enables engineers to focus on delivering value, not fighting tools or processes.
Aligned to our "Developer Experience Matters" and "Minimise Handoffs" policies, this standard improves delivery velocity, engineering satisfaction, and system quality. Without it, productivity drops, morale suffers, and the cost of change increases.
| Category | Description |
|---|---|
| People & Culture | Developers experience frequent blockers, context switches, and unclear responsibilities. There’s low focus on developer satisfaction. |
| Process & Governance | Workflows are inconsistent and manually driven. Processes vary between teams and environments. |
| Technology & Tools | Tooling is fragmented or ad hoc. Setup, onboarding, and daily tasks are slow and error-prone. |
| Measurement & Metrics | Developer productivity and experience are not tracked. |
| Practices | Teams rely on workaround strategies to get work done. |
| Category | Description |
|---|---|
| People & Culture | Awareness of developer pain points is growing. Efforts begin to improve onboarding and reduce obvious friction. |
| Process & Governance | Some standard workflows and practices are emerging. Common tools are introduced, but inconsistently applied. |
| Technology & Tools | Teams adopt version control, task boards, and basic CI/CD tools. Tool usage is still uneven. |
| Measurement & Metrics | Anecdotal developer feedback is occasionally gathered. No structured measurement yet. |
| Practices | Teams attempt to streamline manual tasks and improve development speed. |
| Category | Description |
|---|---|
| People & Culture | Developer experience is treated as a strategic concern. Teams use shared, consistent workflows. |
| Process & Governance | Toolchains, development practices, and review processes are standardised across teams. |
| Technology & Tools | Developer environments, pipelines, and observability tools are consistent and documented. Automation reduces manual toil. |
| Measurement & Metrics | Developer satisfaction, time-to-commit, and time-to-merge are measured regularly. |
| Practices | Practices like trunk-based development, pre-commit hooks, and automated testing are adopted. |
| Category | Description |
|---|---|
| People & Culture | Teams are proactive in identifying inefficiencies and improving workflows. Developer happiness and productivity are reviewed as part of retrospectives. |
| Process & Governance | Metrics drive decisions on developer tooling and experience improvements. |
| Technology & Tools | Developer platforms, templates, and self-service tooling accelerate delivery. |
| Measurement & Metrics | Metrics such as cognitive load, tool wait times, and DevEx scores are reviewed. |
| Practices | Continuous feedback loops inform workflow improvements. Blockers are addressed with urgency. |
| Category | Description |
|---|---|
| People & Culture | Developer workflows are constantly iterated based on live telemetry and user feedback. Experimentation and learning are encouraged. |
| Process & Governance | Workflow friction is monitored and addressed in real time. Changes are rapidly implemented across the ecosystem. |
| Technology & Tools | Tools are intuitive, integrated, and evolve based on developer needs. Developer Portals and Internal Platforms are widely adopted. |
| Measurement & Metrics | Developer Net Promoter Score (Dev-NPS), time to onboard, and satisfaction trends show continuous improvement. |
| Practices | Developers contribute to improving the system. Team practices evolve based on data and experimentation. |