The application I'm working on maintains lists of timezones, countries, cities, & venues, and it allows the user to manage those lists (list/add/edit/remove) via a menu.
My initial approach was to create a menu header 'Locations' and list the data types in the order above, thereby providing the user a visual representation of the context of the data they're working with. The menu items become increasingly more specific as you go down the list.
It occurs to me however that the frequency with which the user will need to manage these data types is the inverse - they will need to manage venues much more often than timezones. This would suggest inverting the menu order to put the most frequently accessed item at the top.
When doing this however, the sense of context is somewhat lost and it feels less intuitive.
Has anyone conducted any studies or have any experience that would guide such a decision between these two alternatives?