Incorrect "Value" field in Nudge Tracking

[Rory_OG]

While tracking a nudge plan, I noticed the value metric below one of the KPIs, the information tool tip suggests this dollar amount takes from the employee salary field. If that salary field is not present, it assumes a rate of $75/hour. In my case, we don't have salary data uploaded but it looks like a $1/hour rate is assumed? 

Has anyone else seen a similar metric? I don't really use this for anything so it's not that important, but more something I was curious about. Seems like the code that calculates value may need to be adjusted to multiple the hours field by 75 to display the right value here. 

[Dazza]

Hi @Rory_OG!

I'm wondering whether there is any further development going into this feature at all, as my understanding is that the ability to create plans directly from Teams is taking preference over this feature. I do however still see the value in this, and would love to know what the answer is - hence joining the thread. 

FYI - this is what I see on my side for a Collaboration Plan that I started in February - Unfortunately in my instance - it does appear that there has been no real change 🙂 - BUT it could indicate that the calculation is not happening on this "tile". 

[Rory_OG]

Ah I didn't realize you could make plans from viva insights in teams. It seems I can't get the viva insights app in teams, which probably has something to do with it being a limited Pilot study for us right now and IT has may not have rolled out that app in my organization. 

[Dazza]

Yes, this is a relatively new feature that is available through the app. You can read more about it here - My team in Viva Insights | Microsoft Docs.

Note that these two solutions are slightly different. Plans from the app are meant to be created by the end user (ie. Team Leader or Manager), whereas the Plans on the backend are only accessible by the Analyst or Program Managers, probably targeting larger teams or groups - more on this here - Introduction to Viva Insights plans | Microsoft Docs.

@Jake_Caddes - would it be possible if you could get someone from the Product Team to advise on what the way forward is with these features, and look into the discrepancy pointed out by @Rory_OG?

[Rory_OG]

Thanks for sharing those Docs, Dazza. I was not aware there was an option available for teams to do this, locally. That is very cool, much more of a grassroots approach to changing meeting behavior in organizations.

[Jake_Caddes · Accepted solution]

Hi @Rory_OG I apologize for the delay in getting back to you. I heard back from engineering and the product team who looked into this for us. They said in this case the customer has uploaded HR file that contains HourlyRate column and that column has value of 1 or lower. That results in the calculation error. 

Their advice was to let you know that you should reach out to Viva Insights/WPA Administrator to upload a new file with corrected HourlyRate values.