Overdue Tasks Impact SuccessScore
We would love the ability to have a SuccessScore metric tied to some threshold for the number of tasks/milestones that are overdue.
Currently, that is loosely accounted for in the # of days on a journey stage, but in some cases, that is too high level and can hide issues where things are getting dropped and we may not see that for 30-60 days or more depending on stage length. At that point, we are dealing with unnecessary fires.
It would be great to have some metric for the number of overdue/late tasks that we can use as an element of the health score, but then also be able to build some automation / alerting / reporting for managers when we have an employee that has a large number of overdue tasks so we can provide support, mentoring or training.
Currently, that is loosely accounted for in the # of days on a journey stage, but in some cases, that is too high level and can hide issues where things are getting dropped and we may not see that for 30-60 days or more depending on stage length. At that point, we are dealing with unnecessary fires.
It would be great to have some metric for the number of overdue/late tasks that we can use as an element of the health score, but then also be able to build some automation / alerting / reporting for managers when we have an employee that has a large number of overdue tasks so we can provide support, mentoring or training.
1