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:
Why This Matters
Traditional feature-based delivery often leads to waste, misalignment, and missed opportunities. By focusing on outcomes over outputs, we:
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.