LEAVE MANAGEMENT SYSTEM
An internal application used by employees to plan and manage leaves.
Client Challenge : The look and feel of the existing application was not in line with the visual identity guidelines Too many navigation items with some features being replicated across different sections. The current application was non-responsive and hence there were limitations in using the application on smartphones and tablets
Objective : Provide a visually appealing and consistent user interface Organize the content to provide a clear visual hierarchy and establish a consistent layout Optimize the navigation and content organization to eliminate redundancy wherever possible
Solution : Existing processes were analyzed to understand key modules that are frequently accessed by users Initial wireframes were discussed to understand gaps in and finalize screen flows Bootstrap framework used to develop responsive web design for compatibility across various devices HTML 5/ CSS 3/ jQuery used to deliver solution in line with current web standards
KEY WINS:
1. VISIBILITY OF SYSTEM STATUS - Appropriate feedback messages and indicators were used to convey progress & status information.
1. VISIBILITY OF SYSTEM STATUS - Appropriate feedback messages and indicators were used to convey progress & status information.
2. MATCH BETWEEN SYSTEM AND THE REAL WORLD - A dashboard layout was adopted for the home page as users were more familiar with this style, and information was presented in a format that provided users with the data that they usually look for.
The older version of the application had a complex view of the leave balance calculation — a long tabular layout with a detailed history of leaves. This was changed to a more simpler summary view in which the calculations were easier to grasp.
3. USER CONTROL AND FREEDOM - While employees tend to access the application through a desktop more often, there are situations where approvers (managers and higher levels) need quick access to leave data (for approvals and reports). Typically, the senior management rely on smartphones or mobile devices rather than desktops. Rather than force users to use a certain device, the application was designed for seamless use across all devices
4. ERROR PREVENTION - This included identifying sections where the probability of error was high and adopting the following techniques
5. RECOGNITION RATHER THAN RECALL- Rather than have the user remember what certain roles or policy related words/terminology mean, quick references were used to clarify.In this example where user needs to select applicable roles, a quick link was provided so user can easily refer to it rather than navigate away from the page or look it up elsewhere.
6. FLEXIBILITY AND EFFICIENCY OF USE - Being a role-based system meant that users only see what is relevant for their roles. In the older version, many screens were duplicated to accommodate such differences (which in turn led to complex, long menus).
The new version relied on a more efficient approach to provide optimized screens.
The new version relied on a more efficient approach to provide optimized screens.
