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

What are you looking for?

Standard : Teams work backwards from customer and user value

Purpose and Strategic Importance

This standard ensures that teams anchor all delivery decisions in clearly defined customer and user value. By working backwards from desired outcomes—rather than forward from tasks or features—teams can focus effort where it matters most. This mindset shifts delivery from output to outcome, ensuring resources are invested in initiatives that make a tangible difference.

It supports our policy to “Prioritise the Highest Value Work” by reinforcing the importance of value clarity and alignment. Without this approach, teams risk over-delivering on low-impact features while underinvesting in what truly benefits customers and the business.

Strategic Impact

  • Increases delivery impact by tying work to real customer and business needs
  • Enhances prioritisation discipline across teams
  • Reduces waste by eliminating effort on low-value features
  • Strengthens customer empathy and user-centric thinking
  • Aligns engineering, product, and design around shared outcomes

Risks of Not Having This Standard

  • Work is prioritised based on habit, assumption, or internal preference
  • Delivery focuses on outputs (tickets, features) instead of outcomes
  • Misalignment between team activity and customer needs
  • Value is difficult to measure or validate post-release
  • Teams lose sight of who they’re building for and why

CMMI Maturity Model

Level 1 – Initial

Category Description
People & Culture - Delivery is task-driven with little reference to customer needs.
- Value is interpreted inconsistently across teams.
Process & Governance - Work is selected based on capacity or internal urgency.
Technology & Tools - No mechanisms to trace features to user outcomes.
Measurement & Metrics - Success measured by volume of work completed.

Level 2 – Managed

Category Description
People & Culture - Teams recognise the need to focus on value but lack a shared language.
- Some initiatives are loosely aligned to user outcomes.
Process & Governance - Stakeholder input occasionally shapes backlog prioritisation.
Technology & Tools - Basic tooling enables tagging or categorisation of work items.
Measurement & Metrics - Feature adoption and usage tracked post-delivery.

Level 3 – Defined

Category Description
People & Culture - Teams define and validate value hypotheses before committing work.
- Product and engineering collaborate closely on prioritisation.
Process & Governance - Backlog grooming includes impact analysis and user research.
Technology & Tools - Work items linked to measurable outcomes or OKRs.
Measurement & Metrics - % of work tied to validated customer outcomes.

Level 4 – Quantitatively Managed

Category Description
People & Culture - Teams engage with users regularly and use insights to shape delivery.
- Value thinking embedded in ceremonies and decision-making.
Process & Governance - Economic value and opportunity cost inform prioritisation decisions.
Technology & Tools - Tools integrate with analytics platforms for real-time outcome tracking.
Measurement & Metrics - Time-to-value and outcome-to-effort ratios monitored and improved.

Level 5 – Optimising

Category Description
People & Culture - Teams continuously refine what “value” means for each customer segment.
- User feedback is treated as a strategic asset.
Process & Governance - Prioritisation processes adapt based on value learning loops.
Technology & Tools - Automated value impact dashboards drive real-time adjustments.
Measurement & Metrics - % of roadmap items contributing to defined customer value goals.

Key Measures

  • % of work items linked to customer or business outcomes
  • Time from idea to validated customer impact
  • Feature adoption and user satisfaction scores
  • % of backlog items with defined value hypotheses
  • Outcome-to-effort ratio across delivered initiatives
Associated Policies
Associated Practices
  • Customer-Centric Sprint Planning
  • User Research Sprints

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

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