Productivity Insights
13 min
productivity insights is available to organization users that has the role team manager assigned to them this page surfaces your organizationβs annotation and review productivity in one place, updating automatically every 10 minutes note βannotation pointsβ is a project level metric see our annotation points & targets https //docs kognic com/annotation points and target guide for details a screenshot of the productivity insights view, detailing the data produced in a particular project 2\ annotate productivity tab path campus βΆοΈ productivity insights βΆοΈ annotate productivity track how your annotators perform against targets 2 1 summary cards total productivity overall annotation productivity (% of target) β shown only if review tasks are not selected total tasks completed sum of all completed tasks in the interval team ap total annotation points awarded total objects sum of all objects created total shapes sum of all shapes (e g polygons, boxes) created 2 2 annotators table a pageable table listing each userβs metrics column description name userβs name and email click to drill into their personal user productivity page ongoing tasks number of tasks currently in progress productivity (ap) % of target ap achieved (green if β₯ 100%, red if < 100%) actual ap in parentheses tasks completed count of tasks finished tasks reviewed number of tasks that received at least one review working time stopwatch reported time falls back to annotation time if no stopwatch data (asterisk ) time allocation ratio of annotation time vs total working time (colored red/yellow/white to indicate too low/high allocation) objects produced net objects created (can be negative if users remove objects in correct/review tasks) shapes produced net shapes created (can be negative if shapes are removed in correct/review tasks) 2 3 columns (detailed explanation) this section describes the different columns present in the table name this is the name and email of the given user you are able to click on the name of a user to be taken to another view to gain even more insights into their performance ongoing tasks the number of currently ongoing tasks that the users are assigned to productivity (ap) this column details how productive the the listed users are in the selected timespan in comparison with the expected productivity this metric is displayed as a percentage which is colored green if the user is exceeding expectations, and red if the user is not inside the parenthesis the actual number of produces annotation points is displayed as an example, if a user has worked 2h in a selected time period, they have produced 100aps in this period, and the target is 100ap/h, the user will have a productivity of 50% the productivity metric is computed using the stopwatch time reporting feature, is this feature is not used this view will not contain productivity metrics, instead a n/a will be displayed tasks completed this is how many tasks that the user has completed during the selected timespan tasks reviewed this is the number of tasks that the user has completed within the selected timespan that has been reviewed working time how much time has been reported from stopwatch during the selected timespan if no time has been reported, we will fall back to showing the time spent annotating in this case, a red asterisk will indicate that there is no stopwatch time available, and this will also make it impossible to compute a productivity metric time allocation the ratio of time allocated to annotation, and the total time reported during the selected timespan this metric is in this table in order to verify that users are not working too much or too little if a user does not take any breaks during a workday, this probably indicates a problem the time allocation is colored according to the following in order to indicate is a value is acceptable, too high or too low ratio indicator β€ 0 75 π΄ too low 0 75β0 90 π’ optimal β₯ 0 90 π΄ too high objects produced this is how many objects that the user has created during the selected timespan note, that this might be a negative number, if the user is doing correction tasks and is removing objects the user is doing review tasks and is removing objects the user started the day by removing objects from a scene started on a previous day, and the timespan only accounts for today shapes produced this is how many shapes has created during the selected timespan note, that this might be a negative number, if the user is doing correction tasks and is removing shapes the user is doing review tasks and is removing shapes the user started the day by removing shapes from a scene started on a previous day, and the timespan only accounts for today for a distinction between objects and shapes, see objects and shapes https //docs kognic com/key concepts#ifnby 3\ review productivity tab path campus βΆοΈ productivity insights βΆοΈ review productivity gauge how your reviewers are keeping up with and finding errors in annotation work 3 1 summary cards time budget usage (time spent on review / review time budget docid\ e97p577erchm0lwk8t zw ) 100 total tasks completed number of review tasks submitted found errors % of errors detected by reviewers compared to a follow up reviewer total follow up reviews count of second pass reviews performed image showing the review productivity table 3 2 reviewers table column description name reviewerβs name and email review coverage % of annotation points reviewed / annotation points created tasks completed number of review tasks finished found errors % of errors the reviewer flagged versus those found by the follow up review follow up reviews count of follow up reviews on this reviewerβs work review time time spent in the annotation tool performing reviews review ratio review time / annotation time ratio feedback created number of feedback items the reviewer submitted 4\ faqs q why is working time not showing correctly? a make sure the task category is including training and onboarding q why is working time not showing correctly i've toggled the additional filters? a if working time is not showing correctly and time utilization is >1 0, it means that the annotator accidentally turned of the stopwatch while working to get an accurate measurement of annotation time please check the graphs in user productivity q how often does this view update? a every 10 minutesβno manual refresh needed q who can see this view? a only users with the team manager role


