WATCH NOW: Measurable outcomes in digital product delivery

The conversation centred around a shared frustration: progress continues to be measured using traditional metrics such as velocity. As Ritam Gandhi puts it: “It’s not about velocity – It is about making sure we are having metrics that are measuring impact.” During this discussion, the panel advocated for outcome-based delivery; tying engineering work directly to ROI, customer satisfaction and business goals.

One example was Studio Graphene’s recent launch of its proprietary technology platform, Pulse, which was developed to track both performance and sentiment across delivery teams. Studio Graphene quickly realised that raw metrics such as code do not tell the whole story. What really drives quality, they found, is how engineers feel about their work – and whether they understand why they are building it.

That emphasis on purpose echoed throughout the discussion. Teams perform better when they are aligned around a shared goal and empowered to contribute to product thinking, not just execution. Several speakers highlighted the value of creating space for creativity, with Cameron Bing noting: “Some of the best ideas come from the most junior engineers who are stuck in the code and solving problems.”

The conversation also looked ahead. As AI accelerates the pace of software creation, panellists predicted a greater need for clarity around product vision, ethical use of data, and meaningful measurement. Output will become cheaper, outcomes will not.

Real success lies not in how much we build, but in what that work achieves. The best teams will be the ones who measure what matters and ignore what doesn’t. You can read more about this subject here “Driving Digital Product Delivery Excellence Report“.