They want to please everyone. Basically, what ends up happening is that new features get added but the company doesn't want to choose which buttons are more imp

They want to please everyone. Basically, what ends up happening is that new features get added but the company doesn't want to choose which buttons are more important than others. There is no one-size-fits all solution: every option makes somebody else's workflow worse. The most "neutral" and "logical" solution is to construct an ontology of button types and then materialize that in the form of nested menus. Hurts everyone the same. I think this is a problem at the product-management level, where they cannot decide which user persona they want to prioritize. Could also be financially related, and other users complain when the company picks a side.