Standards

This standard ensures that confidence levels in data are clearly visible and well-understood at the point of decision-making. It enables teams to make faster, safer, and more informed choices by surfacing data reliability alongside the data itself.

Aligned to our "Data-Driven Decision-Making" policy, this standard strengthens trust in systems, reduces rework caused by poor-quality data, and supports a more transparent, accountable engineering culture.

This standard ensures systems are instrumented to expose meaningful data about their behaviour, enabling teams to detect issues early, understand impact, and make informed decisions.

Aligned to our "Data-Driven Decision-Making" and "Engineering Excellence First" policies, this standard supports proactive monitoring, faster recovery, and better user outcomes. Without it, teams operate in the dark, increasing risk and reducing system trust.

This standard ensures teams plan and execute work based on measurable outcomes rather than just outputs—focusing on the real impact achieved. It aligns efforts with meaningful goals, driving more informed decisions and reducing wasted effort.

Aligned to our "Outcome-Driven Development" policy, this standard keeps teams laser-focused on delivering tangible, trackable value. Without it, work drifts toward checking boxes instead of creating true impact.

This standard ensures that outcomes from completed work are regularly reviewed and used to guide future investments—bridging the gap between delivery and strategy. It closes feedback loops, fosters continuous improvement, and sharpens focus on real impact.

Aligned to our "Outcome-Driven Development" policy, this standard ensures data informs decisions, preventing wasted resources on work that doesn’t deliver tangible value. Without it, prioritisation drifts, and opportunities for meaningful impact are missed.

Continuous Value Flow means every change – big or small – moves through an automated pipeline from merge to production in a consistent, observable, low-risk fashion. Embedding this outcome ensures teams deliver user value faster, recover from failures more quickly, and maintain a high bar on quality.

This standard ensures that the active work being done consistently reflects current business priorities, keeping teams focused on what matters most. It promotes agility, reduces wasted effort, and accelerates value delivery.

Aligned to our "Limit Work in Progress (WIP)" and "Outcome-Driven Development" policies, this standard helps teams adapt quickly to shifting needs. Without it, misaligned work undermines strategic goals, slows feedback, and wastes resources.

This standard ensures every piece of work has clearly defined, measured, and shared business value – aligning delivery with tangible outcomes. It creates transparency on why the work matters and how success is tracked.

Aligned to our "Measure & Validate Value" policy, this standard enables informed prioritisation, continuous feedback, and evidence-based improvement. Without it, teams risk building the wrong things and missing opportunities to maximise impact.

This standard ensures that real-time value metrics are captured and made visible through operational monitoring systems. It helps teams validate that their work delivers measurable outcomes, driving alignment between engineering, product, and business goals.

Aligned to our "Data-Driven Decision-Making" policy, this standard promotes continuous feedback, faster adaptation, and prioritisation based on real impact. Without it, teams risk focusing on technical outputs rather than delivering meaningful customer or business value.

This standard ensures technical excellence is recognised, shared, and celebrated—strengthening quality, innovation, and team pride. By making excellence visible, we fuel continuous learning, collaboration, and higher standards.

Aligned to our "Engineering Excellence First" and "Foster Craftsmanship & Mastery" policies, this standard drives a culture that rewards diligence and craftsmanship. Without it, key achievements go unnoticed, and motivation to raise the bar wanes.

This standard ensures prioritisation decisions are driven by real customer needs, aligning effort with the highest user impact. It keeps teams focused on what matters most for delivering meaningful outcomes.

Aligned to our "Customer-First Thinking" policy, this standard fosters shared clarity on value creation. Without it, resources may be invested in lower-impact work, delaying or diminishing benefits for customers.

This standard ensures systems are integrated through stable, loosely coupled interfaces—enabling teams to evolve domains independently without breaking changes. It supports resilience, modularity, and flexibility at scale.

Aligned to our "Architect for Change" policy, this standard reduces integration risk, improves maintainability, and strengthens autonomy. Without it, changes ripple unpredictably across domains, slowing delivery and increasing system fragility.

This standard ensures that product and engineering decisions are grounded in live, reliable data—enabling teams to prioritise effectively, validate assumptions, and adapt with confidence.

