2.4 |
Key Results and Metrics |
6.5 When adding a Key Result (KR)It is possible to define a metric It's possible to define the following for a metric: (i) Name 6.5.1 Unit of Measurement (entered as text e.g. $ Annual Revenue, Calls per month) (ii) Format (drop down) (ii) Start value (iii) Target value (iv) Current value By default metric fields are enabled. When adding a KR, the user can disable the metric. If disabled, the metric related fields appear disabled. |
2.5 |
Key Results and Metrics |
6.5 The following options are available under Metric - Format: (i) Number x,xxx.xx (ii) Number x,xxx (ii) Percent xx.xx% |
2.6 |
Key Results and Metrics |
6.5 The metric value fields: Start Value, Target Value, and Current Value behaves as defined under Key Result Metric - Value Fields |
2.7 |
Key Results and Metrics |
6.5 The percentage of completion of a Key Result cannot be manually modified. The percentage of completion is automatically generated using from the metric using the formula: Progress % = [(Current value - Starting value) /(Target value - Starting value)] x 100 |
2.8 |
Key Results and Metrics |
6.5 If the metric is disabled, for progress calculations, status "Pending" and "In Progress" are considered as 0% and "Achieved" is considered as 100%. |
2.9 |
Key Results and Metrics |
6.5 From within an Objective, it is possible to view a list of KRs assigned to it. The following columns are displayed: Name, Owner, Completion, Metric The Metric column displays: (i) If metric enabled: [current value of the metric] + [metric name] (ii) If metric not enabled: [current completion status] It is possible to add/modify/delete KRs from this view. |
2.10 |
Key Results and Metrics |
6.5 When an Objective (OKR) is deleted, the associated key results are also deleted. Even if the user cannot access some of the owners of the Key Results, still deleting an Objective would delete all associated key results. |
3 |
Bulk Assign Goal |
6.4.11 When bulk assigning a goal to multiple employees, the progress is indicated using a progress bar. |
3.1 |
Bulk Assign Goal |
After bulk adding a goal to multiple employees, system will track each employees' goal as a separate Individual Goal |
4 |
View Goal |
It's possible to click on a goal on Goal List or My Goals and view its details. |
4.1 |
View Goal |
If a goal is marked as Read Only (For Assignee), the assigned user cannot update any of the goal fields. |
5 |
Goal Comments |
Users having UPDATE privileges for data group: Performance - Goals, can add/delete notes to goals that they can view from the View/Modify goal screen. |
5.0.1 |
Goal Comments |
System validates the maximum allowed comment length and displays a validation message for text exceeding the length. |
5.1 |
Goal Comments |
A goal comment displays: (i) 6.4.11 Profile image of the employee who commented (ii) Name of employee (First Name and Last Name) who commented (user name is shown for admin user accounts without an associated employee) (iii) Comment text (iv) Date (in system defined date format) and time (hh:mm) of the comment (server time is used) 6.4.10 When a commenter of the goal is purged all the added comments of his/her are gets removed and the name is shown masked. This will not affect the comments, added by other users for that particular goal. 6.4.11 If there are comments added by terminates employees, their names are shown with 'Past Employee' suffix. |
5.1.1 |
Goal Comments |
Comments are shown sorted (descending) by date and time. |
5.2 |
Goal Comments |
A user (even an admin or supervisor) with privileges can only delete notes added by himself/herself. |
6 |
Goal Workflow Actions (if Goal Workflow is enabled) |
6.5 An ESS user can Submit a Saved goal |
6.1 |
6.5 Admins, Supervisors, and HODs can Approve or Reject goals which are "Pending Approval. Upon approving the goal status becomes "Pending" and starts getting listed in the goal list (and my goals) by default.Upon rejecting the goal status becomes "Rejected". Rejected goals are not listed in goal list Rejected goals are not listed under My Goals for the goal owner. They are only listed under the goal owner's Unapproved Goal List |
6.2 |
6.5 Rejected goals can be resubmitted (ONLY) by the ESS user. |
6.3 |
6.5 Goals added by Admins, Supervisors, or HODs need not (cannot) be approved. If an Admin, Supervisor, or HOD saves a goal, it immediately goes to the state Pending |
6.4 |
6.5 Goal workflow is applied to Objectives (OKRs) created by ESS users. Goal workflow is not applied to key results. That is key results need not (and cannot) be approved. |
7 |
Email Notifications |
6.5.1 If Goal Workflow is enabled, Admin -> Configuration -> Email Notifications -> Action Based shows options to subscribe for: (i) Save Goal (ii) Submit Goal (iii) Approve Goal (iv) Reject Goal (v) Update Goal (This is not covered by workflow - is this feasible?) Disabled by default |
7.1 |
6.5.1 If notifications are enabled the Email Notifications are sent to selected subscribers upon performing the workflow actions. Refer table Email Notifications for the default notification settings. |
7.2 |
6.5.1 It is possible to add additional types (commonly supported for all notifications) of subscribers. |
7.3 |
6.5.1 If there's a custom goal workflow, it is possible to define notifications for custom workflow actions from: Database Configuration: by configuring a new notification UI Configuration: (i) Add Email template (ii) Define Workflow actions that trigger notification (iii) Add Subscribers |