It sounds so simple but the amount of work and trade-offs involved in getting to a single list of priorities is where a lot of the difficult work lives.

I’m a big fan of forcing functions and having a single list is a great one.

One big problem with the single list is impedance mismatches between kinds of work i.e. fundamental prerequisites vs. user facing features and tracking dependencies between them. Or operational toil which should not be tracked there but will have an impact on priority and throughput.

https://www.theengineeringmanager.com/growth/one-list-to-rule-them-all/