Aligned to our "Data-Driven Decision-Making" policy, this standard strengthens accountability, improves responsiveness, and reduces risk. Without it, teams operate on guesswork, slowing progress and increasing the chance of misaligned outcomes.

This standard ensures teams regularly review and retire low-value features, preventing bloat and maintaining a clear, high-impact product. It frees up capacity, reduces user confusion, and aligns development with measurable outcomes.

Aligned to our "Measure & Validate Value" policy, this standard drives continuous improvement and focus on what truly matters. Without it, products become cluttered, maintenance costs rise, and user satisfaction suffers.

This standard ensures that monitoring is a first-class capability built into system design, development, and operations. By instrumenting services, infrastructure, and user workflows with real-time metrics, health checks, and user-experience indicators, teams gain the visibility needed to detect anomalies early, troubleshoot effectively, and maintain high levels of service reliability.

This standard ensures teams take active ownership of their internal technical standards, evolving them to meet changing needs while sustaining high engineering quality. By embedding autonomy and accountability into daily work, teams are empowered to innovate confidently while maintaining consistency and alignment.

Aligned to our "Engineering Excellence First" and "Architect for Change" policies, this standard encourages teams to continuously improve their craft, reduce friction, and strengthen their shared identity. Without it, quality drifts, practices stagnate, and teams become overly dependent on top-down mandates.

This standard ensures systems are architected with modularity and adaptability in mind, enabling teams to make changes safely, quickly, and with minimal disruption. It promotes long-term agility and reduces the hidden cost of architectural debt.

Aligned to our "Architect for Change" policy, this standard supports scalable design, faster iteration, and technical resilience. Without it, change becomes costly, fragile, and a blocker to innovation.

This standard ensures that patterns from failures are systematically analysed and used to guide architectural decisions. It turns operational pain into long-term improvement, enabling teams to invest in resilience where it matters most.

Aligned to our "Post-Incident Learning Culture" policy, this standard promotes smarter design, reduces repeat failures, and supports continuous learning. Without it, teams risk fixing symptoms instead of causes—slowing progress and weakening system reliability.

This standard ensures that lessons from incidents are not lost but actively drive engineering improvements. It turns short-term recovery into long-term resilience, helping teams build better systems through continuous learning.

Aligned to our "Post-Incident Learning Culture" policy, this standard fosters accountability, strengthens feedback loops, and prevents recurrence. Without it, incidents repeat, trust erodes, and opportunities to grow are missed.

This standard ensures automation is a core part of team mindset and system architecture—not an afterthought. By embedding automation into how we design and build, teams reduce manual effort, improve consistency, and deliver with greater speed and confidence.

It supports our policy to "Automate everything possible" and reinforces a modern engineering culture that values self-service, resilience, and scalable operations. Without this focus, teams risk fragmented systems, slower delivery, and rising operational debt.

This standard ensures that system documentation evolves alongside the system itself, reflecting both design intent and real-world implementation. By maintaining accurate, up-to-date, and accessible documentation, teams can onboard faster, make safer changes, and retain architectural integrity over time.

Aligned to our "Architect for Change" policy, this standard closes knowledge gaps, strengthens accountability, and reduces delivery friction. Without it, organisations risk confusion, inconsistency, and repeated mistakes due to missing or misleading documentation.

This standard ensures that tests provide reliable, actionable confidence in code changes, allowing teams to move quickly without compromising stability. Effective testing practices catch issues early, reduce rework, and underpin safe, continuous delivery.

Aligned to our "Engineering Excellence First" and "Architect for Change" policies, this standard promotes technical assurance, repeatable quality, and accelerated learning. Without it, teams ship with uncertainty, increasing the risk of defects, regressions, and user impact.

This standard ensures build, test, and deploy processes are fully automated and consistently applied. By removing manual steps, teams gain speed, reduce errors, and create more stable, reliable releases.

It supports our policy to "Automate everything possible" and drives a delivery culture focused on flow, repeatability, and quality at scale. Without this standard, teams risk slow, error-prone deployments, reduced confidence, and mounting technical debt.

This standard ensures codebases consistently reflect high-quality engineering practices, enabling systems that are reliable, maintainable, and scalable. It promotes shared accountability for technical integrity and strengthens confidence in delivery outcomes.

