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

What are you looking for?

Standard : Customer impact is the basis for all prioritisation

Purpose and Strategic Importance

This standard ensures prioritisation decisions are driven by real customer needs, aligning effort with the highest user impact. It keeps teams focused on what matters most for delivering meaningful outcomes.

Aligned to our "Customer-First Thinking" policy, this standard fosters shared clarity on value creation. Without it, resources may be invested in lower-impact work, delaying or diminishing benefits for customers.

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: Work is prioritised based on internal opinions or stakeholder demands.

  • Level 2 – Managed: Teams occasionally incorporate customer feedback in planning.

  • Level 3 – Defined: Prioritisation frameworks incorporate customer impact consistently.

  • Level 4 – Quantitatively Managed: Customer value metrics guide prioritisation and are reviewed regularly.

  • Level 5 – Optimising: Customer impact is continuously assessed and drives real-time decision-making.


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
  • Customer-First Thinking
  • Outcome-Driven Development
Associated Practices
  • GitOps
  • Trunk-Based Development
  • Application Performance Monitoring (APM)

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

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