> That said, I think anything that makes it to the backlog is naturally low value: if it were higher value, it would have been pushed up. This assumes the com

> That said, I think anything that makes it to the backlog is naturally low value: if it were higher value, it would have been pushed up. This assumes the company is making sound decisions. I see companies prioritise new sales over features that would make the software more usable and effective in existing deployments. This prioritisation of immediate cash flow makes it much harder for the organisation to understand why some customers ditch the product later or don't use it enough to knit it into their processes. It is the perennial enterprise question as to whose needs are more important? The features the CEOs/CTOs of new customers ask for, or the productivity features the users of the products ask for. In other cases operational efficiency can be easily backlogged just because its harder to perceive. I've seen specialists and consultants be required for installation and setup because key features required for ease of deployment and use are never prioritised. Its easier budgetarily to just write a bit of python to paper over some cracks than get the required features into the core product but this just broadens the code base and arguably increases the liability. Later, managers might hand-wring about why its so expensive to deploy and maintain without ever being able to prioritise the relevant tickets to address those issues.