Aligned to our "Engineering Excellence First" policy, this standard drives consistency, readability, and long-term value across teams. Without it, teams risk fragmented code, technical debt, and reduced ability to evolve systems with speed and safety.

AI systems derive value from data. Without reliable access to relevant internal data, AI initiatives remain superficial — relying on generic models that cannot reflect organisational context, knowledge, or operations. This standard ensures that internal data, knowledge artefacts, and operational signals are structured, catalogued, and made accessible through governed mechanisms that allow AI systems to retrieve, interpret, and reason over them safely and accurately.

Aligned to our "Data-Driven Decision-Making" policy, this standard drives the conditions necessary for AI to become a genuine organisational capability rather than a collection of isolated experiments. Accessibility must be balanced with governance: poorly managed access risks data leakage, compliance violations, and incorrect AI outputs. At maturity, data becomes an organisational asset continuously feeding intelligent systems that enhance both operational efficiency and strategic decision-making.

This standard ensures major incidents are followed by timely, blameless reviews that focus on learning, not fault. It helps teams uncover root causes, share insights, and strengthen systems without fear or blame.

Aligned to our "Post-Incident Learning Culture" policy, this standard builds trust, encourages transparency, and improves system resilience. Without it, teams miss critical learning opportunities and risk repeating avoidable failures.

This standard ensures every team member feels safe, respected, and included—regardless of role, background, or perspective. It fosters a culture where people can contribute fully, challenge ideas, and grow with confidence.

Aligned to our "Psychological Safety First" policy, this standard strengthens collaboration, trust, and innovation. Without it, voices go unheard, engagement drops, and team cohesion suffers.

This standard ensures psychological safety is not left to chance but treated as a measurable, improvable component of high-performing teams. It empowers individuals to speak candidly, challenge ideas constructively, and take informed risks without fear of judgment or punishment.

Aligned to our "Psychological Safety First" and "Post-Incident Learning Culture" policies, this standard supports learning, innovation, and resilience. Without it, issues remain hidden, feedback loops break down, and the full potential of people and teams is lost.

This standard ensures that teams deliver at a pace that is sustainable, humane, and productive. By maintaining a healthy rhythm of work, teams can stay energised, resilient, and continuously improve over time. This creates the conditions for innovation and long-term delivery effectiveness.

Aligned to our "Balance Sustainability with Speed" policy, this standard protects team wellbeing, preserves morale, and reduces the cost of overwork and burnout. Without it, delivery becomes short-sighted, reactive, and damaging to both people and outcomes.

This standard ensures high-risk changes are proactively identified, evaluated, and routed through appropriate controls. It helps protect system stability while preserving delivery speed and team confidence. The goal is to avoid both reckless change and excessive bureaucracy.

Aligned to our "Architect for Change" and "Psychological Safety First" policies, this standard reduces the likelihood of failure while enabling fast, informed decision-making. Without it, high-impact issues may go undetected, or delivery may be hindered by unnecessary gatekeeping.

This standard ensures teams treat risk and failure as essential ingredients for learning and innovation. By fostering reflection and experimentation, teams grow stronger and more resilient over time.

Aligned to our "Psychological Safety First" and "Post-Incident Learning Culture" policies, this standard creates space for safe risk-taking and continuous improvement. Without it, fear stifles progress and opportunities for meaningful change are missed.

This standard ensures that teams direct innovation efforts towards opportunities that create lasting competitive advantage. It promotes outcome-focused experimentation and continuous learning that supports our strategic goals.

Aligned to our "Psychological Safety First" and "Invest in Differentiators" policies, this standard enables purpose-led innovation without fear. Without it, innovation risks becoming scattered, short-term, or misaligned with the organisation's direction.

This standard ensures technical debt is actively identified, prioritised, and reduced over time, preventing drag on delivery, quality, and morale. It promotes sustainable engineering practices and long-term team health.

Aligned to our "Balance Sustainability with Speed" and "Eliminate Waste" policies, this standard safeguards system maintainability and developer productivity. Without it, teams struggle with friction, compounding rework, and delivery risk.

