Some thoughts I wanted to get out: I think we need Outcome Driven Development- we define a metric measured in say graphite, we link a ticket to that asserting

Some thoughts I wanted to get out: I think we need Outcome Driven Development- we define a metric measured in say graphite, we link a ticket to that asserting the ticket will make the metric change this way or that, and we commit code to make the metric change so we start a process of defining what we want, implementing how to measure it (there could be a null metric and the ticket is to make it not null) and then measuring our success of changing the metric this will have organisational impacts as well - no one should take a ticket without authority span to impact that metric this will start in the direction of software as literacy or the developer anarchy