Our web application is built around a single entity, say A.
User creates A1. Then user can do a limited number of actions on A1. If one of this actions is taken by the user on A1, A1 changes to another state and the actions available on A1 changes. User takes another action on A1. State changes and user has different available actions and so on.
One user can have around 3 to 5 entities in his/her inventory.
Current navigation system is based on actions organized in a classic drop-down menu. User selects an action and filters entities to take action on. Takes the action on entity. Selects another action from the menu. If the new action is available for the last entity selected, we display the new action page, otherwise we display a filter control to select a suitable entity. This is a problem because there are a lot of actions resulting in a complex menu with lots of items and user stacking on the workflow. (What can/do I do next?)
We are trying to switch to a navigation that is more user friendly and self explanatory.
Here is what we have so far.
- At home page, User selects an entity.
- Available actions displayed.
- User selects an action and navigates to action page.
- A static navigation bar is displayed somewhere on page that shows the current entity and available actions.
- User can change entity from the menu at any time and available actions are displayed on the navigation bar as the selection changes.
Is this a good approach in terms of user experience? Are there any user interface patterns that is applicable to this case?
Thanks in advance.
I will add some sketches.
Here is the current menu-driven navigation system.
User Selects an Action
User Finds an Entity
User Selects an Entity
User Performs the Action
Action Complete
And here is task-driven navigation system.
User Selects an Entity
User Selects an Action
User Performs Action
Action Complete