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

What are you looking for?

Policy : Outcome-Driven Development

Commitment to Business and Customer Impact
We do not measure success by the number of features delivered or the complexity of our technology. We measure success by the value we create. Every engineering effort must be driven by clear, measurable business and customer outcomes, ensuring that our work translates into meaningful impact.
We believe that great engineering is not just about writing code - it’s about solving the right problems, at the right time, for the right reasons. By aligning our work with well-defined outcomes, we ensure that our technology investments drive growth, efficiency, and competitive advantage.

What This Means
Teams must shift from a mindset of delivering outputs to delivering outcomes. Engineering decisions should be guided by real business needs, customer pain points, and long-term strategic goals.

Our commitment to Outcome-Driven Development is built on:

  • Alignment with Business Goals – Every engineering initiative must contribute to clear business priorities, ensuring that technology delivers tangible value.
  • Customer & User Impact as a North Star – We design and build with a deep understanding of customer needs, ensuring that our solutions solve real problems.
  • Data-Driven Decision-Making – We use metrics, experimentation, and feedback loops to validate that our work achieves the intended outcomes.
  • Collaboration Across Functions – Engineering works closely with product, design, and business stakeholders to ensure a shared understanding of success.
  • Adaptive, Learning-Based Delivery – We continuously inspect, adapt, and refine our work to ensure alignment with evolving business and customer needs.

Why This Matters
Traditional feature-based delivery often leads to waste, misalignment, and missed opportunities. By focusing on outcomes over outputs, we:

  • Maximise return on engineering investment by ensuring every effort contributes to business success.
  • Increase customer satisfaction by solving meaningful problems, not just shipping features.
  • Foster innovation by enabling teams to experiment, learn, and adapt based on real impact.
  • Enhance agility by focusing on continuous value delivery, rather than rigid, predefined roadmaps.

Our Expectation
All engineering teams must work with a clear understanding of the outcomes they aim to achieve. Leaders must champion outcome-driven thinking, ensuring that work is prioritised, measured, and iterated based on its impact.
To support this policy, clear business metrics, OKRs, and feedback mechanisms will be established, enabling teams to validate success and continuously improve. By embedding Outcome-Driven Development into our ways of working, we ensure that every engineering effort is purposeful, impactful, and aligned with delivering Better Value Sooner Safer Happier.

This policy sets a strong foundation for ensuring engineering teams focus on impact, not just execution.

Associated Standards
  • Customer impact is the basis for all prioritisation.
  • Outcomes are reviewed and used to guide future investments.
  • Teams frame and plan work around outcomes, not outputs.

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

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