Nothing else works for prioritisation, any other categorising into "High/Medium/Low" just fails.
By doing so you end up with the nonsense we had at a company I once worked for, where stories were all put in medium.
This was because stories in low were simply never actioned, they'd never ever get done, everyone came to implicitly understand this. It was still a useful dumping ground for the kinds of stories you know you ought to do, but no-one wanted to do, but it was useful to have noted on record. But for prioritising actual work, it was useless.
Stories in High had a special process defined in a handbook that no-one wanted the hassle of dealing with.
So everything was Medium.
This had obvious problems, and it grew larger than could be managed.
So "Just Above Medium" was born, for stories that were higher priority than your everyday stories in Medium.
This in time grew too, so "Just Above Just Above Medium" (aka JAJAM) was born.
By the time I started, there was even a "JAJAM+" category, for stories that had to be fast-tracked through the process too.
The whole thing essentially fell back to having the product/development leads come to an understanding of what work needed to be done. Which is the right way to do it, but that should simply be made more explicit and part of the process by simply having all stories ranked.
Then you don't need the mental overhead of trying to decide in a design meeting if something is "Just above Medium" or just above that...
CEO can't login during a demo. Sandra from accounting can't print from the closest printer and confirmed this is higher priority
Ticket A: Elevated Response times for Server A outside of allowed tolerance, people experiencing timeouts
Ticket B: Change the colour of a button
I wish Ticket B Submitter could see the ticket before them to gauge what critical actually means.
Long story short: I discontinued their program and it's been 2 years and I still receive those action required emails only to find out that there is absolutely no action required on my side. Harassing users is their favorite past time I swear. Ask the Github desktop folks. On Mac OS, there is no option to disable automatic updates. It loves installing a helper that runs 24/7 with admin privileges. If you click on deny, it will keep harassing you - every. single. day. First thing in the morning - 3 times, 3 times in the evening. You could be in the middle of something important, like a meeting or a screen share or running some serious stuff like CNC milling (which I do) and this thing will just popup and ask you for admin privileges until you accept.
And even if you accept and give it permissions, it just buys you a few days time. People have tried before to open an issue on Github - their response was simply "This isn't a priority for us right now" and they just closed the issue.
Same story with Windows too. I wish there was a law to prevent this kind of bullying behaviour.
Even MS's staff couldn't figure out what resources the "Action Required" email had to do with.