4.02-07 Avoid buttons for Navigation

rob_marshall
rob_marshall
in Planual

Use the contents page for navigation rather than clutter the dashboards with buttons

 

Exceptions:
4.02-07a Iterative processes: When the user needs to toggle back and forth between dashboards, it is acceptable to have navigation buttons (old UX)

Tagged:

Comments

  • Misbah
    Misbah

    Rule 4.02-07 Avoid buttons for Navigation. Use the contents page for navigation rather than clutter the dashboards with buttons

     Here is how it was done in Pre Planual Era: How often have we seen this kind of layout on our dashboards. That is exactly what should NOT be done

    Misbah_0-1594203927434.png

    What is wrong with this method?  It goes against UX principles as it clutters the dashboard and takes good amount of space based on the description of the button

    Here is how it should be done in Planual Way: Educate users to use Content Panel of the model instead of buttons on the dashboard

    Misbah_1-1594203938792.png

    Exception: 4.02-07a Iterative processes “When the user needs to toggle back and forth between dashboards, it is acceptable to have navigation buttons”

    If there is link between dashboards and a user necessarily has to navigate to another dashboard to complete the activities then it is ok to create navigation buttons on the dashboard

Title

Categories