• Home
  • BVSSH
  • Engineering Enablement
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Guardrails are co-designed by those closest to delivery

Purpose and Strategic Importance

This standard ensures guardrails are co-designed by the people closest to the work, making them relevant, effective, and trusted. It fosters shared responsibility for safety without imposing top-down controls.

Aligned to our "Guardrails, Not Gates" policy, this standard strengthens autonomy, builds alignment, and increases adoption of safety practices. Without it, guardrails risk being ignored, misaligned, or seen as blockers.

Strategic Impact

  • Improved consistency and quality across teams
  • Reduced operational friction and delivery risks
  • Stronger ownership and autonomy in technical decision-making
  • More inclusive and sustainable engineering culture

Risks of Not Having This Standard

  • Slower time-to-value and increased rework
  • Accumulation of inconsistency and process debt
  • Reduced trust in engineering data, systems, or ownership
  • Loss of agility in the face of change or failure

CMMI Maturity Model

  • Level 1 – Initial: Guardrails are rarely defined or are imposed top-down without input from delivery teams. Adoption is low and enforcement inconsistent.

  • Level 2 – Managed: Some teams begin contributing to the design of guardrails, but participation is limited and not part of a structured process. Guardrails may still be seen as external constraints.

  • Level 3 – Defined: Guardrails are co-designed with input from delivery teams and subject matter experts. Processes are documented, and teams are empowered to tailor them to context.

  • Level 4 – Quantitatively Managed: Co-designed guardrails are tracked for usage, impact, and effectiveness. Feedback loops ensure they evolve with team needs and system changes.

  • Level 5 – Optimising: Guardrail design is embedded in continuous improvement practices. Teams regularly refine them based on outcomes, and shared ownership fosters a culture of proactive safety and autonomy.


Key Measures

  • Adoption rates and coverage across teams
  • Impact on delivery metrics, quality, or team health
  • Evidence of ownership, governance, or learning loops
Associated Policies
  • Guardrails, Not Gates
  • Balance Sustainability with Speed
Associated Practices
  • Error Budget Policies
  • Live Dashboards
  • Behaviour-Driven Development (BDD)

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering