Policy : Standardise for Repeatability and Quality

Commitment to Consistency and Quality Through Standardisation
We believe that consistent, repeatable approaches are foundational to high-quality engineering. Standardisation enables us to move faster, reduce variability, and scale with confidence—without sacrificing flexibility or innovation. When common tasks are simplified through shared standards and reusable assets, teams can focus more energy on solving meaningful problems.

What This Means
We systematise repeatable work using well-defined patterns, templates, and practices. Whether writing code, building infrastructure, managing data pipelines, or resolving incidents, teams should have reliable starting points that reflect best practices and reduce the need to reinvent the wheel.

Our commitment to standardisation and quality is built on:

• Shared Templates and Reusable Modules – Engineering teams use version-controlled templates such as Terraform modules, pipeline definitions, and cookiecutter repositories to ensure consistency and reduce drift.
• Agreed Data Patterns – Data pipelines follow standardised blueprints for ingestion, transformation, validation, and error handling—promoting maintainability and trust in data.
• Golden Paths and Developer Portals – Platform engineering defines and maintains golden paths through curated self-service tooling and documentation that streamline common engineering tasks.
• Engineering Discipline in Git – Git branching models, commit conventions, pull request templates, and code review standards are defined and adopted team-wide to ensure traceability and shared expectations.
• Standard Operating Procedures (SOPs) – Common activities such as deployments, maintenance tasks, and incident responses are backed by documented runbooks that promote consistency under pressure.

Why This Matters
Lack of standardisation leads to duplication, quality issues, and cognitive overload. When every team does things differently, knowledge becomes fragmented, onboarding becomes harder, and issues become harder to diagnose. By contrast, clear standards create a shared baseline that allows quality to scale alongside velocity.

Our Expectation
All teams must adopt shared standards where they exist and contribute to their evolution over time. This includes aligning with versioned templates, collaborating on platform tooling, and maintaining discipline in documentation and runbook usage.

To support this policy, teams will be guided by documented engineering playbooks, agreed templates, platform tooling, and regular reviews of adoption and effectiveness. By standardising for repeatability and quality, we reduce variation, improve reliability, and create a foundation for scalable, sustainable delivery.