This standard ensures that team health indicators—such as morale, workload, and burnout risk—are reviewed alongside delivery metrics. It promotes balanced decision-making that values both wellbeing and outcomes, helping teams sustain performance over time.

Aligned to our "Balance Sustainability with Speed" and "Measure & Validate Value" policies, this standard creates space for reflection, support, and continuous adaptation. Without it, teams risk burning out in pursuit of delivery goals, leading to talent attrition, declining quality, and short-lived wins.

This standard ensures that decision-making authority is embedded within the teams closest to the work rather than concentrated at the top of the organisational hierarchy. It supports speed, clarity, and ownership—key drivers of a high-performing and motivated engineering culture.

Aligned to our "Decentralised Decision-Making" and "Developer Experience Matters" policies, this standard eliminates unnecessary escalation, reduces bottlenecks, and encourages accountability. Without it, decisions are delayed, quality suffers, and autonomy is undermined.

This standard ensures that our hiring, onboarding, and progression practices are inclusive, equitable, and transparent—creating an environment where all individuals have equal opportunity to thrive. It helps us attract and retain diverse talent, reduce bias, and build a culture of fairness, representation, and psychological safety.

Aligned to our "Inclusive & Diverse Engineering Culture" and "Psychological Safety First" policies, this standard enables teams to be stronger, more creative, and more resilient through diversity of thought. Without it, we risk perpetuating exclusion, limiting potential, and undermining our values.

This standard ensures feedback flows upward to leadership as well as across teams, enabling informed decision-making, transparent communication, and a culture of continuous improvement. It helps leaders stay close to delivery reality and adapt based on real-world insight—not just assumptions.

Aligned to our "Fast Feedback Loops" and "Minimise Handoffs" policies, this standard builds trust, nurtures psychological safety, and gives teams a voice in shaping the environment they operate within. Without it, leadership blind spots persist, challenges fester, and performance stagnates.

This standard ensures teams embrace and celebrate growth through intentional learning practices—like retrospectives, pairing, and knowledge sharing. It cultivates curiosity, reinforces mastery, and builds collective confidence.

Aligned to our "Psychological Safety First" policy, this standard helps teams treat learning as progress, not failure. Without it, growth becomes accidental, and valuable insights are lost or overlooked.

This standard ensures engineers can make meaningful contributions from their first day, supported by streamlined onboarding, accessible documentation, intuitive tools, and a welcoming culture. It accelerates time-to-impact, boosts early confidence, and builds momentum in the developer journey.

Aligned to our "Developer Experience Matters" and "Foster Craftsmanship & Mastery" policies, this standard reduces friction, increases engagement, and ensures that new joiners quickly become productive members of the team. Without it, valuable time is lost, early motivation declines, and delivery suffers.

This standard ensures teams regularly reflect on their technical decisions, patterns, and practices – creating space for deliberate improvement and shared learning. It deepens expertise and strengthens engineering culture.

Aligned to our "Foster Craftsmanship & Mastery" policy, this standard promotes continuous growth and thoughtful delivery. Without it, teams risk stagnation, repeated mistakes, and missed opportunities to raise the bar.

This standard ensures teams have autonomy to shape and optimise their development environments to suit their needs, improving productivity, satisfaction, and delivery flow. It supports faster onboarding, focused development, and a stronger sense of ownership.

Aligned to our "Developer Experience Matters" and "Empower Teams to Self-Serve" policies, this standard reduces engineering friction and enables secure, scalable customisation. Without it, engineers face rigid tooling, inconsistent environments, and low engagement.

This standard ensures teams are alerted whenever critical feedback loops—like monitoring, user feedback channels, or metrics—stop providing insights. It prevents blind spots that delay detection of issues or drift from goals.

Aligned to our "Fast Feedback Loops" policy, this standard protects against silent failures in telemetry and communication. Without it, problems go unnoticed, causing longer recovery times and lost opportunities to adapt.

This standard ensures that systems deliver timely, context-aware notifications to the right stakeholders—before thresholds are breached or incidents occur. By designing proactive notification capabilities into services, teams surface actionable insights, prevent escalations, and maintain stakeholder confidence.

