I am redesigning a navigation menu for a web-based application. The current menu is a list of tasks, grouped by service. The list is growing steadily as we are adding new functionalities and now the users have to scroll down to see all of it. We ideally want the list to be only one page long. Two solutions have been presented:
- Present an accordeon-like menu that will expand for each service
- Grouping tasks together to reduce the menu
For example, our current menu presents options like:
- Change password
- Set permissions
- Manage spam settings
- Search spam
With solution 1, you would only see User and Mailbox, then clicking on either would expand to show the tasks outlined above.
With solution 2, the new menu would present something like:
Solution 1, while decluttering the interface on the first level, will still present the user with a lot of text to read on the second level.
With solution 2, I am worried that the users won't find what they are looking for. For example, a user who is looking to change his password would not nescessarily know to go in the user settings.
Both have their advantages and disadvantages - so which is better? Presenting more options to the user so they can find the exact task they want to do, or grouping the tasks together under a general heading?
Edit: As requested, I have included a screen mockup of the application. On the left is the list of users, selecting a user brings up the task for a user on the right hand side.