Your comment sparked an idea. Most ticket systems have what can become a somewhat useless “Priority” field which occasionally ends up meaning “above X or below

Your comment sparked an idea. Most ticket systems have what can become a somewhat useless “Priority” field which occasionally ends up meaning “above X or below X”. We try to select the things from every priority that seem either valuable at higher priorities or easy at lower priorities, but a lot of time can get wasted reviewing the same tickets to decide. I am thinking a second similar field of “Risk” would be a great play on this Cost of Delay concept without adding much complexity and might help with more meaningful sorting. Something may be a low priority but a high risk(maybe it isn’t important in itself, but might represent a slice of a bigger risk), or a high priority but a low risk (like something customers want, but in reality is just a nice to have and the product would be fine without it). I suspect “Risk” could be arbitrary or whatever it means to a business, as long as it is consistent. Definitely given something to consider. Thanks for sharing.