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

What are you looking for?

Standard : Outcomes are reviewed and used to guide future investments

Purpose and Strategic Importance

This standard ensures that outcomes from completed work are regularly reviewed and used to guide future investments-bridging the gap between delivery and strategy. It closes feedback loops, fosters continuous improvement, and sharpens focus on real impact.

Aligned to our "Outcome-Driven Development" policy, this standard ensures data informs decisions, preventing wasted resources on work that doesn’t deliver tangible value. Without it, prioritisation drifts, and opportunities for meaningful impact are missed.

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: Outcome data is rarely collected or used.

  • Level 2 – Managed: Some outcome reviews are held, but impact on strategy is minimal.

  • Level 3 – Defined: Outcome reviews are standard practice and influence future planning.

  • Level 4 – Quantitatively Managed: Outcome trends are tracked over time to inform portfolio decisions.

  • Level 5 – Optimising: Continuous outcome analysis actively shapes product strategy and investment cycles.


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
  • Outcome-Driven Development
Associated Practices
  • Feature Toggles (Flags)
  • Static Application Security Testing (SAST)
  • Integration Testing

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

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