Integrated Staffing Workflow

2,528 views
2,413 views

Published on

Published in: Design, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,528
On SlideShare
0
From Embeds
0
Number of Embeds
140
Actions
Shares
0
Downloads
20
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Integrated Staffing Workflow

  1. 1. Vinay Mohanty ISW User Interface Re-design
  2. 2. Original screen The columns do not follow a logical order & are not grouped Taking an action on a link is not intuitive, you should be clicking on your task to do your task. The ‘status’ has some affinity or connection with these two columns : opened-date , start-date you take action on the task at hand. ( task is to propose associates ) Columns don’t have left-right arrangement according to priority & frequency of usage. The information in that column and columns not logical-grouped. We should have some basic columns and allow the user to show/hide other columns as per his need.
  3. 3. Required Changes in User Interface. <ul><li>Search capability, search included in the sequence. So that you get only that what you asked for. </li></ul><ul><li>The ‘status’ column has affinity with the opened date and start-date columns. We need to reflect that mapping in the User Interface by grouping these columns. </li></ul><ul><li>Requisition ID and the task that we need to do should come together. </li></ul><ul><li>Red, green , yellow legends reduce column-width and give visual overview. </li></ul><ul><li>Taking an action on a link is not intuitive, you take action on the task . The task is to propose associates. </li></ul>
  4. 4. Search in the sequence Making search a part of sequence map, Search parameters, Search results displayed this way you get only what you want
  5. 5. Required Changes in UI. <ul><li>A project wise grouping will let us know what resources are needed/allocated for every project. </li></ul><ul><li>By doing a task-analysis of real users, we can find the relative importance and frequency of usage of data in each </li></ul><ul><li>column. Divide columns into LP ( Low Priority ) & HP (High Priority). </li></ul><ul><li>e.g.: Revenue, Iterations, Edit come on extreme right are grouped. </li></ul><ul><li>Position IDs which are not required for an overview should be hidden , Project plan needs to be reflected in ISW interface. </li></ul>
  6. 6. Columns grouped Logically Logical groupings of columns Low priority columns grouped on extreme right
  7. 7. Project grouping Project and Account based grouping. This gives the user a visual overview of the staff needs of a particular account.
  8. 8. Final screen Project and Account based grouping. This gives the user a visual overview of the staff needs of a particular account. Position ID hidden ( Progressive disclosure), saves many row spaces The main task has click associated with it. (Intuitive) Visual overview of status( red for escalated, green for normal )
  9. 9. Need for Mapping between Price Estimation Sheet and ISW <ul><li>The Price Estimation Sheet time plan and requirements not properly reflected in the ISW interface. </li></ul><ul><li>As a solution we have a drop down, slide - open panel that displays the time plan . </li></ul><ul><li>An overview mode gives an idea of work to do. </li></ul><ul><li>‘ Progressive disclosure’ : show assign action only when you need to do it not in the overview. </li></ul><ul><li>Final assigning i.e. the action that takes you to the next application is done here. </li></ul>
  10. 10. Price sheet Out of these 3 categories, ROLE & TIMELINE are of interest in ISW Three categories of info : about role , billing costs , timeline Role Billing costs Timeline
  11. 11. Widget closed Collapsible action rows
  12. 12. Widget open Information from project plan integrated in ISW This takes you to next application where you do this step of proposing assoc.
  13. 13. Some examples Original interface
  14. 14. Final screen Redesign interface

×