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

What are you looking for?

Standard : Real-time value metrics are surfaced through monitoring

Purpose and Strategic Importance

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.

Strategic Impact

  • Improved decision-making quality and speed
  • Greater alignment between engineering work and value outcomes
  • Faster detection of misaligned or underperforming features
  • Increased confidence in delivery prioritisation
  • Stronger continuous improvement culture

Risks of Not Having This Standard

  • Delivery becomes output-focused rather than outcome-focused
  • Delayed discovery of misaligned features or initiatives
  • Reduced stakeholder confidence in engineering work
  • Missed opportunities to innovate based on customer needs
  • Difficulty demonstrating impact of engineering investments

CMMI Maturity Model

Level 1 – Initial

Category Description
People & Culture Teams focus on output, not value impact.
Little or no discussion of business outcomes.
Process & Governance Success is measured by activity or volume.
Value is not tracked post-release.
Technology & Tools No systems to monitor real-time value.
Telemetry focuses only on system health.
Measurement & Metrics Value is assumed, not measured.
No link between features and outcomes.

Level 2 – Managed

Category Description
People & Culture Outcomes are discussed occasionally,
typically during retrospectives or reviews.
Process & Governance Some initiatives define intended value,
but tracking is manual or ad hoc.
Technology & Tools Teams use reports or spreadsheets
to track basic outcome indicators.
Measurement & Metrics Outcome data is captured for a few features,
but lacks consistency or depth.

Level 3 – Defined

Category Description
People & Culture Product and engineering define value
metrics together for all significant work.
Process & Governance Value metrics are part of the Definition of Done
and reviewed during delivery ceremonies.
Technology & Tools Dashboards show real-time value telemetry
alongside technical health indicators.
Measurement & Metrics All features are linked to measurable outcomes,
and data is reviewed post-release.

Level 4 – Quantitatively Managed

Category Description
People & Culture Teams adapt based on live value data.
Experimentation is informed by trends.
Process & Governance Continuous improvement incorporates
value signals and customer impact.
Technology & Tools Platforms automatically collect and analyse
value data with alerting thresholds.
Measurement & Metrics Value trends inform product direction.
Metrics drive investment decisions.

Level 5 – Optimising

Category Description
People & Culture A culture of innovation and optimisation
based on value data is embedded.
Process & Governance Predictive insights and market trends
drive proactive planning and investment.
Technology & Tools Analytics tools surface emergent signals
and automate decision triggers.
Measurement & Metrics Value definitions are continuously refined
based on customer behaviour and feedback.

Key Measures

  • % of initiatives with live value metrics
  • % of releases with linked outcome tracking
  • Frequency of roadmap changes informed by value data
  • Detection rate of underperforming features
  • Visibility of value telemetry in operational dashboards
Associated Policies
  • Data-Driven Decision-Making

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

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