A few years after the introduction of 6.4 menu layout (ZBXNEXT-7830), my experience is that most users still find it somehow awkward and obscure.
 
Generally speaking: a good menu layout should respect at least two principles:
 
a) Menu order: it should reflect how often a feature is used by the users or the operational path to complete a task. Example of bad order: Services are a very low-used feature and currently it's the second section in the menu. Similarly, template groups are the first entry under Data collection. 
 
b) Section names: it's not enough to provide an abstract grouping, they should guide the user to find the proper functionality. Moreover, all the contained entries must be consistent with the upper section name.

• Monitoring: Zabbix it's all about monitoring, so this section name does not help new users at all. This section is about visualization, why not simply call it "View"?
• Data collection: Zabbix it's mostly about data collection, so this term does not help user. Also it contains triggers, maintenance, discovery and event correlation which have nothing to do with data collection. Why not simply call it "Configure"? 
• Alerts contains things that are not related to alerts as: autoregistration, discovery, ticket integrations, frontend scripts. Why not simply call it "React"?
• Users: why not simply call it "Security" to be broader?

So here's an example of a possible resulting menu layout:

• View
  • Dashboards
  • Problems
  • Hosts
  • Latest data
  • Maps
  • Discovery

• Configure
  • Hosts
  • Templates
  • Host groups
  • Template groups
  • Maintenance
  • Event correlation
  • Discovery

• React
  • Actions
  • Media types 
  • Scripts

• Security
  • Users
  • User groups
  • User roles
  • API token
  • Authentication
  • Audit