Velocity and KPI

Welcome to the Jira for Designers series brought to you by Design at Scale™ — Academy. In a previous article, we discussed Figmas Segmenst(001↘︎), and we designers help our engineering team locate the right/final things to build. Meanwhile, we will support the ongoing development by versioning our creation. To enhance the impact of the design function in your organisation, we’ll look into Velocity and KPIs. No need to panic. This is a design-centric explanation with further references if you wish to dive deeper into the topic.

Design delivery

Delivery is about the outputs(002↘︎). No outputs, no delivery and no outcomes. Design delivery has often been classed as colouring the wireframes in an advanced sense or, in a loose sense, just a template creation. It took us almost a decade to gain recognition amongst the business and engineering to include the UXR, behaviour-driven CX and automated UI generated by design systems teaming.
Today, design delivery is managed by Waterfall, Agile, Scrum, and Kanban, which have to subserve under the methods that originally didn’t consider the complexity of the reach and impact of “good” and “bad”. That is why the new generation of designers is now asked to measure the impact…