• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Systems expose the data needed to understand their behaviour

Purpose and Strategic Importance

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.

Strategic Impact

  • Faster issue detection and root cause analysis
  • Improved recovery time and reliability
  • Increased engineering confidence and autonomy
  • Higher-quality decisions backed by data
  • Better alignment to business outcomes and performance goals

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

Category Description
People & Culture Teams rely on intuition to understand
system behaviour. Observability is not prioritised.
Process & Governance No standard practice for logging or metrics.
Monitoring is reactive and incomplete.
Technology & Tools Minimal instrumentation or alerting in place.
Data is not centralised or accessible.
Measurement & Metrics No clear definition or tracking of system
behaviour indicators.

Level 2 – Managed

Category Description
People & Culture Some teams begin using metrics and logs
to understand system issues.
Process & Governance Observability is recommended but not
consistently applied across services.
Technology & Tools Logs and metrics exist, but formats and
tools vary across systems.
Measurement & Metrics Behavioural metrics are available for some
services, but without standardisation.

Level 3 – Defined

Category Description
People & Culture Teams consistently use observability
to guide troubleshooting and improvement.
Process & Governance Standard practices define required telemetry
and observability patterns.
Technology & Tools Shared tooling provides access to logs,
metrics, and traces across systems.
Measurement & Metrics Key indicators of system behaviour are
collected and reviewed regularly.

Level 4 – Quantitatively Managed

Category Description
People & Culture Teams are trained in observability best
practices and use them proactively.
Process & Governance Behavioural data feeds into SLOs, SLIs,
and risk assessments.
Technology & Tools Dashboards and alerting tools expose
performance, error, and flow metrics.
Measurement & Metrics Trends in system health guide prioritisation
and drive preventative action.

Level 5 – Optimising

Category Description
People & Culture Observability is embedded in daily work,
from design to deployment.
Process & Governance Observability signals shape technical
strategy and cross-team investments.
Technology & Tools Systems are instrumented by default, exposing
behavioural data at all levels.
Measurement & Metrics Feedback from system behaviour drives
resilience, performance, and design improvements.

Key Measures

  • % of systems with standardised observability patterns
  • Time to detect and diagnose production issues
  • Coverage and freshness of system behaviour metrics
  • Frequency of decisions supported by behavioural data
  • Confidence levels in monitoring and observability tooling
Associated Policies
  • Data-Driven Decision-Making
Associated Practices
  • Live Dashboards
  • Synthetic Monitoring
  • Custom Metrics Instrumentation
  • End-user Experience Monitoring
  • Application Performance Monitoring (APM)
  • Distributed Tracing
  • Real-Time Logging

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

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