• Home
  • BVSSH
  • C4E
  • 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

Category Description
People & Culture Priorities are set based on internal preferences or politics.
Little to no connection to customer outcomes.
Process & Governance Prioritisation criteria are undocumented.
Stakeholder opinion often overrides user needs.
Technology & Tools No tooling connects customer feedback to planning.
Decisions are ad hoc or reactive.
Measurement & Metrics No tracking of value delivered to customers.
Feedback loops are informal or absent.

Level 2 – Managed

Category Description
People & Culture Teams acknowledge the importance of customer impact.
Some effort is made to consider it.
Process & Governance Feedback is used inconsistently in prioritisation.
No standard process exists.
Technology & Tools Some tools capture feedback or usage data,
but not tied into work planning.
Measurement & Metrics Value is occasionally inferred from NPS or support data,
but not structured or reliable.

Level 3 – Defined

Category Description
People & Culture Teams embrace customer-centricity in prioritisation.
Customer outcomes are regularly discussed.
Process & Governance A shared framework (e.g., RICE, impact mapping)
is used to prioritise based on user impact.
Technology & Tools Product analytics and customer feedback tools
inform backlogs and delivery plans.
Measurement & Metrics Customer impact is scoped upfront and tracked post-release
via defined success measures.

Level 4 – Quantitatively Managed

Category Description
People & Culture Prioritisation discussions are guided by customer data.
Teams challenge assumptions with real-world insights.
Process & Governance Decisions are regularly reviewed against outcomes.
Planning cycles adjust based on value delivered.
Technology & Tools Data pipelines connect telemetry, user feedback,
and planning tools.
Measurement & Metrics Impact metrics are tracked and benchmarked
across product areas.

Level 5 – Optimising

Category Description
People & Culture Continuous discovery and delivery converge.
Teams test value hypotheses through iterative releases.
Process & Governance Prioritisation adapts in real time to user behaviour,
emerging needs, and contextual feedback.
Technology & Tools Predictive insights from user signals,
segmentation and sentiment drive strategy.
Measurement & Metrics Value delivery is continuously refined.
Lagging and leading indicators steer product direction.

Key Measures

  • Percentage of prioritised work linked to defined customer outcomes
  • Use of prioritisation frameworks that incorporate customer impact
  • NPS, CSAT or feedback trends pre- and post-release
  • Percentage of features validated through user testing or real-world feedback
  • Backlog items linked to explicit customer problems or usage data
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