Today we've discussed navigation problems in TargetProcess and all agreed that we have four major issues:
- Similar labels in menu (for example, Reports inside a project area and Custom Reports in top menu).
- Too many links in the header (for example, in Project -> Planning area there are 31 links to click).
- Menu structure and how to get into required place (why Tags Board is in the Dashboard section?).
- It is not clear whether we are inside a project or outside.
We've come up to several improvements that may resolve the problems.
First, we agreed that there were two major different areas: inside and outside of a project. If a user is inside the project, he focuses on project's tasks and will likely not go to Admin or Projects list. So we decided to separate global menu and project menu. It means that inside the project user will not see the top level menu, but just Back to Home link. Also there is no company logo and company name in the project area. It may look like that (just a mockup, not sure about final design):
Benefits? Sure, there are plenty!
- 17 links instead of 31 and more air in the menu.
- No frustration where to click.
- Clear sign that we are in the project area (large gray project name).
There is only one downside - one extra click if you need to change settings in Admin, check custom reports, etc. if you are inside a project. Quite rare operations to sacrifice simplicity.
Labels: developing, navigation, usability, v.3.0



5 Comments:
Hello Guys. Important conclusions. Could you also define different logos per project?
What about a simple tree on the left? It could even be collapsable with the ExtJS stuff you are using.
Seriously, a tree would be a much easier way to navigate. Your current IA at the top (and the proposed) looks really complicated.
As we see it now, there will be no logo at all in the project area as well as company name.
This post has been removed by the author.
The tree has several drawbacks:
1. It takes space (collapsible is a viable solution though)
2. TP hierarchy is quite complex. Should we show hierarchy as Project - Release - Iteration - Stories -Tasks? Then what about backlog?
It seems the correct hierarchy should be
Project
--Release
----Story
------Task
----Bug
----Iteration
------Story
--------Task
------Bug
--Story
--Bug
Not sure how it will be usable..
Post a Comment
Links to this post:
Create a Link
<< Home