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

What are you looking for?

Standard : Technical excellence is made visible and valued

Purpose and Strategic Importance

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.

Strategic Impact

Clearly defined impacts of meeting this standard include improved delivery flow, reduced risk, higher system resilience, and better alignment to business needs. Over time, teams will see reduced rework, faster time to value, and stronger system integrity.

Risks of Not Having This Standard

  • Reduced ability to respond to change or failure
  • Accumulation of technical debt or friction
  • Poor developer experience and morale
  • Decreased confidence in releases and features
  • Misalignment between technical implementation and business priorities

CMMI Maturity Model

  • Level 1 – Initial: Excellence is not recognised or shared systematically.

  • Level 2 – Managed: Some teams highlight achievements, but without broad visibility.

  • Level 3 – Defined: Mechanisms exist to regularly surface and showcase excellence.

  • Level 4 – Quantitatively Managed: Recognition and outcomes are tracked to inform development culture.

  • Level 5 – Optimising: Excellence is systematically amplified to drive pride, community learning, and differentiation.


Key Measures

  • Adoption metrics relevant to the standard (to be defined)
  • Quality, throughput, and system health metrics aligned to capability
  • Maturity scores based on structured assessment
Associated Policies
  • Engineering Excellence First
  • Foster Craftsmanship & Mastery
Associated Practices
  • Alert Fatigue Management
  • Feature Toggles (Flags)
  • Architecture Decision Forums
  • Mob Programming

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

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