Aligned to our "Automate Everything Possible" policy, this standard transforms monitoring from a reactive safety net into a proactive enabler of resilience and operational excellence. Without it, teams face higher incident volumes, slower recovery times, and reduced trust from users and stakeholders.

This standard ensures Continuous Integration (CI) pipelines are engineered for speed, reliability, and enforce essential quality gates automatically. Fast, stable pipelines shorten feedback loops, reduce the cost of change, and ensure defects are caught early without slowing down delivery.

Aligned to our "Automate Everything Possible" and "Engineering Excellence First" policies, this standard improves team velocity, delivery confidence, and technical quality. Without it, delivery slows down, errors creep into production, and engineering teams lose confidence in their ability to release safely at speed.

This standard ensures strategy and delivery remain in sync through continuous feedback loops—letting teams adjust execution based on real-time insights. It fosters agility, reduces misalignment, and maximises impact.

Aligned to our "Fast Feedback Loops" policy, this standard drives iterative learning and strategic refinement. Without it, delivery drifts off-course, wasting effort and diluting business value.

This standard ensures teams measure time spent in each stage of their delivery workflow, making bottlenecks and wait states visible. By tracking time-in-status data, teams can continuously optimise flow and reduce wasted effort.

Aligned with our "Limit Work in Progress (WIP)" policy, this standard promotes faster, more predictable delivery and stronger collaboration. Without it, bottlenecks remain hidden, lead times stretch, and continuous improvement stalls.

This standard ensures that artifact promotion between environments (e.g., development, staging, production) is fully automated, governed, and traceable. Promoting validated artifacts without rebuilds preserves integrity, reduces human error, and accelerates safe delivery.

Aligned to our "Automate Everything Possible" and "Architect for Change" policies, this standard protects build fidelity, strengthens security, and increases deployment speed and confidence. Without it, deployments become manual, inconsistent, and error-prone, undermining trust in delivery pipelines.

This standard ensures changes are deployed to production frequently and sustainably, enabling faster feedback, safer releases, and quicker time-to-value. Deployment Frequency (DF) is a key DORA metric and a signal of healthy engineering flow.

Aligned to our "Fast Feedback Loops" and "Empower Teams to Self-Serve" policies, this standard promotes autonomy, reduces risk, and supports continuous delivery. Without it, releases become bottlenecks, innovation slows, and operational risk increases.

This standard ensures each platform capability defines clear boundaries of responsibility—what it owns, how it’s used, and where teams maintain control. It streamlines collaboration and fosters autonomy.

Aligned to our "Empower Teams to Self-Serve" policy, this standard avoids confusion, reduces misaligned dependencies, and accelerates delivery. Without it, overlaps and gaps in accountability slow progress and create unnecessary friction.

This standard ensures recurring operational tasks are automated before they become a burden, preserving engineering focus for high-value work. It helps teams scale sustainably and avoid burnout from repetitive manual effort.

Aligned to our "Automate everything possible" policy, this standard improves efficiency, consistency, and system reliability. Without it, teams risk wasted effort, growing technical debt, and reduced capacity for innovation.

This standard ensures teams have the autonomy to decommission their own systems and services when they no longer add value. It prevents accumulation of legacy platforms and drives continuous improvement in architecture.

Aligned to our "Decentralised Decision-Making" policy, this standard promotes ownership, agility, and efficient resource use. Without it, outdated systems linger, slowing progress and increasing maintenance overhead.

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.

This standard ensures teams minimise lead time—from the start of work to safe production deployment—by targeting Lead Time for Change (LTFC), a key DORA metric. Shorter lead time lowers risk, accelerates learning, and increases delivery flow efficiency.

Aligned to our "Fast Feedback Loops" and "Limit Work in Progress (WIP)" policies, this standard reveals and resolves bottlenecks that slow value creation. Without it, teams endure lengthy development cycles, delayed feedback, and hidden coordination costs.

This standard ensures customer feedback is continuously captured, analysed, and acted on—closing the loop between delivery and real-world outcomes. It helps teams stay responsive, reduce waste, and build what truly matters.

Aligned to our "Fast Feedback Loops" and "Customer-First Thinking" policies, this standard turns insights into action and strengthens user-centric design. Without it, teams risk drifting from user needs, repeating mistakes, and missing opportunities for improvement.